Results from /fix:all

Author: opentelemetrybot

content/en/docs/collector/deployment/gateway/index.md

@@ -254,30 +254,30 @@ Cons:
 
 ## Multiple collectors and the single-writer principle
 
-All metric data streams within
-OTLP must have a [single writer](/docs/specs/otel/metrics/data-model/#single-writer).
-When deploying multiple collectors in a gateway configuration, it's important to
+All metric data streams within OTLP must have a
+[single writer](/docs/specs/otel/metrics/data-model/#single-writer). When
+deploying multiple collectors in a gateway configuration, it's important to
 ensure that all metric data streams have a single writer and a globally unique
 identity.
 
 ### Potential problems
 
-Concurrent access from multiple applications that modify or report on
-the same data can lead to data loss or degraded data
-quality. For example, you might see inconsistent data from multiple sources
-on the same resource, where the different sources can overwrite each other because
-the resource is not uniquely identified.
+Concurrent access from multiple applications that modify or report on the same
+data can lead to data loss or degraded data quality. For example, you might see
+inconsistent data from multiple sources on the same resource, where the
+different sources can overwrite each other because the resource is not uniquely
+identified.
 
 There are patterns in the data that may provide some insight into whether this
 is happening or not. For example, upon visual inspection, a series with
 unexplained gaps or jumps in the same series may be a clue that multiple
-collectors are sending the same samples. 
-You might also see errors in your backend. For example, with a Prometheus backend:
+collectors are sending the same samples. You might also see errors in your
+backend. For example, with a Prometheus backend:
 
 `Error on ingesting out-of-order samples`
 
-This error could indicate that identical targets exist in two jobs, and the order of
-the timestamps is incorrect. For example:
+This error could indicate that identical targets exist in two jobs, and the
+order of the timestamps is incorrect. For example:
 
 - Metric `M1` received at `T1` with a timestamp 13:56:04 with value `100`
 - Metric `M1` received at `T2` with a timestamp 13:56:24 with value `120`
@@ -287,7 +287,9 @@ the timestamps is incorrect. For example:
 
 ### Best practices
 
-- Use the [Kubernetes attributes processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/k8sattributesprocessor)
+- Use the
+  [Kubernetes attributes processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/k8sattributesprocessor)
   to add labels to different Kubernetes resources.
-- Use the [resource detector processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/resourcedetectionprocessor/README.md)
+- Use the
+  [resource detector processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/resourcedetectionprocessor/README.md)
   to detect resource information from the host and collect resource metadata.