Merge pull request #7555 from OpenLiberty/7459-mptel-logs

fix link

modules/ROOT/pages/custom-mptelemetry-metrics.adoc

@@ -18,7 +18,7 @@ For more information about collecting and emitting metrics with MicroProfile Tel
 
 For more information about OpenTelemetry metrics, see the link:https://www.javadoc.io/doc/io.opentelemetry/opentelemetry-api/1.39.0/io/opentelemetry/api/metrics/package-summary.html[OpenTelemetry metrics API documentation].
 
-Before you can use MicroProfile Telemetry to define custom metrics metrics, you must enable MicroProfile Telemetry in your development environment by editing your runtime configuration. You must also add the OpenTelemetry API and annotations as a dependency on your build path. For more information, see xref:prepare-mptelemetry-metrics.adoc[Prepare your development environment for MicroProfile Telemetry].
+Before you can use MicroProfile Telemetry to define custom metrics metrics, you must enable MicroProfile Telemetry in your development environment by editing your runtime configuration. You must also add the OpenTelemetry API and annotations as a dependency on your build path. For more information, see xref:prepare-mptelemetry.adoc[Prepare your development environment for MicroProfile Telemetry].
 
 The following example defines a custom counter metric:
 

modules/ROOT/pages/observability.adoc

@@ -19,7 +19,7 @@ With MicroProfile Telemetry 2.0 and later, you can manage logs, metrics, and tra
 
 The following topics provide information to help you develop observable applications with Open Liberty.
 
-xref:prepare-mptelemetry-metrics.adoc[Prepare your development environment for MicroProfile Telemetry]::
+xref:prepare-mptelemetry.adoc[Prepare your development environment for MicroProfile Telemetry]::
 Before you manually instrument your code to use MicroProfile Telemetry to collect metrics and traces, you must enable MicroProfile Telemetry in your development environment by editing your runtime configuration. You must also add the OpenTelemetry API and annotations as a dependency on your build path.
 
 xref:custom-mptelemetry-metrics.adoc[Define custom MicroProfile Telemetry metrics]::

modules/ROOT/pages/telemetry-trace.adoc

@@ -52,7 +52,7 @@ otel.exporter.zipkin.endpoint=http://localhost:9411/api/v2/spans
 
 Automatic instrumentation is available only for JAX-RS and Jakarta RESTful web service applications. To create spans for other operations, such as database calls, you can add manual instrumentation to the source code for those operations by using the https://www.javadoc.io/doc/io.opentelemetry/opentelemetry-api/1.39.0/io/opentelemetry/api/trace/package-summary.html[OpenTelemetry API].
 
-However, before you manually instrument your code, you must enable MicroProfile Telemetry in your development environment by editing your runtime configuration. You must also add the OpenTelemetry API and annotations as a dependency on your build path. For more information, see xref:prepare-mptelemetry-metrics.adoc[Prepare your development environment for MicroProfile Telemetry].
+However, before you manually instrument your code, you must enable MicroProfile Telemetry in your development environment by editing your runtime configuration. You must also add the OpenTelemetry API and annotations as a dependency on your build path. For more information, see xref:prepare-mptelemetry.adoc[Prepare your development environment for MicroProfile Telemetry].
 
 After you complete those prerequisites, you're ready to instrument your code. The following examples show configuration options with the OpenTelemetry API.