Skip to content

Commit 494e36e

Browse files
committed
modify words to make clear
1 parent 4c28c0a commit 494e36e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/en/docs/concepts/cluster-administration/system-traces.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ with the gRPC exporter and can be collected and routed to tracing backends using
2222

2323
## Trace Collection
2424

25-
Kubernetes components have built-in grpc exporters for OTLP to export traces, either with an OpenTelemetry Collector,
25+
Kubernetes components have built-in gRPC exporters for OTLP to export traces, either with an OpenTelemetry Collector,
2626
or without an OpenTelemetry Collector.
2727

2828
For a complete guide to collecting traces and using the collector, see
@@ -51,7 +51,7 @@ service:
5151
```
5252
5353
To directly emit traces to a backend without utilizing a collector,
54-
specify the endpoint field in the Kubernetes TracingConfiguration with the desired trace backend address.
54+
specify the endpoint field in the Kubernetes tracing configuration file with the desired trace backend address.
5555
This method negates the need for a collector and simplifies the overall structure.
5656
5757
For trace backend header configuration, including authentication details, environment variables can be used with `OTEL_EXPORTER_OTLP_HEADERS`,

0 commit comments

Comments
 (0)