fix(OTEL): minor style edits

src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-otel-applications-kubernetes.mdx

@@ -34,7 +34,7 @@ To successfully complete the steps below, you should already be familiar with Op
 
 * Instrumented your applications with [OpenTelemetry](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-setup/), and successfully sent data to New Relic via OpenTelemetry Protocol (OTLP).
 
-If you've general questions about using Collectors with New Relic, see our [Introduction to OpenTelemetry Collector with New Relic](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/opentelemetry-collector-intro).
+If you have general questions about using Collectors with New Relic, see our [Introduction to OpenTelemetry Collector with New Relic](/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/collector/opentelemetry-collector-intro).
 
 ## Configure your application to send telemetry data to the OpenTelemetry Collector [#instrument]
 
@@ -205,7 +205,7 @@ You can choose one of these options to monitor your cluster:
 You should be able to verify that your configurations are working once you have successfully linked your OpenTelemetry data with your Kubernetes data.
 
 <Callout variant="caution">
-  Note that the [Kubernetes summary page](/docs/apm/apm-ui-pages/monitoring/kubernetes-summary-page) has a limitation. You must monitor Kubernetes and APM with New Relic's proprietary agents or with OpenTelemetry. If you've a mix of different instrumentation providers (New Relic and OpenTelemetry), you won't see any data on this page.
+ The [Kubernetes summary page](/docs/apm/apm-ui-pages/monitoring/kubernetes-summary-page) only displays data from applications monitored by New Relic's agents or OpenTelemetry. If your environment uses a mix of different instrumentation providers, you may not see complete data on this page.
 </Callout>