docs/otel-direct: fix code snippet rendering in table (#4095)

* docs/otel-direct: fix code snippet rendering in table

* Update docs/en/observability/apm/otel-direct.asciidoc

docs/en/observability/apm/otel-direct.asciidoc

@@ -108,14 +108,14 @@ java -javaagent:/path/to/opentelemetry-javaagent-all.jar \
 
 | `OTEL_EXPORTER_OTLP_ENDPOINT` | APM Server URL. The host and port that APM Server listens for events on.
 
-| `OTEL_EXPORTER_OTLP_HEADERS` | Authorization header that includes the Elastic APM Secret token or API key: `"Authorization=Bearer an_apm_secret_token"` or `"Authorization=ApiKey an_api_key"`.
+| `OTEL_EXPORTER_OTLP_HEADERS` a| Authorization header that includes the Elastic APM Secret token or API key: `"Authorization=Bearer an_apm_secret_token"` or `"Authorization=ApiKey an_api_key"`.
 
 For information on how to format an API key, see
 {observability-guide}/apm-api-key.html[API keys].
 
 Please note the required space between `Bearer` and `an_apm_secret_token`, and `ApiKey` and `an_api_key`.
 
-Some language implementations of the OpenTelemetry agent, namely Python, requires the content of the header to be URL encoded. For the `Bearer` token that would mean just substituting the space between `Bearer` an the token with `%20`, e.g. ``"Authorization=Bearer%20an_apm_secret_token"`, for an API Key you can use the following snippet to handle that:
+Some language implementations of the OpenTelemetry agent, namely Python, requires the content of the header to be URL encoded. For the `Bearer` token that would mean just substituting the space between `Bearer` an the token with `%20`, e.g. `"Authorization=Bearer%20an_apm_secret_token"`, for an API key you can use the following snippet to handle that:
 
 [source,python]
 ----