Merge pull request #17234 from newrelic/ally-sassman-patch-19

fix(OTEL): move version support section to the bottom

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

@@ -23,7 +23,6 @@ New Relic supports native OTLP ingest, and recommends it as the preferred method
 
 * If you haven't already done so, sign up for a free [New Relic account](https://newrelic.com/signup).
 * Get the [license key](https://one.newrelic.com/launcher/api-keys-ui.launcher) for the New Relic account to which you want to report data. This license key will be used to [configure the `api-key` header](#api-key).
-* Review your OTLP version: New Relic uses [OTLP release v0.18.0](https://github.com/open-telemetry/opentelemetry-proto/releases/tag/v0.18.0). Later versions are supported but new features are not yet implemented. Experimental features which were are no longer available in 0.18.0 are not supported.
 
 ## Config: OTLP endpoint, port, and protocol [#configure-endpoint-port-protocol]
 
@@ -279,6 +278,10 @@ In order to send OTLP metric data to New Relic, you should configure your OTLP m
 The mechanism to configure the endpoint will vary, but OpenTelemetry language SDKs generally support setting the `OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION=base2_exponential_bucket_histogram` environment variable (see [OpenTelemetry docs](https://opentelemetry.io/docs/specs/otel/metrics/sdk_exporters/otlp/) for more info).
 
 
+## OTLP protocol version [#otlp-version-support]
+
+New Relic uses [OTLP release v0.18.0](https://github.com/open-telemetry/opentelemetry-proto/releases/tag/v0.18.0). Later versions are supported but new features are not yet implemented. Experimental features which were are no longer available in 0.18.0 are not supported.
+
 ## OTLP response payloads [#payloads]
 
 Please note the following details regarding New Relic OTLP endpoint response payloads: