feat(OTEL): Edit new callout for metrics support

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

@@ -19,7 +19,7 @@ import histogram1 from 'images/histogram-1.png'
 
 import histogram2 from 'images/histogram-2.png'
 
-Here are some best practices based on how OpenTelemetry works with New Relic:
+Here are some best practices based on how OpenTelemetry works with New Relic. For information about resolving specific issues, see our [troubleshooting guide](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-troubleshooting).
 
 * [Resources](#resources)
 * [Batching](#batching)
@@ -29,15 +29,12 @@ Here are some best practices based on how OpenTelemetry works with New Relic:
 * [Metrics](#metrics)
 * [Logs](#logs)
 
-<Callout variant="tip">
-  For information about resolving specific issues, see our [troubleshooting guide](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-troubleshooting).
-</Callout>
-
-
 <Callout variant="important">
-  Now that OpenTelemetry Protocol for Metrics is stable we intend to move our support from v0.10 to v0.16. This necessitates ending support for removed fields and data types, including the `Int` data point types for Metrics, `LogRecord.Name` for Logs, and status code for Traces.
-  Other significant changes include the renaming of `InstrumentationLibrary` to `InstrumentationScope`. We recommend upgrading your collector or instrumentation if you depend on removed or deprecated features. We expect to make this change during or after the week of April 18, 2022.
+Now that OpenTelemetry protocol for metrics is stable, we intend to move our support from v0.10 to v0.16. This means we'll be ending support for removed fields and data types, including the `Int` data point types for metrics, `LogRecord.Name` for logs, and status code for traces.
+
+Other significant changes include the renaming of `InstrumentationLibrary` to `InstrumentationScope`. We recommend you upgrade your collector or instrumentation if you depend on removed or deprecated features. We expect to make this change during or after the week of April 18, 2022.
 </Callout>
+
 ## Resources [#resources]
 
 A resource in OpenTelemetry represents information about an entity generating telemetry data. All telemetry data sent to New Relic is expected to be associated with a resource so that it can be linked with the appropriate entity in New Relic. The [OpenTelemetry Resource SDK specification](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/sdk.md) defines the functionality implemented by all language SDKs for defining a resource.