[editorial] Clarify wording on exporter interfaces (#2673)

open-telemetry · Jul 25, 2022 · 71b5032 · 71b5032
1 parent dfb1977
commit 71b5032
Showing 1 changed file with 2 additions and 3 deletions.
diff --git a/specification/trace/sdk.md b/specification/trace/sdk.md
@@ -603,9 +603,8 @@ primarily a simple telemetry data encoder and transmitter.
 ### Interface Definition
 
 The exporter MUST support three functions: **Export**, **Shutdown**, and **ForceFlush**.
-In strongly typed languages typically there will be 2 separate `Exporter`
-interfaces, one that accepts spans (SpanExporter) and one that accepts metrics
-(MetricsExporter).
+In strongly typed languages typically there will be one separate `Exporter`
+interface per signal (`SpanExporter`, ...).
 
 #### `Export(batch)`