Skip to content

Commit c76ff0c

Browse files
authored
[chore] fix a typo (#1309)
1 parent 8597598 commit c76ff0c

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/advanced-configuration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -768,7 +768,7 @@ agent:
768768
* It is not possible to run the persistent buffering if there are multiple replicas of a pod and `gateway` runs 3 replicas by default.
769769
* Even if support is somehow provided, only one of the pods will be able to acquire the lock and run, while the others will be blocked and unable to operate.
770770
* Cluster Receiver support
771-
* Cluster receiver is a 1-replica deployment of Open-temlemetry collector.
771+
* Cluster receiver is a 1-replica deployment of OpenTelemetry collector.
772772
* As any available node can be selected by the Kubernetes control plane to run the cluster receiver pod (unless we explicitly specify the `clusterReceiver.nodeSelector` to pin the pod to a specific node), `hostPath` or `local` volume mounts wouldn't work for such envrionments.
773773
* Data Persistence is currently not applicable to the k8s cluster metrics and k8s events.
774774

helm-charts/splunk-otel-collector/values.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -450,7 +450,7 @@ agent:
450450

451451
################################################################################
452452
# OpenTelemetry Kubernetes cluster receiver
453-
# This is an extra 1-replica deployment of Open-temlemetry collector used
453+
# This is an extra 1-replica deployment of OpenTelemetry collector used
454454
# specifically for collecting metrics from kubernetes API.
455455
################################################################################
456456

@@ -1050,7 +1050,7 @@ securityContextConstraintsOverwrite: {}
10501050

10511051
################################################################################
10521052
# OpenTelemetry "collector" k8s deployment configuration.
1053-
# This is an additional deployment of Open-telemetry collector that can be used
1053+
# This is an additional deployment of OpenTelemetry collector that can be used
10541054
# to pass traces trough it, make k8s metadata enrichment and batching.
10551055
# Another use case is to point tracing instrumentation libraries directly to
10561056
# the collector endpoint instead of local agents. The collector running in the

0 commit comments

Comments
 (0)