Typos

newrelic · May 6, 2024 · e3cebd4 · e3cebd4
1 parent 5d08e8b
commit e3cebd4
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/...urce-telemetry-integrations/opentelemetry/best-practices/opentelemetry-otlp.mdx b/...urce-telemetry-integrations/opentelemetry/best-practices/opentelemetry-otlp.mdx
@@ -209,7 +209,7 @@ Notes:
 - Resource attributes are subject to attribute limits, but there are no standard environment variables to limit them. If a resource attribute is over the allowed limit, consider truncating using the collector [transform processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/transformprocessor), or overwriting the resource attribute to another value.
 - There is no standard mechanism to limit attribute names. However, instrumentation generally does not produce attribute names which exceed New Relic limits. If you encounter name length limits, remove the attribute using the collector.
 
-## Config: Payloads Batching, Compression and Rate Limits [#payload]
+## Config: Payload Batching, Compression and Rate Limits [#payload]
 
 Requirement level: **Required**
 
@@ -239,7 +239,7 @@ Requirement level: **Recommended**
 
 In order to send OTLP data to New Relic, you should configure your OTLP exporter to retry when transient errors occur. The internet is unreliable, and failure to retry increases the likelihood of data loss.
 
-The mechanism to configure retry will vary. Some OpenTelemetry SDKs may have language specific environment variables (for example [java supports](https://github.com/open-telemetry/opentelemetry-java/tree/main/sdk-extensions/autoconfigure) setting `OTEL_EXPERIMENTAL_EXPORTER_OTLP_RETRY_ENABLED=true`)), but there is no general mechanism. Programmatic configuration may be required.
+The mechanism to configure retry will vary. Some OpenTelemetry SDKs may have language specific environment variables (for example [java supports](https://github.com/open-telemetry/opentelemetry-java/tree/main/sdk-extensions/autoconfigure) setting `OTEL_EXPERIMENTAL_EXPORTER_OTLP_RETRY_ENABLED=true`), but there is no general mechanism. Programmatic configuration may be required.
 
 If using the collector, the `otlphttpexporter` and `otlpexporter` retry by default. See [exporterhelper](https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/exporterhelper/README.md) for more details.