From 9b53527853049b249f60f12a000c0d85b9e5f5dc Mon Sep 17 00:00:00 2001
From: Puneet Arora <135100789+puneet-ekline@users.noreply.github.com>
Date: Wed, 2 Oct 2024 08:46:47 -0700
Subject: [PATCH] Removing repeated words (#5164)

Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com>
---
 content/en/docs/collector/building/receiver.md       |  4 ++--
 content/en/docs/kubernetes/collector/components.md   |  2 +-
 content/en/docs/languages/erlang/propagation.md      |  2 +-
 content/en/docs/languages/java/performance.md        | 12 ++++++------
 .../zero-code/java/agent/instrumentation/_index.md   |  4 ++--
 5 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/content/en/docs/collector/building/receiver.md b/content/en/docs/collector/building/receiver.md
index 49d653d3827b..d9f61884ba5f 100644
--- a/content/en/docs/collector/building/receiver.md
+++ b/content/en/docs/collector/building/receiver.md
@@ -520,8 +520,8 @@ func createTracesReceiver(_ context.Context, params receiver.CreateSettings, bas
 ```
 
 You now have all the necessary components to successfully instantiate your
-receiver factory using the `receiver.NewFactory` function. Go ahead and and
-update your `NewFactory()` function in your `factory.go` file as follow:
+receiver factory using the `receiver.NewFactory` function. Go ahead and update
+your `NewFactory()` function in your `factory.go` file as follows:
 
 ```go
 // NewFactory creates a factory for tailtracer receiver.
diff --git a/content/en/docs/kubernetes/collector/components.md b/content/en/docs/kubernetes/collector/components.md
index 9394c4cd2f1e..51bd7749bd68 100644
--- a/content/en/docs/kubernetes/collector/components.md
+++ b/content/en/docs/kubernetes/collector/components.md
@@ -554,7 +554,7 @@ started.
 
 For objects configuring for pulling, the receiver will use the Kubernetes API to
 periodically list all the objects in the Cluster. Each object will be converted
-to its own log. For objects configured for watching, the receiver creates a a
+to its own log. For objects configured for watching, the receiver creates a
 stream with the Kubernetes API and which receives updates as the objects change.
 
 To see which objects are available for collection run in your cluster run
diff --git a/content/en/docs/languages/erlang/propagation.md b/content/en/docs/languages/erlang/propagation.md
index 380506745455..67c3b60cde99 100644
--- a/content/en/docs/languages/erlang/propagation.md
+++ b/content/en/docs/languages/erlang/propagation.md
@@ -25,7 +25,7 @@ propagators. By default the global propagators used are the W3C
 [Trace Context](https://w3c.github.io/trace-context/) and
 [Baggage](https://www.w3.org/TR/baggage/) formats.
 
-You can configure global propagators using the the OTP application environment
+You can configure global propagators using the OTP application environment
 variable `text_map_propagators`:
 
 {{< tabpane text=true >}} {{% tab Erlang %}}
diff --git a/content/en/docs/languages/java/performance.md b/content/en/docs/languages/java/performance.md
index 1c93542accf0..116fa72f8319 100644
--- a/content/en/docs/languages/java/performance.md
+++ b/content/en/docs/languages/java/performance.md
@@ -78,12 +78,12 @@ settings. See [Scaling](/docs/collector/scaling/).
 ## Constraints impacting the performance of the Java agent
 
 In general, the more telemetry you collect from your application, the greater
-the the impact on agent overhead. For example, tracing methods that aren't
-relevant to your application can still produce considerable agent overhead
-because tracing such methods is computationally more expensive than running the
-method itself. Similarly, high cardinality tags in metrics might increase memory
-usage. Debug logging, if turned on, also increases write operations to disk and
-memory usage.
+the impact on agent overhead. For example, tracing methods that aren't relevant
+to your application can still produce considerable agent overhead because
+tracing such methods is computationally more expensive than running the method
+itself. Similarly, high cardinality tags in metrics might increase memory usage.
+Debug logging, if turned on, also increases write operations to disk and memory
+usage.
 
 Some instrumentations, for example JDBC or Redis, produce high span volumes that
 increase agent overhead. For more information on how to turn off unnecessary
diff --git a/content/en/docs/zero-code/java/agent/instrumentation/_index.md b/content/en/docs/zero-code/java/agent/instrumentation/_index.md
index d0fde2bb94a7..29a400501d65 100644
--- a/content/en/docs/zero-code/java/agent/instrumentation/_index.md
+++ b/content/en/docs/zero-code/java/agent/instrumentation/_index.md
@@ -43,8 +43,8 @@ For example, if set to the following:
 ```
 
 Then, requests to `1.2.3.4` will have no override for `peer.service` attribute,
-while `1.2.3.4:443` will have have `peer.service` of `cats-service` and requests
-to `dogs-abcdef123.serverlessapis.com:80/api/v1` will have an attribute of
+while `1.2.3.4:443` will have `peer.service` of `cats-service` and requests to
+`dogs-abcdef123.serverlessapis.com:80/api/v1` will have an attribute of
 `dogs-api`.
 
 {{% /config_option %}}