Merge pull request #7101 from OpenLiberty/6776-telemetry

edits

modules/ROOT/pages/microprofile-telemetry.adoc

@@ -20,6 +20,8 @@ link:https://projects.eclipse.org/projects/technology.microprofile/releases/micr
 
 MicroProfile Telemetry replaces MicroProfile OpenTracing. For information about migrating your applications from MicroProfile OpenTracing to MicroProfile Telemetry, see xref:reference:diff/mp-50-60-diff.adoc#telemetry[Differences between MicroProfile Telemetry 1.0 and MicroProfile OpenTracing 3.0].
 
+The following sections explain how to prepare your Open Liberty runtime and application code to use MicroProfile Telemetry.
+
 - <<#ol-config, Configuring Open Liberty to use MicroProfile Telemetry>>
 - <<#code, Code instrumentation>>
 - <<#trouble, Troubleshooting MicroProfile Telemetry>>
@@ -30,14 +32,6 @@ MicroProfile Telemetry replaces MicroProfile OpenTracing. For information about
 To enable MicroProfile Telemetry in your Open Liberty runtime, you must add the MicroProfile Telemetry feature to your `server.xml` file and specify MicroProfile Config properties to configure how MicroProfile Telemetry collects and exports traces.
 
 . Add a version of the feature:mpTelemetry[display=MicroProfile Telemetry] feature to your `server.xml` file.
-////
-+
-Different versions of the MicroProfile Telemetry feature are compatible with different MicroProfile versions, Jakarta and Java Enterprise Editions, and the Open Liberty umbrella features that support them. Both feature:mpTelemetry-1.0[] and feature:mpTelemetry-1.1[] are compatible with feature:jakartaee-10.0[] and feature:microProfile-6.0[]. However, `mpTelemetry-1.1` is also compatible with the following earlier umbrella features:
-+
-*  feature:javaee-7.0[] and feature:microProfile-1.4[]
-*  feature:jakartaee-8.0[] and feature:microProfile-4.1[]
-*  feature:jakartaee-9.1[] and feature:microProfile-5.0[]
-////
 
 . Enable tracing and configure a trace storage system by specifying MicroProfile Config properties.
 +
@@ -273,3 +267,12 @@ If you enable the `mpTelemetry-1.1` or `mpTelemetry-1.0` feature, you must also
 You receive the CWMOT5003W message that the application attempted to acquire MicroProfile Telemetry after shut down::
 
 Review the application to see why it attempted to use MicroProfile Telemetry after it shut down. Actions that might trigger MicroProfile Telemetry include calling a method that is annotated with `@WithSpan`` or making a request with a JAX-RS Client or MP Rest Client.
+
+////
++
+Different versions of the MicroProfile Telemetry feature are compatible with different MicroProfile versions, Jakarta and Java Enterprise Editions, and the Open Liberty umbrella features that support them. Both feature:mpTelemetry-1.0[] and feature:mpTelemetry-1.1[] are compatible with feature:jakartaee-10.0[] and feature:microProfile-6.0[]. However, `mpTelemetry-1.1` is also compatible with the following earlier umbrella features:
++
+*  feature:javaee-7.0[] and feature:microProfile-1.4[]
+*  feature:jakartaee-8.0[] and feature:microProfile-4.1[]
+*  feature:jakartaee-9.1[] and feature:microProfile-5.0[]
+////