Fix needed for layout errors after configuration table in opentelemetry output plugin doc. Fixes #2083.

pipeline/outputs/opentelemetry.md

@@ -93,15 +93,14 @@ Only HTTP endpoints are supported.
 | `tls.windows.use_enterprise_store`        | Sets whether using enterprise certstore or not on an output (Windows).                                                                                  | _none_                                                                          |
 | `traces_uri`                              | Specify an optional HTTP URI for the target OTel endpoint.                                                                                              | `/v1/traces`                                                                    |
 
-== Get started
+## Get started
 
 The OpenTelemetry plugin works with logs and only the metrics collected from one of the metric input plugins. In the following example, log records generated by the dummy plugin and the host metrics collected by the node exporter metrics plugin are exported by the OpenTelemetry output plugin.
 
 {% tabs %}
 {% tab title="fluent-bit.yaml" %}
 
-[source,yaml]
-----
+```yaml
 # Dummy Logs and traces with Node Exporter Metrics export using OpenTelemetry output plugin
 # -------------------------------------------
 # The following example collects host metrics on Linux and dummy logs and traces and delivers
@@ -144,13 +143,12 @@ pipeline:
       add_label:
         - app fluent-bit
         - color blue
-----
+```
 
 {% endtab %}
 {% tab title="fluent-bit.conf" %}
 
-[source,text]
-----
+```text
 # Dummy Logs and traces with Node Exporter Metrics export using OpenTelemetry output plugin
 # -------------------------------------------
 # The following example collects host metrics on Linux and dummy logs and traces and delivers
@@ -193,7 +191,7 @@ pipeline:
   # add user-defined labels
   add_label            app fluent-bit
   add_label            color blue
-----
+```
 
 {% endtab %}
 {% endtabs %}