From d650488e129ed95aa8166bf5ea4e97e6d0dde3aa Mon Sep 17 00:00:00 2001
From: Max Leonov <mleonov@redhat.com>
Date: Tue, 15 Jul 2025 11:03:37 +0200
Subject: [PATCH] OBSDOCS-1157: Fix instrumentation annotations in OTel docs

---
 modules/otel-config-instrumentation.adoc | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/modules/otel-config-instrumentation.adoc b/modules/otel-config-instrumentation.adoc
index 1c42fe3a765b..8d42bef7cee8 100644
--- a/modules/otel-config-instrumentation.adoc
+++ b/modules/otel-config-instrumentation.adoc
@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 // 
-// * observability/otel/otel-instrumentation.adoc
+// * observability/otel/otel-configuration-of-instrumentation.adoc
 
 :_mod-docs-content-type: REFERENCE
 [id="otel-instrumentation-config_{context}"]
@@ -284,7 +284,7 @@ include::snippets/technology-preview.adoc[leveloffset=+1]
 
 |`version`
 |Apache HTTP Server version.
-|2.4
+|`2.4`
 
 |===
 
@@ -360,7 +360,9 @@ By default, this feature injects unsupported, upstream instrumentation libraries
 [source,yaml]
 ----
 instrumentation.opentelemetry.io/inject-go: "true"
+instrumentation.opentelemetry.io/otel-go-auto-target-exe: "/<path>/<to>/<container>/<executable>" # <1>
 ----
+<1> Sets the value for the required `OTEL_GO_AUTO_TARGET_EXE` environment variable.
 
 .Additional permissions required for the Go auto-instrumentation in the OpenShift cluster
 [source,yaml]
@@ -459,11 +461,8 @@ By default, this feature injects unsupported, upstream instrumentation libraries
 [source,yaml]
 ----
 instrumentation.opentelemetry.io/inject-nodejs: "true"
-instrumentation.opentelemetry.io/otel-go-auto-target-exe: "/path/to/container/executable"
 ----
 
-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
 
@@ -507,8 +506,9 @@ The instrumentation is run on the first container that is available by default a
 .Pod annotation
 [source,yaml]
 ----
-instrumentation.opentelemetry.io/container-names: "<container_1>,<container_2>"
+instrumentation.opentelemetry.io/container-names: "<container_1>,<container_2>" # <1>
 ----
+<1> Use this annotation when you want to inject a single instrumentation in multiple containers.
 
 [NOTE]
 ====
@@ -533,7 +533,7 @@ instrumentation.opentelemetry.io/<application_language>-container-names: "<conta
 |Language |Value for `<application_language>`
 
 |ApacheHTTPD
-|`apache`
+|`apache-httpd`
 
 |DotNet
 |`dotnet`
@@ -558,4 +558,4 @@ instrumentation.opentelemetry.io/<application_language>-container-names: "<conta
 [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.
+When using the `Instrumentation` custom resource (CR) with {SMProductName}, you must use the `b3multi` propagator.