OBSDOCS-1058: Update docs about instrumentation for multi-container pods

Signed-off-by: Israel Blancas <[email protected]>

Author: iblancasa

modules/otel-config-instrumentation.adoc

@@ -113,7 +113,7 @@ spec:
 
 |`configPath`
 |Location of the Apache HTTP Server configuration.
-|/usr/local/apache2/conf
+|`/usr/local/apache2/conf`
 
 |`env`
 |Environment variables specific to the Apache HTTP Server.
@@ -340,6 +340,46 @@ instrumentation.opentelemetry.io/container-names: "<container_1>,<container_2>"
 The Go auto-instrumentation does not support multi-container auto-instrumentation injection.
 ====
 
+[id="otel-multi-container-pods-multi-instrumentations_{context}"]
+== Multi-container pods with multiple instrumentations
+
+Injecting instrumentation for an application language to one or more containers in a multi-container pod requires the following annotation:
+
+[source,yaml]
+----
+instrumentation.opentelemetry.io/<application_language>-container-names: "<container_1>,<container_2>" # <1>
+----
+<1> You can inject instrumentation for only one language per container. For the list of supported `<application_language>` values, see the following table.
+
+.Supported values for the `<application_language>`
+[options="header"]
+[cols="a, a"]
+|===
+|Language |Value for `<application_language>`
+
+|ApacheHTTPD
+|`apache`
+
+|DotNet
+|`dotnet`
+
+|Java
+|`java`
+
+|NGINX
+|`inject-nginx`
+
+|NodeJS
+|`nodejs`
+
+|Python
+|`python`
+
+|SDK
+|`sdk`
+
+|===
+
 [id="otel-using-instrumentation-cr-with-service-mesh_{context}"]
 == Using the instrumentation CR with Service Mesh