Merge pull request #83383 from max-cx/OBSDOCS-1406

OBSDOCS-1406: Fix section heading level and move one section

Author: ShaunaDiaz

modules/otel-config-instrumentation.adoc

@@ -98,13 +98,8 @@ spec:
 
 |===
 
-[id="otel-using-instrumentation-cr-with-service-mesh_{context}"]
-== Using the instrumentation CR with Service Mesh
-
-When using the instrumentation custom resource (CR) with {SMProductName}, you must use the `b3multi` propagator.
-
 [id="otel-configuration-of-apache-http-server-auto-instrumentation_{context}"]
-=== Configuration of the Apache HTTP Server auto-instrumentation
+== Configuration of the Apache HTTP Server auto-instrumentation
 
 .Parameters for the `+.spec.apacheHttpd+` field
 [options="header"]
@@ -145,7 +140,7 @@ instrumentation.opentelemetry.io/inject-apache-httpd: "true"
 ----
 
 [id="otel-configuration-of-dotnet-auto-instrumentation_{context}"]
-=== Configuration of the .NET auto-instrumentation
+== Configuration of the .NET auto-instrumentation
 
 [options="header"]
 [cols="a, a"]
@@ -172,7 +167,7 @@ instrumentation.opentelemetry.io/inject-dotnet: "true"
 ----
 
 [id="otel-configuration-of-go-auto-instrumentation_{context}"]
-=== Configuration of the Go auto-instrumentation
+== Configuration of the Go auto-instrumentation
 
 [options="header"]
 [cols="a, a"]
@@ -230,7 +225,7 @@ $ oc adm policy add-scc-to-user otel-go-instrumentation-scc -z <service_account>
 ====
 
 [id="otel-configuration-of-java-auto-instrumentation_{context}"]
-=== Configuration of the Java auto-instrumentation
+== Configuration of the Java auto-instrumentation
 
 [options="header"]
 [cols="a, a"]
@@ -255,7 +250,7 @@ instrumentation.opentelemetry.io/inject-java: "true"
 ----
 
 [id="otel-configuration-of-nodejs-auto-instrumentation_{context}"]
-=== Configuration of the Node.js auto-instrumentation
+== Configuration of the Node.js auto-instrumentation
 
 [options="header"]
 [cols="a, a"]
@@ -283,7 +278,7 @@ instrumentation.opentelemetry.io/otel-go-auto-target-exe: "/path/to/container/ex
 The `+instrumentation.opentelemetry.io/otel-go-auto-target-exe+` annotation sets the value for the required `OTEL_GO_AUTO_TARGET_EXE` environment variable.
 
 [id="otel-configuration-of-python-auto-instrumentation_{context}"]
-=== Configuration of the Python auto-instrumentation
+== Configuration of the Python auto-instrumentation
 
 [options="header"]
 [cols="a, a"]
@@ -310,7 +305,7 @@ instrumentation.opentelemetry.io/inject-python: "true"
 ----
 
 [id="otel-configuration-of-opentelemetry-sdk-variables_{context}"]
-=== Configuration of the OpenTelemetry SDK variables
+== Configuration of the OpenTelemetry SDK variables
 
 The OpenTelemetry SDK variables in your pod are configurable by using the following annotation:
 
@@ -330,7 +325,7 @@ Note that all the annotations accept the following values:
 `other-namespace/instrumentation-name`:: The name of the instrumentation resource to inject from another namespace.
 
 [id="otel-multi-container-pods_{context}"]
-=== Multi-container pods
+== Multi-container pods
 
 The instrumentation is run on the first container that is available by default according to the pod specification. In some cases, you can also specify target containers for injection.
 
@@ -344,3 +339,8 @@ instrumentation.opentelemetry.io/container-names: "<container_1>,<container_2>"
 ====
 The Go auto-instrumentation does not support multi-container auto-instrumentation injection.
 ====
+
+[id="otel-using-instrumentation-cr-with-service-mesh_{context}"]
+== Using the instrumentation CR with Service Mesh
+
+When using the instrumentation custom resource (CR) with {SMProductName}, you must use the `b3multi` propagator.