Reword metric temporality config

src/content/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/best-practices/opentelemetry-otlp.mdx

@@ -255,7 +255,7 @@ Requirement level: **Recommended**
 
 In order to send OTLP metric data to New Relic, you should configure your OTLP metrics exporter to prefer delta [aggregation temporality](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#temporality). While New Relic supports cumulative aggregation temporality, the New Relic metrics architecture is generally a delta metrics system. Using the default cumulative setting will generally incur more memory usage from SDKs and result in high data ingest.
 
-The mechanism to configure the endpoint will vary, but OpenTelemetry language SDKs generally support setting the `OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE=delta` environment variable (see [OpenTelemetry docs](https://opentelemetry.io/docs/specs/otel/metrics/sdk_exporters/otlp/) for more info). If manually setting temporality as a function of instrument kind, configure as follows:
+The mechanism to configure the endpoint will vary, but OpenTelemetry language SDKs generally support setting the `OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE=delta` environment variable (see [OpenTelemetry docs](https://opentelemetry.io/docs/specs/otel/metrics/sdk_exporters/otlp/) for more info). If manually setting temporality, configure by instrument kind as follows:
 
 - Counter, Asynchronous Counter, Histogram: Delta
 - UpDownCounter, Asynchronous UpDownCounter, Gauge, Asynchronous Gauge: Cumulative