Merge pull request #18367 from newrelic/clang/fix-img-whats-new

fix: fix image path

src/content/whats-new/2024/07/whats-new-7-23-OtelK8s-PP.md

@@ -2,29 +2,26 @@
 title: 'Native support for open standards'
 summary: 'OpenTelemetry-instrumented Kubernetes and Prometheus-instrumented hosts'
 releaseDate: '2024-07-23'
-learnMoreLink: 'https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-otel/' 
+learnMoreLink: 'https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-otel/'
 ---
 
-
-Analyzing OpenTelemetry and/or Prometheus metrics alongside the rest of your performance data typically requires significant expertise and effort to set up instrumentation and build custom dashboards. And then, you still have to manually correlate data across different screens. 
+Analyzing OpenTelemetry and/or Prometheus metrics alongside the rest of your performance data typically requires significant expertise and effort to set up instrumentation and build custom dashboards. And then, you still have to manually correlate data across different screens.
 
 We've eliminated those challenges with native support for hosts instrumented with either OpenTelemetry or Prometheus, as well as for Kubernetes clusters instrumented with OpenTelemetry. Our solutions give you easy instrumentation that populates native UIs with golden signals and automatically correlates application and infrastructure performance. You can now quickly detect and isolate issues using your preferred open source telemetry data with no vendor lock-in, in one place.
 
 ## Capabilities
 
-* One-step instrumentation for Kubernetes clusters using the OpenTelemetry collector.
-* One-step instrumentation for Prometheus-instrumented hosts with Node Exporter.
-* Native UIs populated with OpenTelemetry and Prometheus-generated golden signals. 
-* Automatic service and infrastructure relationship mapping to understand dependencies across your stack.
-* Automatic correlation between OpenTelemetry-instrumented applications and infrastructure resources to understand how the performance of each layer impacts each other.
+- One-step instrumentation for Kubernetes clusters using the OpenTelemetry collector.
+- One-step instrumentation for Prometheus-instrumented hosts with Node Exporter.
+- Native UIs populated with OpenTelemetry and Prometheus-generated golden signals.
+- Automatic service and infrastructure relationship mapping to understand dependencies across your stack.
+- Automatic correlation between OpenTelemetry-instrumented applications and infrastructure resources to understand how the performance of each layer impacts each other.
 
 ## Learn more
-
-* [**Documentation OpenTelemetry instrumented Kubernetes**](https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-otel)
-* [**Documentation Prometheus instrumented hosts**](https://docs.newrelic.com/docs/infrastructure/prometheus-integrations/integrations-list/node-exporter-integration)
-
-![A screenshot showing OpenTelemetry-instrumented Kubernetes and a Prometheus-instrumented host](images/OtelK8s.webp "A screenshot showing OpenTelemetry-instrumented Kubernetes and Prometheus-instrumented host")
 
-<figcaption>OpenTelemetry-instrumented Kubernetes and Prometheus-instrumented hosts</figcaption>
+- [**Documentation OpenTelemetry instrumented Kubernetes**](https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-otel)
+- [**Documentation Prometheus instrumented hosts**](https://docs.newrelic.com/docs/infrastructure/prometheus-integrations/integrations-list/node-exporter-integration)
 
+![A screenshot showing OpenTelemetry-instrumented Kubernetes and a Prometheus-instrumented host](./images/OtelK8s.webp 'A screenshot showing OpenTelemetry-instrumented Kubernetes and Prometheus-instrumented host')
 
+<figcaption>OpenTelemetry-instrumented Kubernetes and Prometheus-instrumented hosts</figcaption>