diff --git a/docs/sources/collect/choose-component.md b/docs/sources/collect/choose-component.md
index 36a880d54c..383a0df610 100644
--- a/docs/sources/collect/choose-component.md
+++ b/docs/sources/collect/choose-component.md
@@ -6,7 +6,7 @@ menuTitle: Choose a component
 weight: 100
 ---
 
-# Choose a  {{< param "FULL_PRODUCT_NAME" >}} component
+# Choose a {{< param "FULL_PRODUCT_NAME" >}} component
 
 [Components][components] are the building blocks of {{< param "FULL_PRODUCT_NAME" >}}, and there is a [large number of them][components-ref].
 The components you select and configure depend on the telemetry signals you want to collect.
@@ -24,7 +24,7 @@ For example, you can get metrics for a Linux host using `prometheus.exporter.uni
 You can also scrape any Prometheus endpoint using `prometheus.scrape`.
 Use `discovery.*` components to find targets for `prometheus.scrape`.
 
-[Grafana Infrastructure Observability]:https://grafana.com/docs/grafana-cloud/monitor-infrastructure/
+[Grafana Infrastructure Observability]: https://grafana.com/docs/grafana-cloud/monitor-infrastructure/
 
 ## Metrics for applications
 
@@ -36,7 +36,7 @@ For example, use `otelcol.receiver.otlp` to collect metrics from OpenTelemetry-i
 If your application is already instrumented with Prometheus metrics, there is no need to use `otelcol.*` components.
 Use `prometheus.*` components for the entire pipeline and send the metrics using `prometheus.remote_write`.
 
-[Grafana Application Observability]:https://grafana.com/docs/grafana-cloud/monitor-applications/application-observability/introduction/
+[Grafana Application Observability]: https://grafana.com/docs/grafana-cloud/monitor-applications/application-observability/introduction/
 
 ## Logs from infrastructure
 
@@ -58,7 +58,7 @@ All application telemetry must follow the [OpenTelemetry semantic conventions][O
 
 For example, if your application runs on Kubernetes, every trace, log, and metric can have a `k8s.namespace.name` resource attribute.
 
-[OTel-semantics]:https://opentelemetry.io/docs/concepts/semantic-conventions/
+[OTel-semantics]: https://opentelemetry.io/docs/concepts/semantic-conventions/
 
 ## Traces
 
diff --git a/docs/sources/collect/datadog-traces-metrics.md b/docs/sources/collect/datadog-traces-metrics.md
index 2ab9da3590..ba39d81f62 100644
--- a/docs/sources/collect/datadog-traces-metrics.md
+++ b/docs/sources/collect/datadog-traces-metrics.md
@@ -14,17 +14,17 @@ You can configure {{< param "PRODUCT_NAME" >}} to collect [Datadog][] traces and
 
 This topic describes how to:
 
-* Configure {{< param "PRODUCT_NAME" >}} to send traces and metrics.
-* Configure the {{< param "PRODUCT_NAME" >}} Datadog Receiver.
-* Configure the Datadog Agent to forward traces and metrics to the {{< param "PRODUCT_NAME" >}} Datadog Receiver.
+- Configure {{< param "PRODUCT_NAME" >}} to send traces and metrics.
+- Configure the {{< param "PRODUCT_NAME" >}} Datadog Receiver.
+- Configure the Datadog Agent to forward traces and metrics to the {{< param "PRODUCT_NAME" >}} Datadog Receiver.
 
 ## Before you begin
 
-* Ensure that at least one instance of the [Datadog Agent][] is collecting metrics and traces.
-* Identify where to write the collected telemetry.
+- Ensure that at least one instance of the [Datadog Agent][] is collecting metrics and traces.
+- Identify where to write the collected telemetry.
   Metrics can be written to [Prometheus][] or any other OpenTelemetry-compatible database such as Grafana Mimir, Grafana Cloud, or Grafana Enterprise Metrics.
   Traces can be written to Grafana Tempo, Grafana Cloud, or Grafana Enterprise Traces.
-* Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
+- Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
 
 ## Configure {{% param "PRODUCT_NAME" %}} to send traces and metrics
 
@@ -45,7 +45,7 @@ The [otelcol.exporter.otlp][] component is responsible for delivering OTLP data
 
    Replace the following:
 
-   * _`<OTLP_ENDPOINT_URL>`_: The full URL of the OpenTelemetry-compatible endpoint where metrics and traces are sent, such as `https://otlp-gateway-prod-eu-west-2.grafana.net/otlp`.
+   - _`<OTLP_ENDPOINT_URL>`_: The full URL of the OpenTelemetry-compatible endpoint where metrics and traces are sent, such as `https://otlp-gateway-prod-eu-west-2.grafana.net/otlp`.
 
 1. If your endpoint requires basic authentication, paste the following inside the `endpoint` block.
 
@@ -58,8 +58,8 @@ The [otelcol.exporter.otlp][] component is responsible for delivering OTLP data
 
    Replace the following:
 
-   * _`<USERNAME>`_: The basic authentication username.
-   * _`<PASSWORD>`_: The basic authentication password or API key.
+   - _`<USERNAME>`_: The basic authentication username.
+   - _`<PASSWORD>`_: The basic authentication password or API key.
 
 ## Configure the {{% param "PRODUCT_NAME" %}} Datadog Receiver
 
@@ -88,8 +88,8 @@ The [otelcol.exporter.otlp][] component is responsible for delivering OTLP data
 
    Replace the following:
 
-   * _`<MAX_STALE>`_: How long until a series not receiving new samples is removed, such as "5m".
-   * _`<MAX_STREAMS>`_: The upper limit of streams to track. New streams exceeding this limit are dropped.
+   - _`<MAX_STALE>`_: How long until a series not receiving new samples is removed, such as "5m".
+   - _`<MAX_STREAMS>`_: The upper limit of streams to track. New streams exceeding this limit are dropped.
 
 1. Add the following `otelcol.receiver.datadog` component to your configuration file.
 
@@ -103,10 +103,10 @@ The [otelcol.exporter.otlp][] component is responsible for delivering OTLP data
    }
    ```
 
-    Replace the following:
+   Replace the following:
 
-    * _`<HOST>`_: The host address where the receiver listens.
-    * _`<PORT>`_: The port where the receiver listens.
+   - _`<HOST>`_: The host address where the receiver listens.
+   - _`<PORT>`_: The port where the receiver listens.
 
 1. If your endpoint requires basic authentication, paste the following inside the `endpoint` block.
 
@@ -117,10 +117,10 @@ The [otelcol.exporter.otlp][] component is responsible for delivering OTLP data
    }
    ```
 
-    Replace the following:
+   Replace the following:
 
-    * _`<USERNAME>`_: The basic authentication username.
-    * _`<PASSWORD>`_: The basic authentication password or API key.
+   - _`<USERNAME>`_: The basic authentication username.
+   - _`<PASSWORD>`_: The basic authentication password or API key.
 
 ## Configure Datadog Agent to forward telemetry to the {{% param "PRODUCT_NAME" %}} Datadog Receiver
 
@@ -139,8 +139,8 @@ We recommend this approach for current Datadog users who want to try using {{< p
 
    Replace the following:
 
-   * _`<DATADOG_RECEIVER_HOST>`_: The hostname where the {{< param "PRODUCT_NAME" >}} receiver is found.
-   * _`<DATADOG_RECEIVER_PORT>`_: The port where the {{< param "PRODUCT_NAME" >}} receiver is exposed.
+   - _`<DATADOG_RECEIVER_HOST>`_: The hostname where the {{< param "PRODUCT_NAME" >}} receiver is found.
+   - _`<DATADOG_RECEIVER_PORT>`_: The port where the {{< param "PRODUCT_NAME" >}} receiver is exposed.
 
 Alternatively, you might want your Datadog Agent to send metrics only to {{< param "PRODUCT_NAME" >}}.
 You can do this by setting up your Datadog Agent in the following way:
@@ -148,7 +148,7 @@ You can do this by setting up your Datadog Agent in the following way:
 1. Replace the DD_URL in the configuration YAML:
 
    ```yaml
-    dd_url: http://<DATADOG_RECEIVER_HOST>:<DATADOG_RECEIVER_PORT>
+   dd_url: http://<DATADOG_RECEIVER_HOST>:<DATADOG_RECEIVER_PORT>
    ```
 
    Or by setting an environment variable:
@@ -162,9 +162,9 @@ You can do this by setting up your Datadog Agent in the following way:
 The `otelcol.receiver.datadog` component is experimental.
 To use this component, you need to start {{< param "PRODUCT_NAME" >}} with additional command line flags:
 
-   ```bash
-   alloy run config.alloy --stability.level=experimental
-   ```
+```bash
+alloy run config.alloy --stability.level=experimental
+```
 
 [Datadog]: https://www.datadoghq.com/
 [Datadog Agent]: https://docs.datadoghq.com/agent/
diff --git a/docs/sources/collect/ecs-opentelemetry-data.md b/docs/sources/collect/ecs-opentelemetry-data.md
index 298bd73bc2..e405fd9a73 100644
--- a/docs/sources/collect/ecs-opentelemetry-data.md
+++ b/docs/sources/collect/ecs-opentelemetry-data.md
@@ -20,10 +20,10 @@ There are three different ways you can use {{< param "PRODUCT_NAME" >}} to colle
 
 ## Before you begin
 
-* Ensure that you have basic familiarity with instrumenting applications with OpenTelemetry.
-* Have an available Amazon ECS or AWS Fargate deployment.
-* Identify where {{< param "PRODUCT_NAME" >}} writes received telemetry data.
-* Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
+- Ensure that you have basic familiarity with instrumenting applications with OpenTelemetry.
+- Have an available Amazon ECS or AWS Fargate deployment.
+- Identify where {{< param "PRODUCT_NAME" >}} writes received telemetry data.
+- Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
 
 ## Use a custom OpenTelemetry configuration file from the SSM Parameter store
 
@@ -39,8 +39,8 @@ In ECS, you can set the values of environment variables from AWS Systems Manager
 
    1. Open the AWS Systems Manager console.
    1. Select Elastic Container Service.
-   1. In the navigation pane, choose *Task definition*.
-   1. Choose *Create new revision*.
+   1. In the navigation pane, choose _Task definition_.
+   1. Choose _Create new revision_.
 
 1. Add an environment variable.
 
@@ -53,15 +53,15 @@ In ECS, you can set the values of environment variables from AWS Systems Manager
 ### Create the SSM parameter
 
 1. Open the AWS Systems Manager console.
-1. In the navigation pane, choose *Parameter Store*.
-1. Choose *Create parameter*.
+1. In the navigation pane, choose _Parameter Store_.
+1. Choose _Create parameter_.
 1. Create a parameter with the following values:
 
-   * Name: `otel-collector-config`
-   * Tier: `Standard`
-   * Type: `String`
-   * Data type: `Text`
-   * Value: Copy and paste your custom OpenTelemetry configuration file or [{{< param "PRODUCT_NAME" >}} configuration file][configure].
+   - Name: `otel-collector-config`
+   - Tier: `Standard`
+   - Type: `String`
+   - Data type: `Text`
+   - Value: Copy and paste your custom OpenTelemetry configuration file or [{{< param "PRODUCT_NAME" >}} configuration file][configure].
 
 ### Run your task
 
@@ -75,13 +75,13 @@ To create an ECS Task Definition for AWS Fargate with an ADOT collector, complet
 
 1. Download the [ECS Fargate task definition template][template] from GitHub.
 1. Edit the task definition template and add the following parameters.
-   * `{{region}}`: The region to send the data to.
-   * `{{ecsTaskRoleArn}}`: The AWSOTTaskRole ARN.
-   * `{{ecsExecutionRoleArn}}`: The AWSOTTaskExcutionRole ARN.
-   * `command` - Assign a value to the command variable to select the path to the configuration file.
+   - `{{region}}`: The region to send the data to.
+   - `{{ecsTaskRoleArn}}`: The AWSOTTaskRole ARN.
+   - `{{ecsExecutionRoleArn}}`: The AWSOTTaskExcutionRole ARN.
+   - `command` - Assign a value to the command variable to select the path to the configuration file.
      The AWS Collector comes with two configurations. Select one of them based on your environment:
-     * Use `--config=/etc/ecs/ecs-default-config.yaml` to consume StatsD metrics, OTLP metrics and traces, and AWS X-Ray SDK traces.
-     * Use `--config=/etc/ecs/container-insights/otel-task-metrics-config.yaml` to use StatsD, OTLP, AWS X-Ray, and Container Resource utilization metrics.
+     - Use `--config=/etc/ecs/ecs-default-config.yaml` to consume StatsD metrics, OTLP metrics and traces, and AWS X-Ray SDK traces.
+     - Use `--config=/etc/ecs/container-insights/otel-task-metrics-config.yaml` to use StatsD, OTLP, AWS X-Ray, and Container Resource utilization metrics.
 1. Follow the ECS Fargate setup instructions to [create a task definition][task] using the template.
 
 ## Run {{% param "PRODUCT_NAME" %}} directly in your instance, or as a Kubernetes sidecar
diff --git a/docs/sources/collect/logs-in-kubernetes.md b/docs/sources/collect/logs-in-kubernetes.md
index d8b8b17fb2..5feda702fb 100644
--- a/docs/sources/collect/logs-in-kubernetes.md
+++ b/docs/sources/collect/logs-in-kubernetes.md
@@ -4,7 +4,7 @@ aliases:
   - ../tasks/collect-logs-in-kubernetes/ # /docs/alloy/latest/tasks/collect-logs-in-kubernetes/
 description: Learn how to collect logs on Kubernetes and forward them to Loki
 menuTitle: Collect Kubernetes logs
-title:  Collect Kubernetes logs and forward them to Loki
+title: Collect Kubernetes logs and forward them to Loki
 weight: 250
 ---
 
@@ -14,26 +14,26 @@ You can configure {{< param "PRODUCT_NAME" >}} to collect logs and forward them
 
 This topic describes how to:
 
-* Configure logs delivery.
-* Collect logs from Kubernetes Pods.
+- Configure logs delivery.
+- Collect logs from Kubernetes Pods.
 
 ## Components used in this topic
 
-* [`discovery.kubernetes`][discovery.kubernetes]
-* [`discovery.relabel`][discovery.relabel]
-* [`local.file_match`][local.file_match]
-* [`loki.source.file`][loki.source.file]
-* [`loki.source.kubernetes`][loki.source.kubernetes]
-* [`loki.source.kubernetes_events`][loki.source.kubernetes_events]
-* [`loki.process`][loki.process]
-* [`loki.write`][loki.write]
+- [`discovery.kubernetes`][discovery.kubernetes]
+- [`discovery.relabel`][discovery.relabel]
+- [`local.file_match`][local.file_match]
+- [`loki.source.file`][loki.source.file]
+- [`loki.source.kubernetes`][loki.source.kubernetes]
+- [`loki.source.kubernetes_events`][loki.source.kubernetes_events]
+- [`loki.process`][loki.process]
+- [`loki.write`][loki.write]
 
 ## Before you begin
 
-* Ensure that you are familiar with logs labelling when working with Loki.
-* Identify where to write collected logs.
+- Ensure that you are familiar with logs labelling when working with Loki.
+- Identify where to write collected logs.
   You can write logs to Loki endpoints such as Grafana Loki, Grafana Cloud, or Grafana Enterprise Logs.
-* Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
+- Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
 
 ## Configure logs delivery
 
@@ -56,9 +56,9 @@ To configure a `loki.write` component for logs delivery, complete the following
 
    Replace the following:
 
-   * _`<LABEL>`_: The label for the component, such as `default`.
+   - _`<LABEL>`_: The label for the component, such as `default`.
      The label you use must be unique across all `loki.write` components in the same configuration file.
-   * _`<LOKI_URL>`_ : The full URL of the Loki endpoint where logs are sent, such as `https://logs-us-central1.grafana.net/loki/api/v1/push`.
+   - _`<LOKI_URL>`_ : The full URL of the Loki endpoint where logs are sent, such as `https://logs-us-central1.grafana.net/loki/api/v1/push`.
 
 1. If your endpoint requires basic authentication, paste the following inside the `endpoint` block.
 
@@ -71,8 +71,8 @@ To configure a `loki.write` component for logs delivery, complete the following
 
    Replace the following:
 
-   * _`<USERNAME>`_: The basic authentication username.
-   * _`<PASSWORD>`_: The basic authentication password or API key.
+   - _`<USERNAME>`_: The basic authentication username.
+   - _`<PASSWORD>`_: The basic authentication password or API key.
 
 1. If you have more than one endpoint to write logs to, repeat the `endpoint` block for additional endpoints.
 
@@ -110,8 +110,8 @@ loki.source.file "example" {
 
 Replace the following:
 
-* _`<USERNAME>`_: The remote write username.
-* _`<PASSWORD>`_: The remote write password.
+- _`<USERNAME>`_: The remote write username.
+- _`<PASSWORD>`_: The remote write password.
 
 For more information on configuring logs delivery, refer to [loki.write][].
 
@@ -129,9 +129,9 @@ Thanks to the component architecture, you can follow one or all of the next sect
 
 To get the system logs, you should use the following components:
 
-* [`local.file_match`][local.file_match]: Discovers files on the local filesystem.
-* [`loki.source.file`][loki.source.file]: Reads log entries from files.
-* [`loki.write`][loki.write]: Send logs to the Loki endpoint. You should have configured it in the [Configure logs delivery](#configure-logs-delivery) section.
+- [`local.file_match`][local.file_match]: Discovers files on the local filesystem.
+- [`loki.source.file`][loki.source.file]: Reads log entries from files.
+- [`loki.write`][loki.write]: Send logs to the Loki endpoint. You should have configured it in the [Configure logs delivery](#configure-logs-delivery) section.
 
 Here is an example using those stages.
 
@@ -157,8 +157,8 @@ loki.source.file "node_logs" {
 
 Replace the following values:
 
-* _`<CLUSTER_NAME>`_: The label for this specific Kubernetes cluster, such as `production` or `us-east-1`.
-* _`<WRITE_COMPONENT_NAME>`_: The name of your `loki.write` component, such as `default`.
+- _`<CLUSTER_NAME>`_: The label for this specific Kubernetes cluster, such as `production` or `us-east-1`.
+- _`<WRITE_COMPONENT_NAME>`_: The name of your `loki.write` component, such as `default`.
 
 ### Pods logs
 
@@ -168,11 +168,11 @@ You can get pods logs through the log files on each node. In this guide, you get
 
 You need the following components:
 
-* [`discovery.kubernetes`][discovery.kubernetes]: Discover pods information and list them for components to use.
-* [`discovery.relabel`][discovery.relabel]: Enforce relabelling strategies on the list of pods.
-* [`loki.source.kubernetes`][loki.source.kubernetes]: Tails logs from a list of Kubernetes pods targets.
-* [`loki.process`][loki.process]: Modify the logs before sending them to the next component.
-* [`loki.write`][loki.write]: Send logs to the Loki endpoint. You should have configured it in the [Configure logs delivery](#configure-logs-delivery) section.
+- [`discovery.kubernetes`][discovery.kubernetes]: Discover pods information and list them for components to use.
+- [`discovery.relabel`][discovery.relabel]: Enforce relabelling strategies on the list of pods.
+- [`loki.source.kubernetes`][loki.source.kubernetes]: Tails logs from a list of Kubernetes pods targets.
+- [`loki.process`][loki.process]: Modify the logs before sending them to the next component.
+- [`loki.write`][loki.write]: Send logs to the Loki endpoint. You should have configured it in the [Configure logs delivery](#configure-logs-delivery) section.
 
 Here is an example using those stages:
 
@@ -267,16 +267,16 @@ loki.process "pod_logs" {
 
 Replace the following values:
 
-* _`<CLUSTER_NAME>`_: The label for this specific Kubernetes cluster, such as `production` or `us-east-1`.
-* _`<WRITE_COMPONENT_NAME>`_: The name of your `loki.write` component, such as `default`.
+- _`<CLUSTER_NAME>`_: The label for this specific Kubernetes cluster, such as `production` or `us-east-1`.
+- _`<WRITE_COMPONENT_NAME>`_: The name of your `loki.write` component, such as `default`.
 
 ### Kubernetes Cluster Events
 
 You need the following components:
 
-* [`loki.source.kubernetes_events`][loki.source.kubernetes_events]: Tails events from Kubernetes API.
-* [`loki.process`][loki.process]: Modify the logs before sending them to the next component.
-* [`loki.write`][loki.write]: Send logs to the Loki endpoint. You should have configured it in the [Configure logs delivery](#configure-logs-delivery) section.
+- [`loki.source.kubernetes_events`][loki.source.kubernetes_events]: Tails events from Kubernetes API.
+- [`loki.process`][loki.process]: Modify the logs before sending them to the next component.
+- [`loki.write`][loki.write]: Send logs to the Loki endpoint. You should have configured it in the [Configure logs delivery](#configure-logs-delivery) section.
 
 Here is an example using those stages:
 
@@ -312,8 +312,8 @@ loki.process "cluster_events" {
 
 Replace the following values:
 
-* _`<CLUSTER_NAME>`_: The label for this specific Kubernetes cluster, such as `production` or `us-east-1`.
-* _`<WRITE_COMPONENT_NAME>`_: The name of your `loki.write` component, such as `default`.
+- _`<CLUSTER_NAME>`_: The label for this specific Kubernetes cluster, such as `production` or `us-east-1`.
+- _`<WRITE_COMPONENT_NAME>`_: The name of your `loki.write` component, such as `default`.
 
 [Loki]: https://grafana.com/oss/loki/
 [discovery.kubernetes]: ../../reference/components/discovery/discovery.kubernetes/
diff --git a/docs/sources/collect/metamonitoring.md b/docs/sources/collect/metamonitoring.md
index 9bb30dce19..0a1ae70c43 100644
--- a/docs/sources/collect/metamonitoring.md
+++ b/docs/sources/collect/metamonitoring.md
@@ -16,21 +16,21 @@ This topic describes how to collect and forward metrics, logs, and traces data f
 
 ## Components and configuration blocks used in this topic
 
-* [`prometheus.exporter.self`][prometheus.exporter.self]
-* [`prometheus.scrape`][prometheus.scrape]
-* [`logging`][logging]
-* [`tracing`][tracing]
+- [`prometheus.exporter.self`][prometheus.exporter.self]
+- [`prometheus.scrape`][prometheus.scrape]
+- [`logging`][logging]
+- [`tracing`][tracing]
 
 ## Before you begin
 
-* Identify where to send {{< param "PRODUCT_NAME" >}}'s telemetry data.
-* Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
+- Identify where to send {{< param "PRODUCT_NAME" >}}'s telemetry data.
+- Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
 
 ## Meta-monitoring metrics
 
 {{< param "PRODUCT_NAME" >}} exposes its internal metrics using the Prometheus exposition format.
 
-In this task, you use the [`prometheus.exporter.self`][prometheus.exporter.self] and [`prometheus.scrape`][prometheus.scrape] components to scrape {{< param "PRODUCT_NAME" >}}'s  internal metrics and forward it to compatible {{< param "PRODUCT_NAME" >}} components.
+In this task, you use the [`prometheus.exporter.self`][prometheus.exporter.self] and [`prometheus.scrape`][prometheus.scrape] components to scrape {{< param "PRODUCT_NAME" >}}'s internal metrics and forward it to compatible {{< param "PRODUCT_NAME" >}} components.
 
 1. Add the following `prometheus.exporter.self` component to your configuration. The component accepts no arguments.
 
@@ -49,9 +49,10 @@ In this task, you use the [`prometheus.exporter.self`][prometheus.exporter.self]
    ```
 
    Replace the following:
-   * _`<SELF_LABEL>`_: The label for the component such as `default` or `metamonitoring`. The label must be unique across all `prometheus.exporter.self` components in the same configuration file.
-   * _`<SCRAPE_LABEL>`_: The label for the scrape component such as `default`. The label must be unique across all `prometheus.scrape` components in the same configuration file.
-   * _`<METRICS_RECEIVER_LIST>`_: A comma-delimited list of component receivers to forward metrics to.
+
+   - _`<SELF_LABEL>`_: The label for the component such as `default` or `metamonitoring`. The label must be unique across all `prometheus.exporter.self` components in the same configuration file.
+   - _`<SCRAPE_LABEL>`_: The label for the scrape component such as `default`. The label must be unique across all `prometheus.scrape` components in the same configuration file.
+   - _`<METRICS_RECEIVER_LIST>`_: A comma-delimited list of component receivers to forward metrics to.
      For example, to send to a remote write component, use `prometheus.remote_write.WRITE_LABEL.receiver`.
      Similarly, to send data to a relabeling component, use `prometheus.relabel.PROCESS_LABEL.receiver`.
      To use data in the OTLP format, you can send data to a converter component, like `otelcol.receiver.prometheus.OTEL.receiver`.
@@ -92,9 +93,10 @@ The block is specified without a label and can only be provided once per configu
    ```
 
    Replace the following:
-   * _`<LOG_LEVEL>`_: The log level to use for {{< param "PRODUCT_NAME" >}}'s logs. If the attribute isn't set, it defaults to `info`.
-   * _`<LOG_FORMAT>`_: The log format to use for {{< param "PRODUCT_NAME" >}}'s logs. If the attribute isn't set, it defaults to `logfmt`.
-   * _`<LOGS_RECEIVER_LIST>`_: A comma-delimited list of component receivers to forward logs to.
+
+   - _`<LOG_LEVEL>`_: The log level to use for {{< param "PRODUCT_NAME" >}}'s logs. If the attribute isn't set, it defaults to `info`.
+   - _`<LOG_FORMAT>`_: The log format to use for {{< param "PRODUCT_NAME" >}}'s logs. If the attribute isn't set, it defaults to `logfmt`.
+   - _`<LOGS_RECEIVER_LIST>`_: A comma-delimited list of component receivers to forward logs to.
      For example, to send to a processing component, use `loki.process.PROCESS_LABEL.receiver`.
      Similarly, to send data to a relabeling component, use `loki.relabel.PROCESS_LABEL.receiver`.
      To use data in the OTLP format, you can send data to a converter component, like `otelcol.receiver.loki.OTEL.receiver`.
@@ -132,8 +134,9 @@ In this task, you use the [tracing][] block to forward {{< param "PRODUCT_NAME"
    ```
 
    Replace the following:
-   * _`<SAMPLING_FRACTION>`_: The fraction of traces to keep. If the attribute isn't set, it defaults to `0.1`.
-   * _`<TRACES_RECEIVER_LIST>`_: A comma-delimited list of component receivers to forward traces to.
+
+   - _`<SAMPLING_FRACTION>`_: The fraction of traces to keep. If the attribute isn't set, it defaults to `0.1`.
+   - _`<TRACES_RECEIVER_LIST>`_: A comma-delimited list of component receivers to forward traces to.
      For example, to send to an OpenTelemetry exporter component use `otelcol.exporter.otlp.EXPORT_LABEL.input`.
 
 The following example demonstrates configuring the tracing block and sending to a compatible component.
diff --git a/docs/sources/collect/opentelemetry-data.md b/docs/sources/collect/opentelemetry-data.md
index 651ba3747a..ade3202fab 100644
--- a/docs/sources/collect/opentelemetry-data.md
+++ b/docs/sources/collect/opentelemetry-data.md
@@ -14,24 +14,24 @@ You can configure {{< param "PRODUCT_NAME" >}} to collect [OpenTelemetry][]-comp
 
 This topic describes how to:
 
-* Configure OpenTelemetry data delivery.
-* Configure batching.
-* Receive OpenTelemetry data over OTLP.
+- Configure OpenTelemetry data delivery.
+- Configure batching.
+- Receive OpenTelemetry data over OTLP.
 
 ## Components used in this topic
 
-* [`otelcol.auth.basic`][otelcol.auth.basic]
-* [`otelcol.exporter.otlp`][otelcol.exporter.otlp]
-* [`otelcol.exporter.otlphttp`][otelcol.exporter.otlphttp]
-* [`otelcol.processor.batch`][otelcol.processor.batch]
-* [`otelcol.receiver.otlp`][otelcol.receiver.otlp]
+- [`otelcol.auth.basic`][otelcol.auth.basic]
+- [`otelcol.exporter.otlp`][otelcol.exporter.otlp]
+- [`otelcol.exporter.otlphttp`][otelcol.exporter.otlphttp]
+- [`otelcol.processor.batch`][otelcol.processor.batch]
+- [`otelcol.receiver.otlp`][otelcol.receiver.otlp]
 
 ## Before you begin
 
-* Ensure that you have basic familiarity with instrumenting applications with OpenTelemetry.
-* Have a set of OpenTelemetry applications ready to push telemetry data to {{< param "PRODUCT_NAME" >}}.
-* Identify where {{< param "PRODUCT_NAME" >}} writes received telemetry data.
-* Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
+- Ensure that you have basic familiarity with instrumenting applications with OpenTelemetry.
+- Have a set of OpenTelemetry applications ready to push telemetry data to {{< param "PRODUCT_NAME" >}}.
+- Identify where {{< param "PRODUCT_NAME" >}} writes received telemetry data.
+- Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
 
 ## Configure an OpenTelemetry Protocol exporter
 
@@ -45,6 +45,7 @@ After an exporter component is defined, you can use other {{< param "PRODUCT_NAM
 Refer to the list of available [Components][] for the full list of `otelcol.exporter` components that you can use to export OpenTelemetry data.
 
 [Components]: ../../get-started/components/
+
 {{< /admonition >}}
 
 To configure an `otelcol.exporter.otlp` component for exporting OpenTelemetry data using OTLP, complete the following steps:
@@ -61,38 +62,38 @@ To configure an `otelcol.exporter.otlp` component for exporting OpenTelemetry da
 
    Replace the following:
 
-   * _`<EXPORTER_LABEL>`_: The label for the component, such as `default`.
+   - _`<EXPORTER_LABEL>`_: The label for the component, such as `default`.
      The label you use must be unique across all `otelcol.exporter.otlp` components in the same configuration file.
-   * _`<HOST>`_: The hostname or IP address of the server to send OTLP requests to.
-   * _`<PORT>`_: The port of the server to send OTLP requests to.
+   - _`<HOST>`_: The hostname or IP address of the server to send OTLP requests to.
+   - _`<PORT>`_: The port of the server to send OTLP requests to.
 
 1. If your server requires basic authentication, complete the following:
 
-    1. Add the following `otelcol.auth.basic` component to your configuration file:
+   1. Add the following `otelcol.auth.basic` component to your configuration file:
 
-       ```alloy
-       otelcol.auth.basic "<BASIC_AUTH_LABEL>" {
-         username = "<USERNAME>"
-         password = "<PASSWORD>"
-       }
-       ```
+      ```alloy
+      otelcol.auth.basic "<BASIC_AUTH_LABEL>" {
+        username = "<USERNAME>"
+        password = "<PASSWORD>"
+      }
+      ```
 
-       Replace the following:
+      Replace the following:
 
-       * _`<BASIC_AUTH_LABEL>`_: The label for the component, such as `default`.
-         The label you use must be unique across all `otelcol.auth.basic` components in the same configuration file.
-       * _`<USERNAME>`_: The basic authentication username.
-       * _`<PASSWORD>`_: The basic authentication password or API key.
+      - _`<BASIC_AUTH_LABEL>`_: The label for the component, such as `default`.
+        The label you use must be unique across all `otelcol.auth.basic` components in the same configuration file.
+      - _`<USERNAME>`_: The basic authentication username.
+      - _`<PASSWORD>`_: The basic authentication password or API key.
 
-    1. Add the following line inside of the `client` block of your `otelcol.exporter.otlp` component:
+   1. Add the following line inside of the `client` block of your `otelcol.exporter.otlp` component:
 
-       ```alloy
-       auth = otelcol.auth.basic.<BASIC_AUTH_LABEL>.handler
-       ```
+      ```alloy
+      auth = otelcol.auth.basic.<BASIC_AUTH_LABEL>.handler
+      ```
 
-       Replace the following:
+      Replace the following:
 
-       * _`<BASIC_AUTH_LABEL>`_: The label for the `otelcol.auth.basic` component.
+      - _`<BASIC_AUTH_LABEL>`_: The label for the `otelcol.auth.basic` component.
 
 1. If you have more than one server to export metrics to, create an `otelcol.exporter.otlp` component for each additional server.
 
@@ -101,6 +102,7 @@ To configure an `otelcol.exporter.otlp` component for exporting OpenTelemetry da
 To send to a server using HTTP/1.1, follow the preceding steps, but use the [`otelcol.exporter.otlphttp`][otelcol.exporter.otlphttp] component instead.
 
 [otelcol.exporter.otlphttp]: ../../reference/components/otelcol/otelcol.exporter.otlphttp/
+
 {{< /admonition >}}
 
 The following example demonstrates configuring `otelcol.exporter.otlp` with authentication and a component that forwards data to it:
@@ -153,6 +155,7 @@ Refer to the list of available [Components][] for the full list of `otelcol.proc
 You can chain processors by having one processor send data to another processor.
 
 [Components]: ../../get-started/components/
+
 {{< /admonition >}}
 
 To configure an `otelcol.processor.batch` component, complete the following steps:
@@ -173,9 +176,9 @@ To configure an `otelcol.processor.batch` component, complete the following step
 
    Replace the following:
 
-   * _`<PROCESSOR_LABEL>`_: The label for the component, such as `default`.
+   - _`<PROCESSOR_LABEL>`_: The label for the component, such as `default`.
      The label you use must be unique across all `otelcol.processor.batch` components in the same configuration file.
-   * _`<EXPORTER_LABEL>`_: The label for your `otelcol.exporter.otlp` component.
+   - _`<EXPORTER_LABEL>`_: The label for your `otelcol.exporter.otlp` component.
 
    1. To disable one of the telemetry types, set the relevant type in the `output` block to the empty list, such as `metrics = []`.
 
@@ -244,9 +247,9 @@ To configure an `otelcol.receiver.otlp` component for receiving OTLP data, compl
 
    Replace the following:
 
-   * _`<LABEL>`_: The label for the component, such as `default`.
+   - _`<LABEL>`_: The label for the component, such as `default`.
      The label you use must be unique across all `otelcol.receiver.otlp` components in the same configuration file.
-   * _`<COMPONENT_INPUT_LIST>`_: A comma-delimited list of component inputs to forward received data to.
+   - _`<COMPONENT_INPUT_LIST>`_: A comma-delimited list of component inputs to forward received data to.
      For example, to send data to a batch processor component, use `otelcol.processor.batch.PROCESSOR_LABEL.input`.
      To send data directly to an exporter component, use `otelcol.exporter.otlp.EXPORTER_LABEL.input`.
 
@@ -260,7 +263,7 @@ To configure an `otelcol.receiver.otlp` component for receiving OTLP data, compl
 
       Replace the following:
 
-      * _`<HOST>`_: A host to listen to traffic on. Use a narrowly scoped listen address whenever possible.
+      - _`<HOST>`_: A host to listen to traffic on. Use a narrowly scoped listen address whenever possible.
         To listen on all network interfaces, replace _`<HOST>`_ with `0.0.0.0`.
 
    1. To allow applications to send OTLP data over HTTP/1.1 on port `4318`, add the following to your `otelcol.receiver.otlp` component.
@@ -273,7 +276,7 @@ To configure an `otelcol.receiver.otlp` component for receiving OTLP data, compl
 
       Replace the following:
 
-      * _`<HOST>`_: The host to listen to traffic on. Use a narrowly scoped listen address whenever possible.
+      - _`<HOST>`_: The host to listen to traffic on. Use a narrowly scoped listen address whenever possible.
         To listen on all network interfaces, replace _`<HOST>`_ with `0.0.0.0`.
 
    1. To disable one of the telemetry types, set the relevant type in the `output` block to the empty list, such as `metrics = []`.
diff --git a/docs/sources/collect/opentelemetry-to-lgtm-stack.md b/docs/sources/collect/opentelemetry-to-lgtm-stack.md
index 6c81534be8..6ac8163346 100644
--- a/docs/sources/collect/opentelemetry-to-lgtm-stack.md
+++ b/docs/sources/collect/opentelemetry-to-lgtm-stack.md
@@ -14,28 +14,28 @@ You can configure {{< param "PRODUCT_NAME" >}} to collect [OpenTelemetry][]-comp
 
 This topic describes how to:
 
-* Configure {{< param "PRODUCT_NAME" >}} to send your data to Loki.
-* Configure {{< param "PRODUCT_NAME" >}} to send your data to Tempo.
-* Configure {{< param "PRODUCT_NAME" >}} to send your data to Mimir or Prometheus Remote Write.
+- Configure {{< param "PRODUCT_NAME" >}} to send your data to Loki.
+- Configure {{< param "PRODUCT_NAME" >}} to send your data to Tempo.
+- Configure {{< param "PRODUCT_NAME" >}} to send your data to Mimir or Prometheus Remote Write.
 
 ## Components used in this topic
 
-* [`loki.write`][loki.write]
-* [`otelcol.auth.basic`][otelcol.auth.basic]
-* [`otelcol.exporter.loki`][otelcol.exporter.loki]
-* [`otelcol.exporter.otlp`][otelcol.exporter.otlp]
-* [`otelcol.exporter.prometheus`][otelcol.exporter.prometheus]
-* [`otelcol.processor.batch`][otelcol.processor.batch]
-* [`otelcol.receiver.otlp`][otelcol.receiver.otlp]
-* [`prometheus.remote_write`][prometheus.remote_write]
+- [`loki.write`][loki.write]
+- [`otelcol.auth.basic`][otelcol.auth.basic]
+- [`otelcol.exporter.loki`][otelcol.exporter.loki]
+- [`otelcol.exporter.otlp`][otelcol.exporter.otlp]
+- [`otelcol.exporter.prometheus`][otelcol.exporter.prometheus]
+- [`otelcol.processor.batch`][otelcol.processor.batch]
+- [`otelcol.receiver.otlp`][otelcol.receiver.otlp]
+- [`prometheus.remote_write`][prometheus.remote_write]
 
 ## Before you begin
 
-* Ensure that you have basic familiarity with instrumenting applications with OpenTelemetry.
-* Have a set of OpenTelemetry applications ready to push telemetry data to {{< param "PRODUCT_NAME" >}}.
-* Identify where {{< param "PRODUCT_NAME" >}} writes received telemetry data.
-* Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
-* Complete the [Collect open telemetry data][] task.
+- Ensure that you have basic familiarity with instrumenting applications with OpenTelemetry.
+- Have a set of OpenTelemetry applications ready to push telemetry data to {{< param "PRODUCT_NAME" >}}.
+- Identify where {{< param "PRODUCT_NAME" >}} writes received telemetry data.
+- Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
+- Complete the [Collect open telemetry data][] task.
 
 ## The pipeline
 
@@ -103,9 +103,9 @@ otelcol.exporter.otlphttp "default" {
 
 Replace the following:
 
-* _`<ACCOUNT ID>`_: Your Grafana Cloud account ID.
-* _`<API TOKEN>`_: Your Grafana Cloud API token.
-* _`<OTLP_ENDPOINT>`_: Your OTLP endpoint.
+- _`<ACCOUNT ID>`_: Your Grafana Cloud account ID.
+- _`<API TOKEN>`_: Your Grafana Cloud API token.
+- _`<OTLP_ENDPOINT>`_: Your OTLP endpoint.
 
 This configuration uses the credentials stored in `otelcol.auth.basic "default"` to authenticate against the Grafana Cloud OTLP endpoints, and you should start to see your data arrive.
 
diff --git a/docs/sources/collect/prometheus-metrics.md b/docs/sources/collect/prometheus-metrics.md
index 153f116e66..a26ecc74ff 100644
--- a/docs/sources/collect/prometheus-metrics.md
+++ b/docs/sources/collect/prometheus-metrics.md
@@ -13,22 +13,22 @@ You can configure {{< param "PRODUCT_NAME" >}} to collect [Prometheus][] metrics
 
 This topic describes how to:
 
-* Configure metrics delivery.
-* Collect metrics from Kubernetes Pods.
+- Configure metrics delivery.
+- Collect metrics from Kubernetes Pods.
 
 ## Components used in this topic
 
-* [`discovery.kubernetes`][discovery.kubernetes]
-* [`prometheus.remote_write`][prometheus.remote_write]
-* [`prometheus.scrape`][prometheus.scrape]
+- [`discovery.kubernetes`][discovery.kubernetes]
+- [`prometheus.remote_write`][prometheus.remote_write]
+- [`prometheus.scrape`][prometheus.scrape]
 
 ## Before you begin
 
-* Ensure that you have basic familiarity with instrumenting applications with Prometheus.
-* Have a set of Prometheus exports or applications exposing Prometheus metrics that you want to collect metrics from.
-* Identify where to write collected metrics.
+- Ensure that you have basic familiarity with instrumenting applications with Prometheus.
+- Have a set of Prometheus exports or applications exposing Prometheus metrics that you want to collect metrics from.
+- Identify where to write collected metrics.
   Metrics can be written to Prometheus or Prometheus-compatible endpoints such as Grafana Mimir, Grafana Cloud, or Grafana Enterprise Metrics.
-* Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
+- Be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
 
 ## Configure metrics delivery
 
@@ -51,9 +51,9 @@ To configure a `prometheus.remote_write` component for metrics delivery, complet
 
    Replace the following:
 
-   * _`<LABEL>`_: The label for the component, such as `default`.
+   - _`<LABEL>`_: The label for the component, such as `default`.
      The label you use must be unique across all `prometheus.remote_write` components in the same configuration file.
-   * _`<PROMETHEUS_URL>`_ The full URL of the Prometheus-compatible endpoint where metrics are sent, such as `https://prometheus-us-central1.grafana.net/api/v1/write` for Prometheus or `https://mimir-us-central1.grafana.net/api/v1/push/` for Mimir. The endpoint URL depends on the database you use.
+   - _`<PROMETHEUS_URL>`_ The full URL of the Prometheus-compatible endpoint where metrics are sent, such as `https://prometheus-us-central1.grafana.net/api/v1/write` for Prometheus or `https://mimir-us-central1.grafana.net/api/v1/push/` for Mimir. The endpoint URL depends on the database you use.
 
 1. If your endpoint requires basic authentication, paste the following inside the `endpoint` block.
 
@@ -66,8 +66,8 @@ To configure a `prometheus.remote_write` component for metrics delivery, complet
 
    Replace the following:
 
-   * _`<USERNAME>`_: The basic authentication username.
-   * _`<PASSWORD>`_: The basic authentication password or API key.
+   - _`<USERNAME>`_: The basic authentication username.
+   - _`<PASSWORD>`_: The basic authentication password or API key.
 
 1. If you have more than one endpoint to write metrics to, repeat the `endpoint` block for additional endpoints.
 
@@ -115,86 +115,86 @@ To collect metrics from Kubernetes Pods, complete the following steps:
 
 1. Discover Kubernetes Pods:
 
-    1. Add the following `discovery.kubernetes` component to your configuration file to discover every Pod in the cluster across all Namespaces.
+   1. Add the following `discovery.kubernetes` component to your configuration file to discover every Pod in the cluster across all Namespaces.
 
-       ```alloy
-       discovery.kubernetes "<DISCOVERY_LABEL>" {
-         role = "pod"
-       }
-       ```
+      ```alloy
+      discovery.kubernetes "<DISCOVERY_LABEL>" {
+        role = "pod"
+      }
+      ```
 
-       Replace the following
+      Replace the following
 
-       * _`<DISCOVERY_LABEL>`_: The label for the component, such as `pods`.
-         The label you use must be unique across all `discovery.kubernetes` components in the same configuration file.
+      - _`<DISCOVERY_LABEL>`_: The label for the component, such as `pods`.
+        The label you use must be unique across all `discovery.kubernetes` components in the same configuration file.
 
-       This generates one Prometheus target for every exposed port on every discovered Pod.
+      This generates one Prometheus target for every exposed port on every discovered Pod.
 
-    1. To limit the Namespaces that Pods are discovered in, add the following block inside the `discovery.kubernetes` component.
+   1. To limit the Namespaces that Pods are discovered in, add the following block inside the `discovery.kubernetes` component.
 
-       ```alloy
-       namespaces {
-         own_namespace = true
-         names         = [<NAMESPACE_NAMES>]
-       }
-       ```
+      ```alloy
+      namespaces {
+        own_namespace = true
+        names         = [<NAMESPACE_NAMES>]
+      }
+      ```
 
-       Replace the following:
+      Replace the following:
 
-       * _`<NAMESPACE_NAMES>`_: A comma-delimited list of strings representing Namespaces to search.
-         Each string must be wrapped in double quotes. For example, `"default","kube-system"`.
+      - _`<NAMESPACE_NAMES>`_: A comma-delimited list of strings representing Namespaces to search.
+        Each string must be wrapped in double quotes. For example, `"default","kube-system"`.
 
-       If you don't want to search for Pods in the Namespace {{< param "PRODUCT_NAME" >}} is running in, set `own_namespace` to `false`.
+      If you don't want to search for Pods in the Namespace {{< param "PRODUCT_NAME" >}} is running in, set `own_namespace` to `false`.
 
-    1. To use a field selector to limit the number of discovered Pods, add the following block inside the `discovery.kubernetes` component.
+   1. To use a field selector to limit the number of discovered Pods, add the following block inside the `discovery.kubernetes` component.
 
-       ```alloy
-       selectors {
-         role  = "pod"
-         field = "<FIELD_SELECTOR>"
-       }
-       ```
+      ```alloy
+      selectors {
+        role  = "pod"
+        field = "<FIELD_SELECTOR>"
+      }
+      ```
 
-       Replace the following:
+      Replace the following:
 
-       * _`<FIELD_SELECTOR>`_: The Kubernetes field selector to use, such as `metadata.name=my-service`.
-         For more information on field selectors, refer to the Kubernetes documentation on [Field Selectors][].
+      - _`<FIELD_SELECTOR>`_: The Kubernetes field selector to use, such as `metadata.name=my-service`.
+        For more information on field selectors, refer to the Kubernetes documentation on [Field Selectors][].
 
-       Create additional `selectors` blocks for each field selector you want to apply.
+      Create additional `selectors` blocks for each field selector you want to apply.
 
-    1. To use a label selector to limit the number of discovered Pods, add the following block inside the `discovery.kubernetes` component.
+   1. To use a label selector to limit the number of discovered Pods, add the following block inside the `discovery.kubernetes` component.
 
-       ```alloy
-       selectors {
-         role  = "pod"
-         label = "LABEL_SELECTOR"
-       }
-       ```
+      ```alloy
+      selectors {
+        role  = "pod"
+        label = "LABEL_SELECTOR"
+      }
+      ```
 
-       Replace the following:
+      Replace the following:
 
-       * _`<LABEL_SELECTOR>`_: The Kubernetes label selector, such as `environment in (production, qa)`.
-         For more information on label selectors, refer to the Kubernetes documentation on [Labels and Selectors][].
+      - _`<LABEL_SELECTOR>`_: The Kubernetes label selector, such as `environment in (production, qa)`.
+        For more information on label selectors, refer to the Kubernetes documentation on [Labels and Selectors][].
 
-       Create additional `selectors` blocks for each label selector you want to apply.
+      Create additional `selectors` blocks for each label selector you want to apply.
 
 1. Collect metrics from discovered Pods:
 
-    1. Add the following `prometheus.scrape` component to your configuration file.
+   1. Add the following `prometheus.scrape` component to your configuration file.
 
-       ```alloy
-       prometheus.scrape "<SCRAPE_LABEL>" {
-         targets    = discovery.kubernetes.<DISCOVERY_LABEL>.targets
-         forward_to = [prometheus.remote_write.<REMOTE_WRITE_LABEL>.receiver]
-       }
-       ```
+      ```alloy
+      prometheus.scrape "<SCRAPE_LABEL>" {
+        targets    = discovery.kubernetes.<DISCOVERY_LABEL>.targets
+        forward_to = [prometheus.remote_write.<REMOTE_WRITE_LABEL>.receiver]
+      }
+      ```
 
-       Replace the following:
+      Replace the following:
 
-       * _`<SCRAPE_LABEL>`_: The label for the component, such as `pods`.
-         The label you use must be unique across all `prometheus.scrape` components in the same configuration file.
-       * _`<DISCOVERY_LABEL>`_: The label for the `discovery.kubernetes` component.
-       * _`<REMOTE_WRITE_LABEL>`_: The label for your `prometheus.remote_write` component.
+      - _`<SCRAPE_LABEL>`_: The label for the component, such as `pods`.
+        The label you use must be unique across all `prometheus.scrape` components in the same configuration file.
+      - _`<DISCOVERY_LABEL>`_: The label for the `discovery.kubernetes` component.
+      - _`<REMOTE_WRITE_LABEL>`_: The label for your `prometheus.remote_write` component.
 
 The following example demonstrates configuring {{< param "PRODUCT_NAME" >}} to collect metrics from running production Kubernetes Pods in the `default` Namespace.
 
@@ -241,86 +241,86 @@ To collect metrics from Kubernetes Services, complete the following steps.
 
 1. Discover Kubernetes Services:
 
-    1. Add the following `discovery.kubernetes` component to your configuration file to discover every Services in the cluster across all Namespaces.
+   1. Add the following `discovery.kubernetes` component to your configuration file to discover every Services in the cluster across all Namespaces.
 
-       ```alloy
-       discovery.kubernetes "<DISCOVERY_LABEL>" {
-         role = "service"
-       }
-       ```
+      ```alloy
+      discovery.kubernetes "<DISCOVERY_LABEL>" {
+        role = "service"
+      }
+      ```
 
-       Replace the following:
+      Replace the following:
 
-       * _`<DISCOVERY_LABEL>`_: A label for the component, such as `services`.
-         The label you use must be unique across all `discovery.kubernetes` components in the same configuration file.
+      - _`<DISCOVERY_LABEL>`_: A label for the component, such as `services`.
+        The label you use must be unique across all `discovery.kubernetes` components in the same configuration file.
 
-       This generates one Prometheus target for every exposed port on every discovered Service.
+      This generates one Prometheus target for every exposed port on every discovered Service.
 
-    1. To limit the Namespaces that Services are discovered in, add the following block inside the `discovery.kubernetes` component.
+   1. To limit the Namespaces that Services are discovered in, add the following block inside the `discovery.kubernetes` component.
 
-       ```alloy
-       namespaces {
-         own_namespace = true
-         names         = [<NAMESPACE_NAMES>]
-       }
-       ```
+      ```alloy
+      namespaces {
+        own_namespace = true
+        names         = [<NAMESPACE_NAMES>]
+      }
+      ```
 
-       Replace the following:
+      Replace the following:
 
-       * _`<NAMESPACE_NAMES>`_: A comma-delimited list of strings representing Namespaces to search.
-         Each string must be wrapped in double quotes. For example, `"default","kube-system"`.
+      - _`<NAMESPACE_NAMES>`_: A comma-delimited list of strings representing Namespaces to search.
+        Each string must be wrapped in double quotes. For example, `"default","kube-system"`.
 
-       If you don't want to search for Services in the Namespace {{< param "PRODUCT_NAME" >}} is running in, set `own_namespace` to `false`.
+      If you don't want to search for Services in the Namespace {{< param "PRODUCT_NAME" >}} is running in, set `own_namespace` to `false`.
 
-    1. To use a field selector to limit the number of discovered Services, add the following block inside the `discovery.kubernetes` component.
+   1. To use a field selector to limit the number of discovered Services, add the following block inside the `discovery.kubernetes` component.
 
-       ```alloy
-       selectors {
-         role  = "service"
-         field = "<FIELD_SELECTOR>"
-       }
-       ```
+      ```alloy
+      selectors {
+        role  = "service"
+        field = "<FIELD_SELECTOR>"
+      }
+      ```
 
-       Replace the following:
+      Replace the following:
 
-       * _`<FIELD_SELECTOR>`_: The Kubernetes field selector, such as `metadata.name=my-service`.
-         For more information on field selectors, refer to the Kubernetes documentation on [Field Selectors][].
+      - _`<FIELD_SELECTOR>`_: The Kubernetes field selector, such as `metadata.name=my-service`.
+        For more information on field selectors, refer to the Kubernetes documentation on [Field Selectors][].
 
-       Create additional `selectors` blocks for each field selector you want to apply.
+      Create additional `selectors` blocks for each field selector you want to apply.
 
-    1. To use a label selector to limit the number of discovered Services, add the following block inside the `discovery.kubernetes` component.
+   1. To use a label selector to limit the number of discovered Services, add the following block inside the `discovery.kubernetes` component.
 
-       ```alloy
-       selectors {
-         role  = "service"
-         label = "<LABEL_SELECTOR>"
-       }
-       ```
+      ```alloy
+      selectors {
+        role  = "service"
+        label = "<LABEL_SELECTOR>"
+      }
+      ```
 
-       Replace the following:
+      Replace the following:
 
-       * _`<LABEL_SELECTOR>`_: The Kubernetes label selector, such as `environment in (production, qa)`.
-         For more information on label selectors, refer to the Kubernetes documentation on [Labels and Selectors][].
+      - _`<LABEL_SELECTOR>`_: The Kubernetes label selector, such as `environment in (production, qa)`.
+        For more information on label selectors, refer to the Kubernetes documentation on [Labels and Selectors][].
 
-       Create additional `selectors` blocks for each label selector you want to apply.
+      Create additional `selectors` blocks for each label selector you want to apply.
 
 1. Collect metrics from discovered Services:
 
-    1. Add the following `prometheus.scrape` component to your configuration file.
+   1. Add the following `prometheus.scrape` component to your configuration file.
 
-       ```alloy
-       prometheus.scrape "<SCRAPE_LABEL>" {
-         targets    = discovery.kubernetes.<DISCOVERY_LABEL>.targets
-         forward_to = [prometheus.remote_write.<REMOTE_WRITE_LABEL>.receiver]
-       }
-       ```
+      ```alloy
+      prometheus.scrape "<SCRAPE_LABEL>" {
+        targets    = discovery.kubernetes.<DISCOVERY_LABEL>.targets
+        forward_to = [prometheus.remote_write.<REMOTE_WRITE_LABEL>.receiver]
+      }
+      ```
 
-       Replace the following:
+      Replace the following:
 
-       * _`<SCRAPE_LABEL>`_: The label for the component, such as `services`.
-         The label you use must be unique across all `prometeus.scrape` components in the same configuration file.
-       * _`<DISCOVERY_LABEL>`_: The label for the `discovery.kubernetes` component.
-       * _`<REMOTE_WRITE_LABEL>`_: The label for your `prometheus.remote_write` component.
+      - _`<SCRAPE_LABEL>`_: The label for the component, such as `services`.
+        The label you use must be unique across all `prometeus.scrape` components in the same configuration file.
+      - _`<DISCOVERY_LABEL>`_: The label for the `discovery.kubernetes` component.
+      - _`<REMOTE_WRITE_LABEL>`_: The label for your `prometheus.remote_write` component.
 
 The following example demonstrates configuring {{< param "PRODUCT_NAME" >}} to collect metrics from running production Kubernetes Services in the `default` Namespace.
 
@@ -373,20 +373,20 @@ To collect metrics from a custom set of targets, complete the following steps.
 
    Replace the following:
 
-   * _`<SCRAPE_LABEL>`: The label for the component, such as `custom_targets`.
+   - \_`<SCRAPE_LABEL>`: The label for the component, such as `custom_targets`.
      The label you use must be unique across all `prometheus.scrape` components in the same configuration file.
-   * _`<TARGET_LIST>`_: A comma-delimited list of [Objects][] denoting the Prometheus target.
+   - _`<TARGET_LIST>`_: A comma-delimited list of [Objects][] denoting the Prometheus target.
      Each object must conform to the following rules:
 
-     * There must be an `__address__` key denoting the `HOST:PORT` of the target to collect metrics from.
-     * To explicitly specify which protocol to use, set the `__scheme__` key to `"http"` or `"https"`.
+     - There must be an `__address__` key denoting the `HOST:PORT` of the target to collect metrics from.
+     - To explicitly specify which protocol to use, set the `__scheme__` key to `"http"` or `"https"`.
        If the `__scheme__` key isn't provided, the protocol to use is inherited by the settings of the `prometheus.scrape` component. The default is `"http"`.
-     * To explicitly specify which HTTP path to collect metrics from, set the `__metrics_path__` key to the HTTP path to use.
+     - To explicitly specify which HTTP path to collect metrics from, set the `__metrics_path__` key to the HTTP path to use.
        If the `__metrics_path__` key isn't provided, the path to use is inherited by the settings of the `prometheus.scrape` component. The default is `"/metrics"`.
-     * Add additional keys as desired to inject extra labels to collected metrics.
+     - Add additional keys as desired to inject extra labels to collected metrics.
        Any label starting with two underscores (`__`) is dropped prior to scraping.
 
-   * _`<REMOTE_WRITE_LABEL>`_: The label for your `prometheus.remote_write` component.
+   - _`<REMOTE_WRITE_LABEL>`_: The label for your `prometheus.remote_write` component.
 
 The following example demonstrates configuring `prometheus.scrape` to collect metrics from a custom set of endpoints.
 
diff --git a/docs/sources/configure/_index.md b/docs/sources/configure/_index.md
index a74ac9cf4f..4945842746 100644
--- a/docs/sources/configure/_index.md
+++ b/docs/sources/configure/_index.md
@@ -13,9 +13,9 @@ weight: 90
 You can configure {{< param "PRODUCT_NAME" >}} after it's [installed][].
 The default configuration file location for {{< param "PRODUCT_NAME" >}} is:
 
-* Linux: `/etc/alloy/config.alloy`
-* macOS: `$(brew --prefix)/etc/alloy/config.alloy`
-* Windows: `%ProgramFiles%\GrafanaLabs\Alloy\config.alloy`
+- Linux: `/etc/alloy/config.alloy`
+- macOS: `$(brew --prefix)/etc/alloy/config.alloy`
+- Windows: `%ProgramFiles%\GrafanaLabs\Alloy\config.alloy`
 
 This section includes information that helps you configure {{< param "PRODUCT_NAME" >}}.
 
diff --git a/docs/sources/configure/kubernetes.md b/docs/sources/configure/kubernetes.md
index 4dcb08e1e4..2c367fbbbd 100644
--- a/docs/sources/configure/kubernetes.md
+++ b/docs/sources/configure/kubernetes.md
@@ -44,9 +44,9 @@ To modify {{< param "PRODUCT_NAME" >}}'s Helm chart configuration, perform the f
 
    Replace the following:
 
-   * _`<NAMESPACE>`_: The namespace you used for your {{< param "PRODUCT_NAME" >}} installation.
-   * _`<RELEASE_NAME>`_: The name you used for your {{< param "PRODUCT_NAME" >}} installation.
-   * _`<VALUES_PATH>`_: The path to your copy of `values.yaml` to use.
+   - _`<NAMESPACE>`_: The namespace you used for your {{< param "PRODUCT_NAME" >}} installation.
+   - _`<RELEASE_NAME>`_: The name you used for your {{< param "PRODUCT_NAME" >}} installation.
+   - _`<VALUES_PATH>`_: The path to your copy of `values.yaml` to use.
 
 ## Kustomize considerations
 
@@ -97,9 +97,9 @@ Use this method if you prefer to embed your {{< param "PRODUCT_NAME" >}} configu
 
    Replace the following:
 
-   * _`<NAMESPACE>`_: The namespace you used for your {{< param "PRODUCT_NAME" >}} installation.
-   * _`<RELEASE_NAME>`_: The name you used for your {{< param "PRODUCT_NAME" >}} installation.
-   * _`<VALUES_PATH>`_: The path to your copy of `values.yaml` to use.
+   - _`<NAMESPACE>`_: The namespace you used for your {{< param "PRODUCT_NAME" >}} installation.
+   - _`<RELEASE_NAME>`_: The name you used for your {{< param "PRODUCT_NAME" >}} installation.
+   - _`<VALUES_PATH>`_: The path to your copy of `values.yaml` to use.
 
 ### Method 2: Create a separate ConfigMap from a file
 
@@ -123,7 +123,7 @@ Use this method if you prefer to write your {{< param "PRODUCT_NAME" >}} configu
 
    Replace the following:
 
-   * _`<NAMESPACE>`_: The namespace you used for your {{< param "PRODUCT_NAME" >}} installation.
+   - _`<NAMESPACE>`_: The namespace you used for your {{< param "PRODUCT_NAME" >}} installation.
 
 1. Modify Helm Chart's configuration in your `values.yaml` to use the existing ConfigMap:
 
@@ -143,9 +143,9 @@ Use this method if you prefer to write your {{< param "PRODUCT_NAME" >}} configu
 
    Replace the following:
 
-   * _`<NAMESPACE>`_: The namespace you used for your {{< param "PRODUCT_NAME" >}} installation.
-   * _`<RELEASE_NAME>`_: The name you used for your {{< param "PRODUCT_NAME" >}} installation.
-   * _`<VALUES_PATH>`_: The path to your copy of `values.yaml` to use.
+   - _`<NAMESPACE>`_: The namespace you used for your {{< param "PRODUCT_NAME" >}} installation.
+   - _`<RELEASE_NAME>`_: The name you used for your {{< param "PRODUCT_NAME" >}} installation.
+   - _`<VALUES_PATH>`_: The path to your copy of `values.yaml` to use.
 
 [values.yaml]: https://raw.githubusercontent.com/grafana/alloy/main/operations/helm/charts/alloy/values.yaml
 [Helm chart]: https://github.com/grafana/alloy/tree/main/operations/helm/charts/alloy
diff --git a/docs/sources/configure/linux.md b/docs/sources/configure/linux.md
index e05fff9d35..489e890cec 100644
--- a/docs/sources/configure/linux.md
+++ b/docs/sources/configure/linux.md
@@ -24,8 +24,8 @@ To change the configuration file used by the service, perform the following step
 
 1. Edit the environment file for the service:
 
-   * Debian or Ubuntu: edit `/etc/default/alloy`
-   * RHEL/Fedora or SUSE/openSUSE: edit `/etc/sysconfig/alloy`
+   - Debian or Ubuntu: edit `/etc/default/alloy`
+   - RHEL/Fedora or SUSE/openSUSE: edit `/etc/sysconfig/alloy`
 
 1. Change the contents of the `CONFIG_FILE` environment variable to point at the new configuration file.
 
@@ -39,14 +39,14 @@ To change the configuration file used by the service, perform the following step
 
 By default, the {{< param "PRODUCT_NAME" >}} service launches with the [run][] command, passing the following flags:
 
-* `--storage.path=/var/lib/alloy`
+- `--storage.path=/var/lib/alloy`
 
 To pass additional command-line flags to the {{< param "PRODUCT_NAME" >}} binary, perform the following steps:
 
 1. Edit the environment file for the service:
 
-   * Debian-based systems: edit `/etc/default/alloy`
-   * RedHat or SUSE-based systems: edit `/etc/sysconfig/alloy`
+   - Debian-based systems: edit `/etc/default/alloy`
+   - RedHat or SUSE-based systems: edit `/etc/sysconfig/alloy`
 
 1. Change the contents of the `CUSTOM_ARGS` environment variable to specify
    command-line flags to pass.
@@ -77,10 +77,10 @@ To expose the UI to other machines, complete the following steps:
 
    Replace the following:
 
-   * _`<LISTEN_ADDR>`_: An IP address which other machines on the network have access to.
+   - _`<LISTEN_ADDR>`_: An IP address which other machines on the network have access to.
      For example, the IP address of the machine {{< param "PRODUCT_NAME" >}} is running on.
 
      To listen on all interfaces, replace _`<LISTEN_ADDR>`_ with `0.0.0.0`.
 
-[run]:../../reference/cli/run/
+[run]: ../../reference/cli/run/
 [UI]: ../../troubleshoot/debug/#alloy-ui
diff --git a/docs/sources/configure/macos.md b/docs/sources/configure/macos.md
index 206825cef4..0f78468354 100644
--- a/docs/sources/configure/macos.md
+++ b/docs/sources/configure/macos.md
@@ -38,9 +38,9 @@ To customize the {{< param "PRODUCT_NAME" >}} service on macOS, perform the foll
 
 1. Modify the `service` section as desired to change things such as:
 
-   * The configuration file used by {{< param "PRODUCT_NAME" >}}.
-   * Flags passed to the {{< param "PRODUCT_NAME" >}} binary.
-   * Location of log files.
+   - The configuration file used by {{< param "PRODUCT_NAME" >}}.
+   - Flags passed to the {{< param "PRODUCT_NAME" >}} binary.
+   - Location of log files.
 
 1. Save the modified file.
 
diff --git a/docs/sources/configure/nonroot.md b/docs/sources/configure/nonroot.md
index 5218fd26b8..fd990d4ab9 100644
--- a/docs/sources/configure/nonroot.md
+++ b/docs/sources/configure/nonroot.md
@@ -12,8 +12,8 @@ weight: 600
 
 The [{{< param "PRODUCT_NAME" >}} Docker image][image] contains two users:
 
-* A `root` user.
-* A non-root user named `alloy` with UID `473` and gid `473`.
+- A `root` user.
+- A non-root user named `alloy` with UID `473` and gid `473`.
 
 By default, the `alloy` binary runs as `root`. This is because some {{< param "PRODUCT_NAME" >}} components like [beyla.ebpf][] require root permissions.
 
@@ -25,6 +25,7 @@ You can configure a non-root user when you deploy {{< param "PRODUCT_NAME" >}} i
 Running {{< param "PRODUCT_NAME" >}} as a non-root user won't work if you are using components like [beyla.ebpf][] that require root rights.
 
 [beyla.ebpf]: ../../reference/components/beyla/beyla.ebpf/
+
 {{< /admonition >}}
 
 To run {{< param "PRODUCT_NAME" >}} as a non-root user, configure a [security context][] for the {{< param "PRODUCT_NAME" >}} container. If you are using the [Grafana Helm chart][] you can add the following snippet to `values.yaml`:
diff --git a/docs/sources/configure/windows.md b/docs/sources/configure/windows.md
index 08148156ac..2c175ec9da 100644
--- a/docs/sources/configure/windows.md
+++ b/docs/sources/configure/windows.md
@@ -30,9 +30,9 @@ To configure {{< param "PRODUCT_NAME" >}} on Windows, perform the following step
 
 By default, the {{< param "PRODUCT_NAME" >}} service will launch and pass the following arguments to the {{< param "PRODUCT_NAME" >}} binary:
 
-* `run`
-* `%PROGRAMFILES%\GrafanaLabs\Alloy\config.alloy`
-* `--storage.path=%PROGRAMDATA%\GrafanaLabs\Alloy\data`
+- `run`
+- `%PROGRAMFILES%\GrafanaLabs\Alloy\config.alloy`
+- `--storage.path=%PROGRAMDATA%\GrafanaLabs\Alloy\data`
 
 To change the set of command-line arguments passed to the {{< param "PRODUCT_NAME" >}} binary, perform the following steps:
 
@@ -44,7 +44,7 @@ To change the set of command-line arguments passed to the {{< param "PRODUCT_NAM
 
 1. Navigate to the key at the path `HKEY_LOCAL_MACHINE\SOFTWARE\GrafanaLabs\Alloy`.
 
-1. Double-click on the value called **Arguments***.
+1. Double-click on the value called **Arguments\***.
 
 1. In the dialog box, enter the arguments to pass to the {{< param "PRODUCT_NAME" >}} binary.
    Make sure that each argument is on its own line.
@@ -79,7 +79,7 @@ To expose the UI to other machines, complete the following steps:
 
    Replace the following:
 
-   * _`<LISTEN_ADDR>`_: An IP address which other machines on the network have access to.
+   - _`<LISTEN_ADDR>`_: An IP address which other machines on the network have access to.
      For example, the IP address of the machine {{< param "PRODUCT_NAME" >}} is running on.
 
      To listen on all interfaces, replace _`<LISTEN_ADDR>`_ with `0.0.0.0`.
diff --git a/docs/sources/data-collection.md b/docs/sources/data-collection.md
index cbda9effce..f885b6cbae 100644
--- a/docs/sources/data-collection.md
+++ b/docs/sources/data-collection.md
@@ -15,14 +15,14 @@ Statistics help Grafana better understand how {{< param "PRODUCT_NAME" >}} is us
 
 The usage information includes the following details:
 
-* A randomly generated, anonymous, unique ID (UUID).
-* Timestamp of when the UID was first generated.
-* Timestamp of when the report was created (by default, every four hours).
-* The version of {{< param "PRODUCT_NAME" >}}.
-* The operating system {{< param "PRODUCT_NAME" >}} is running on.
-* The system architecture {{< param "PRODUCT_NAME" >}} is running on.
-* A list of enabled [components][]
-* The method used to deploy {{< param "PRODUCT_NAME" >}}, for example Docker, Helm, or a Linux package.
+- A randomly generated, anonymous, unique ID (UUID).
+- Timestamp of when the UID was first generated.
+- Timestamp of when the report was created (by default, every four hours).
+- The version of {{< param "PRODUCT_NAME" >}}.
+- The operating system {{< param "PRODUCT_NAME" >}} is running on.
+- The system architecture {{< param "PRODUCT_NAME" >}} is running on.
+- A list of enabled [components][]
+- The method used to deploy {{< param "PRODUCT_NAME" >}}, for example Docker, Helm, or a Linux package.
 
 This list may change over time.
 All newly reported data is documented in the CHANGELOG.
@@ -34,6 +34,7 @@ You can use the `--disable-reporting` [command line flag][] to disable the repor
 ### Opt-out of data collection with Ansible
 
 Example:
+
 ```
 - name: Install Alloy
   hosts: all
diff --git a/docs/sources/get-started/community_components.md b/docs/sources/get-started/community_components.md
index 1051e48ff7..a3664dbe2f 100644
--- a/docs/sources/get-started/community_components.md
+++ b/docs/sources/get-started/community_components.md
@@ -7,16 +7,16 @@ weight: 100
 
 # Community components
 
-__Community components__ are [components][Components] implemented and maintained by the community.
+**Community components** are [components][Components] implemented and maintained by the community.
 
 While Grafana doesn't offer commercial support for these components, they still undergo acceptance and review by the {{< param "PRODUCT_NAME" >}} development team before being added to the repository.
 
 To use these community components, you must explicitly pass the `--feature.community-components.enabled` flag to the `run` command.
 
-__Community components__ don't have a stability level. They aren't covered by the [backward compatibility strategy][backward-compatibility].
+**Community components** don't have a stability level. They aren't covered by the [backward compatibility strategy][backward-compatibility].
 
 {{< admonition type="warning" >}}
-__Community components__ without a maintainer may be disabled or removed if the components prevent or block the development of {{< param "PRODUCT_NAME" >}}.
+**Community components** without a maintainer may be disabled or removed if the components prevent or block the development of {{< param "PRODUCT_NAME" >}}.
 {{< /admonition >}}
 
 [Components]: ../components/
diff --git a/docs/sources/get-started/component_controller.md b/docs/sources/get-started/component_controller.md
index 3c2afc3207..3488b6053b 100644
--- a/docs/sources/get-started/component_controller.md
+++ b/docs/sources/get-started/component_controller.md
@@ -13,10 +13,10 @@ The _component controller_ is the core part of {{< param "PRODUCT_NAME" >}} whic
 
 The component controller is responsible for:
 
-* Reading and validating the configuration file.
-* Managing the lifecycle of defined components.
-* Evaluating the arguments used to configure components.
-* Reporting the health of defined components.
+- Reading and validating the configuration file.
+- Managing the lifecycle of defined components.
+- Evaluating the arguments used to configure components.
+- Reporting the health of defined components.
 
 ## Component graph
 
diff --git a/docs/sources/get-started/components.md b/docs/sources/get-started/components.md
index 0e7888a752..6cd394f7d1 100644
--- a/docs/sources/get-started/components.md
+++ b/docs/sources/get-started/components.md
@@ -14,8 +14,8 @@ Each component handles a single task, such as retrieving secrets or collecting P
 
 Components are composed of the following:
 
-* **Arguments:** Settings that configure a component.
-* **Exports:** Named values that a component exposes to other components.
+- **Arguments:** Settings that configure a component.
+- **Exports:** Named values that a component exposes to other components.
 
 Each component has a name that describes what that component is responsible for.
 For example, the `local.file` component is responsible for retrieving the contents of files on disk.
diff --git a/docs/sources/get-started/configuration-syntax/_index.md b/docs/sources/get-started/configuration-syntax/_index.md
index d5240015b8..e8e423f4f4 100644
--- a/docs/sources/get-started/configuration-syntax/_index.md
+++ b/docs/sources/get-started/configuration-syntax/_index.md
@@ -82,9 +82,9 @@ prometheus.remote_write "default" {
 
 The preceding example has two blocks:
 
-* `prometheus.remote_write "default"`: A labeled block which instantiates a `prometheus.remote_write` component.
+- `prometheus.remote_write "default"`: A labeled block which instantiates a `prometheus.remote_write` component.
   The label is the string `"default"`.
-* `endpoint`: An unlabeled block inside the component that configures an endpoint to send metrics to.
+- `endpoint`: An unlabeled block inside the component that configures an endpoint to send metrics to.
   This block sets the `url` attribute to specify the endpoint.
 
 ## Attributes
@@ -104,10 +104,10 @@ You use expressions to compute the value of an attribute.
 The simplest expressions are constant values like `"debug"`, `32`, or `[1, 2, 3, 4]`.
 The {{< param "PRODUCT_NAME" >}} syntax supports complex expressions, for example:
 
-* Referencing the exports of components: `local.file.password_file.content`
-* Mathematical operations: `1 + 2`, `3 * 4`, `(5 * 6) + (7 + 8)`
-* Equality checks: `local.file.file_a.content == local.file.file_b.content`
-* Calling functions from {{< param "PRODUCT_NAME" >}}'s standard library: `sys.env("HOME")` retrieves the value of the `HOME` environment variable.
+- Referencing the exports of components: `local.file.password_file.content`
+- Mathematical operations: `1 + 2`, `3 * 4`, `(5 * 6) + (7 + 8)`
+- Equality checks: `local.file.file_a.content == local.file.file_b.content`
+- Calling functions from {{< param "PRODUCT_NAME" >}}'s standard library: `sys.env("HOME")` retrieves the value of the `HOME` environment variable.
 
 You can use expressions for any attribute inside a component definition.
 
@@ -121,25 +121,25 @@ label (for example, `password_file`), and export name (for example, `content`),
 
 {{< param "PRODUCT_NAME" >}} is:
 
-* _Fast_: The configuration language is fast, so the component controller can quickly evaluate changes.
-* _Simple_: The configuration language is easy to read and write to minimize the learning curve.
-* _Easy to debug_: The configuration language gives detailed information when there's a mistake in the configuration file.
+- _Fast_: The configuration language is fast, so the component controller can quickly evaluate changes.
+- _Simple_: The configuration language is easy to read and write to minimize the learning curve.
+- _Easy to debug_: The configuration language gives detailed information when there's a mistake in the configuration file.
 
 The {{< param "PRODUCT_NAME" >}} configuration syntax is a distinct language with custom syntax and features, such as first-class functions.
 
-* Blocks are a group of related settings and usually represent creating a component.
+- Blocks are a group of related settings and usually represent creating a component.
   Blocks have a name that consists of zero or more identifiers separated by `.`, an optional user label, and a body containing attributes and nested blocks.
-* Attributes appear within blocks and assign a value to a name.
-* Expressions represent a value, either literally or by referencing and combining other values.
+- Attributes appear within blocks and assign a value to a name.
+- Expressions represent a value, either literally or by referencing and combining other values.
   You use expressions to compute a value for an attribute.
 
 ## Tooling
 
 You can use one or all of the following tools to help you write {{< param "PRODUCT_NAME" >}} configuration files.
 
-* Editor support for:
-  * [VSCode](https://github.com/grafana/vscode-alloy)
-  * [Vim/Neovim](https://github.com/grafana/vim-alloy)
-* Code formatting using the [`alloy fmt` command][fmt]
+- Editor support for:
+  - [VSCode](https://github.com/grafana/vscode-alloy)
+  - [Vim/Neovim](https://github.com/grafana/vim-alloy)
+- Code formatting using the [`alloy fmt` command][fmt]
 
 [fmt]: ../../reference/cli/fmt/
diff --git a/docs/sources/get-started/configuration-syntax/components.md b/docs/sources/get-started/configuration-syntax/components.md
index 479ee60b4d..c279fc0501 100644
--- a/docs/sources/get-started/configuration-syntax/components.md
+++ b/docs/sources/get-started/configuration-syntax/components.md
@@ -23,11 +23,11 @@ All components are identified by their name, describing what the component is re
 
 Most user interactions with components center around two basic concepts, _arguments_ and _exports_.
 
-* _Arguments_ are settings that modify the behavior of a component.
+- _Arguments_ are settings that modify the behavior of a component.
   They can be any number of attributes or nested unlabeled blocks, some required and some optional.
   Any optional arguments that aren't set take on their default values.
 
-* _Exports_ are zero or more output values that other components can refer to and can be of any {{< param "PRODUCT_NAME" >}} type.
+- _Exports_ are zero or more output values that other components can refer to and can be of any {{< param "PRODUCT_NAME" >}} type.
 
 The following block defines a `local.file` component labeled "targets".
 The `local.file.targets` component exposes the file `content` as a string in its exports.
diff --git a/docs/sources/get-started/configuration-syntax/expressions/function_calls.md b/docs/sources/get-started/configuration-syntax/expressions/function_calls.md
index f80995ac08..bb3fcb3e07 100644
--- a/docs/sources/get-started/configuration-syntax/expressions/function_calls.md
+++ b/docs/sources/get-started/configuration-syntax/expressions/function_calls.md
@@ -27,4 +27,4 @@ sys.env("HOME")
 encoding.from_json(local.file.cfg.content)["namespace"]
 ```
 
-[standard library]:../../../../reference/stdlib/
+[standard library]: ../../../../reference/stdlib/
diff --git a/docs/sources/get-started/configuration-syntax/expressions/operators.md b/docs/sources/get-started/configuration-syntax/expressions/operators.md
index dc1933db21..ef08808ce7 100644
--- a/docs/sources/get-started/configuration-syntax/expressions/operators.md
+++ b/docs/sources/get-started/configuration-syntax/expressions/operators.md
@@ -14,50 +14,50 @@ All operations follow the standard [PEMDAS][] order of mathematical operations.
 
 ## Arithmetic operators
 
-Operator | Description
----------|---------------------------------------------------
-`+`      | Adds two numbers.
-`-`      | Subtracts two numbers.
-`*`      | Multiplies two numbers.
-`/`      | Divides two numbers.
-`%`      | Computes the remainder after dividing two numbers.
-`^`      | Raises the number to the specified power.
+| Operator | Description                                        |
+| -------- | -------------------------------------------------- |
+| `+`      | Adds two numbers.                                  |
+| `-`      | Subtracts two numbers.                             |
+| `*`      | Multiplies two numbers.                            |
+| `/`      | Divides two numbers.                               |
+| `%`      | Computes the remainder after dividing two numbers. |
+| `^`      | Raises the number to the specified power.          |
 
 ## String operators
 
-Operator | Description
----------|-------------------------
-`+`      | Concatenate two strings.
+| Operator | Description              |
+| -------- | ------------------------ |
+| `+`      | Concatenate two strings. |
 
 ## Comparison operators
 
-Operator | Description
----------|---------------------------------------------------------------------
-`==`     | `true` when two values are equal.
-`!=`     | `true` when two values aren't equal.
-`<`      | `true` when the left value is less than the right value.
-`<=`     | `true` when the left value is less than or equal to the right value.
-`>`      | `true` when the left value is greater than the right value.
-`>=`     | `true` when the left value is greater or equal to the right value.
+| Operator | Description                                                          |
+| -------- | -------------------------------------------------------------------- |
+| `==`     | `true` when two values are equal.                                    |
+| `!=`     | `true` when two values aren't equal.                                 |
+| `<`      | `true` when the left value is less than the right value.             |
+| `<=`     | `true` when the left value is less than or equal to the right value. |
+| `>`      | `true` when the left value is greater than the right value.          |
+| `>=`     | `true` when the left value is greater or equal to the right value.   |
 
 You can apply the equality operators `==` and `!=` to any operands.
 
-The two operands in ordering operators `<` `<=` `>` and `>=`  must both be _orderable_ and of the same type.
+The two operands in ordering operators `<` `<=` `>` and `>=` must both be _orderable_ and of the same type.
 The results of the comparisons are:
 
-* Boolean values are equal if they're either both true or both false.
-* Numerical (integer and floating-point) values are orderable in the usual way.
-* String values are orderable lexically byte-wise.
-* Objects are equal if all their fields are equal.
-* Array values are equal if their corresponding elements are equal.
+- Boolean values are equal if they're either both true or both false.
+- Numerical (integer and floating-point) values are orderable in the usual way.
+- String values are orderable lexically byte-wise.
+- Objects are equal if all their fields are equal.
+- Array values are equal if their corresponding elements are equal.
 
 ## Logical operators
 
-Operator | Description
----------|---------------------------------------------------------
-`&&`     | `true` when the both left _and_ right value are `true`.
-`\|\|`   | `true` when the either left _or_ right value are `true`.
-`!`      | Negates a boolean value.
+| Operator | Description                                              |
+| -------- | -------------------------------------------------------- |
+| `&&`     | `true` when the both left _and_ right value are `true`.  |
+| `\|\|`   | `true` when the either left _or_ right value are `true`. |
+| `!`      | Negates a boolean value.                                 |
 
 Logical operators apply to boolean values and yield a boolean result.
 
@@ -68,19 +68,19 @@ The {{< param "PRODUCT_NAME" >}} configuration syntax uses `=` as its assignment
 An assignment statement may only assign a single value.
 Each value must be _assignable_ to the attribute or object key.
 
-* You can assign `null` to any attribute.
-* You can assign numerical, string, boolean, array, function, capsule, and object types to attributes of the corresponding type.
-* You can assign numbers to string attributes with an implicit conversion.
-* You can assign strings to numerical attributes if they represent a number.
-* You can't assign blocks.
+- You can assign `null` to any attribute.
+- You can assign numerical, string, boolean, array, function, capsule, and object types to attributes of the corresponding type.
+- You can assign numbers to string attributes with an implicit conversion.
+- You can assign strings to numerical attributes if they represent a number.
+- You can't assign blocks.
 
 ## Brackets
 
-Brackets | Description
----------|------------------------------------
-`{ }`    | Defines blocks and objects.
-`( )`    | Groups and prioritizes expressions.
-`[ ]`    | Defines arrays.
+| Brackets | Description                         |
+| -------- | ----------------------------------- |
+| `{ }`    | Defines blocks and objects.         |
+| `( )`    | Groups and prioritizes expressions. |
+| `[ ]`    | Defines arrays.                     |
 
 The following example uses curly braces and square brackets to define an object and an array.
 
@@ -91,10 +91,10 @@ arr = [1, true, 7 * (1+1), 3]
 
 ## Access operators
 
-Operator | Description
----------|------------------------------------------------------------------------
-`[ ]`    | Access a member of an array or object.
-`.`      | Access a named member of an object or an exported field of a component.
+| Operator | Description                                                             |
+| -------- | ----------------------------------------------------------------------- |
+| `[ ]`    | Access a member of an array or object.                                  |
+| `.`      | Access a named member of an object or an exported field of a component. |
 
 You can access arbitrarily nested values with {{< param "PRODUCT_NAME" >}}'s access operators.
 You can use square brackets to access zero-indexed array indices and object fields by enclosing the field name in double quotes.
diff --git a/docs/sources/get-started/configuration-syntax/expressions/types_and_values.md b/docs/sources/get-started/configuration-syntax/expressions/types_and_values.md
index 596e6913a3..c65f7c6225 100644
--- a/docs/sources/get-started/configuration-syntax/expressions/types_and_values.md
+++ b/docs/sources/get-started/configuration-syntax/expressions/types_and_values.md
@@ -11,33 +11,33 @@ weight: 100
 
 The {{< param "PRODUCT_NAME" >}} syntax uses the following types for its values:
 
-* `number`: Any numeric value, like `3` or `3.14`.
-* `string`: A sequence of Unicode characters representing text, like `"Hello, world!"`.
-* `bool`: A boolean value, either `true` or `false`.
-* `array`: A sequence of values, like `[1, 2, 3]`. Elements within the list are indexed by whole numbers, starting with zero.
-* `object`: A group of values identified by named labels, like `{ name = "John" }`.
-* `function`: A value representing a routine that runs with arguments to compute another value, like `sys.env("HOME")`.
+- `number`: Any numeric value, like `3` or `3.14`.
+- `string`: A sequence of Unicode characters representing text, like `"Hello, world!"`.
+- `bool`: A boolean value, either `true` or `false`.
+- `array`: A sequence of values, like `[1, 2, 3]`. Elements within the list are indexed by whole numbers, starting with zero.
+- `object`: A group of values identified by named labels, like `{ name = "John" }`.
+- `function`: A value representing a routine that runs with arguments to compute another value, like `sys.env("HOME")`.
   Functions take zero or more arguments as input and always return a single value as output.
-* `null`: A type that has no value.
+- `null`: A type that has no value.
 
 ## Naming convention
 
 In addition to the preceding types, the [component reference][] documentation uses the following conventions for referring to types:
 
-* `any`: A value of any type.
-* `map(T)`: an `object` with the value type `T`.
+- `any`: A value of any type.
+- `map(T)`: an `object` with the value type `T`.
   For example, `map(string)` is an object where all the values are strings.
   The key type of an object is always a string or an identifier converted into a string.
-* `list(T)`: an `array` with the value type`T`.
+- `list(T)`: an `array` with the value type`T`.
   For example, `list(string)` is an array where all the values are strings.
-* `duration`: a `string` denoting a duration of time, such as `"100ms"`, `"1h30m"`, `"10s"`.
+- `duration`: a `string` denoting a duration of time, such as `"100ms"`, `"1h30m"`, `"10s"`.
   Valid units are:
 
-  * `h` for hours.
-  * `m` for minutes.
-  * `s` for seconds.
-  * `ms` for milliseconds.
-  * `ns` for nanoseconds.
+  - `h` for hours.
+  - `m` for minutes.
+  - `s` for seconds.
+  - `ms` for milliseconds.
+  - `ns` for nanoseconds.
 
   You can combine values of descending units to add their values together. For example, `"1h30m"` is the same as `"90m"`.
 
@@ -64,7 +64,7 @@ A `\` in a string starts an escape sequence to represent a special character.
 The following table shows the supported escape sequences.
 
 | Sequence     | Replacement                                                                             |
-|--------------|-----------------------------------------------------------------------------------------|
+| ------------ | --------------------------------------------------------------------------------------- |
 | `\\`         | The `\` character `U+005C`                                                              |
 | `\a`         | The alert or bell character `U+0007`                                                    |
 | `\b`         | The backspace character `U+0008`                                                        |
@@ -82,7 +82,7 @@ The following table shows the supported escape sequences.
 
 ## Raw strings
 
-Raw strings are represented by sequences of Unicode characters surrounded by backticks ``` `` ```.
+Raw strings are represented by sequences of Unicode characters surrounded by backticks ` `` `.
 Raw strings don't support any escape sequences.
 
 ```alloy
@@ -159,11 +159,12 @@ If the key isn't a valid identifier, you must wrap it in double quotes like a st
 {{< admonition type="note" >}}
 Don't confuse objects with blocks.
 
-* An _object_ is a value assigned to an [Attribute][]. You **must** use commas between key-value pairs on separate lines.
-* A [Block][] is a named structural element composed of multiple attributes. You **must not** use commas between attributes.
+- An _object_ is a value assigned to an [Attribute][]. You **must** use commas between key-value pairs on separate lines.
+- A [Block][] is a named structural element composed of multiple attributes. You **must not** use commas between attributes.
 
 [Attribute]: ../../syntax/#attributes
 [Block]: ../../syntax/#blocks
+
 {{< /admonition >}}
 
 ## Functions
diff --git a/docs/sources/get-started/custom_components.md b/docs/sources/get-started/custom_components.md
index 42ded3e07f..b538ea0586 100644
--- a/docs/sources/get-started/custom_components.md
+++ b/docs/sources/get-started/custom_components.md
@@ -13,9 +13,9 @@ _Custom components_ are a way to create new components from a pipeline of built-
 
 A custom component is composed of:
 
-* _Arguments_: Settings that configure the custom component.
-* _Exports_: Values that a custom component exposes to its consumers.
-* _Components_: Built-in and custom components that are run as part of the custom component.
+- _Arguments_: Settings that configure the custom component.
+- _Exports_: Values that a custom component exposes to its consumers.
+- _Components_: Built-in and custom components that are run as part of the custom component.
 
 ## Create custom components
 
@@ -24,9 +24,9 @@ The label of the block determines the name of the custom component.
 
 The following custom configuration blocks can be used inside a `declare` block:
 
-* [argument][]: Create a new named argument, whose current value can be referenced using the expression `argument.NAME.value`.
+- [argument][]: Create a new named argument, whose current value can be referenced using the expression `argument.NAME.value`.
   Argument values are determined by the user of a custom component.
-* [export][]: Expose a new named value to custom component users.
+- [export][]: Expose a new named value to custom component users.
 
 Custom components are useful for reusing a common pipeline multiple times.
 To learn how to share custom components across multiple files, refer to [Modules][].
diff --git a/docs/sources/get-started/modules.md b/docs/sources/get-started/modules.md
index 852e7bd94c..cac5445d47 100644
--- a/docs/sources/get-started/modules.md
+++ b/docs/sources/get-started/modules.md
@@ -19,10 +19,10 @@ Modules can be [imported](#import-modules) to enable the reuse of [custom compon
 A module can be _imported_, allowing the custom components defined by that module to be used by other modules, called the _importing module_.
 Modules can be imported from multiple locations using one of the `import` configuration blocks:
 
-* [`import.file`][import.file]: Imports a module from a file on disk.
-* [`import.git`][import.git]: Imports a module from a file located in a Git repository.
-* [`import.http`][import.http]: Imports a module from the response of an HTTP request.
-* [`import.string`][import.string]: Imports a module from a string.
+- [`import.file`][import.file]: Imports a module from a file on disk.
+- [`import.git`][import.git]: Imports a module from a file located in a Git repository.
+- [`import.http`][import.http]: Imports a module from the response of an HTTP request.
+- [`import.string`][import.string]: Imports a module from a string.
 
 {{< admonition type="warning" >}}
 You can't import a module that contains top-level blocks other than `declare` or `import`.
diff --git a/docs/sources/introduction/_index.md b/docs/sources/introduction/_index.md
index 483eaf0b64..1d9fc2e094 100644
--- a/docs/sources/introduction/_index.md
+++ b/docs/sources/introduction/_index.md
@@ -17,18 +17,18 @@ It's fully compatible with the most popular open source observability standards
 
 Some of the key features of {{< param "PRODUCT_NAME" >}} include:
 
-* **Custom components:** You can use {{< param "PRODUCT_NAME" >}} to create and share custom components.
+- **Custom components:** You can use {{< param "PRODUCT_NAME" >}} to create and share custom components.
   Custom components combine a pipeline of existing components into a single, easy-to-understand component that's just a few lines long.
   You can use pre-built custom components from the community, ones packaged by Grafana, or create your own.
-* **Reusable components:** You can use the output of a component as the input for multiple other components.
-* **Chained components:** You can chain components together to form a pipeline.
-* **Single task per component:** The scope of each component is limited to one specific task.
-* **GitOps compatibility:** {{< param "PRODUCT_NAME" >}} uses frameworks to pull configurations from Git, S3, HTTP endpoints, and just about any other source.
-* **Clustering support:** {{< param "PRODUCT_NAME" >}} has native clustering support.
+- **Reusable components:** You can use the output of a component as the input for multiple other components.
+- **Chained components:** You can chain components together to form a pipeline.
+- **Single task per component:** The scope of each component is limited to one specific task.
+- **GitOps compatibility:** {{< param "PRODUCT_NAME" >}} uses frameworks to pull configurations from Git, S3, HTTP endpoints, and just about any other source.
+- **Clustering support:** {{< param "PRODUCT_NAME" >}} has native clustering support.
   Clustering helps distribute the workload and ensures you have high availability.
   You can quickly create horizontally scalable deployments with minimal resource and operational overhead.
-* **Security:** {{< param "PRODUCT_NAME" >}} helps you manage authentication credentials and connect to HashiCorp Vaults or Kubernetes clusters to retrieve secrets.
-* **Debugging utilities:** {{< param "PRODUCT_NAME" >}} provides troubleshooting support and an embedded [user interface][UI] to help you identify and resolve configuration problems.
+- **Security:** {{< param "PRODUCT_NAME" >}} helps you manage authentication credentials and connect to HashiCorp Vaults or Kubernetes clusters to retrieve secrets.
+- **Debugging utilities:** {{< param "PRODUCT_NAME" >}} provides troubleshooting support and an embedded [user interface][UI] to help you identify and resolve configuration problems.
 
 ## How does {{% param "PRODUCT_NAME" %}} work as an OpenTelemetry collector?
 
@@ -55,11 +55,11 @@ You can use transformations to inject extra metadata into telemetry or filter ou
 
 ## Next steps
 
-* [Install][] {{< param "PRODUCT_NAME" >}}.
-* Learn about the core [Concepts][] of {{< param "PRODUCT_NAME" >}}.
-* Follow the [tutorials][] for hands-on learning about {{< param "PRODUCT_NAME" >}}.
-* Learn how to [collect and forward data][Collect] with {{< param "PRODUCT_NAME" >}}.
-* Check out the [reference][] documentation to find information about the {{< param "PRODUCT_NAME" >}} components, configuration blocks, and command line tools.
+- [Install][] {{< param "PRODUCT_NAME" >}}.
+- Learn about the core [Concepts][] of {{< param "PRODUCT_NAME" >}}.
+- Follow the [tutorials][] for hands-on learning about {{< param "PRODUCT_NAME" >}}.
+- Learn how to [collect and forward data][Collect] with {{< param "PRODUCT_NAME" >}}.
+- Check out the [reference][] documentation to find information about the {{< param "PRODUCT_NAME" >}} components, configuration blocks, and command line tools.
 
 [OpenTelemetry]: https://opentelemetry.io/ecosystem/distributions/
 [Install]: ../set-up/install/
diff --git a/docs/sources/introduction/backward-compatibility.md b/docs/sources/introduction/backward-compatibility.md
index 32ca3c9002..0431e1f8bf 100644
--- a/docs/sources/introduction/backward-compatibility.md
+++ b/docs/sources/introduction/backward-compatibility.md
@@ -13,27 +13,27 @@ weight: 999
 
 Documented functionality that's released as _Generally available_ is covered by backward compatibility, including:
 
-* **User configuration**, including the {{< param "PRODUCT_NAME" >}} configuration syntax, the semantics of the configuration file, and the command-line interface.
+- **User configuration**, including the {{< param "PRODUCT_NAME" >}} configuration syntax, the semantics of the configuration file, and the command-line interface.
 
-* **APIs**, for any network or code API released as v1.0.0 or later.
+- **APIs**, for any network or code API released as v1.0.0 or later.
 
-* **Observability data used in official dashboards**, where the official set of dashboards are found in the [`alloy-mixin/`][alloy-mixin] directory.
+- **Observability data used in official dashboards**, where the official set of dashboards are found in the [`alloy-mixin/`][alloy-mixin] directory.
 
 ## Exceptions
 
 We strive to maintain backward compatibility, but there are situations that may arise that require a breaking change without a new major version, deviating from [item 8 of the semver specification][]:
 
-* **Security**: A security issue may arise that requires breaking compatibility.
+- **Security**: A security issue may arise that requires breaking compatibility.
 
-* **Legal requirements**: If an exposed behavior violates a licensing or legal requirement, a breaking change may be required.
+- **Legal requirements**: If an exposed behavior violates a licensing or legal requirement, a breaking change may be required.
 
-* **Specification errors**: If a specification for a feature is found to be incomplete or inconsistent, fixing the specification may require a breaking change.
+- **Specification errors**: If a specification for a feature is found to be incomplete or inconsistent, fixing the specification may require a breaking change.
 
-* **Bugs**: If a bug is found that goes against the documented specification of that functionality, fixing the bug may require breaking compatibility for users who are relying on the incorrect behavior.
+- **Bugs**: If a bug is found that goes against the documented specification of that functionality, fixing the bug may require breaking compatibility for users who are relying on the incorrect behavior.
 
-* **Upstream changes**: Much of the functionality of {{< param "PRODUCT_NAME" >}} is built on top of other software, such as OpenTelemetry Collector and Prometheus. If upstream software breaks compatibility, we may need to reflect this in {{< param "PRODUCT_NAME" >}}.
+- **Upstream changes**: Much of the functionality of {{< param "PRODUCT_NAME" >}} is built on top of other software, such as OpenTelemetry Collector and Prometheus. If upstream software breaks compatibility, we may need to reflect this in {{< param "PRODUCT_NAME" >}}.
 
-* **Community components**: Community components are components implemented and maintained by the community. They aren't covered by the backward compatibility strategy.
+- **Community components**: Community components are components implemented and maintained by the community. They aren't covered by the backward compatibility strategy.
 
 We try, whenever possible, to resolve these issues without breaking compatibility.
 
diff --git a/docs/sources/introduction/estimate-resource-usage.md b/docs/sources/introduction/estimate-resource-usage.md
index 561156537a..553b57bc64 100644
--- a/docs/sources/introduction/estimate-resource-usage.md
+++ b/docs/sources/introduction/estimate-resource-usage.md
@@ -24,9 +24,9 @@ The Prometheus metrics resource usage depends mainly on the number of active ser
 
 As a rule of thumb, **per each 1 million active series** and with the default scrape interval, you can expect to use approximately:
 
-* 0.4 CPU cores
-* 11 GiB of memory
-* 1.5 MiB/s of total network bandwidth, send and receive
+- 0.4 CPU cores
+- 11 GiB of memory
+- 1.5 MiB/s of total network bandwidth, send and receive
 
 These recommendations are based on deployments that use [clustering][], but they broadly apply to other deployment modes.
 Refer to [Deploy {{< param "FULL_PRODUCT_NAME" >}}][deploy] for more information on how to deploy {{< param "PRODUCT_NAME" >}}.
@@ -37,8 +37,8 @@ Loki logs resource usage depends mainly on the volume of logs ingested.
 
 As a rule of thumb, **per each 1 MiB/second of logs ingested**, you can expect to use approximately:
 
-* 1 CPU core
-* 120 MiB of memory
+- 1 CPU core
+- 120 MiB of memory
 
 These recommendations are based on Kubernetes DaemonSet deployments on clusters with relatively small number of nodes and high logs volume on each.
 The resource usage can be higher per each 1 MiB/second of logs if you have a large number of small nodes due to the constant overhead of running the {{< param "PRODUCT_NAME" >}} on each node.
@@ -51,8 +51,8 @@ Pyroscope profiles resource usage depends mainly on the volume of profiles.
 
 As a rule of thumb, **per each 100 profiles/second**, you can expect to use approximately:
 
-* 1 CPU core
-* 10 GiB of memory
+- 1 CPU core
+- 10 GiB of memory
 
 Factors such as size of each profile and frequency of fetching them also play a role in the overall resource usage.
 
diff --git a/docs/sources/introduction/supported-platforms.md b/docs/sources/introduction/supported-platforms.md
index b79fde02af..f81dc54af0 100644
--- a/docs/sources/introduction/supported-platforms.md
+++ b/docs/sources/introduction/supported-platforms.md
@@ -12,20 +12,20 @@ The following operating systems and hardware architecture are supported.
 
 ## Linux
 
-* Minimum version: kernel 2.6.32 or later
-* Architectures: AMD64, ARM64
+- Minimum version: kernel 2.6.32 or later
+- Architectures: AMD64, ARM64
 
 ## Windows
 
-* Minimum version: Windows Server 2016 or later, or Windows 10 or later.
-* Architectures: AMD64
+- Minimum version: Windows Server 2016 or later, or Windows 10 or later.
+- Architectures: AMD64
 
 ## macOS
 
-* Minimum version: macOS 10.13 or later
-* Architectures: AMD64 on Intel, ARM64 on Apple Silicon
+- Minimum version: macOS 10.13 or later
+- Architectures: AMD64 on Intel, ARM64 on Apple Silicon
 
 ## FreeBSD
 
-* Minimum version: FreeBSD 10 or later
-* Architectures: AMD64
+- Minimum version: FreeBSD 10 or later
+- Architectures: AMD64
diff --git a/docs/sources/reference/cli/_index.md b/docs/sources/reference/cli/_index.md
index d4c51254d4..565762ed4e 100644
--- a/docs/sources/reference/cli/_index.md
+++ b/docs/sources/reference/cli/_index.md
@@ -14,12 +14,12 @@ The most common subcommand is [`run`][run] which accepts a configuration file an
 
 Available commands:
 
-* [`convert`][convert]: Convert an {{< param "PRODUCT_NAME" >}} configuration file.
-* [`fmt`][fmt]: Format an {{< param "PRODUCT_NAME" >}} configuration file.
-* [`run`][run]: Start {{< param "PRODUCT_NAME" >}}, given a configuration file.
-* [`tools`][tools]: Read the WAL and provide statistical information.
-* `completion`: Generate shell completion for the `alloy` CLI.
-* `help`: Print help for supported commands.
+- [`convert`][convert]: Convert an {{< param "PRODUCT_NAME" >}} configuration file.
+- [`fmt`][fmt]: Format an {{< param "PRODUCT_NAME" >}} configuration file.
+- [`run`][run]: Start {{< param "PRODUCT_NAME" >}}, given a configuration file.
+- [`tools`][tools]: Read the WAL and provide statistical information.
+- `completion`: Generate shell completion for the `alloy` CLI.
+- `help`: Print help for supported commands.
 
 [run]: ./run/
 [fmt]: ./fmt/
diff --git a/docs/sources/reference/cli/convert.md b/docs/sources/reference/cli/convert.md
index 0d633fbab2..a4219b1e39 100644
--- a/docs/sources/reference/cli/convert.md
+++ b/docs/sources/reference/cli/convert.md
@@ -22,8 +22,8 @@ alloy convert [<FLAG> ...] <FILE_NAME>
 
 Replace the following:
 
-* _`<FLAG>`_: One or more flags that define the input and output of the command.
-* _`<FILE_NAME>`_: The {{< param "PRODUCT_NAME" >}} configuration file.
+- _`<FLAG>`_: One or more flags that define the input and output of the command.
+- _`<FILE_NAME>`_: The {{< param "PRODUCT_NAME" >}} configuration file.
 
 If the _`<FILE_NAME>`_ argument isn't provided or if the _`<FILE_NAME>`_ argument is equal to `-`, `convert` converts the contents of standard input.
 Otherwise, `convert` reads and converts the file from disk specified by the argument.
@@ -36,19 +36,19 @@ The command fails if the source configuration has syntactically incorrect config
 
 The following flags are supported:
 
-* `--output`, `-o`: The filepath and filename where the output is written.
-* `--report`, `-r`: The filepath and filename where the report is written.
-* `--source-format`, `-f`: Required. The format of the source file. Supported formats: [`otelcol`][otelcol], [`prometheus`][prometheus], [`promtail`][promtail], [`static`][static].
-* `--bypass-errors`, `-b`: Enable bypassing errors when converting.
-* `--extra-args`, `e`: Extra arguments from the original format used by the converter.
+- `--output`, `-o`: The filepath and filename where the output is written.
+- `--report`, `-r`: The filepath and filename where the report is written.
+- `--source-format`, `-f`: Required. The format of the source file. Supported formats: [`otelcol`][otelcol], [`prometheus`][prometheus], [`promtail`][promtail], [`static`][static].
+- `--bypass-errors`, `-b`: Enable bypassing errors when converting.
+- `--extra-args`, `e`: Extra arguments from the original format used by the converter.
 
 ### Defaults
 
 {{< param "PRODUCT_NAME" >}} defaults are managed as follows:
 
-* If a provided source configuration value matches an {{< param "PRODUCT_NAME" >}} default value, the property is left off the output.
-* If a non-provided source configuration value default matches an {{< param "PRODUCT_NAME" >}} default value, the property is left off the output.
-* If a non-provided source configuration value default doesn't match an {{< param "PRODUCT_NAME" >}} default value, the default value is included in the output.
+- If a provided source configuration value matches an {{< param "PRODUCT_NAME" >}} default value, the property is left off the output.
+- If a non-provided source configuration value default matches an {{< param "PRODUCT_NAME" >}} default value, the property is left off the output.
+- If a non-provided source configuration value default doesn't match an {{< param "PRODUCT_NAME" >}} default value, the default value is included in the output.
 
 ### Errors
 
diff --git a/docs/sources/reference/cli/environment-variables.md b/docs/sources/reference/cli/environment-variables.md
index 82d5ef6e77..5d45b7157a 100644
--- a/docs/sources/reference/cli/environment-variables.md
+++ b/docs/sources/reference/cli/environment-variables.md
@@ -12,12 +12,11 @@ You can use environment variables to control the run-time behavior of {{< param
 
 The following environment variables are supported:
 
-* `GODEBUG`
-* `HTTP_PROXY`
-* `PPROF_MUTEX_PROFILING_PERCENT`
-* `PPROF_BLOCK_PROFILING_RATE`
-* `GOMEMLIMIT`
-
+- `GODEBUG`
+- `HTTP_PROXY`
+- `PPROF_MUTEX_PROFILING_PERCENT`
+- `PPROF_BLOCK_PROFILING_RATE`
+- `GOMEMLIMIT`
 
 Refer to the [Go runtime][runtime] documentation for more information about Go runtime environment variables.
 
@@ -25,15 +24,15 @@ Refer to the [Go runtime][runtime] documentation for more information about Go r
 
 You can use the `GODEBUG` environment variable to control the debugging variables within the Go runtime. The following arguments are supported.
 
-Argument               | Description                                                                                          | Default
------------------------|------------------------------------------------------------------------------------------------------|--------
-`x509usefallbackroots` | Enforce a fallback on the X.509 trusted root certificates. Set to `1` to enable.                     | `0`
-`netdns`               | Force a resolver. Set to `go` for a pure Go resolver. Set to `cgo` or `win32` for a native resolver. |
-`netdns`               | Show resolver debugging information. Set to `1` for basic information. Set to `2` for verbose.       |
+| Argument               | Description                                                                                          | Default |
+| ---------------------- | ---------------------------------------------------------------------------------------------------- | ------- |
+| `x509usefallbackroots` | Enforce a fallback on the X.509 trusted root certificates. Set to `1` to enable.                     | `0`     |
+| `netdns`               | Force a resolver. Set to `go` for a pure Go resolver. Set to `cgo` or `win32` for a native resolver. |
+| `netdns`               | Show resolver debugging information. Set to `1` for basic information. Set to `2` for verbose.       |
 
 ## HTTP_PROXY
 
-You can use the `HTTP_PROXY` environment variable to define the hostname or IP address of the proxy server.  For example, you can set the proxy to `http://proxy.example.com`.
+You can use the `HTTP_PROXY` environment variable to define the hostname or IP address of the proxy server. For example, you can set the proxy to `http://proxy.example.com`.
 
 ## PPROF_MUTEX_PROFILING_PERCENT
 
@@ -43,9 +42,9 @@ You can use the `PPROF_MUTEX_PROFILING_PERCENT` environment variable to define t
 
 You can use the `PPROF_BLOCK_PROFILING_RATE` environment variable to define the rate that mutexes are tracked. You can use the following values with this environment variable. The default value is `10000`.
 
-* `0`: Nothing is tracked.
-* `1`: All mutexes are tracked.
-* A value greater than `1`: The number of nanoseconds to track mutexes.
+- `0`: Nothing is tracked.
+- `1`: All mutexes are tracked.
+- A value greater than `1`: The number of nanoseconds to track mutexes.
 
 ### GOMEMLIMIT
 
@@ -55,13 +54,13 @@ You can use the `GOMEMLIMIT` environment variable to set a soft memory cap and l
 You can set `GOMEMLIMIT` to a numeric value in bytes with an optional unit suffix.
 The supported unit suffixes are `B`, `KiB`, `MiB`, `GiB`, and `TiB`.
 Don't treat the `GOMEMLIMIT` environment variable as a hard memory limit.
-{{< param "PRODUCT_NAME" >}}  processes can use more memory if that memory is required.
+{{< param "PRODUCT_NAME" >}} processes can use more memory if that memory is required.
 A rough number is to set `GOMEMLIMIT` to is 90% of the maximum memory required.
 For example, if you want to keep memory usage below `10GiB`, use `GOMEMLIMIT=9GiB`.
 
 ### Automatically set GOMEMLIMIT
 
-The `GOMEMLIMIT` environment variable is either automatically set to 90% of an available `cgroup` value, or you can explicitly set the  `GOMEMLIMIT` environment variable before you run  {{< param "PRODUCT_NAME" >}}.
-No changes will occur if the limit cannot be determined and you did not explicitly define a  `GOMEMLIMIT` value.
+The `GOMEMLIMIT` environment variable is either automatically set to 90% of an available `cgroup` value, or you can explicitly set the `GOMEMLIMIT` environment variable before you run {{< param "PRODUCT_NAME" >}}.
+No changes will occur if the limit cannot be determined and you did not explicitly define a `GOMEMLIMIT` value.
 
 [runtime]: https://pkg.go.dev/runtime
diff --git a/docs/sources/reference/cli/fmt.md b/docs/sources/reference/cli/fmt.md
index 3fdf9d0097..c53729f1e1 100644
--- a/docs/sources/reference/cli/fmt.md
+++ b/docs/sources/reference/cli/fmt.md
@@ -18,8 +18,8 @@ alloy fmt [<FLAG> ...] <FILE_NAME>
 
 Replace the following:
 
-* _`<FLAG>`_: One or more flags that define the input and output of the command.
-* _`<FILE_NAME>`_: The {{< param "PRODUCT_NAME" >}} configuration file.
+- _`<FLAG>`_: One or more flags that define the input and output of the command.
+- _`<FILE_NAME>`_: The {{< param "PRODUCT_NAME" >}} configuration file.
 
 If the _`<FILE_NAME>`_ argument isn't provided or if the _`<FILE_NAME>`_ argument is equal to `-`, `fmt` formats the contents of standard input.
 Otherwise, `fmt` reads and formats the file from disk specified by the argument.
@@ -35,5 +35,5 @@ The command fails if the file being formatted has syntactically incorrect {{< pa
 
 The following flags are supported:
 
-* `--write`, `-w`: Write the formatted file back to disk when not reading from standard input.
-* `--test`, `-t`: Only test the input and return a non-zero exit code if changes would have been made.
+- `--write`, `-w`: Write the formatted file back to disk when not reading from standard input.
+- `--test`, `-t`: Only test the input and return a non-zero exit code if changes would have been made.
diff --git a/docs/sources/reference/cli/run.md b/docs/sources/reference/cli/run.md
index 4cbe811690..2f4670380e 100644
--- a/docs/sources/reference/cli/run.md
+++ b/docs/sources/reference/cli/run.md
@@ -18,8 +18,8 @@ alloy run [<FLAG> ...] <PATH_NAME>
 
 Replace the following:
 
-* _`<FLAG>`_: One or more flags that define the input and output of the command.
-* _`<PATH_NAME>`_: Required. The {{< param "PRODUCT_NAME" >}} configuration file/directory path.
+- _`<FLAG>`_: One or more flags that define the input and output of the command.
+- _`<PATH_NAME>`_: Required. The {{< param "PRODUCT_NAME" >}} configuration file/directory path.
 
 If the _`<PATH_NAME>`_ argument isn't provided, or if the configuration path can't be loaded or contains errors during the initial load, the `run` command immediately exits and shows an error message.
 
@@ -34,39 +34,39 @@ The HTTP server is also exposes a UI at `/` for debugging running components.
 
 The following flags are supported:
 
-* `--server.http.enable-pprof`: Enable /debug/pprof profiling endpoints. (default `true`).
-* `--server.http.memory-addr`: Address to listen for [in-memory HTTP traffic][] on (default `alloy.internal:12345`).
-* `--server.http.listen-addr`: Address to listen for HTTP traffic on (default `127.0.0.1:12345`).
-* `--server.http.ui-path-prefix`: Base path where the UI is exposed (default `/`).
-* `--storage.path`: Base directory where components can store data (default `data-alloy/`).
-* `--disable-reporting`: Disable [data collection][] (default `false`).
-* `--disable-support-bundle`: Disable [support bundle][] endpoint (default `false`).
-* `--cluster.enabled`: Start {{< param "PRODUCT_NAME" >}} in clustered mode (default `false`).
-* `--cluster.node-name`: The name to use for this node (defaults to the environment's hostname).
-* `--cluster.join-addresses`: Comma-separated list of addresses to join the cluster at (default `""`). Mutually exclusive with `--cluster.discover-peers`.
-* `--cluster.discover-peers`: List of key-value tuples for discovering peers (default `""`). Mutually exclusive with `--cluster.join-addresses`.
-* `--cluster.rejoin-interval`: How often to rejoin the list of peers (default `"60s"`).
-* `--cluster.advertise-address`: Address to advertise to other cluster nodes (default `""`).
-* `--cluster.advertise-interfaces`: List of interfaces used to infer an address to advertise. Set to `all` to use all available network interfaces on the system. (default `"eth0,en0"`).
-* `--cluster.max-join-peers`: Number of peers to join from the discovered set (default `5`).
-* `--cluster.name`: Name to prevent nodes without this identifier from joining the cluster (default `""`).
-* `--cluster.enable-tls`: Specifies whether TLS should be used for communication between peers (default `false`).
-* `--cluster.tls-ca-path`: Path to the CA certificate file used for peer communication over TLS.
-* `--cluster.tls-cert-path`: Path to the certificate file used for peer communication over TLS.
-* `--cluster.tls-key-path`: Path to the key file used for peer communication over TLS.
-* `--cluster.tls-server-name`: Server name used for peer communication over TLS.
-* `--config.format`: The format of the source file. Supported formats: `alloy`, `otelcol`, `prometheus`, `promtail`, `static` (default `"alloy"`).
-* `--config.bypass-conversion-errors`: Enable bypassing errors when converting (default `false`).
-* `--config.extra-args`: Extra arguments from the original format used by the converter.
-* `--stability.level`: The minimum permitted stability level of functionality to run. Supported values: `experimental`, `public-preview`, `generally-available` (default `"generally-available"`).
-* `--feature.community-components.enabled`: Enable community components (default `false`).
+- `--server.http.enable-pprof`: Enable /debug/pprof profiling endpoints. (default `true`).
+- `--server.http.memory-addr`: Address to listen for [in-memory HTTP traffic][] on (default `alloy.internal:12345`).
+- `--server.http.listen-addr`: Address to listen for HTTP traffic on (default `127.0.0.1:12345`).
+- `--server.http.ui-path-prefix`: Base path where the UI is exposed (default `/`).
+- `--storage.path`: Base directory where components can store data (default `data-alloy/`).
+- `--disable-reporting`: Disable [data collection][] (default `false`).
+- `--disable-support-bundle`: Disable [support bundle][] endpoint (default `false`).
+- `--cluster.enabled`: Start {{< param "PRODUCT_NAME" >}} in clustered mode (default `false`).
+- `--cluster.node-name`: The name to use for this node (defaults to the environment's hostname).
+- `--cluster.join-addresses`: Comma-separated list of addresses to join the cluster at (default `""`). Mutually exclusive with `--cluster.discover-peers`.
+- `--cluster.discover-peers`: List of key-value tuples for discovering peers (default `""`). Mutually exclusive with `--cluster.join-addresses`.
+- `--cluster.rejoin-interval`: How often to rejoin the list of peers (default `"60s"`).
+- `--cluster.advertise-address`: Address to advertise to other cluster nodes (default `""`).
+- `--cluster.advertise-interfaces`: List of interfaces used to infer an address to advertise. Set to `all` to use all available network interfaces on the system. (default `"eth0,en0"`).
+- `--cluster.max-join-peers`: Number of peers to join from the discovered set (default `5`).
+- `--cluster.name`: Name to prevent nodes without this identifier from joining the cluster (default `""`).
+- `--cluster.enable-tls`: Specifies whether TLS should be used for communication between peers (default `false`).
+- `--cluster.tls-ca-path`: Path to the CA certificate file used for peer communication over TLS.
+- `--cluster.tls-cert-path`: Path to the certificate file used for peer communication over TLS.
+- `--cluster.tls-key-path`: Path to the key file used for peer communication over TLS.
+- `--cluster.tls-server-name`: Server name used for peer communication over TLS.
+- `--config.format`: The format of the source file. Supported formats: `alloy`, `otelcol`, `prometheus`, `promtail`, `static` (default `"alloy"`).
+- `--config.bypass-conversion-errors`: Enable bypassing errors when converting (default `false`).
+- `--config.extra-args`: Extra arguments from the original format used by the converter.
+- `--stability.level`: The minimum permitted stability level of functionality to run. Supported values: `experimental`, `public-preview`, `generally-available` (default `"generally-available"`).
+- `--feature.community-components.enabled`: Enable community components (default `false`).
 
 ## Update the configuration file
 
 The configuration file can be reloaded from disk by either:
 
-* Sending an HTTP POST request to the `/-/reload` endpoint.
-* Sending a `SIGHUP` signal to the {{< param "PRODUCT_NAME" >}} process.
+- Sending an HTTP POST request to the `/-/reload` endpoint.
+- Sending a `SIGHUP` signal to the {{< param "PRODUCT_NAME" >}} process.
 
 When this happens, the [component controller][] synchronizes the set of running components with the latest set of components specified in the configuration file.
 Components that are no longer defined in the configuration file after reloading are shut down, and components that have been added to the configuration file since the previous reload are created.
@@ -79,17 +79,17 @@ By default, {{< param "PRODUCT_NAME" >}} only allows you to use functionality th
 
 To use [Experimental][stability] or [Public preview][stability] functionality, set the `--stability.level` flag to the level you want to use:
 
-* `--stability.level=experimental`: Use functionality marked as _Experimental_ and above.
-* `--stability.level=public-preview`: Use functionality marked as _Public preview_ and above.
-* `--stability.level=generally-available`: Use functionality marked as _Generally available_.
+- `--stability.level=experimental`: Use functionality marked as _Experimental_ and above.
+- `--stability.level=public-preview`: Use functionality marked as _Public preview_ and above.
+- `--stability.level=generally-available`: Use functionality marked as _Generally available_.
 
 {{< admonition type="caution" >}}
 Setting `--stability.level` to `experimental` or `public-preview` may enable _Experimental_ or _Public preview_ behavior for items otherwise marked _Generally available_, such as:
 
-* The component controller
-* Components in the main configuration or in imported modules
-* Configuration blocks in the main configuration
-{{< /admonition >}}
+- The component controller
+- Components in the main configuration or in imported modules
+- Configuration blocks in the main configuration
+  {{< /admonition >}}
 
 [stability]: https://grafana.com/docs/release-life-cycle/
 
@@ -148,9 +148,9 @@ Attempting to join a cluster with a wrong `--cluster.name` results in a "failed
 
 Clustered {{< param "PRODUCT_NAME" >}}s are in one of three states:
 
-* **Viewer**: {{< param "PRODUCT_NAME" >}} has a read-only view of the cluster and isn't participating in workload distribution.
-* **Participant**: {{< param "PRODUCT_NAME" >}} is participating in workload distribution for components that have clustering enabled.
-* **Terminating**: {{< param "PRODUCT_NAME" >}} is shutting down and no longer assigning new work to itself.
+- **Viewer**: {{< param "PRODUCT_NAME" >}} has a read-only view of the cluster and isn't participating in workload distribution.
+- **Participant**: {{< param "PRODUCT_NAME" >}} is participating in workload distribution for components that have clustering enabled.
+- **Terminating**: {{< param "PRODUCT_NAME" >}} is shutting down and no longer assigning new work to itself.
 
 Each {{< param "PRODUCT_NAME" >}} initially joins the cluster in the viewer state and then transitions to the participant state after the process startup completes.
 Each {{< param "PRODUCT_NAME" >}} then transitions to the terminating state when shutting down.
@@ -171,7 +171,7 @@ Include `--config.extra-args` to pass additional command line flags from the ori
 Refer to [alloy convert][] for more details on how `extra-args` work.
 
 [alloy convert]: ../convert/
-[clustering]:  ../../../get-started/clustering/
+[clustering]: ../../../get-started/clustering/
 [go-discover]: https://github.com/hashicorp/go-discover
 [in-memory HTTP traffic]: ../../../get-started/component_controller/#in-memory-traffic
 [data collection]: ../../../data-collection/
diff --git a/docs/sources/reference/cli/tools.md b/docs/sources/reference/cli/tools.md
index 8c62607dac..31c63274ea 100644
--- a/docs/sources/reference/cli/tools.md
+++ b/docs/sources/reference/cli/tools.md
@@ -24,23 +24,23 @@ alloy tools prometheus.remote_write sample-stats [<FLAG> ...] <WAL_DIRECTORY>
 
 Replace the following:
 
-* _`<FLAG>`_: One or more flags that define the input and output of the command.
-* _`<WAL_DIRECTORY>`_: The WAL directory.
+- _`<FLAG>`_: One or more flags that define the input and output of the command.
+- _`<WAL_DIRECTORY>`_: The WAL directory.
 
-The `sample-stats` command reads the Write-Ahead Log (WAL) specified by _`<WAL_DIRECTORY>`+ and collects information on metric samples within it.
+The `sample-stats` command reads the Write-Ahead Log (WAL) specified by \_`<WAL_DIRECTORY>`+ and collects information on metric samples within it.
 
 For each metric discovered, `sample-stats` emits:
 
-* The timestamp of the oldest sample received for that metric.
-* The timestamp of the newest sample received for that metric.
-* The total number of samples discovered for that metric.
+- The timestamp of the oldest sample received for that metric.
+- The timestamp of the newest sample received for that metric.
+- The total number of samples discovered for that metric.
 
 By default, `sample-stats` returns information for every metric in the WAL.
 You can pass the `--selector` flag to filter the reported metrics to a smaller set.
 
 The following flag is supported:
 
-* `--selector`: A PromQL label selector to filter data by. (default `{}`)
+- `--selector`: A PromQL label selector to filter data by. (default `{}`)
 
 ### prometheus.remote_write target-stats
 
@@ -54,8 +54,8 @@ For the target specified by the `--job` and `--instance` flags, unique metric na
 
 The following flags are supported:
 
-* `--job`: The `job` label of the target.
-* `--instance`: The `instance` label of the target.
+- `--job`: The `job` label of the target.
+- `--instance`: The `instance` label of the target.
 
 The `--job` and `--instance` labels are required.
 
@@ -67,21 +67,21 @@ alloy tools prometheus.remote_write wal-stats <WAL_DIRECTORY>
 
 Replace the following:
 
-* _`<WAL_DIRECTORY>`_: The WAL directory.
+- _`<WAL_DIRECTORY>`_: The WAL directory.
 
 The `wal-stats` command reads the Write-Ahead Log (WAL) specified by _`<WAL_DIRECTORY>`_ and collects general information about it.
 
 The following information is reported:
 
-* The timestamp of the oldest sample in the WAL.
-* The timestamp of the newest sample in the WAL.
-* The total number of unique series defined in the WAL.
-* The total number of samples in the WAL.
-* The number of hash collisions detected, if any.
-* The total number of invalid records in the WAL, if any.
-* The most recent WAL checkpoint segment number.
-* The oldest segment number in the WAL.
-* The newest segment number in the WAL.
+- The timestamp of the oldest sample in the WAL.
+- The timestamp of the newest sample in the WAL.
+- The total number of unique series defined in the WAL.
+- The total number of samples in the WAL.
+- The number of hash collisions detected, if any.
+- The total number of invalid records in the WAL, if any.
+- The most recent WAL checkpoint segment number.
+- The oldest segment number in the WAL.
+- The newest segment number in the WAL.
 
 Additionally, `wal-stats` reports per-target information, where a target is defined as a unique combination of the `job` and `instance` label values.
 For each target, `wal-stats` reports the number of series and the number of metric samples associated with that target.
diff --git a/docs/sources/reference/compatibility/_index.md b/docs/sources/reference/compatibility/_index.md
index e075f76321..9286bf06a3 100644
--- a/docs/sources/reference/compatibility/_index.md
+++ b/docs/sources/reference/compatibility/_index.md
@@ -18,9 +18,9 @@ Refer to each component's documentation for more details on what values are acce
 
 For example:
 
-* A Prometheus component may always expect an `"__address__"` label inside a list of targets.
-* A `string` argument may only accept certain values like "traceID" or "spanID".
-{{< /admonition >}}
+- A Prometheus component may always expect an `"__address__"` label inside a list of targets.
+- A `string` argument may only accept certain values like "traceID" or "spanID".
+  {{< /admonition >}}
 
 ## Targets
 
@@ -34,6 +34,7 @@ It's recommended to always check component references for details when working w
 [string]: ../../get-started/configuration-syntax/expressions/types_and_values/#strings
 
 <!-- NOTE: this title is used as an anchor in links. Do not change. -->
+
 ### Targets Exporters
 
 The following components, grouped by namespace, _export_ Targets.
@@ -41,10 +42,12 @@ The following components, grouped by namespace, _export_ Targets.
 <!-- START GENERATED SECTION: EXPORTERS OF Targets -->
 
 {{< collapse title="beyla" >}}
+
 - [beyla.ebpf](../components/beyla/beyla.ebpf)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="discovery" >}}
+
 - [discovery.azure](../components/discovery/discovery.azure)
 - [discovery.consul](../components/discovery/discovery.consul)
 - [discovery.consulagent](../components/discovery/discovery.consulagent)
@@ -76,13 +79,15 @@ The following components, grouped by namespace, _export_ Targets.
 - [discovery.serverset](../components/discovery/discovery.serverset)
 - [discovery.triton](../components/discovery/discovery.triton)
 - [discovery.uyuni](../components/discovery/discovery.uyuni)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="local" >}}
+
 - [local.file_match](../components/local/local.file_match)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="prometheus" >}}
+
 - [prometheus.exporter.apache](../components/prometheus/prometheus.exporter.apache)
 - [prometheus.exporter.azure](../components/prometheus/prometheus.exporter.azure)
 - [prometheus.exporter.blackbox](../components/prometheus/prometheus.exporter.blackbox)
@@ -110,11 +115,12 @@ The following components, grouped by namespace, _export_ Targets.
 - [prometheus.exporter.statsd](../components/prometheus/prometheus.exporter.statsd)
 - [prometheus.exporter.unix](../components/prometheus/prometheus.exporter.unix)
 - [prometheus.exporter.windows](../components/prometheus/prometheus.exporter.windows)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 <!-- END GENERATED SECTION: EXPORTERS OF Targets -->
 
 <!-- NOTE: this title is used as an anchor in links. Do not change. -->
+
 ### Targets Consumers
 
 The following components, grouped by namespace, _consume_ Targets.
@@ -122,33 +128,39 @@ The following components, grouped by namespace, _consume_ Targets.
 <!-- START GENERATED SECTION: CONSUMERS OF Targets -->
 
 {{< collapse title="discovery" >}}
+
 - [discovery.process](../components/discovery/discovery.process)
 - [discovery.relabel](../components/discovery/discovery.relabel)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="local" >}}
+
 - [local.file_match](../components/local/local.file_match)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="loki" >}}
+
 - [loki.source.docker](../components/loki/loki.source.docker)
 - [loki.source.file](../components/loki/loki.source.file)
 - [loki.source.kubernetes](../components/loki/loki.source.kubernetes)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="otelcol" >}}
+
 - [otelcol.processor.discovery](../components/otelcol/otelcol.processor.discovery)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="prometheus" >}}
+
 - [prometheus.scrape](../components/prometheus/prometheus.scrape)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="pyroscope" >}}
+
 - [pyroscope.ebpf](../components/pyroscope/pyroscope.ebpf)
 - [pyroscope.java](../components/pyroscope/pyroscope.java)
 - [pyroscope.scrape](../components/pyroscope/pyroscope.scrape)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 <!-- END GENERATED SECTION: CONSUMERS OF Targets -->
 
@@ -162,6 +174,7 @@ Use the following components to build your Prometheus metrics pipeline:
 [capsules]: ../../get-started/configuration-syntax/expressions/types_and_values/#capsules
 
 <!-- NOTE: this title is used as an anchor in links. Do not change. -->
+
 ### Prometheus `MetricsReceiver` Exporters
 
 The following components, grouped by namespace, _export_ Prometheus `MetricsReceiver`.
@@ -169,18 +182,21 @@ The following components, grouped by namespace, _export_ Prometheus `MetricsRece
 <!-- START GENERATED SECTION: EXPORTERS OF Prometheus `MetricsReceiver` -->
 
 {{< collapse title="otelcol" >}}
+
 - [otelcol.receiver.prometheus](../components/otelcol/otelcol.receiver.prometheus)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="prometheus" >}}
+
 - [prometheus.relabel](../components/prometheus/prometheus.relabel)
 - [prometheus.remote_write](../components/prometheus/prometheus.remote_write)
 - [prometheus.write.queue](../components/prometheus/prometheus.write.queue)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 <!-- END GENERATED SECTION: EXPORTERS OF Prometheus `MetricsReceiver` -->
 
 <!-- NOTE: this title is used as an anchor in links. Do not change. -->
+
 ### Prometheus `MetricsReceiver` Consumers
 
 The following components, grouped by namespace, _consume_ Prometheus `MetricsReceiver`.
@@ -188,17 +204,19 @@ The following components, grouped by namespace, _consume_ Prometheus `MetricsRec
 <!-- START GENERATED SECTION: CONSUMERS OF Prometheus `MetricsReceiver` -->
 
 {{< collapse title="otelcol" >}}
+
 - [otelcol.exporter.prometheus](../components/otelcol/otelcol.exporter.prometheus)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="prometheus" >}}
+
 - [prometheus.operator.podmonitors](../components/prometheus/prometheus.operator.podmonitors)
 - [prometheus.operator.probes](../components/prometheus/prometheus.operator.probes)
 - [prometheus.operator.servicemonitors](../components/prometheus/prometheus.operator.servicemonitors)
 - [prometheus.receive_http](../components/prometheus/prometheus.receive_http)
 - [prometheus.relabel](../components/prometheus/prometheus.relabel)
 - [prometheus.scrape](../components/prometheus/prometheus.scrape)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 <!-- END GENERATED SECTION: CONSUMERS OF Prometheus `MetricsReceiver` -->
 
@@ -209,6 +227,7 @@ Components that consume `LogsReceiver` as an argument typically send logs to it.
 Use the following components to build your Loki logs pipeline:
 
 <!-- NOTE: this title is used as an anchor in links. Do not change. -->
+
 ### Loki `LogsReceiver` Exporters
 
 The following components, grouped by namespace, _export_ Loki `LogsReceiver`.
@@ -216,20 +235,23 @@ The following components, grouped by namespace, _export_ Loki `LogsReceiver`.
 <!-- START GENERATED SECTION: EXPORTERS OF Loki `LogsReceiver` -->
 
 {{< collapse title="loki" >}}
+
 - [loki.echo](../components/loki/loki.echo)
 - [loki.process](../components/loki/loki.process)
 - [loki.relabel](../components/loki/loki.relabel)
 - [loki.secretfilter](../components/loki/loki.secretfilter)
 - [loki.write](../components/loki/loki.write)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="otelcol" >}}
+
 - [otelcol.receiver.loki](../components/otelcol/otelcol.receiver.loki)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 <!-- END GENERATED SECTION: EXPORTERS OF Loki `LogsReceiver` -->
 
 <!-- NOTE: this title is used as an anchor in links. Do not change. -->
+
 ### Loki `LogsReceiver` Consumers
 
 The following components, grouped by namespace, _consume_ Loki `LogsReceiver`.
@@ -237,10 +259,12 @@ The following components, grouped by namespace, _consume_ Loki `LogsReceiver`.
 <!-- START GENERATED SECTION: CONSUMERS OF Loki `LogsReceiver` -->
 
 {{< collapse title="faro" >}}
+
 - [faro.receiver](../components/faro/faro.receiver)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="loki" >}}
+
 - [loki.process](../components/loki/loki.process)
 - [loki.relabel](../components/loki/loki.relabel)
 - [loki.secretfilter](../components/loki/loki.secretfilter)
@@ -260,11 +284,12 @@ The following components, grouped by namespace, _consume_ Loki `LogsReceiver`.
 - [loki.source.podlogs](../components/loki/loki.source.podlogs)
 - [loki.source.syslog](../components/loki/loki.source.syslog)
 - [loki.source.windowsevent](../components/loki/loki.source.windowsevent)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="otelcol" >}}
+
 - [otelcol.exporter.loki](../components/otelcol/otelcol.exporter.loki)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 <!-- END GENERATED SECTION: CONSUMERS OF Loki `LogsReceiver` -->
 
@@ -278,6 +303,7 @@ Refer to the component reference pages for more details on what is supported.
 Use the following components to build your OpenTelemetry pipeline:
 
 <!-- NOTE: this title is used as an anchor in links. Do not change. -->
+
 ### OpenTelemetry `otelcol.Consumer` Exporters
 
 The following components, grouped by namespace, _export_ OpenTelemetry `otelcol.Consumer`.
@@ -285,6 +311,7 @@ The following components, grouped by namespace, _export_ OpenTelemetry `otelcol.
 <!-- START GENERATED SECTION: EXPORTERS OF OpenTelemetry `otelcol.Consumer` -->
 
 {{< collapse title="otelcol" >}}
+
 - [otelcol.connector.host_info](../components/otelcol/otelcol.connector.host_info)
 - [otelcol.connector.servicegraph](../components/otelcol/otelcol.connector.servicegraph)
 - [otelcol.connector.spanlogs](../components/otelcol/otelcol.connector.spanlogs)
@@ -312,11 +339,12 @@ The following components, grouped by namespace, _export_ OpenTelemetry `otelcol.
 - [otelcol.processor.span](../components/otelcol/otelcol.processor.span)
 - [otelcol.processor.tail_sampling](../components/otelcol/otelcol.processor.tail_sampling)
 - [otelcol.processor.transform](../components/otelcol/otelcol.processor.transform)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 <!-- END GENERATED SECTION: EXPORTERS OF OpenTelemetry `otelcol.Consumer` -->
 
 <!-- NOTE: this title is used as an anchor in links. Do not change. -->
+
 ### OpenTelemetry `otelcol.Consumer` Consumers
 
 The following components, grouped by namespace, _consume_ OpenTelemetry `otelcol.Consumer`.
@@ -324,14 +352,17 @@ The following components, grouped by namespace, _consume_ OpenTelemetry `otelcol
 <!-- START GENERATED SECTION: CONSUMERS OF OpenTelemetry `otelcol.Consumer` -->
 
 {{< collapse title="beyla" >}}
+
 - [beyla.ebpf](../components/beyla/beyla.ebpf)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="faro" >}}
+
 - [faro.receiver](../components/faro/faro.receiver)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 {{< collapse title="otelcol" >}}
+
 - [otelcol.connector.host_info](../components/otelcol/otelcol.connector.host_info)
 - [otelcol.connector.servicegraph](../components/otelcol/otelcol.connector.servicegraph)
 - [otelcol.connector.spanlogs](../components/otelcol/otelcol.connector.spanlogs)
@@ -360,7 +391,7 @@ The following components, grouped by namespace, _consume_ OpenTelemetry `otelcol
 - [otelcol.receiver.prometheus](../components/otelcol/otelcol.receiver.prometheus)
 - [otelcol.receiver.vcenter](../components/otelcol/otelcol.receiver.vcenter)
 - [otelcol.receiver.zipkin](../components/otelcol/otelcol.receiver.zipkin)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 <!-- END GENERATED SECTION: CONSUMERS OF OpenTelemetry `otelcol.Consumer` -->
 
@@ -372,6 +403,7 @@ Components that can consume Pyroscope profiles can be passed the `ProfilesReceiv
 Use the following components to build your Pyroscope profiles pipeline:
 
 <!-- NOTE: this title is used as an anchor in links. Do not change. -->
+
 ### Pyroscope `ProfilesReceiver` Exporters
 
 The following components, grouped by namespace, _export_ Pyroscope `ProfilesReceiver`.
@@ -379,12 +411,14 @@ The following components, grouped by namespace, _export_ Pyroscope `ProfilesRece
 <!-- START GENERATED SECTION: EXPORTERS OF Pyroscope `ProfilesReceiver` -->
 
 {{< collapse title="pyroscope" >}}
+
 - [pyroscope.write](../components/pyroscope/pyroscope.write)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 <!-- END GENERATED SECTION: EXPORTERS OF Pyroscope `ProfilesReceiver` -->
 
 <!-- NOTE: this title is used as an anchor in links. Do not change. -->
+
 ### Pyroscope `ProfilesReceiver` Consumers
 
 The following components, grouped by namespace, _consume_ Pyroscope `ProfilesReceiver`.
@@ -392,10 +426,11 @@ The following components, grouped by namespace, _consume_ Pyroscope `ProfilesRec
 <!-- START GENERATED SECTION: CONSUMERS OF Pyroscope `ProfilesReceiver` -->
 
 {{< collapse title="pyroscope" >}}
+
 - [pyroscope.ebpf](../components/pyroscope/pyroscope.ebpf)
 - [pyroscope.java](../components/pyroscope/pyroscope.java)
 - [pyroscope.receive_http](../components/pyroscope/pyroscope.receive_http)
 - [pyroscope.scrape](../components/pyroscope/pyroscope.scrape)
-{{< /collapse >}}
+  {{< /collapse >}}
 
 <!-- END GENERATED SECTION: CONSUMERS OF Pyroscope `ProfilesReceiver` -->
diff --git a/docs/sources/reference/components/beyla/beyla.ebpf.md b/docs/sources/reference/components/beyla/beyla.ebpf.md
index ae711052ca..e1b9752406 100644
--- a/docs/sources/reference/components/beyla/beyla.ebpf.md
+++ b/docs/sources/reference/components/beyla/beyla.ebpf.md
@@ -102,15 +102,15 @@ If `cluster_name` isn't set, Beyla tries to detect the cluster name from the Kub
 
 If `enable` is set to `true`, Beyla decorates the metrics and traces with Kubernetes metadata. The following labels are added:
 
-* `k8s.namespace.name`
-* `k8s.deployment.name`
-* `k8s.statefulset.name`
-* `k8s.replicaset.name`
-* `k8s.daemonset.name`
-* `k8s.node.name`
-* `k8s.pod.name`
-* `k8s.pod.uid`
-* `k8s.pod.start_time`
+- `k8s.namespace.name`
+- `k8s.deployment.name`
+- `k8s.statefulset.name`
+- `k8s.replicaset.name`
+- `k8s.daemonset.name`
+- `k8s.node.name`
+- `k8s.pod.name`
+- `k8s.pod.uid`
+- `k8s.pod.start_time`
 
 If `enable` is set to `false`, the Kubernetes metadata decorator is disabled.
 
@@ -170,20 +170,20 @@ The `metrics` block configures which metrics Beyla collects.
 
 `features` is a list of features to enable for the metrics. The following features are available:
 
-* `application` exports application-level metrics.
-* `application_process` exports metrics about the processes that run the instrumented application.
-* `application_service_graph` exports application-level service graph metrics.
-* `application_span` exports application-level metrics in traces span metrics format.
-* `network` exports network-level metrics.
+- `application` exports application-level metrics.
+- `application_process` exports metrics about the processes that run the instrumented application.
+- `application_service_graph` exports application-level service graph metrics.
+- `application_span` exports application-level metrics in traces span metrics format.
+- `network` exports network-level metrics.
 
 `instrumentations` is a list of instrumentations to enable for the metrics. The following instrumentations are available:
 
-* `*` enables all `instrumentations`. If `*` is present in the list, the other values are ignored.
-* `grpc` enables the collection of gRPC application metrics.
-* `http` enables the collection of HTTP/HTTPS/HTTP2 application metrics.
-* `kafka` enables the collection of Kafka client/server message queue metrics.
-* `redis` enables the collection of Redis client/server database metrics.
-* `sql` enables the collection of SQL database client call metrics.
+- `*` enables all `instrumentations`. If `*` is present in the list, the other values are ignored.
+- `grpc` enables the collection of gRPC application metrics.
+- `http` enables the collection of HTTP/HTTPS/HTTP2 application metrics.
+- `kafka` enables the collection of Kafka client/server message queue metrics.
+- `redis` enables the collection of Redis client/server database metrics.
+- `sql` enables the collection of SQL database client call metrics.
 
 #### `network`
 
@@ -206,24 +206,24 @@ The `routes` block configures the routes to match HTTP paths into user-provided
 
 `ignore_mode` properties are:
 
-* `all` discards metrics and traces matching the `ignored_patterns`.
-* `metrics` discards only the metrics that match the `ignored_patterns`. No trace events are ignored.
-* `traces` discards only the traces that match the `ignored_patterns`. No metric events are ignored.
+- `all` discards metrics and traces matching the `ignored_patterns`.
+- `metrics` discards only the metrics that match the `ignored_patterns`. No trace events are ignored.
+- `traces` discards only the traces that match the `ignored_patterns`. No metric events are ignored.
 
 `patterns` and `ignore_patterns` are a list of patterns which a URL path with specific tags which allow for grouping path segments (or ignored them).
 The matcher tags can be in the `:name` or `{name}` format.
 
 `unmatched` properties are:
 
-* `heuristic` automatically derives the `http.route` field property from the path value based on the following rules:
-  * Any path components that have numbers or characters outside of the ASCII alphabet (or `-` and _), are replaced by an asterisk `*`.
-  * Any alphabetical components that don't look like words are replaced by an asterisk `*`.
-* `path` copies the `http.route` field property to the path value.
+- `heuristic` automatically derives the `http.route` field property from the path value based on the following rules:
+  - Any path components that have numbers or characters outside of the ASCII alphabet (or `-` and \_), are replaced by an asterisk `*`.
+  - Any alphabetical components that don't look like words are replaced by an asterisk `*`.
+- `path` copies the `http.route` field property to the path value.
   {{< admonition type="caution" >}}
   This property could lead to a cardinality explosion on the ingester side.
   {{< /admonition >}}
-* `unset` leaves the `http.route` property as unset.
-* `wildcard` sets the `http.route` field property to a generic asterisk-based `/**` value.
+- `unset` leaves the `http.route` property as unset.
+- `wildcard` sets the `http.route` field property to a generic asterisk-based `/**` value.
 
 ## Exported fields
 
@@ -278,10 +278,10 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<OPEN_PORT>`_: The port of the running service for Beyla automatically instrumented with eBPF.
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<OPEN_PORT>`_: The port of the running service for Beyla automatically instrumented with eBPF.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 ### Traces
 
@@ -310,8 +310,8 @@ otelcol.exporter.otlp "default" {
 
 Replace the following:
 
-* _`<OPEN_PORT>`_: The port of the running service for Beyla automatically instrumented with eBPF.
-* _`<OTLP_ENDPOINT>`_: The endpoint of the OpenTelemetry Collector to send traces to.
+- _`<OPEN_PORT>`_: The port of the running service for Beyla automatically instrumented with eBPF.
+- _`<OTLP_ENDPOINT>`_: The endpoint of the OpenTelemetry Collector to send traces to.
 
 [Grafana Beyla]: https://github.com/grafana/beyla
 [eBPF]: https://ebpf.io/
diff --git a/docs/sources/reference/components/discovery/discovery.azure.md b/docs/sources/reference/components/discovery/discovery.azure.md
index ccfb793970..ba0a8656b9 100644
--- a/docs/sources/reference/components/discovery/discovery.azure.md
+++ b/docs/sources/reference/components/discovery/discovery.azure.md
@@ -90,19 +90,19 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_azure_machine_computer_name`: The host OS name of the VM.
-* `__meta_azure_machine_id`: The UUID of the Azure VM.
-* `__meta_azure_machine_location`: The region the VM is in.
-* `__meta_azure_machine_name`: The name of the VM.
-* `__meta_azure_machine_os_type`: The OS the VM is running, either `Linux` or `Windows`.
-* `__meta_azure_machine_private_ip`: The private IP address of the VM.
-* `__meta_azure_machine_public_ip`: The public IP address of the VM.
-* `__meta_azure_machine_resource_group`: The name of the resource group the VM is in.
-* `__meta_azure_machine_scale_set`: The name of the scale set the VM is in.
-* `__meta_azure_machine_size`: The size of the VM.
-* `__meta_azure_machine_tag_*`: A tag on the VM. There is one label per tag.
-* `__meta_azure_subscription_id`: The Azure subscription ID.
-* `__meta_azure_tenant_id`: The Azure tenant ID.
+- `__meta_azure_machine_computer_name`: The host OS name of the VM.
+- `__meta_azure_machine_id`: The UUID of the Azure VM.
+- `__meta_azure_machine_location`: The region the VM is in.
+- `__meta_azure_machine_name`: The name of the VM.
+- `__meta_azure_machine_os_type`: The OS the VM is running, either `Linux` or `Windows`.
+- `__meta_azure_machine_private_ip`: The private IP address of the VM.
+- `__meta_azure_machine_public_ip`: The public IP address of the VM.
+- `__meta_azure_machine_resource_group`: The name of the resource group the VM is in.
+- `__meta_azure_machine_scale_set`: The name of the scale set the VM is in.
+- `__meta_azure_machine_size`: The size of the VM.
+- `__meta_azure_machine_tag_*`: A tag on the VM. There is one label per tag.
+- `__meta_azure_subscription_id`: The Azure subscription ID.
+- `__meta_azure_tenant_id`: The Azure tenant ID.
 
 Each discovered VM maps to a single target.
 The `__address__` label is set to the `private_ip:port` of the VM if the private IP is an IPv4 address, or `[private_ip]:port` if the private IP of the VM is an IPv6 address.
@@ -152,13 +152,13 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<AZURE_SUBSCRIPTION_ID>`_: Your Azure subscription ID.
-* _`<AZURE_CLIENT_ID>`_: Your Azure client ID.
-* _`<AZURE_CLIENT_SECRET>`_: Your Azure client secret.
-* _`<AZURE_TENANT_ID>`_: Your Azure tenant ID.
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<AZURE_SUBSCRIPTION_ID>`_: Your Azure subscription ID.
+- _`<AZURE_CLIENT_ID>`_: Your Azure client ID.
+- _`<AZURE_CLIENT_SECRET>`_: Your Azure client secret.
+- _`<AZURE_TENANT_ID>`_: Your Azure tenant ID.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.consul.md b/docs/sources/reference/components/discovery/discovery.consul.md
index 8b7d9359a1..ed93c8ad08 100644
--- a/docs/sources/reference/components/discovery/discovery.consul.md
+++ b/docs/sources/reference/components/discovery/discovery.consul.md
@@ -51,13 +51,13 @@ You can use the following arguments with `discovery.consul`:
 | `token`                  | `secret`            | Secret token used to access the Consul API.                                                                     |                  | no       |
 | `username`               | `string`            | The username to use. Deprecated in favor of the `basic_auth` configuration.                                     |                  | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -118,17 +118,17 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_consul_address`: The address of the target.
-* `__meta_consul_metadata_<key>`: Each node metadata key value of the target.
-* `__meta_consul_node`: The node name defined for the target.
-* `__meta_consul_partition`: The administrator partition name where the service is registered.
-* `__meta_consul_service_address`: The service address of the target.
-* `__meta_consul_service_id`: The service ID of the target.
-* `__meta_consul_service_metadata_<key>`: Each service metadata key value of the target.
-* `__meta_consul_service_port`: The service port of the target.
-* `__meta_consul_service`: The name of the service the target belongs to.
-* `__meta_consul_tagged_address_<key>`: Each node tagged address key value of the target.
-* `__meta_consul_tags`: The list of tags of the target joined by the tag separator.
+- `__meta_consul_address`: The address of the target.
+- `__meta_consul_metadata_<key>`: Each node metadata key value of the target.
+- `__meta_consul_node`: The node name defined for the target.
+- `__meta_consul_partition`: The administrator partition name where the service is registered.
+- `__meta_consul_service_address`: The service address of the target.
+- `__meta_consul_service_id`: The service ID of the target.
+- `__meta_consul_service_metadata_<key>`: Each service metadata key value of the target.
+- `__meta_consul_service_port`: The service port of the target.
+- `__meta_consul_service`: The name of the service the target belongs to.
+- `__meta_consul_tagged_address_<key>`: Each node tagged address key value of the target.
+- `__meta_consul_tags`: The list of tags of the target joined by the tag separator.
 
 ## Component health
 
@@ -175,9 +175,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.consulagent.md b/docs/sources/reference/components/discovery/discovery.consulagent.md
index 67bd608d52..48e2b8a5b8 100644
--- a/docs/sources/reference/components/discovery/discovery.consulagent.md
+++ b/docs/sources/reference/components/discovery/discovery.consulagent.md
@@ -67,18 +67,18 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_consulagent_address`: The address of the target.
-* `__meta_consulagent_dc`: The data center name for the target.
-* `__meta_consulagent_health`: The health status of the service.
-* `__meta_consulagent_metadata_<key>`: Each node metadata key value of the target.
-* `__meta_consulagent_node`: The node name defined for the target.
-* `__meta_consulagent_service_address`: The service address of the target.
-* `__meta_consulagent_service_id`: The service ID of the target.
-* `__meta_consulagent_service_metadata_<key>`: Each service metadata key value of the target.
-* `__meta_consulagent_service_port`: The service port of the target.
-* `__meta_consulagent_service`: The name of the service the target belongs to.
-* `__meta_consulagent_tagged_address_<key>`: Each node tagged address key value of the target.
-* `__meta_consulagent_tags`: The list of tags of the target joined by the tag separator.
+- `__meta_consulagent_address`: The address of the target.
+- `__meta_consulagent_dc`: The data center name for the target.
+- `__meta_consulagent_health`: The health status of the service.
+- `__meta_consulagent_metadata_<key>`: Each node metadata key value of the target.
+- `__meta_consulagent_node`: The node name defined for the target.
+- `__meta_consulagent_service_address`: The service address of the target.
+- `__meta_consulagent_service_id`: The service ID of the target.
+- `__meta_consulagent_service_metadata_<key>`: Each service metadata key value of the target.
+- `__meta_consulagent_service_port`: The service port of the target.
+- `__meta_consulagent_service`: The name of the service the target belongs to.
+- `__meta_consulagent_tagged_address_<key>`: Each node tagged address key value of the target.
+- `__meta_consulagent_tags`: The list of tags of the target joined by the tag separator.
 
 ## Component health
 
@@ -91,12 +91,13 @@ In those cases, exported fields retain their last healthy values.
 
 ## Debug metrics
 
-* `discovery_consulagent_rpc_duration_seconds` (SummaryVec): The duration of a Consul Agent RPC call in seconds.
-* `discovery_consulagent_rpc_failures_total` (Counter): The number of Consul Agent RPC call failures.
+- `discovery_consulagent_rpc_duration_seconds` (SummaryVec): The duration of a Consul Agent RPC call in seconds.
+- `discovery_consulagent_rpc_failures_total` (Counter): The number of Consul Agent RPC call failures.
 
 ## Example
 
 <!-- TODO: Include a logging example -->
+
 This example discovers targets from a Consul Agent for the specified list of services:
 
 ```alloy
@@ -127,9 +128,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.digitalocean.md b/docs/sources/reference/components/discovery/discovery.digitalocean.md
index 4d422b9885..beb84dcb0a 100644
--- a/docs/sources/reference/components/discovery/discovery.digitalocean.md
+++ b/docs/sources/reference/components/discovery/discovery.digitalocean.md
@@ -63,19 +63,19 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_digitalocean_droplet_id`: ID of the Droplet.
-* `__meta_digitalocean_droplet_name`: Name of the Droplet.
-* `__meta_digitalocean_features`: Optional properties configured for the Droplet, such as IPV6 networking, private networking, or backups.
-* `__meta_digitalocean_image_name`: Name of the image used to create the Droplet.
-* `__meta_digitalocean_image`: The image slug (unique text identifier of the image) used to create the Droplet.
-* `__meta_digitalocean_private_ipv4`: The private IPv4 address of the Droplet.
-* `__meta_digitalocean_public_ipv4`: The public IPv4 address of the Droplet.
-* `__meta_digitalocean_public_ipv6`: The public IPv6 address of the Droplet.
-* `__meta_digitalocean_region`: The region the Droplet is running in.
-* `__meta_digitalocean_size`: The size of the Droplet.
-* `__meta_digitalocean_status`: The current status of the Droplet.
-* `__meta_digitalocean_tags`: The tags assigned to the Droplet.
-* `__meta_digitalocean_vpc`: The ID of the VPC where the Droplet is located.
+- `__meta_digitalocean_droplet_id`: ID of the Droplet.
+- `__meta_digitalocean_droplet_name`: Name of the Droplet.
+- `__meta_digitalocean_features`: Optional properties configured for the Droplet, such as IPV6 networking, private networking, or backups.
+- `__meta_digitalocean_image_name`: Name of the image used to create the Droplet.
+- `__meta_digitalocean_image`: The image slug (unique text identifier of the image) used to create the Droplet.
+- `__meta_digitalocean_private_ipv4`: The private IPv4 address of the Droplet.
+- `__meta_digitalocean_public_ipv4`: The public IPv4 address of the Droplet.
+- `__meta_digitalocean_public_ipv6`: The public IPv6 address of the Droplet.
+- `__meta_digitalocean_region`: The region the Droplet is running in.
+- `__meta_digitalocean_size`: The size of the Droplet.
+- `__meta_digitalocean_status`: The current status of the Droplet.
+- `__meta_digitalocean_tags`: The tags assigned to the Droplet.
+- `__meta_digitalocean_vpc`: The ID of the VPC where the Droplet is located.
 
 Each discovered Droplet maps to one target.
 
@@ -122,9 +122,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.dns.md b/docs/sources/reference/components/discovery/discovery.dns.md
index 6562da6c94..94928d0191 100644
--- a/docs/sources/reference/components/discovery/discovery.dns.md
+++ b/docs/sources/reference/components/discovery/discovery.dns.md
@@ -45,11 +45,11 @@ The following field is exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_dns_mx_record_target`: Target field of the MX record.
-* `__meta_dns_name`: Name of the record that produced the discovered target.
-* `__meta_dns_ns_record_target`: Target field of the NS record.
-* `__meta_dns_srv_record_port`: Port field of the SRV record.
-* `__meta_dns_srv_record_target`: Target field of the SRV record.
+- `__meta_dns_mx_record_target`: Target field of the MX record.
+- `__meta_dns_name`: Name of the record that produced the discovered target.
+- `__meta_dns_ns_record_target`: Target field of the NS record.
+- `__meta_dns_srv_record_port`: Port field of the SRV record.
+- `__meta_dns_srv_record_target`: Target field of the SRV record.
 
 ## Component health
 
@@ -94,9 +94,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.docker.md b/docs/sources/reference/components/discovery/discovery.docker.md
index aa1df6c6b8..4b53ca8246 100644
--- a/docs/sources/reference/components/discovery/discovery.docker.md
+++ b/docs/sources/reference/components/discovery/discovery.docker.md
@@ -41,13 +41,13 @@ You can use the following arguments with `discovery.docker`:
 | `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |               | no       |
 | `refresh_interval`       | `duration`          | Frequency to refresh list of containers.                                                         | `"1m"`        | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
 [arguments]: #arguments
 
@@ -123,20 +123,20 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_docker_container_id`: ID of the container.
-* `__meta_docker_container_label_<labelname>`: Each label from the container.
-* `__meta_docker_container_name`: Name of the container.
-* `__meta_docker_container_network_mode`: Network mode of the container.
-* `__meta_docker_network_id`: ID of the Docker network the container is in.
-* `__meta_docker_network_ingress`: Set to `true` if the Docker network is an ingress network.
-* `__meta_docker_network_internal`: Set to `true` if the Docker network is an internal network.
-* `__meta_docker_network_ip`: The IP of the container in the network.
-* `__meta_docker_network_label_<labelname>`: Each label from the network the container is in.
-* `__meta_docker_network_name`: Name of the Docker network the container is in.
-* `__meta_docker_network_scope`: The scope of the network the container is in.
-* `__meta_docker_port_private`: The private port on the container.
-* `__meta_docker_port_public_ip`: The public IP of the container, if a port mapping exists.
-* `__meta_docker_port_public`: The publicly exposed port from the container, if a port mapping exists.
+- `__meta_docker_container_id`: ID of the container.
+- `__meta_docker_container_label_<labelname>`: Each label from the container.
+- `__meta_docker_container_name`: Name of the container.
+- `__meta_docker_container_network_mode`: Network mode of the container.
+- `__meta_docker_network_id`: ID of the Docker network the container is in.
+- `__meta_docker_network_ingress`: Set to `true` if the Docker network is an ingress network.
+- `__meta_docker_network_internal`: Set to `true` if the Docker network is an internal network.
+- `__meta_docker_network_ip`: The IP of the container in the network.
+- `__meta_docker_network_label_<labelname>`: Each label from the network the container is in.
+- `__meta_docker_network_name`: Name of the Docker network the container is in.
+- `__meta_docker_network_scope`: The scope of the network the container is in.
+- `__meta_docker_port_private`: The private port on the container.
+- `__meta_docker_port_public_ip`: The public IP of the container, if a port mapping exists.
+- `__meta_docker_port_public`: The publicly exposed port from the container, if a port mapping exists.
 
 Each discovered container maps to one target per unique combination of networks and port mappings used by the container.
 
@@ -183,9 +183,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 ### Windows hosts
 
@@ -219,9 +219,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.dockerswarm.md b/docs/sources/reference/components/discovery/discovery.dockerswarm.md
index 5aacbd6eac..917d0f2af4 100644
--- a/docs/sources/reference/components/discovery/discovery.dockerswarm.md
+++ b/docs/sources/reference/components/discovery/discovery.dockerswarm.md
@@ -40,13 +40,13 @@ You can use the following arguments with `discovery.dockerswarm`:
 | `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                                                          |         | no       |
 | `refresh_interval`       | `duration`          | Interval at which to refresh the list of targets.                                                                             | `"60s"` | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -92,9 +92,9 @@ The `filter` block limits the discovery process to a subset of available resourc
 You can define multiple `filter` blocks within the `discovery.dockerswarm` block.
 The list of available filters depends on the `role`:
 
-* [nodes filters](https://docs.docker.com/engine/api/v1.40/#operation/NodeList)
-* [services filters](https://docs.docker.com/engine/api/v1.40/#operation/ServiceList)
-* [tasks filters](https://docs.docker.com/engine/api/v1.40/#operation/TaskList)
+- [nodes filters](https://docs.docker.com/engine/api/v1.40/#operation/NodeList)
+- [services filters](https://docs.docker.com/engine/api/v1.40/#operation/ServiceList)
+- [tasks filters](https://docs.docker.com/engine/api/v1.40/#operation/TaskList)
 
 You can use the following arguments to configure a filter.
 
@@ -135,21 +135,21 @@ If a service has no published ports, a target per service is created using the `
 
 Available meta labels:
 
-* `__meta_dockerswarm_network_id`: The ID of the network.
-* `__meta_dockerswarm_network_ingress`: Whether the network is ingress.
-* `__meta_dockerswarm_network_internal`: Whether the network is internal.
-* `__meta_dockerswarm_network_label_<labelname>`: Each label of the network.
-* `__meta_dockerswarm_network_name`: The name of the network.
-* `__meta_dockerswarm_network_scope`: The scope of the network.
-* `__meta_dockerswarm_service_endpoint_port_name`: The name of the endpoint port, if available.
-* `__meta_dockerswarm_service_endpoint_port_publish_mode`: The publish mode of the endpoint port.
-* `__meta_dockerswarm_service_id`: The ID of the service.
-* `__meta_dockerswarm_service_label_<labelname>`: Each label of the service.
-* `__meta_dockerswarm_service_mode`: The mode of the service.
-* `__meta_dockerswarm_service_name`: The name of the service.
-* `__meta_dockerswarm_service_task_container_hostname`: The container hostname of the target, if available.
-* `__meta_dockerswarm_service_task_container_image`: The container image of the target.
-* `__meta_dockerswarm_service_updating_status`: The status of the service, if available.
+- `__meta_dockerswarm_network_id`: The ID of the network.
+- `__meta_dockerswarm_network_ingress`: Whether the network is ingress.
+- `__meta_dockerswarm_network_internal`: Whether the network is internal.
+- `__meta_dockerswarm_network_label_<labelname>`: Each label of the network.
+- `__meta_dockerswarm_network_name`: The name of the network.
+- `__meta_dockerswarm_network_scope`: The scope of the network.
+- `__meta_dockerswarm_service_endpoint_port_name`: The name of the endpoint port, if available.
+- `__meta_dockerswarm_service_endpoint_port_publish_mode`: The publish mode of the endpoint port.
+- `__meta_dockerswarm_service_id`: The ID of the service.
+- `__meta_dockerswarm_service_label_<labelname>`: Each label of the service.
+- `__meta_dockerswarm_service_mode`: The mode of the service.
+- `__meta_dockerswarm_service_name`: The name of the service.
+- `__meta_dockerswarm_service_task_container_hostname`: The container hostname of the target, if available.
+- `__meta_dockerswarm_service_task_container_image`: The container image of the target.
+- `__meta_dockerswarm_service_updating_status`: The status of the service, if available.
 
 ### `tasks`
 
@@ -159,33 +159,33 @@ If a task has no published ports, a target per task is created using the `port`
 
 Available meta labels:
 
-* `__meta_dockerswarm_container_label_<labelname>`: Each label of the container.
-* `__meta_dockerswarm_network_id`: The ID of the network.
-* `__meta_dockerswarm_network_ingress`: Whether the network is ingress.
-* `__meta_dockerswarm_network_internal`: Whether the network is internal.
-* `__meta_dockerswarm_network_label_<labelname>`: Each label of the network.
-* `__meta_dockerswarm_network_label`: Each label of the network.
-* `__meta_dockerswarm_network_name`: The name of the network.
-* `__meta_dockerswarm_network_scope`: The scope of the network.
-* `__meta_dockerswarm_node_address`: The address of the node.
-* `__meta_dockerswarm_node_availability`: The availability of the node.
-* `__meta_dockerswarm_node_hostname`: The hostname of the node.
-* `__meta_dockerswarm_node_id`: The ID of the node.
-* `__meta_dockerswarm_node_label_<labelname>`: Each label of the node.
-* `__meta_dockerswarm_node_platform_architecture`: The architecture of the node.
-* `__meta_dockerswarm_node_platform_os`: The operating system of the node.
-* `__meta_dockerswarm_node_role`: The role of the node.
-* `__meta_dockerswarm_node_status`: The status of the node.
-* `__meta_dockerswarm_service_id`: The ID of the service.
-* `__meta_dockerswarm_service_label_<labelname>`: Each label of the service.
-* `__meta_dockerswarm_service_mode`: The mode of the service.
-* `__meta_dockerswarm_service_name`: The name of the service.
-* `__meta_dockerswarm_task_container_id`: The container ID of the task.
-* `__meta_dockerswarm_task_desired_state`: The desired state of the task.
-* `__meta_dockerswarm_task_id`: The ID of the task.
-* `__meta_dockerswarm_task_port_publish_mode`: The publish mode of the task port.
-* `__meta_dockerswarm_task_slot`: The slot of the task.
-* `__meta_dockerswarm_task_state`: The state of the task.
+- `__meta_dockerswarm_container_label_<labelname>`: Each label of the container.
+- `__meta_dockerswarm_network_id`: The ID of the network.
+- `__meta_dockerswarm_network_ingress`: Whether the network is ingress.
+- `__meta_dockerswarm_network_internal`: Whether the network is internal.
+- `__meta_dockerswarm_network_label_<labelname>`: Each label of the network.
+- `__meta_dockerswarm_network_label`: Each label of the network.
+- `__meta_dockerswarm_network_name`: The name of the network.
+- `__meta_dockerswarm_network_scope`: The scope of the network.
+- `__meta_dockerswarm_node_address`: The address of the node.
+- `__meta_dockerswarm_node_availability`: The availability of the node.
+- `__meta_dockerswarm_node_hostname`: The hostname of the node.
+- `__meta_dockerswarm_node_id`: The ID of the node.
+- `__meta_dockerswarm_node_label_<labelname>`: Each label of the node.
+- `__meta_dockerswarm_node_platform_architecture`: The architecture of the node.
+- `__meta_dockerswarm_node_platform_os`: The operating system of the node.
+- `__meta_dockerswarm_node_role`: The role of the node.
+- `__meta_dockerswarm_node_status`: The status of the node.
+- `__meta_dockerswarm_service_id`: The ID of the service.
+- `__meta_dockerswarm_service_label_<labelname>`: Each label of the service.
+- `__meta_dockerswarm_service_mode`: The mode of the service.
+- `__meta_dockerswarm_service_name`: The name of the service.
+- `__meta_dockerswarm_task_container_id`: The container ID of the task.
+- `__meta_dockerswarm_task_desired_state`: The desired state of the task.
+- `__meta_dockerswarm_task_id`: The ID of the task.
+- `__meta_dockerswarm_task_port_publish_mode`: The publish mode of the task port.
+- `__meta_dockerswarm_task_slot`: The slot of the task.
+- `__meta_dockerswarm_task_state`: The state of the task.
 
 The `__meta_dockerswarm_network_*` meta labels aren't populated for ports which are published with mode=host.
 
@@ -195,19 +195,19 @@ The `nodes` role is used to discover [Swarm nodes](https://docs.docker.com/engin
 
 Available meta labels:
 
-* `__meta_dockerswarm_node_address`: The address of the node.
-* `__meta_dockerswarm_node_availability`: The availability of the node.
-* `__meta_dockerswarm_node_engine_version`: The version of the node engine.
-* `__meta_dockerswarm_node_hostname`: The hostname of the node.
-* `__meta_dockerswarm_node_id`: The ID of the node.
-* `__meta_dockerswarm_node_label_<labelname>`: Each label of the node.
-* `__meta_dockerswarm_node_manager_address`: The address of the manager component of the node.
-* `__meta_dockerswarm_node_manager_leader`: The leadership status of the manager component of the node (true or false).
-* `__meta_dockerswarm_node_manager_reachability`: The reachability of the manager component of the node.
-* `__meta_dockerswarm_node_platform_architecture`: The architecture of the node.
-* `__meta_dockerswarm_node_platform_os`: The operating system of the node.
-* `__meta_dockerswarm_node_role`: The role of the node.
-* `__meta_dockerswarm_node_status`: The status of the node.
+- `__meta_dockerswarm_node_address`: The address of the node.
+- `__meta_dockerswarm_node_availability`: The availability of the node.
+- `__meta_dockerswarm_node_engine_version`: The version of the node engine.
+- `__meta_dockerswarm_node_hostname`: The hostname of the node.
+- `__meta_dockerswarm_node_id`: The ID of the node.
+- `__meta_dockerswarm_node_label_<labelname>`: Each label of the node.
+- `__meta_dockerswarm_node_manager_address`: The address of the manager component of the node.
+- `__meta_dockerswarm_node_manager_leader`: The leadership status of the manager component of the node (true or false).
+- `__meta_dockerswarm_node_manager_reachability`: The reachability of the manager component of the node.
+- `__meta_dockerswarm_node_platform_architecture`: The architecture of the node.
+- `__meta_dockerswarm_node_platform_os`: The operating system of the node.
+- `__meta_dockerswarm_node_role`: The role of the node.
+- `__meta_dockerswarm_node_status`: The status of the node.
 
 ## Component health
 
@@ -261,9 +261,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.ec2.md b/docs/sources/reference/components/discovery/discovery.ec2.md
index fe761cbd9b..ed82988084 100644
--- a/docs/sources/reference/components/discovery/discovery.ec2.md
+++ b/docs/sources/reference/components/discovery/discovery.ec2.md
@@ -45,15 +45,15 @@ You can use the following arguments with `discovery.ec2`:
 | `role_arn`               | `string`            | AWS Role Amazon Resource Name (ARN), an alternative to using AWS API keys.                                              |         | no       |
 | `secret_key`             | `string`            | The AWS API key secret. If blank, the environment variable `AWS_SECRET_ACCESS_KEY` is used.                             |         | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`](#arguments) argument
-* [`bearer_token`](#arguments) argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`](#arguments) argument
+- [`bearer_token`](#arguments) argument
+- [`oauth2`][oauth2] block
 
- {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
+{{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
 ## Blocks
 
@@ -126,26 +126,26 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_ec2_ami`: The EC2 Amazon Machine Image.
-* `__meta_ec2_architecture`: The architecture of the instance.
-* `__meta_ec2_availability_zone_id`: The availability zone ID in which the instance is running. Requires `ec2:DescribeAvailabilityZones`.
-* `__meta_ec2_availability_zone`: The availability zone in which the instance is running.
-* `__meta_ec2_instance_id`: The EC2 instance ID.
-* `__meta_ec2_instance_lifecycle`: The lifecycle of the EC2 instance, set only for 'spot' or 'scheduled' instances, absent otherwise.
-* `__meta_ec2_instance_state`: The state of the EC2 instance.
-* `__meta_ec2_instance_type`: The type of the EC2 instance.
-* `__meta_ec2_ipv6_addresses`: Comma-separated list of IPv6 addresses assigned to the instance's network interfaces, if present.
-* `__meta_ec2_owner_id`: The ID of the AWS account that owns the EC2 instance.
-* `__meta_ec2_platform`: The Operating System platform, set to 'windows' on Windows servers, absent otherwise.
-* `__meta_ec2_primary_subnet_id`: The subnet ID of the primary network interface, if available.
-* `__meta_ec2_private_dns_name`: The private DNS name of the instance, if available.
-* `__meta_ec2_private_ip`: The private IP address of the instance, if present.
-* `__meta_ec2_public_dns_name`: The public DNS name of the instance, if available.
-* `__meta_ec2_public_ip`: The public IP address of the instance, if available.
-* `__meta_ec2_region`: The region of the instance.
-* `__meta_ec2_subnet_id`: Comma-separated list of subnets IDs in which the instance is running, if available.
-* `__meta_ec2_tag_<tagkey>`: Each tag value of the instance.
-* `__meta_ec2_vpc_id`: The ID of the VPC in which the instance is running, if available.
+- `__meta_ec2_ami`: The EC2 Amazon Machine Image.
+- `__meta_ec2_architecture`: The architecture of the instance.
+- `__meta_ec2_availability_zone_id`: The availability zone ID in which the instance is running. Requires `ec2:DescribeAvailabilityZones`.
+- `__meta_ec2_availability_zone`: The availability zone in which the instance is running.
+- `__meta_ec2_instance_id`: The EC2 instance ID.
+- `__meta_ec2_instance_lifecycle`: The lifecycle of the EC2 instance, set only for 'spot' or 'scheduled' instances, absent otherwise.
+- `__meta_ec2_instance_state`: The state of the EC2 instance.
+- `__meta_ec2_instance_type`: The type of the EC2 instance.
+- `__meta_ec2_ipv6_addresses`: Comma-separated list of IPv6 addresses assigned to the instance's network interfaces, if present.
+- `__meta_ec2_owner_id`: The ID of the AWS account that owns the EC2 instance.
+- `__meta_ec2_platform`: The Operating System platform, set to 'windows' on Windows servers, absent otherwise.
+- `__meta_ec2_primary_subnet_id`: The subnet ID of the primary network interface, if available.
+- `__meta_ec2_private_dns_name`: The private DNS name of the instance, if available.
+- `__meta_ec2_private_ip`: The private IP address of the instance, if present.
+- `__meta_ec2_public_dns_name`: The public DNS name of the instance, if available.
+- `__meta_ec2_public_ip`: The public IP address of the instance, if available.
+- `__meta_ec2_region`: The region of the instance.
+- `__meta_ec2_subnet_id`: Comma-separated list of subnets IDs in which the instance is running, if available.
+- `__meta_ec2_tag_<tagkey>`: Each tag value of the instance.
+- `__meta_ec2_vpc_id`: The ID of the VPC in which the instance is running, if available.
 
 ## Component health
 
@@ -186,9 +186,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.eureka.md b/docs/sources/reference/components/discovery/discovery.eureka.md
index 98a6fa04d1..25593d9623 100644
--- a/docs/sources/reference/components/discovery/discovery.eureka.md
+++ b/docs/sources/reference/components/discovery/discovery.eureka.md
@@ -39,13 +39,13 @@ You can use the following arguments with `discovery.eureka`:
 | `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
 | `refresh_interval`       | `duration`          | Interval at which to refresh the list of targets.                                                | `30s`   | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
 [arguments]: #arguments
 
@@ -105,24 +105,24 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_eureka_app_instance_country_id`
-* `__meta_eureka_app_instance_datacenterinfo_metadata_`
-* `__meta_eureka_app_instance_datacenterinfo_name`
-* `__meta_eureka_app_instance_healthcheck_url`
-* `__meta_eureka_app_instance_homepage_url`
-* `__meta_eureka_app_instance_hostname`
-* `__meta_eureka_app_instance_id`
-* `__meta_eureka_app_instance_ip_addr`
-* `__meta_eureka_app_instance_metadata_`
-* `__meta_eureka_app_instance_port_enabled`
-* `__meta_eureka_app_instance_port`
-* `__meta_eureka_app_instance_secure_port_enabled`
-* `__meta_eureka_app_instance_secure_port`
-* `__meta_eureka_app_instance_secure_vip_address`
-* `__meta_eureka_app_instance_status`
-* `__meta_eureka_app_instance_statuspage_url`
-* `__meta_eureka_app_instance_vip_address`
-* `__meta_eureka_app_name`
+- `__meta_eureka_app_instance_country_id`
+- `__meta_eureka_app_instance_datacenterinfo_metadata_`
+- `__meta_eureka_app_instance_datacenterinfo_name`
+- `__meta_eureka_app_instance_healthcheck_url`
+- `__meta_eureka_app_instance_homepage_url`
+- `__meta_eureka_app_instance_hostname`
+- `__meta_eureka_app_instance_id`
+- `__meta_eureka_app_instance_ip_addr`
+- `__meta_eureka_app_instance_metadata_`
+- `__meta_eureka_app_instance_port_enabled`
+- `__meta_eureka_app_instance_port`
+- `__meta_eureka_app_instance_secure_port_enabled`
+- `__meta_eureka_app_instance_secure_port`
+- `__meta_eureka_app_instance_secure_vip_address`
+- `__meta_eureka_app_instance_status`
+- `__meta_eureka_app_instance_statuspage_url`
+- `__meta_eureka_app_instance_vip_address`
+- `__meta_eureka_app_name`
 
 ## Component health
 
@@ -163,9 +163,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.file.md b/docs/sources/reference/components/discovery/discovery.file.md
index 5884ac3942..64cba8d513 100644
--- a/docs/sources/reference/components/discovery/discovery.file.md
+++ b/docs/sources/reference/components/discovery/discovery.file.md
@@ -45,7 +45,7 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_filepath`: The absolute path to the file the target was discovered from.
+- `__meta_filepath`: The absolute path to the file the target was discovered from.
 
 ## Component health
 
@@ -69,13 +69,13 @@ The following examples show you how to configure the `discovery.file` component.
 ```json
 [
   {
-    "targets": [ "127.0.0.1:9091", "127.0.0.1:9092" ],
+    "targets": ["127.0.0.1:9091", "127.0.0.1:9092"],
     "labels": {
       "environment": "dev"
     }
   },
   {
-    "targets": [ "127.0.0.1:9093" ],
+    "targets": ["127.0.0.1:9093"],
     "labels": {
       "environment": "prod"
     }
@@ -85,12 +85,12 @@ The following examples show you how to configure the `discovery.file` component.
 
 ```yaml
 - targets:
-  - 127.0.0.1:9999
-  - 127.0.0.1:10101
+    - 127.0.0.1:9999
+    - 127.0.0.1:10101
   labels:
     job: worker
 - targets:
-  - 127.0.0.1:9090
+    - 127.0.0.1:9090
   labels:
     job: prometheus
 ```
@@ -123,9 +123,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 ### File discovery with retained file path label
 
@@ -165,9 +165,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.gce.md b/docs/sources/reference/components/discovery/discovery.gce.md
index 6439c05039..35d9eea769 100644
--- a/docs/sources/reference/components/discovery/discovery.gce.md
+++ b/docs/sources/reference/components/discovery/discovery.gce.md
@@ -64,19 +64,19 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_gce_instance_id`: The numeric ID of the instance.
-* `__meta_gce_instance_name`: The name of the instance.
-* `__meta_gce_interface_ipv4_NAME`: The IPv4 address of each named interface.
-* `__meta_gce_label_LABEL_NAME`: Each GCE label of the instance.
-* `__meta_gce_machine_type`: The full or partial URL of the machine type of the instance.
-* `__meta_gce_metadata_NAME`: Each metadata item of the instance.
-* `__meta_gce_network`: The network URL of the instance.
-* `__meta_gce_private_ip`: The private IP address of the instance.
-* `__meta_gce_project`: The GCP project in which the instance is running.
-* `__meta_gce_public_ip`: The public IP address of the instance, if present.
-* `__meta_gce_subnetwork`: The subnetwork URL of the instance.
-* `__meta_gce_tags`: A comma separated list of instance tags.
-* `__meta_gce_zone`: The GCE zone URL in which the instance is running.
+- `__meta_gce_instance_id`: The numeric ID of the instance.
+- `__meta_gce_instance_name`: The name of the instance.
+- `__meta_gce_interface_ipv4_NAME`: The IPv4 address of each named interface.
+- `__meta_gce_label_LABEL_NAME`: Each GCE label of the instance.
+- `__meta_gce_machine_type`: The full or partial URL of the machine type of the instance.
+- `__meta_gce_metadata_NAME`: Each metadata item of the instance.
+- `__meta_gce_network`: The network URL of the instance.
+- `__meta_gce_private_ip`: The private IP address of the instance.
+- `__meta_gce_project`: The GCP project in which the instance is running.
+- `__meta_gce_public_ip`: The public IP address of the instance, if present.
+- `__meta_gce_subnetwork`: The subnetwork URL of the instance.
+- `__meta_gce_tags`: A comma separated list of instance tags.
+- `__meta_gce_zone`: The GCE zone URL in which the instance is running.
 
 ## Component health
 
@@ -118,9 +118,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.hetzner.md b/docs/sources/reference/components/discovery/discovery.hetzner.md
index f7c0661828..c253714be0 100644
--- a/docs/sources/reference/components/discovery/discovery.hetzner.md
+++ b/docs/sources/reference/components/discovery/discovery.hetzner.md
@@ -44,13 +44,13 @@ You can use the following arguments with `discovery.hetzner`:
 
 `role` must be one of `robot` or `hcloud`.
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
 [arguments]: #arguments
 
@@ -110,38 +110,38 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_hetzner_datacenter`: The data center of the server
-* `__meta_hetzner_public_ipv4`: The public IPv4 address of the server.
-* `__meta_hetzner_public_ipv6_network`: The public IPv6 network (/64) of the server.
-* `__meta_hetzner_server_id`: The ID of the server.
-* `__meta_hetzner_server_name`: The name of the server.
-* `__meta_hetzner_server_status`: The status of the server.
+- `__meta_hetzner_datacenter`: The data center of the server
+- `__meta_hetzner_public_ipv4`: The public IPv4 address of the server.
+- `__meta_hetzner_public_ipv6_network`: The public IPv6 network (/64) of the server.
+- `__meta_hetzner_server_id`: The ID of the server.
+- `__meta_hetzner_server_name`: The name of the server.
+- `__meta_hetzner_server_status`: The status of the server.
 
 ### `hcloud`
 
 The labels below are only available for targets with `role` set to `hcloud`:
 
-* `__meta_hetzner_hcloud_cpu_cores`: The CPU cores count of the server.
-* `__meta_hetzner_hcloud_cpu_type`: The CPU type of the server (shared or dedicated).
-* `__meta_hetzner_hcloud_datacenter_location_network_zone`: The network zone of the server.
-* `__meta_hetzner_hcloud_datacenter_location`: The location of the server.
-* `__meta_hetzner_hcloud_disk_size_gb`: The disk size of the server (in GB).
-* `__meta_hetzner_hcloud_image_description`: The description of the server image.
-* `__meta_hetzner_hcloud_image_name`: The image name of the server.
-* `__meta_hetzner_hcloud_image_os_flavor`: The OS flavor of the server image.
-* `__meta_hetzner_hcloud_image_os_version`: The OS version of the server image.
-* `__meta_hetzner_hcloud_label_<labelname>`: Each label of the server.
-* `__meta_hetzner_hcloud_labelpresent_<labelname>`: `true` for each label of the server.
-* `__meta_hetzner_hcloud_memory_size_gb`: The amount of memory of the server (in GB).
-* `__meta_hetzner_hcloud_private_ipv4_<networkname>`: The private IPv4 address of the server within a given network.
-* `__meta_hetzner_hcloud_server_type`: The type of the server.
+- `__meta_hetzner_hcloud_cpu_cores`: The CPU cores count of the server.
+- `__meta_hetzner_hcloud_cpu_type`: The CPU type of the server (shared or dedicated).
+- `__meta_hetzner_hcloud_datacenter_location_network_zone`: The network zone of the server.
+- `__meta_hetzner_hcloud_datacenter_location`: The location of the server.
+- `__meta_hetzner_hcloud_disk_size_gb`: The disk size of the server (in GB).
+- `__meta_hetzner_hcloud_image_description`: The description of the server image.
+- `__meta_hetzner_hcloud_image_name`: The image name of the server.
+- `__meta_hetzner_hcloud_image_os_flavor`: The OS flavor of the server image.
+- `__meta_hetzner_hcloud_image_os_version`: The OS version of the server image.
+- `__meta_hetzner_hcloud_label_<labelname>`: Each label of the server.
+- `__meta_hetzner_hcloud_labelpresent_<labelname>`: `true` for each label of the server.
+- `__meta_hetzner_hcloud_memory_size_gb`: The amount of memory of the server (in GB).
+- `__meta_hetzner_hcloud_private_ipv4_<networkname>`: The private IPv4 address of the server within a given network.
+- `__meta_hetzner_hcloud_server_type`: The type of the server.
 
 ### `robot`
 
 The labels below are only available for targets with `role` set to `robot`:
 
-* `__meta_hetzner_robot_cancelled`: The server cancellation status.
-* `__meta_hetzner_robot_product`: The product of the server.
+- `__meta_hetzner_robot_cancelled`: The server cancellation status.
+- `__meta_hetzner_robot_product`: The product of the server.
 
 ## Component health
 
@@ -184,10 +184,10 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<HETZNER_ROLE>`_: The role of the entities that should be discovered.
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<HETZNER_ROLE>`_: The role of the entities that should be discovered.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.http.md b/docs/sources/reference/components/discovery/discovery.http.md
index 19739dd0c3..43b047800a 100644
--- a/docs/sources/reference/components/discovery/discovery.http.md
+++ b/docs/sources/reference/components/discovery/discovery.http.md
@@ -38,20 +38,17 @@ The following example provides a target with a custom `metricsPath`, scrape inte
 
 ```json
 [
-   {
-      "labels" : {
-         "__metrics_path__" : "/api/prometheus",
-         "__scheme__" : "https",
-         "__scrape_interval__" : "60s",
-         "__scrape_timeout__" : "10s",
-         "service" : "custom-api-service"
-      },
-      "targets" : [
-         "custom-api:443"
-      ]
-   },
+  {
+    "labels": {
+      "__metrics_path__": "/api/prometheus",
+      "__scheme__": "https",
+      "__scrape_interval__": "60s",
+      "__scrape_timeout__": "10s",
+      "service": "custom-api-service"
+    },
+    "targets": ["custom-api:443"]
+  }
 ]
-
 ```
 
 It's also possible to append query parameters to the metrics path with the `__param_<name>` syntax.
@@ -60,21 +57,18 @@ The following example calls the metrics path `/health?target_data=prometheus`:
 
 ```json
 [
-   {
-      "labels" : {
-         "__metrics_path__" : "/health",
-         "__scheme__" : "https",
-         "__scrape_interval__" : "60s",
-         "__scrape_timeout__" : "10s",
-         "__param_target_data": "prometheus",
-         "service" : "custom-api-service"
-      },
-      "targets" : [
-         "custom-api:443"
-      ]
-   },
+  {
+    "labels": {
+      "__metrics_path__": "/health",
+      "__scheme__": "https",
+      "__scrape_interval__": "60s",
+      "__scrape_timeout__": "10s",
+      "__param_target_data": "prometheus",
+      "service": "custom-api-service"
+    },
+    "targets": ["custom-api:443"]
+  }
 ]
-
 ```
 
 For more information on the potential labels you can use, refer to the [`prometheus.scrape` technical details][prometheus.scrape] section, or the [Prometheus Configuration][] documentation.
@@ -106,13 +100,13 @@ You can use the following arguments with `discovery.http`:
 | `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
 | `refresh_interval`       | `duration`          | How often to refresh targets.                                                                    | `"60s"` | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
 [arguments]: #arguments
 
@@ -172,7 +166,7 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_url`: URL the target was obtained from.
+- `__meta_url`: URL the target was obtained from.
 
 ## Component health
 
@@ -185,7 +179,7 @@ In those cases, exported fields retain their last healthy values.
 
 ## Debug metrics
 
-* `prometheus_sd_http_failures_total` (counter): Total number of refresh failures.
+- `prometheus_sd_http_failures_total` (counter): Total number of refresh failures.
 
 ## Examples
 
diff --git a/docs/sources/reference/components/discovery/discovery.ionos.md b/docs/sources/reference/components/discovery/discovery.ionos.md
index 9c38272780..60b95640e4 100644
--- a/docs/sources/reference/components/discovery/discovery.ionos.md
+++ b/docs/sources/reference/components/discovery/discovery.ionos.md
@@ -40,13 +40,13 @@ You can use the following arguments with `discovery.ionos`:
 | `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
 | `refresh_interval`       | `duration`          | The time after which the servers are refreshed.                                                  | `60s`   | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments]
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments]
+- [`oauth2`][oauth2] block
 
 [arguments]: #arguments
 
@@ -100,25 +100,25 @@ The `tls_config` block configures TLS settings for connecting to the endpoint.
 
 The following fields are exported and can be referenced by other components:
 
-Name      | Type                | Description
-----------|---------------------|--------------------------------------------------------
-`targets` | `list(map(string))` | The set of targets discovered from the IONOS Cloud API.
+| Name      | Type                | Description                                             |
+| --------- | ------------------- | ------------------------------------------------------- |
+| `targets` | `list(map(string))` | The set of targets discovered from the IONOS Cloud API. |
 
 Each target includes the following labels:
 
-* `__meta_ionos_server_availability_zone`: The availability zone of the server.
-* `__meta_ionos_server_boot_cdrom_id`: The ID of the CD-ROM the server is booted from.
-* `__meta_ionos_server_boot_image_id`: The ID of the boot image or snapshot the server is booted from.
-* `__meta_ionos_server_boot_volume_id`: The ID of the boot volume.
-* `__meta_ionos_server_cpu_family`: The CPU family of the server to.
-* `__meta_ionos_server_id`: The ID of the server.
-* `__meta_ionos_server_ip`: A comma separated list of all IP addresses assigned to the server.
-* `__meta_ionos_server_lifecycle`: The lifecycle state of the server resource.
-* `__meta_ionos_server_name`: The name of the server.
-* `__meta_ionos_server_nic_ip_<nic_name>`: A comma separated list of IP addresses, grouped by the name of each NIC attached to the server.
-* `__meta_ionos_server_servers_id`: The ID of the servers the server belongs to.
-* `__meta_ionos_server_state`: The execution state of the server.
-* `__meta_ionos_server_type`: The type of the server.
+- `__meta_ionos_server_availability_zone`: The availability zone of the server.
+- `__meta_ionos_server_boot_cdrom_id`: The ID of the CD-ROM the server is booted from.
+- `__meta_ionos_server_boot_image_id`: The ID of the boot image or snapshot the server is booted from.
+- `__meta_ionos_server_boot_volume_id`: The ID of the boot volume.
+- `__meta_ionos_server_cpu_family`: The CPU family of the server to.
+- `__meta_ionos_server_id`: The ID of the server.
+- `__meta_ionos_server_ip`: A comma separated list of all IP addresses assigned to the server.
+- `__meta_ionos_server_lifecycle`: The lifecycle state of the server resource.
+- `__meta_ionos_server_name`: The name of the server.
+- `__meta_ionos_server_nic_ip_<nic_name>`: A comma separated list of IP addresses, grouped by the name of each NIC attached to the server.
+- `__meta_ionos_server_servers_id`: The ID of the servers the server belongs to.
+- `__meta_ionos_server_state`: The execution state of the server.
+- `__meta_ionos_server_type`: The type of the server.
 
 ## Component health
 
@@ -159,9 +159,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.kubelet.md b/docs/sources/reference/components/discovery/discovery.kubelet.md
index 15c669b358..77d58429a9 100644
--- a/docs/sources/reference/components/discovery/discovery.kubelet.md
+++ b/docs/sources/reference/components/discovery/discovery.kubelet.md
@@ -21,8 +21,8 @@ discovery.kubelet "LABEL" {
 
 ## Requirements
 
-* The Kubelet must be reachable from the `alloy` Pod network.
-* Follow the [Kubelet authorization][] documentation to configure authentication to the Kubelet API.
+- The Kubelet must be reachable from the `alloy` Pod network.
+- Follow the [Kubelet authorization][] documentation to configure authentication to the Kubelet API.
 
 [Kubelet authorization]: https://kubernetes.io/docs/reference/access-authn-authz/kubelet-authn-authz/#kubelet-authorization
 
@@ -51,15 +51,15 @@ If omitted, all namespaces are searched.
 You can have additional paths in the `url`.
 For example, if `url` is `https://kubernetes.default.svc.cluster.local:443/api/v1/nodes/cluster-node-1/proxy`, then `discovery.kubelet` sends a request on `https://kubernetes.default.svc.cluster.local:443/api/v1/nodes/cluster-node-1/proxy/pods`
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
- [arguments]: #arguments
+[arguments]: #arguments
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -117,28 +117,28 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__address__`: The target address to scrape derived from the Pod IP and container port.
-* `__meta_kubernetes_namespace`: The namespace of the Pod object.
-* `__meta_kubernetes_pod_name`: The name of the Pod object.
-* `__meta_kubernetes_pod_ip`: The Pod IP of the Pod object.
-* `__meta_kubernetes_pod_label_<labelname>`: Each label from the Pod object.
-* `__meta_kubernetes_pod_labelpresent_<labelname>`: `true` for each label from the Pod object.
-* `__meta_kubernetes_pod_annotation_<annotationname>`: Each annotation from the Pod object.
-* `__meta_kubernetes_pod_annotationpresent_<annotationname>`: `true` for each annotation from the Pod object.
-* `__meta_kubernetes_pod_container_init`: `true` if the container is an `InitContainer`.
-* `__meta_kubernetes_pod_container_name`: Name of the container the target address points to.
-* `__meta_kubernetes_pod_container_id`: ID of the container the target address points to. The ID is in the form `<type>://<container_id>`.
-* `__meta_kubernetes_pod_container_image`: The image the container is using.
-* `__meta_kubernetes_pod_container_port_name`: Name of the container port.
-* `__meta_kubernetes_pod_container_port_number`: Number of the container port.
-* `__meta_kubernetes_pod_container_port_protocol`: Protocol of the container port.
-* `__meta_kubernetes_pod_ready`: Set to `true` or `false` for the Pod's ready state.
-* `__meta_kubernetes_pod_phase`: Set to `Pending`, `Running`, `Succeeded`, `Failed` or `Unknown` in the lifecycle.
-* `__meta_kubernetes_pod_node_name`: The name of the node the Pod is scheduled onto.
-* `__meta_kubernetes_pod_host_ip`: The current host IP of the Pod object.
-* `__meta_kubernetes_pod_uid`: The UID of the Pod object.
-* `__meta_kubernetes_pod_controller_kind`: Object kind of the Pod controller.
-* `__meta_kubernetes_pod_controller_name`: Name of the Pod controller.
+- `__address__`: The target address to scrape derived from the Pod IP and container port.
+- `__meta_kubernetes_namespace`: The namespace of the Pod object.
+- `__meta_kubernetes_pod_name`: The name of the Pod object.
+- `__meta_kubernetes_pod_ip`: The Pod IP of the Pod object.
+- `__meta_kubernetes_pod_label_<labelname>`: Each label from the Pod object.
+- `__meta_kubernetes_pod_labelpresent_<labelname>`: `true` for each label from the Pod object.
+- `__meta_kubernetes_pod_annotation_<annotationname>`: Each annotation from the Pod object.
+- `__meta_kubernetes_pod_annotationpresent_<annotationname>`: `true` for each annotation from the Pod object.
+- `__meta_kubernetes_pod_container_init`: `true` if the container is an `InitContainer`.
+- `__meta_kubernetes_pod_container_name`: Name of the container the target address points to.
+- `__meta_kubernetes_pod_container_id`: ID of the container the target address points to. The ID is in the form `<type>://<container_id>`.
+- `__meta_kubernetes_pod_container_image`: The image the container is using.
+- `__meta_kubernetes_pod_container_port_name`: Name of the container port.
+- `__meta_kubernetes_pod_container_port_number`: Number of the container port.
+- `__meta_kubernetes_pod_container_port_protocol`: Protocol of the container port.
+- `__meta_kubernetes_pod_ready`: Set to `true` or `false` for the Pod's ready state.
+- `__meta_kubernetes_pod_phase`: Set to `Pending`, `Running`, `Succeeded`, `Failed` or `Unknown` in the lifecycle.
+- `__meta_kubernetes_pod_node_name`: The name of the node the Pod is scheduled onto.
+- `__meta_kubernetes_pod_host_ip`: The current host IP of the Pod object.
+- `__meta_kubernetes_pod_uid`: The UID of the Pod object.
+- `__meta_kubernetes_pod_controller_kind`: Object kind of the Pod controller.
+- `__meta_kubernetes_pod_controller_name`: Name of the Pod controller.
 
 {{< admonition type="note" >}}
 The Kubelet API used by this component is an internal API and therefore the data in the response returned from the API can't be guaranteed between different versions of the Kubelet.
@@ -187,9 +187,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 ### Limit searched namespaces
 
@@ -220,9 +220,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.kubernetes.md b/docs/sources/reference/components/discovery/discovery.kubernetes.md
index 388653d176..813c06e054 100644
--- a/docs/sources/reference/components/discovery/discovery.kubernetes.md
+++ b/docs/sources/reference/components/discovery/discovery.kubernetes.md
@@ -42,15 +42,15 @@ You can use the following arguments with `discovery.kubernetes`:
 | `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
 | `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
- [arguments]: #arguments
+[arguments]: #arguments
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -64,13 +64,13 @@ The target address defaults to the first address of the Kubernetes node object i
 
 The following labels are included for discovered nodes:
 
-* `__meta_kubernetes_node_address_<address_type>`: The first address for each node address type, if it exists.
-* `__meta_kubernetes_node_annotation_<annotationname>`: Each annotation from the node object.
-* `__meta_kubernetes_node_annotationpresent_<annotationname>`: Set to `true` for each annotation from the node object.
-* `__meta_kubernetes_node_label_<labelname>`: Each label from the node object.
-* `__meta_kubernetes_node_labelpresent_<labelname>`: Set to `true` for each label from the node object.
-* `__meta_kubernetes_node_name`: The name of the node object.
-* `__meta_kubernetes_node_provider_id`: The cloud provider's name for the node object.
+- `__meta_kubernetes_node_address_<address_type>`: The first address for each node address type, if it exists.
+- `__meta_kubernetes_node_annotation_<annotationname>`: Each annotation from the node object.
+- `__meta_kubernetes_node_annotationpresent_<annotationname>`: Set to `true` for each annotation from the node object.
+- `__meta_kubernetes_node_label_<labelname>`: Each label from the node object.
+- `__meta_kubernetes_node_labelpresent_<labelname>`: Set to `true` for each label from the node object.
+- `__meta_kubernetes_node_name`: The name of the node object.
+- `__meta_kubernetes_node_provider_id`: The cloud provider's name for the node object.
 
 In addition, the `instance` label for the node is set to the node name as retrieved from the API server.
 
@@ -82,18 +82,18 @@ The address is set to the Kubernetes DNS name of the service and respective serv
 
 The following labels are included for discovered services:
 
-* `__meta_kubernetes_namespace`: The namespace of the service object.
-* `__meta_kubernetes_service_annotation_<annotationname>`: Each annotation from the service object.
-* `__meta_kubernetes_service_annotationpresent_<annotationname>`: `true` for each annotation of the service object.
-* `__meta_kubernetes_service_cluster_ip`: The cluster IP address of the service. This doesn't apply to services of type `ExternalName`.
-* `__meta_kubernetes_service_external_name`: The DNS name of the service. This only applies to services of type `ExternalName`.
-* `__meta_kubernetes_service_label_<labelname>`: Each label from the service object.
-* `__meta_kubernetes_service_labelpresent_<labelname>`: `true` for each label of the service object.
-* `__meta_kubernetes_service_name`: The name of the service object.
-* `__meta_kubernetes_service_port_name`: Name of the service port for the target.
-* `__meta_kubernetes_service_port_number`: Number of the service port for the target.
-* `__meta_kubernetes_service_port_protocol`: Protocol of the service port for the target.
-* `__meta_kubernetes_service_type`: The type of the service.
+- `__meta_kubernetes_namespace`: The namespace of the service object.
+- `__meta_kubernetes_service_annotation_<annotationname>`: Each annotation from the service object.
+- `__meta_kubernetes_service_annotationpresent_<annotationname>`: `true` for each annotation of the service object.
+- `__meta_kubernetes_service_cluster_ip`: The cluster IP address of the service. This doesn't apply to services of type `ExternalName`.
+- `__meta_kubernetes_service_external_name`: The DNS name of the service. This only applies to services of type `ExternalName`.
+- `__meta_kubernetes_service_label_<labelname>`: Each label from the service object.
+- `__meta_kubernetes_service_labelpresent_<labelname>`: `true` for each label of the service object.
+- `__meta_kubernetes_service_name`: The name of the service object.
+- `__meta_kubernetes_service_port_name`: Name of the service port for the target.
+- `__meta_kubernetes_service_port_number`: Number of the service port for the target.
+- `__meta_kubernetes_service_port_protocol`: Protocol of the service port for the target.
+- `__meta_kubernetes_service_type`: The type of the service.
 
 ### `pod` role
 
@@ -107,27 +107,27 @@ These targets must have a port manually injected using a [`discovery.relabel` co
 
 The following labels are included for discovered Pods:
 
-* `__meta_kubernetes_namespace`: The namespace of the Pod object.
-* `__meta_kubernetes_pod_annotation_<annotationname>`: Each annotation from the Pod object.
-* `__meta_kubernetes_pod_annotationpresent_<annotationname>`: `true` for each annotation from the Pod object.
-* `__meta_kubernetes_pod_container_id`: ID of the container the target address points to. The ID is in the form `<type>://<container_id>`.
-* `__meta_kubernetes_pod_container_image`: The image the container is using.
-* `__meta_kubernetes_pod_container_init`: `true` if the container is an `InitContainer`.
-* `__meta_kubernetes_pod_container_name`: Name of the container the target address points to.
-* `__meta_kubernetes_pod_container_port_name`: Name of the container port.
-* `__meta_kubernetes_pod_container_port_number`: Number of the container port.
-* `__meta_kubernetes_pod_container_port_protocol`: Protocol of the container port.
-* `__meta_kubernetes_pod_controller_kind`: Object kind of the Pod controller.
-* `__meta_kubernetes_pod_controller_name`: Name of the Pod controller.
-* `__meta_kubernetes_pod_host_ip`: The current host IP of the Pod object.
-* `__meta_kubernetes_pod_ip`: The Pod IP of the Pod object.
-* `__meta_kubernetes_pod_label_<labelname>`: Each label from the Pod object.
-* `__meta_kubernetes_pod_labelpresent_<labelname>`: `true` for each label from the Pod object.
-* `__meta_kubernetes_pod_name`: The name of the Pod object.
-* `__meta_kubernetes_pod_node_name`: The name of the node the Pod is scheduled onto.
-* `__meta_kubernetes_pod_phase`: Set to `Pending`, `Running`, `Succeeded`, `Failed` or `Unknown` in the lifecycle.
-* `__meta_kubernetes_pod_ready`: Set to `true` or `false` for the Pod's ready state.
-* `__meta_kubernetes_pod_uid`: The UID of the Pod object.
+- `__meta_kubernetes_namespace`: The namespace of the Pod object.
+- `__meta_kubernetes_pod_annotation_<annotationname>`: Each annotation from the Pod object.
+- `__meta_kubernetes_pod_annotationpresent_<annotationname>`: `true` for each annotation from the Pod object.
+- `__meta_kubernetes_pod_container_id`: ID of the container the target address points to. The ID is in the form `<type>://<container_id>`.
+- `__meta_kubernetes_pod_container_image`: The image the container is using.
+- `__meta_kubernetes_pod_container_init`: `true` if the container is an `InitContainer`.
+- `__meta_kubernetes_pod_container_name`: Name of the container the target address points to.
+- `__meta_kubernetes_pod_container_port_name`: Name of the container port.
+- `__meta_kubernetes_pod_container_port_number`: Number of the container port.
+- `__meta_kubernetes_pod_container_port_protocol`: Protocol of the container port.
+- `__meta_kubernetes_pod_controller_kind`: Object kind of the Pod controller.
+- `__meta_kubernetes_pod_controller_name`: Name of the Pod controller.
+- `__meta_kubernetes_pod_host_ip`: The current host IP of the Pod object.
+- `__meta_kubernetes_pod_ip`: The Pod IP of the Pod object.
+- `__meta_kubernetes_pod_label_<labelname>`: Each label from the Pod object.
+- `__meta_kubernetes_pod_labelpresent_<labelname>`: `true` for each label from the Pod object.
+- `__meta_kubernetes_pod_name`: The name of the Pod object.
+- `__meta_kubernetes_pod_node_name`: The name of the node the Pod is scheduled onto.
+- `__meta_kubernetes_pod_phase`: Set to `Pending`, `Running`, `Succeeded`, `Failed` or `Unknown` in the lifecycle.
+- `__meta_kubernetes_pod_ready`: Set to `true` or `false` for the Pod's ready state.
+- `__meta_kubernetes_pod_uid`: The UID of the Pod object.
 
 ### `endpoints` role
 
@@ -137,22 +137,23 @@ If the endpoint is backed by a Pod, all container ports of a Pod are discovered
 
 The following labels are included for discovered endpoints:
 
-* `__meta_kubernetes_endpoints_label_<labelname>`: Each label from the endpoints object.
-* `__meta_kubernetes_endpoints_labelpresent_<labelname>`: `true` for each label from the endpoints object.
-* `__meta_kubernetes_endpoints_name:` The names of the endpoints object.
-* `__meta_kubernetes_namespace:` The namespace of the endpoints object.
+- `__meta_kubernetes_endpoints_label_<labelname>`: Each label from the endpoints object.
+- `__meta_kubernetes_endpoints_labelpresent_<labelname>`: `true` for each label from the endpoints object.
+- `__meta_kubernetes_endpoints_name:` The names of the endpoints object.
+- `__meta_kubernetes_namespace:` The namespace of the endpoints object.
 
-* The following labels are attached for all targets discovered directly from the endpoints list:
-  * `__meta_kubernetes_endpoint_address_target_kind`: Kind of the endpoint address target.
-  * `__meta_kubernetes_endpoint_address_target_name`: Name of the endpoint address target.
-  * `__meta_kubernetes_endpoint_hostname`: Hostname of the endpoint.
-  * `__meta_kubernetes_endpoint_node_name`: Name of the node hosting the endpoint.
-  * `__meta_kubernetes_endpoint_port_name`: Name of the endpoint port.
-  * `__meta_kubernetes_endpoint_port_protocol`: Protocol of the endpoint port.
-  * `__meta_kubernetes_endpoint_ready`: Set to `true` or `false` for the endpoint's ready state.
+- The following labels are attached for all targets discovered directly from the endpoints list:
 
-* If the endpoints belong to a service, all labels of the `service` role discovery are attached.
-* For all targets backed by a Pod, all labels of the `pod` role discovery are attached.
+  - `__meta_kubernetes_endpoint_address_target_kind`: Kind of the endpoint address target.
+  - `__meta_kubernetes_endpoint_address_target_name`: Name of the endpoint address target.
+  - `__meta_kubernetes_endpoint_hostname`: Hostname of the endpoint.
+  - `__meta_kubernetes_endpoint_node_name`: Name of the node hosting the endpoint.
+  - `__meta_kubernetes_endpoint_port_name`: Name of the endpoint port.
+  - `__meta_kubernetes_endpoint_port_protocol`: Protocol of the endpoint port.
+  - `__meta_kubernetes_endpoint_ready`: Set to `true` or `false` for the endpoint's ready state.
+
+- If the endpoints belong to a service, all labels of the `service` role discovery are attached.
+- For all targets backed by a Pod, all labels of the `pod` role discovery are attached.
 
 ### `endpointslice` role
 
@@ -162,23 +163,23 @@ If the endpoint is backed by a Pod, all container ports of a Pod are discovered
 
 The following labels are included for discovered endpoint slices:
 
-* `__meta_kubernetes_endpointslice_name`: The name of endpoint slice object.
-* `__meta_kubernetes_namespace`: The namespace of the endpoints object.
+- `__meta_kubernetes_endpointslice_name`: The name of endpoint slice object.
+- `__meta_kubernetes_namespace`: The namespace of the endpoints object.
 
-* The following labels are attached for all targets discovered directly from the endpoint slice list:
+- The following labels are attached for all targets discovered directly from the endpoint slice list:
 
-  * `__meta_kubernetes_endpointslice_address_target_kind`: Kind of the referenced object.
-  * `__meta_kubernetes_endpointslice_address_target_name`: Name of referenced object.
-  * `__meta_kubernetes_endpointslice_address_type`: The IP protocol family of the address of the target.
-  * `__meta_kubernetes_endpointslice_endpoint_conditions_ready`: Set to `true` or `false` for the referenced endpoint's ready state.
-  * `__meta_kubernetes_endpointslice_endpoint_topology_kubernetes_io_hostname`: Name of the node hosting the referenced endpoint.
-  * `__meta_kubernetes_endpointslice_endpoint_topology_present_kubernetes_io_hostname`: `true` if the referenced object has a `kubernetes.io/hostname` annotation.
-  * `__meta_kubernetes_endpointslice_port_name`: Named port of the referenced endpoint.
-  * `__meta_kubernetes_endpointslice_port_protocol`: Protocol of the referenced endpoint.
-  * `__meta_kubernetes_endpointslice_port`: Port of the referenced endpoint.
+  - `__meta_kubernetes_endpointslice_address_target_kind`: Kind of the referenced object.
+  - `__meta_kubernetes_endpointslice_address_target_name`: Name of referenced object.
+  - `__meta_kubernetes_endpointslice_address_type`: The IP protocol family of the address of the target.
+  - `__meta_kubernetes_endpointslice_endpoint_conditions_ready`: Set to `true` or `false` for the referenced endpoint's ready state.
+  - `__meta_kubernetes_endpointslice_endpoint_topology_kubernetes_io_hostname`: Name of the node hosting the referenced endpoint.
+  - `__meta_kubernetes_endpointslice_endpoint_topology_present_kubernetes_io_hostname`: `true` if the referenced object has a `kubernetes.io/hostname` annotation.
+  - `__meta_kubernetes_endpointslice_port_name`: Named port of the referenced endpoint.
+  - `__meta_kubernetes_endpointslice_port_protocol`: Protocol of the referenced endpoint.
+  - `__meta_kubernetes_endpointslice_port`: Port of the referenced endpoint.
 
-* If the endpoints belong to a service, all labels of the `service` role discovery are attached.
-* For all targets backed by a Pod, all labels of the `pod` role discovery are attached.
+- If the endpoints belong to a service, all labels of the `service` role discovery are attached.
+- For all targets backed by a Pod, all labels of the `pod` role discovery are attached.
 
 ### `ingress` role
 
@@ -188,15 +189,15 @@ The address is set to the host specified in the Kubernetes `Ingress`'s `spec` bl
 
 The following labels are included for discovered ingress objects:
 
-* `__meta_kubernetes_ingress_annotation_<annotationname>`: Each annotation from the ingress object.
-* `__meta_kubernetes_ingress_annotationpresent_<annotationname>`: `true` for each annotation from the ingress object.
-* `__meta_kubernetes_ingress_class_name`: Class name from ingress spec, if present.
-* `__meta_kubernetes_ingress_label_<labelname>`: Each label from the ingress object.
-* `__meta_kubernetes_ingress_labelpresent_<labelname>`: `true` for each label from the ingress object.
-* `__meta_kubernetes_ingress_name`: The name of the ingress object.
-* `__meta_kubernetes_ingress_path`: Path from ingress spec. Defaults to /.
-* `__meta_kubernetes_ingress_scheme`: Protocol scheme of ingress, `https` if TLS config is set. Defaults to `http`.
-* `__meta_kubernetes_namespace`: The namespace of the ingress object.
+- `__meta_kubernetes_ingress_annotation_<annotationname>`: Each annotation from the ingress object.
+- `__meta_kubernetes_ingress_annotationpresent_<annotationname>`: `true` for each annotation from the ingress object.
+- `__meta_kubernetes_ingress_class_name`: Class name from ingress spec, if present.
+- `__meta_kubernetes_ingress_label_<labelname>`: Each label from the ingress object.
+- `__meta_kubernetes_ingress_labelpresent_<labelname>`: `true` for each label from the ingress object.
+- `__meta_kubernetes_ingress_name`: The name of the ingress object.
+- `__meta_kubernetes_ingress_path`: Path from ingress spec. Defaults to /.
+- `__meta_kubernetes_ingress_scheme`: Protocol scheme of ingress, `https` if TLS config is set. Defaults to `http`.
+- `__meta_kubernetes_namespace`: The namespace of the ingress object.
 
 ## Blocks
 
@@ -344,9 +345,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 ### Kubeconfig authentication
 
@@ -377,9 +378,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 ### Limit searched namespaces and filter by labels value
 
@@ -418,9 +419,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 ### Limit to only Pods on the same node
 
@@ -460,9 +461,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.kuma.md b/docs/sources/reference/components/discovery/discovery.kuma.md
index fc41192152..68d8be4f78 100644
--- a/docs/sources/reference/components/discovery/discovery.kuma.md
+++ b/docs/sources/reference/components/discovery/discovery.kuma.md
@@ -40,13 +40,13 @@ You can use the following arguments with `discovery.kuma`:
 | `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
 | `refresh_interval`       | `duration`          | The time to wait between polling update requests.                                                | `"30s"` | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
 [arguments]: #arguments
 
@@ -106,10 +106,10 @@ The following fields are exported and can be referenced by other components:
 
 The following meta labels are available on targets and can be used by the `discovery.relabel` component:
 
-* `__meta_kuma_dataplane`: The name of the proxy.
-* `__meta_kuma_label_<tagname>`: Each tag of the proxy.
-* `__meta_kuma_mesh`: The name of the proxy's Mesh.
-* `__meta_kuma_service`: The name of the proxy's associated Service.
+- `__meta_kuma_dataplane`: The name of the proxy.
+- `__meta_kuma_label_<tagname>`: Each tag of the proxy.
+- `__meta_kuma_mesh`: The name of the proxy's Mesh.
+- `__meta_kuma_service`: The name of the proxy's associated Service.
 
 ## Component health
 
@@ -147,9 +147,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.lightsail.md b/docs/sources/reference/components/discovery/discovery.lightsail.md
index 265eec5712..c3f5959eae 100644
--- a/docs/sources/reference/components/discovery/discovery.lightsail.md
+++ b/docs/sources/reference/components/discovery/discovery.lightsail.md
@@ -44,13 +44,13 @@ You can use the following arguments with `discovery.lightsail`:
 
 At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token][arguments] argument
+- [`oauth2`][oauth2] block
 
- [arguments]: #arguments
+[arguments]: #arguments
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -108,17 +108,17 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_lightsail_availability_zone`: The availability zone in which the instance is running.
-* `__meta_lightsail_blueprint_id`: The Lightsail blueprint ID.
-* `__meta_lightsail_bundle_id`: The Lightsail bundle ID.
-* `__meta_lightsail_instance_name`: The name of the Lightsail instance.
-* `__meta_lightsail_instance_state`: The state of the Lightsail instance.
-* `__meta_lightsail_instance_support_code`: The support code of the Lightsail instance.
-* `__meta_lightsail_ipv6_addresses`: Comma-separated list of IPv6 addresses assigned to the instance's network interfaces, if present.
-* `__meta_lightsail_private_ip`: The private IP address of the instance.
-* `__meta_lightsail_public_ip`: The public IP address of the instance, if available.
-* `__meta_lightsail_region`: The region of the instance.
-* `__meta_lightsail_tag_<tagkey>`: Each tag value of the instance.
+- `__meta_lightsail_availability_zone`: The availability zone in which the instance is running.
+- `__meta_lightsail_blueprint_id`: The Lightsail blueprint ID.
+- `__meta_lightsail_bundle_id`: The Lightsail bundle ID.
+- `__meta_lightsail_instance_name`: The name of the Lightsail instance.
+- `__meta_lightsail_instance_state`: The state of the Lightsail instance.
+- `__meta_lightsail_instance_support_code`: The support code of the Lightsail instance.
+- `__meta_lightsail_ipv6_addresses`: Comma-separated list of IPv6 addresses assigned to the instance's network interfaces, if present.
+- `__meta_lightsail_private_ip`: The private IP address of the instance.
+- `__meta_lightsail_public_ip`: The public IP address of the instance, if available.
+- `__meta_lightsail_region`: The region of the instance.
+- `__meta_lightsail_tag_<tagkey>`: Each tag value of the instance.
 
 ## Component health
 
@@ -159,9 +159,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.linode.md b/docs/sources/reference/components/discovery/discovery.linode.md
index 806acb381b..b9473dc747 100644
--- a/docs/sources/reference/components/discovery/discovery.linode.md
+++ b/docs/sources/reference/components/discovery/discovery.linode.md
@@ -45,13 +45,13 @@ You can use the following arguments with `discovery.linode`:
 | `refresh_interval`       | `duration`          | The time to wait between polling update requests.                                                | `"60s"` | no       |
 | `tag_separator`          | `string`            | The string by which Linode Instance tags are joined into the tag label.                          | `,`     | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
 [arguments]: #arguments
 
@@ -111,24 +111,24 @@ The following fields are exported and can be referenced by other components:
 
 The following meta labels are available on targets and can be used by the discovery.relabel component:
 
-* `__meta_linode_backups`: The backup service status of the Linode instance.
-* `__meta_linode_extra_ips`: A list of all extra IPv4 addresses assigned to the Linode instance joined by the tag separator.
-* `__meta_linode_group`: The display group a Linode instance is a member of.
-* `__meta_linode_hypervisor`: The virtualization software powering the Linode instance.
-* `__meta_linode_image`: The slug of the Linode instance's image.
-* `__meta_linode_instance_id`: The ID of the Linode instance.
-* `__meta_linode_instance_label`: The label of the Linode instance.
-* `__meta_linode_private_ipv4`: The private IPv4 of the Linode instance.
-* `__meta_linode_public_ipv4`: The public IPv4 of the Linode instance.
-* `__meta_linode_public_ipv6`: The public IPv6 of the Linode instance.
-* `__meta_linode_region`: The region of the Linode instance.
-* `__meta_linode_specs_disk_bytes`: The amount of storage space the Linode instance has access to.
-* `__meta_linode_specs_memory_bytes`: The amount of RAM the Linode instance has access to.
-* `__meta_linode_specs_transfer_bytes`: The amount of network transfer the Linode instance is allotted each month.
-* `__meta_linode_specs_vcpus`: The number of VCPUS this Linode has access to.
-* `__meta_linode_status`: The status of the Linode instance.
-* `__meta_linode_tags`: A list of tags of the Linode instance joined by the tag separator.
-* `__meta_linode_type`: The type of the Linode instance.
+- `__meta_linode_backups`: The backup service status of the Linode instance.
+- `__meta_linode_extra_ips`: A list of all extra IPv4 addresses assigned to the Linode instance joined by the tag separator.
+- `__meta_linode_group`: The display group a Linode instance is a member of.
+- `__meta_linode_hypervisor`: The virtualization software powering the Linode instance.
+- `__meta_linode_image`: The slug of the Linode instance's image.
+- `__meta_linode_instance_id`: The ID of the Linode instance.
+- `__meta_linode_instance_label`: The label of the Linode instance.
+- `__meta_linode_private_ipv4`: The private IPv4 of the Linode instance.
+- `__meta_linode_public_ipv4`: The public IPv4 of the Linode instance.
+- `__meta_linode_public_ipv6`: The public IPv6 of the Linode instance.
+- `__meta_linode_region`: The region of the Linode instance.
+- `__meta_linode_specs_disk_bytes`: The amount of storage space the Linode instance has access to.
+- `__meta_linode_specs_memory_bytes`: The amount of RAM the Linode instance has access to.
+- `__meta_linode_specs_transfer_bytes`: The amount of network transfer the Linode instance is allotted each month.
+- `__meta_linode_specs_vcpus`: The number of VCPUS this Linode has access to.
+- `__meta_linode_status`: The status of the Linode instance.
+- `__meta_linode_tags`: A list of tags of the Linode instance joined by the tag separator.
+- `__meta_linode_type`: The type of the Linode instance.
 
 ## Component health
 
@@ -167,9 +167,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 ### Use a private IP address
 
@@ -203,9 +203,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.marathon.md b/docs/sources/reference/components/discovery/discovery.marathon.md
index af4ede83fb..cbc1f35478 100644
--- a/docs/sources/reference/components/discovery/discovery.marathon.md
+++ b/docs/sources/reference/components/discovery/discovery.marathon.md
@@ -39,15 +39,15 @@ You can use the following arguments with `discovery.marathon`:
 | `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
 | `refresh_interval`       | `duration`          | Interval at which to refresh the list of targets.                                                | `"30s"` | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`auth_token_file`][arguments] argument
-* [`auth_token`][arguments] argument
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`auth_token_file`][arguments] argument
+- [`auth_token`][arguments] argument
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
 [arguments]: #arguments
 
@@ -107,13 +107,13 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_marathon_app_label_<labelname>`: Any Marathon labels attached to the app.
-* `__meta_marathon_app`: The name of the app, with slashes replaced by dashes.
-* `__meta_marathon_image`: The name of the Docker image used, if available.
-* `__meta_marathon_port_definition_label_<labelname>`: The port definition labels.
-* `__meta_marathon_port_index`: The port index number, for example 1 for PORT1.
-* `__meta_marathon_port_mapping_label_<labelname>`: The port mapping labels.
-* `__meta_marathon_task`: The ID of the Apache Mesos task.
+- `__meta_marathon_app_label_<labelname>`: Any Marathon labels attached to the app.
+- `__meta_marathon_app`: The name of the app, with slashes replaced by dashes.
+- `__meta_marathon_image`: The name of the Docker image used, if available.
+- `__meta_marathon_port_definition_label_<labelname>`: The port definition labels.
+- `__meta_marathon_port_index`: The port index number, for example 1 for PORT1.
+- `__meta_marathon_port_mapping_label_<labelname>`: The port mapping labels.
+- `__meta_marathon_task`: The ID of the Apache Mesos task.
 
 ## Component health
 
@@ -156,9 +156,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.nerve.md b/docs/sources/reference/components/discovery/discovery.nerve.md
index 74e668fc65..58ade88ae9 100644
--- a/docs/sources/reference/components/discovery/discovery.nerve.md
+++ b/docs/sources/reference/components/discovery/discovery.nerve.md
@@ -49,10 +49,10 @@ The following fields are exported and can be referenced by other components:
 
 The following meta labels are available on targets and can be used by the discovery.relabel component
 
-* `__meta_nerve_endpoint_host`: The host of the endpoint.
-* `__meta_nerve_endpoint_name`: The name of the endpoint.
-* `__meta_nerve_endpoint_port`: The port of the endpoint.
-* `__meta_nerve_path`: The full path to the endpoint node in Zookeeper.
+- `__meta_nerve_endpoint_host`: The host of the endpoint.
+- `__meta_nerve_endpoint_name`: The name of the endpoint.
+- `__meta_nerve_endpoint_port`: The port of the endpoint.
+- `__meta_nerve_path`: The full path to the endpoint node in Zookeeper.
 
 ## Component health
 
@@ -92,9 +92,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.nomad.md b/docs/sources/reference/components/discovery/discovery.nomad.md
index bfbadca75e..9ac65dd00f 100644
--- a/docs/sources/reference/components/discovery/discovery.nomad.md
+++ b/docs/sources/reference/components/discovery/discovery.nomad.md
@@ -40,13 +40,13 @@ You can use the following arguments with `discovery.nomad`:
 | `server`                 | `string`            | Address of nomad server.                                                                         | `http://localhost:4646` | no       |
 | `tag_separator`          | `string`            | Separator to join nomad tags into Prometheus labels.                                             | `,`                     | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
 [arguments]: #arguments
 
@@ -106,15 +106,15 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_nomad_address`: The service address of the target.
-* `__meta_nomad_dc`: The data center name for the target.
-* `__meta_nomad_namespace`: The namespace of the target.
-* `__meta_nomad_node_id`: The node name defined for the target.
-* `__meta_nomad_service_address`: The service address of the target.
-* `__meta_nomad_service_id`: The service ID of the target.
-* `__meta_nomad_service_port`: The service port of the target.
-* `__meta_nomad_service`: The name of the service the target belongs to.
-* `__meta_nomad_tags`: The list of tags of the target joined by the tag separator.
+- `__meta_nomad_address`: The service address of the target.
+- `__meta_nomad_dc`: The data center name for the target.
+- `__meta_nomad_namespace`: The namespace of the target.
+- `__meta_nomad_node_id`: The node name defined for the target.
+- `__meta_nomad_service_address`: The service address of the target.
+- `__meta_nomad_service_id`: The service ID of the target.
+- `__meta_nomad_service_port`: The service port of the target.
+- `__meta_nomad_service`: The name of the service the target belongs to.
+- `__meta_nomad_tags`: The list of tags of the target joined by the tag separator.
 
 ## Component health
 
@@ -156,9 +156,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.openstack.md b/docs/sources/reference/components/discovery/discovery.openstack.md
index d6a538a5cf..0cfa87b51d 100644
--- a/docs/sources/reference/components/discovery/discovery.openstack.md
+++ b/docs/sources/reference/components/discovery/discovery.openstack.md
@@ -90,29 +90,29 @@ The following fields are exported and can be referenced by other components:
 The `hypervisor` role discovers one target per Nova hypervisor node.
 The target address defaults to the `host_ip` attribute of the hypervisor.
 
-* `__meta_openstack_hypervisor_host_ip`: The hypervisor node's IP address.
-* `__meta_openstack_hypervisor_hostname`: The hypervisor node's name.
-* `__meta_openstack_hypervisor_id`: The hypervisor node's ID.
-* `__meta_openstack_hypervisor_state`: The hypervisor node's state.
-* `__meta_openstack_hypervisor_status`: The hypervisor node's status.
-* `__meta_openstack_hypervisor_type`: The hypervisor node's type.
+- `__meta_openstack_hypervisor_host_ip`: The hypervisor node's IP address.
+- `__meta_openstack_hypervisor_hostname`: The hypervisor node's name.
+- `__meta_openstack_hypervisor_id`: The hypervisor node's ID.
+- `__meta_openstack_hypervisor_state`: The hypervisor node's state.
+- `__meta_openstack_hypervisor_status`: The hypervisor node's status.
+- `__meta_openstack_hypervisor_type`: The hypervisor node's type.
 
 ### `instance` role
 
 The `instance` role discovers one target per network interface of Nova instance.
 The target address defaults to the private IP address of the network interface.
 
-* `__meta_openstack_address_pool`: The pool of the private IP.
-* `__meta_openstack_instance_flavor`: The flavor of the OpenStack instance.
-* `__meta_openstack_instance_id`: The OpenStack instance ID.
-* `__meta_openstack_instance_image`: The ID of the image the OpenStack instance is using.
-* `__meta_openstack_instance_name`: The OpenStack instance name.
-* `__meta_openstack_instance_status`: The status of the OpenStack instance.
-* `__meta_openstack_private_ip`: The private IP of the OpenStack instance.
-* `__meta_openstack_project_id`: The project (tenant) owning this instance.
-* `__meta_openstack_public_ip`: The public IP of the OpenStack instance.
-* `__meta_openstack_tag_<tagkey>`: Each tag value of the instance.
-* `__meta_openstack_user_id`: The user account owning the tenant.
+- `__meta_openstack_address_pool`: The pool of the private IP.
+- `__meta_openstack_instance_flavor`: The flavor of the OpenStack instance.
+- `__meta_openstack_instance_id`: The OpenStack instance ID.
+- `__meta_openstack_instance_image`: The ID of the image the OpenStack instance is using.
+- `__meta_openstack_instance_name`: The OpenStack instance name.
+- `__meta_openstack_instance_status`: The status of the OpenStack instance.
+- `__meta_openstack_private_ip`: The private IP of the OpenStack instance.
+- `__meta_openstack_project_id`: The project (tenant) owning this instance.
+- `__meta_openstack_public_ip`: The public IP of the OpenStack instance.
+- `__meta_openstack_tag_<tagkey>`: Each tag value of the instance.
+- `__meta_openstack_user_id`: The user account owning the tenant.
 
 ## Component health
 
@@ -154,11 +154,11 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<OPENSTACK_ROLE>`_: Your OpenStack role.
-* _`<OPENSTACK_REGION>`_: Your OpenStack region.
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<OPENSTACK_ROLE>`_: Your OpenStack role.
+- _`<OPENSTACK_REGION>`_: Your OpenStack region.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.ovhcloud.md b/docs/sources/reference/components/discovery/discovery.ovhcloud.md
index 6b317f0439..9e487fdab1 100644
--- a/docs/sources/reference/components/discovery/discovery.ovhcloud.md
+++ b/docs/sources/reference/components/discovery/discovery.ovhcloud.md
@@ -67,40 +67,40 @@ Multiple meta labels are available on `targets` and can be used by the `discover
 
 [VPS][] meta labels:
 
-* `__meta_ovhcloud_vps_cluster`: The cluster of the server.
-* `__meta_ovhcloud_vps_datacenter`: The data center of the server.
-* `__meta_ovhcloud_vps_disk`: The disk of the server.
-* `__meta_ovhcloud_vps_display_name`: The display name of the server.
-* `__meta_ovhcloud_vps_ipv4`: The IPv4 of the server.
-* `__meta_ovhcloud_vps_ipv6`: The IPv6 of the server.
-* `__meta_ovhcloud_vps_keymap`: The KVM keyboard layout of the server.
-* `__meta_ovhcloud_vps_maximum_additional_ip`: The maximum additional IP addresses of the server.
-* `__meta_ovhcloud_vps_memory_limit`: The memory limit of the server.
-* `__meta_ovhcloud_vps_memory`: The memory of the server.
-* `__meta_ovhcloud_vps_monitoring_ip_blocks`: The monitoring IP blocks of the server.
-* `__meta_ovhcloud_vps_name`: The name of the server.
-* `__meta_ovhcloud_vps_netboot_mode`: The netboot mode of the server.
-* `__meta_ovhcloud_vps_offer_type`: The offer type of the server.
-* `__meta_ovhcloud_vps_offer`: The offer of the server.
-* `__meta_ovhcloud_vps_state`: The state of the server.
-* `__meta_ovhcloud_vps_vcore`: The number of virtual cores of the server.
-* `__meta_ovhcloud_vps_version`: The version of the server.
-* `__meta_ovhcloud_vps_zone`: The zone of the server.
+- `__meta_ovhcloud_vps_cluster`: The cluster of the server.
+- `__meta_ovhcloud_vps_datacenter`: The data center of the server.
+- `__meta_ovhcloud_vps_disk`: The disk of the server.
+- `__meta_ovhcloud_vps_display_name`: The display name of the server.
+- `__meta_ovhcloud_vps_ipv4`: The IPv4 of the server.
+- `__meta_ovhcloud_vps_ipv6`: The IPv6 of the server.
+- `__meta_ovhcloud_vps_keymap`: The KVM keyboard layout of the server.
+- `__meta_ovhcloud_vps_maximum_additional_ip`: The maximum additional IP addresses of the server.
+- `__meta_ovhcloud_vps_memory_limit`: The memory limit of the server.
+- `__meta_ovhcloud_vps_memory`: The memory of the server.
+- `__meta_ovhcloud_vps_monitoring_ip_blocks`: The monitoring IP blocks of the server.
+- `__meta_ovhcloud_vps_name`: The name of the server.
+- `__meta_ovhcloud_vps_netboot_mode`: The netboot mode of the server.
+- `__meta_ovhcloud_vps_offer_type`: The offer type of the server.
+- `__meta_ovhcloud_vps_offer`: The offer of the server.
+- `__meta_ovhcloud_vps_state`: The state of the server.
+- `__meta_ovhcloud_vps_vcore`: The number of virtual cores of the server.
+- `__meta_ovhcloud_vps_version`: The version of the server.
+- `__meta_ovhcloud_vps_zone`: The zone of the server.
 
 [Dedicated servers][] meta labels:
 
-* `__meta_ovhcloud_dedicated_server_commercial_range`: The commercial range of the server.
-* `__meta_ovhcloud_dedicated_server_datacenter`: The data center of the server.
-* `__meta_ovhcloud_dedicated_server_ipv4`: The IPv4 of the server.
-* `__meta_ovhcloud_dedicated_server_ipv6`: The IPv6 of the server.
-* `__meta_ovhcloud_dedicated_server_link_speed`: The link speed of the server.
-* `__meta_ovhcloud_dedicated_server_name`: The name of the server.
-* `__meta_ovhcloud_dedicated_server_os`: The operating system of the server.
-* `__meta_ovhcloud_dedicated_server_rack`: The rack of the server.
-* `__meta_ovhcloud_dedicated_server_reverse`: The reverse DNS name of the server.
-* `__meta_ovhcloud_dedicated_server_server_id`: The ID of the server.
-* `__meta_ovhcloud_dedicated_server_state`: The state of the server.
-* `__meta_ovhcloud_dedicated_server_support_level`: The support level of the server.
+- `__meta_ovhcloud_dedicated_server_commercial_range`: The commercial range of the server.
+- `__meta_ovhcloud_dedicated_server_datacenter`: The data center of the server.
+- `__meta_ovhcloud_dedicated_server_ipv4`: The IPv4 of the server.
+- `__meta_ovhcloud_dedicated_server_ipv6`: The IPv6 of the server.
+- `__meta_ovhcloud_dedicated_server_link_speed`: The link speed of the server.
+- `__meta_ovhcloud_dedicated_server_name`: The name of the server.
+- `__meta_ovhcloud_dedicated_server_os`: The operating system of the server.
+- `__meta_ovhcloud_dedicated_server_rack`: The rack of the server.
+- `__meta_ovhcloud_dedicated_server_reverse`: The reverse DNS name of the server.
+- `__meta_ovhcloud_dedicated_server_server_id`: The ID of the server.
+- `__meta_ovhcloud_dedicated_server_state`: The state of the server.
+- `__meta_ovhcloud_dedicated_server_support_level`: The support level of the server.
 
 ## Component health
 
@@ -143,13 +143,13 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<APPLICATION_KEY>`_: The OVHcloud [API][] application key.
-* _`<APPLICATION_SECRET>`_: The OVHcloud [API][] application secret.
-* _`<CONSUMER_KEY>`_: The OVHcloud [API][] consumer key.
-* _`<SERVICE>`_: The OVHcloud service of the targets to retrieve.
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<APPLICATION_KEY>`_: The OVHcloud [API][] application key.
+- _`<APPLICATION_SECRET>`_: The OVHcloud [API][] application secret.
+- _`<CONSUMER_KEY>`_: The OVHcloud [API][] consumer key.
+- _`<SERVICE>`_: The OVHcloud service of the targets to retrieve.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.process.md b/docs/sources/reference/components/discovery/discovery.process.md
index 700af8764c..ff5cc33b54 100644
--- a/docs/sources/reference/components/discovery/discovery.process.md
+++ b/docs/sources/reference/components/discovery/discovery.process.md
@@ -124,13 +124,13 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__container_id__`: The container ID. Taken from `/proc/<pid>/cgroup`. If the process isn't running in a container, this label isn't set.
-* `__meta_process_commandline`: The process command line. Taken from `/proc/<pid>/cmdline`.
-* `__meta_process_cwd`: The process current working directory. Taken from `/proc/<pid>/cwd`.
-* `__meta_process_exe`: The process executable path. Taken from `/proc/<pid>/exe`.
-* `__meta_process_uid`: The process UID. Taken from `/proc/<pid>/status`.
-* `__meta_process_username`: The process username. Taken from `__meta_process_uid` and `os/user/LookupID`.
-* `__process_pid__`: The process PID.
+- `__container_id__`: The container ID. Taken from `/proc/<pid>/cgroup`. If the process isn't running in a container, this label isn't set.
+- `__meta_process_commandline`: The process command line. Taken from `/proc/<pid>/cmdline`.
+- `__meta_process_cwd`: The process current working directory. Taken from `/proc/<pid>/cwd`.
+- `__meta_process_exe`: The process executable path. Taken from `/proc/<pid>/exe`.
+- `__meta_process_uid`: The process UID. Taken from `/proc/<pid>/status`.
+- `__meta_process_username`: The process username. Taken from `__meta_process_uid` and `os/user/LookupID`.
+- `__process_pid__`: The process PID.
 
 ## Component health
 
@@ -209,3 +209,4 @@ Refer to the linked documentation for more details.
 {{< /admonition >}}
 
 <!-- END GENERATED COMPATIBLE COMPONENTS -->
+```
diff --git a/docs/sources/reference/components/discovery/discovery.puppetdb.md b/docs/sources/reference/components/discovery/discovery.puppetdb.md
index 3dcd6cd3c8..df4b734725 100644
--- a/docs/sources/reference/components/discovery/discovery.puppetdb.md
+++ b/docs/sources/reference/components/discovery/discovery.puppetdb.md
@@ -30,29 +30,29 @@ discovery.puppetdb "<LABEL>" {
 
 You can use the following arguments with `discovery.puppetdb`:
 
-| Name                     | Type                | Description                                                                                      | Default | Required |
-| ------------------------ | ------------------- | ------------------------------------------------------------------------------------------------ | ------- | -------- |
-| `query`                  | `string`            | Puppet Query Language (PQL) query. Only resources are supported.                                 |         | yes      |
-| `url`                    | `string`            | The URL of the PuppetDB root query endpoint.                                                     |         | yes      |
-| `bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.                                             |         | no       |
-| `bearer_token`           | `secret`            | Bearer token to authenticate with.                                                               |         | no       |
-| `enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                                                         | `true`  | no       |
-| `follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.                                     | `true`  | no       |
-| `include_parameters`     | `bool`              | Whether to include the parameters as meta labels. Due to the differences between parameter types and Prometheus labels, some parameters might not be rendered. The format of the parameters might also change in future releases. Make sure that you don't have secrets exposed as parameters if you enable this. | `false` | no |
-| `no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. |         | no       |
-| `port`                   | `int`               | The port to scrape metrics from.                                                                 | `80`    | no       |
-| `proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests.                                    |         | no       |
-| `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
-| `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
-| `refresh_interval`       | `duration`          | Frequency to refresh targets.                                                                    | `"30s"` | no       |
-
- At most, one of the following can be provided:
-
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+| Name                     | Type                | Description                                                                                                                                                                                                                                                                                                       | Default | Required |
+| ------------------------ | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | -------- |
+| `query`                  | `string`            | Puppet Query Language (PQL) query. Only resources are supported.                                                                                                                                                                                                                                                  |         | yes      |
+| `url`                    | `string`            | The URL of the PuppetDB root query endpoint.                                                                                                                                                                                                                                                                      |         | yes      |
+| `bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.                                                                                                                                                                                                                                                              |         | no       |
+| `bearer_token`           | `secret`            | Bearer token to authenticate with.                                                                                                                                                                                                                                                                                |         | no       |
+| `enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                                                                                                                                                                                                                                                                          | `true`  | no       |
+| `follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.                                                                                                                                                                                                                                                      | `true`  | no       |
+| `include_parameters`     | `bool`              | Whether to include the parameters as meta labels. Due to the differences between parameter types and Prometheus labels, some parameters might not be rendered. The format of the parameters might also change in future releases. Make sure that you don't have secrets exposed as parameters if you enable this. | `false` | no       |
+| `no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying.                                                                                                                                                                                                                  |         | no       |
+| `port`                   | `int`               | The port to scrape metrics from.                                                                                                                                                                                                                                                                                  | `80`    | no       |
+| `proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests.                                                                                                                                                                                                                                                     |         | no       |
+| `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                                                                                                                                                                                                                                             | `false` | no       |
+| `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                                                                                                                                                                                                                                              |         | no       |
+| `refresh_interval`       | `duration`          | Frequency to refresh targets.                                                                                                                                                                                                                                                                                     | `"30s"` | no       |
+
+At most, one of the following can be provided:
+
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
 [arguments]: #arguments
 
@@ -112,16 +112,16 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_puppetdb_certname`: The name of the node associated with the resource.
-* `__meta_puppetdb_environment`: The environment of the node associated with the resource.
-* `__meta_puppetdb_exported`: Whether the resource is exported, either `true` or `false`.
-* `__meta_puppetdb_file`: The manifest file in which the resource was declared.
-* `__meta_puppetdb_parameter_<parametername>`: The parameters of the resource.
-* `__meta_puppetdb_query`: The Puppet Query Language (PQL) query.
-* `__meta_puppetdb_resource`: A SHA-1 hash of the resource's type, title, and parameters, for identification.
-* `__meta_puppetdb_tags`: A comma separated list of resource tags.
-* `__meta_puppetdb_title`: The resource title.
-* `__meta_puppetdb_type`: The resource type.
+- `__meta_puppetdb_certname`: The name of the node associated with the resource.
+- `__meta_puppetdb_environment`: The environment of the node associated with the resource.
+- `__meta_puppetdb_exported`: Whether the resource is exported, either `true` or `false`.
+- `__meta_puppetdb_file`: The manifest file in which the resource was declared.
+- `__meta_puppetdb_parameter_<parametername>`: The parameters of the resource.
+- `__meta_puppetdb_query`: The Puppet Query Language (PQL) query.
+- `__meta_puppetdb_resource`: A SHA-1 hash of the resource's type, title, and parameters, for identification.
+- `__meta_puppetdb_tags`: A comma separated list of resource tags.
+- `__meta_puppetdb_title`: The resource title.
+- `__meta_puppetdb_type`: The resource type.
 
 ## Component health
 
@@ -166,9 +166,9 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.scaleway.md b/docs/sources/reference/components/discovery/discovery.scaleway.md
index 3609d58240..4474d0dd1b 100644
--- a/docs/sources/reference/components/discovery/discovery.scaleway.md
+++ b/docs/sources/reference/components/discovery/discovery.scaleway.md
@@ -53,8 +53,8 @@ You can use the following arguments with `discovery.scaleway`:
 The `role` argument determines what type of Scaleway machines to discover.
 It must be set to one of the following:
 
-* `"baremetal"`: Discover [bare metal][] Scaleway machines.
-* `"instance"`: Discover virtual Scaleway [instances][instance].
+- `"baremetal"`: Discover [bare metal][] Scaleway machines.
+- `"instance"`: Discover virtual Scaleway [instances][instance].
 
 The `name_filter` and `tags_filter` arguments can be used to filter the set of discovered servers.
 `name_filter` returns machines matching a specific name, while `tags_filter` returns machines who contain _all_ the tags listed in the `tags_filter` argument.
@@ -87,42 +87,42 @@ The following fields are exported and can be referenced by other components:
 
 When `role` is `baremetal`, discovered targets include the following labels:
 
-* `__meta_scaleway_baremetal_id`: The ID of the server.
-* `__meta_scaleway_baremetal_name`: The name of the server.
-* `__meta_scaleway_baremetal_os_name`: The operating system name of the server.
-* `__meta_scaleway_baremetal_os_version`: The operating system version of the server.
-* `__meta_scaleway_baremetal_project_id`: The project ID the server belongs to.
-* `__meta_scaleway_baremetal_public_ipv4`: The public IPv4 address of the server.
-* `__meta_scaleway_baremetal_public_ipv6`: The public IPv6 address of the server.
-* `__meta_scaleway_baremetal_status`: The current status of the server.
-* `__meta_scaleway_baremetal_tags`: The list of tags associated with the server concatenated with a `,`.
-* `__meta_scaleway_baremetal_type`: The commercial type of the server.
-* `__meta_scaleway_baremetal_zone`: The availability zone of the server.
+- `__meta_scaleway_baremetal_id`: The ID of the server.
+- `__meta_scaleway_baremetal_name`: The name of the server.
+- `__meta_scaleway_baremetal_os_name`: The operating system name of the server.
+- `__meta_scaleway_baremetal_os_version`: The operating system version of the server.
+- `__meta_scaleway_baremetal_project_id`: The project ID the server belongs to.
+- `__meta_scaleway_baremetal_public_ipv4`: The public IPv4 address of the server.
+- `__meta_scaleway_baremetal_public_ipv6`: The public IPv6 address of the server.
+- `__meta_scaleway_baremetal_status`: The current status of the server.
+- `__meta_scaleway_baremetal_tags`: The list of tags associated with the server concatenated with a `,`.
+- `__meta_scaleway_baremetal_type`: The commercial type of the server.
+- `__meta_scaleway_baremetal_zone`: The availability zone of the server.
 
 When `role` is `instance`, discovered targets include the following labels:
 
-* `__meta_scaleway_instance_boot_type`: The boot type of the server.
-* `__meta_scaleway_instance_hostname`: The hostname of the server.
-* `__meta_scaleway_instance_id`: The ID of the server.
-* `__meta_scaleway_instance_image_arch`: The architecture of the image the server is running.
-* `__meta_scaleway_instance_image_id`: The ID of the image the server is running.
-* `__meta_scaleway_instance_image_name`: The name of the image the server is running.
-* `__meta_scaleway_instance_location_cluster_id`: The ID of the cluster for the server's location.
-* `__meta_scaleway_instance_location_hypervisor_id`: The hypervisor ID for the server's location.
-* `__meta_scaleway_instance_location_node_id`: The node ID for the server's location.
-* `__meta_scaleway_instance_name`: The name of the server.
-* `__meta_scaleway_instance_organization_id`: The organization ID that the server belongs to.
-* `__meta_scaleway_instance_private_ipv4`: The private IPv4 address of the server.
-* `__meta_scaleway_instance_project_id`: The project ID the server belongs to.
-* `__meta_scaleway_instance_public_ipv4`: The public IPv4 address of the server.
-* `__meta_scaleway_instance_public_ipv6`: The public IPv6 address of the server.
-* `__meta_scaleway_instance_region`: The region of the server.
-* `__meta_scaleway_instance_security_group_id`: The ID of the security group the server is assigned to.
-* `__meta_scaleway_instance_security_group_name`: The name of the security group the server is assigned to.
-* `__meta_scaleway_instance_status`: The current status of the server.
-* `__meta_scaleway_instance_tags`: The list of tags associated with the server concatenated with a `,`.
-* `__meta_scaleway_instance_type`: The commercial type of the server.
-* `__meta_scaleway_instance_zone`: The availability zone of the server.
+- `__meta_scaleway_instance_boot_type`: The boot type of the server.
+- `__meta_scaleway_instance_hostname`: The hostname of the server.
+- `__meta_scaleway_instance_id`: The ID of the server.
+- `__meta_scaleway_instance_image_arch`: The architecture of the image the server is running.
+- `__meta_scaleway_instance_image_id`: The ID of the image the server is running.
+- `__meta_scaleway_instance_image_name`: The name of the image the server is running.
+- `__meta_scaleway_instance_location_cluster_id`: The ID of the cluster for the server's location.
+- `__meta_scaleway_instance_location_hypervisor_id`: The hypervisor ID for the server's location.
+- `__meta_scaleway_instance_location_node_id`: The node ID for the server's location.
+- `__meta_scaleway_instance_name`: The name of the server.
+- `__meta_scaleway_instance_organization_id`: The organization ID that the server belongs to.
+- `__meta_scaleway_instance_private_ipv4`: The private IPv4 address of the server.
+- `__meta_scaleway_instance_project_id`: The project ID the server belongs to.
+- `__meta_scaleway_instance_public_ipv4`: The public IPv4 address of the server.
+- `__meta_scaleway_instance_public_ipv6`: The public IPv6 address of the server.
+- `__meta_scaleway_instance_region`: The region of the server.
+- `__meta_scaleway_instance_security_group_id`: The ID of the security group the server is assigned to.
+- `__meta_scaleway_instance_security_group_name`: The name of the security group the server is assigned to.
+- `__meta_scaleway_instance_status`: The current status of the server.
+- `__meta_scaleway_instance_tags`: The list of tags associated with the server concatenated with a `,`.
+- `__meta_scaleway_instance_type`: The commercial type of the server.
+- `__meta_scaleway_instance_zone`: The availability zone of the server.
 
 ## Component health
 
@@ -166,13 +166,13 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<SCALEWAY_PROJECT_ID>`_: The project ID of your Scaleway machines.
-* _`<SCALEWAY_PROJECT_ROLE>`_: Set to `baremetal` to discover [bare metal][] machines or `instance` to discover [virtual instances][instance].
-* _`<SCALEWAY_ACCESS_KEY>`_: Your Scaleway API access key.
-* _`<SCALEWAY_SECRET_KEY>`_: Your Scaleway API secret key.
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<SCALEWAY_PROJECT_ID>`_: The project ID of your Scaleway machines.
+- _`<SCALEWAY_PROJECT_ROLE>`_: Set to `baremetal` to discover [bare metal][] machines or `instance` to discover [virtual instances][instance].
+- _`<SCALEWAY_ACCESS_KEY>`_: Your Scaleway API access key.
+- _`<SCALEWAY_SECRET_KEY>`_: Your Scaleway API secret key.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.serverset.md b/docs/sources/reference/components/discovery/discovery.serverset.md
index 7fd9deed64..94b2d5ba05 100644
--- a/docs/sources/reference/components/discovery/discovery.serverset.md
+++ b/docs/sources/reference/components/discovery/discovery.serverset.md
@@ -53,13 +53,13 @@ The following fields are exported and can be referenced by other components:
 
 The following metadata labels are available on targets during relabeling:
 
-* `__meta_serverset_endpoint_host_<endpoint>`: The host of the given endpoint.
-* `__meta_serverset_endpoint_host`: The host of the default endpoint.
-* `__meta_serverset_endpoint_port_<endpoint>`: The port of the given endpoint.
-* `__meta_serverset_endpoint_port`: The port of the default endpoint.
-* `__meta_serverset_path`: The full path to the serverset member node in Zookeeper.
-* `__meta_serverset_shard`: The shard number of the member.
-* `__meta_serverset_status`: The status of the member.
+- `__meta_serverset_endpoint_host_<endpoint>`: The host of the given endpoint.
+- `__meta_serverset_endpoint_host`: The host of the default endpoint.
+- `__meta_serverset_endpoint_port_<endpoint>`: The port of the given endpoint.
+- `__meta_serverset_endpoint_port`: The port of the default endpoint.
+- `__meta_serverset_path`: The full path to the serverset member node in Zookeeper.
+- `__meta_serverset_shard`: The shard number of the member.
+- `__meta_serverset_status`: The status of the member.
 
 ## Component health
 
diff --git a/docs/sources/reference/components/discovery/discovery.triton.md b/docs/sources/reference/components/discovery/discovery.triton.md
index e4b088b3f8..0e8096f289 100644
--- a/docs/sources/reference/components/discovery/discovery.triton.md
+++ b/docs/sources/reference/components/discovery/discovery.triton.md
@@ -44,8 +44,8 @@ If you omit `groups`, all containers owned by the requesting account are scraped
 
 `role` can be set to:
 
-* `"container"` to discover virtual machines (SmartOS zones, lx/KVM/bhyve branded zones) running on Triton.
-* `"cn"` to discover compute nodes (servers/global zones) making up the Triton infrastructure.
+- `"container"` to discover virtual machines (SmartOS zones, lx/KVM/bhyve branded zones) running on Triton.
+- `"cn"` to discover compute nodes (servers/global zones) making up the Triton infrastructure.
 
 ## Blocks
 
@@ -73,17 +73,17 @@ The following fields are exported and can be referenced by other components:
 
 When `role` is set to `"container"`, each target includes the following labels:
 
-* `__meta_triton_groups`: The list of groups belonging to the target joined by a comma separator.
-* `__meta_triton_machine_alias`: The alias of the target container.
-* `__meta_triton_machine_brand`: The brand of the target container.
-* `__meta_triton_machine_id`: The UUID of the target container.
-* `__meta_triton_machine_image`: The target container's image type.
-* `__meta_triton_server_id`: The server UUID the target container is running on.
+- `__meta_triton_groups`: The list of groups belonging to the target joined by a comma separator.
+- `__meta_triton_machine_alias`: The alias of the target container.
+- `__meta_triton_machine_brand`: The brand of the target container.
+- `__meta_triton_machine_id`: The UUID of the target container.
+- `__meta_triton_machine_image`: The target container's image type.
+- `__meta_triton_server_id`: The server UUID the target container is running on.
 
 When `role` is set to `"cn"` each target includes the following labels:
 
-* `__meta_triton_machine_alias`: The hostname of the target. Requires triton-cmon 1.7.0 or newer.
-* `__meta_triton_machine_id`: The UUID of the target.
+- `__meta_triton_machine_alias`: The hostname of the target. Requires triton-cmon 1.7.0 or newer.
+- `__meta_triton_machine_id`: The UUID of the target.
 
 ## Component health
 
@@ -126,12 +126,12 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<TRITON_ACCOUNT>`_: Your Triton account.
-* _`<TRITON_DNS_SUFFIX>`_: Your Triton DNS suffix.
-* _`<TRITON_ENDPOINT>`_: Your Triton endpoint.
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<TRITON_ACCOUNT>`_: Your Triton account.
+- _`<TRITON_DNS_SUFFIX>`_: Your Triton DNS suffix.
+- _`<TRITON_ENDPOINT>`_: Your Triton endpoint.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/discovery/discovery.uyuni.md b/docs/sources/reference/components/discovery/discovery.uyuni.md
index ffe5c3fe51..fd5e39b1bb 100644
--- a/docs/sources/reference/components/discovery/discovery.uyuni.md
+++ b/docs/sources/reference/components/discovery/discovery.uyuni.md
@@ -71,15 +71,15 @@ The following fields are exported and can be referenced by other components:
 
 Each target includes the following labels:
 
-* `__meta_uyuni_endpoint_name`: The name of the endpoint.
-* `__meta_uyuni_exporter`: The name of the exporter.
-* `__meta_uyuni_groups`: The groups the Uyuni Minion belongs to.
-* `__meta_uyuni_metrics_path`: The path to the metrics endpoint.
-* `__meta_uyuni_minion_hostname`: The hostname of the Uyuni Minion.
-* `__meta_uyuni_primary_fqdn`: The FQDN of the Uyuni primary.
-* `__meta_uyuni_proxy_module`: The name of the Uyuni module.
-* `__meta_uyuni_scheme`: `https` if TLS is enabled on the endpoint, `http` otherwise.
-* `__meta_uyuni_system_id`: The system ID of the Uyuni Minion.
+- `__meta_uyuni_endpoint_name`: The name of the endpoint.
+- `__meta_uyuni_exporter`: The name of the exporter.
+- `__meta_uyuni_groups`: The groups the Uyuni Minion belongs to.
+- `__meta_uyuni_metrics_path`: The path to the metrics endpoint.
+- `__meta_uyuni_minion_hostname`: The hostname of the Uyuni Minion.
+- `__meta_uyuni_primary_fqdn`: The FQDN of the Uyuni primary.
+- `__meta_uyuni_proxy_module`: The name of the Uyuni module.
+- `__meta_uyuni_scheme`: `https` if TLS is enabled on the endpoint, `http` otherwise.
+- `__meta_uyuni_system_id`: The system ID of the Uyuni Minion.
 
 These labels are largely derived from a [listEndpoints][] API call to the Uyuni Server.
 
@@ -126,11 +126,11 @@ prometheus.remote_write "demo" {
 
 Replace the following:
 
-* _`<UYUNI_USERNAME>`_: The username to use for authentication to the Uyuni server.
-* _`<UYUNI_PASSWORD>`_: The password to use for authentication to the Uyuni server.
-* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
-* _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
-* _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
+- _`<UYUNI_USERNAME>`_: The username to use for authentication to the Uyuni server.
+- _`<UYUNI_PASSWORD>`_: The password to use for authentication to the Uyuni server.
+- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API.
+- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/faro/faro.receiver.md b/docs/sources/reference/components/faro/faro.receiver.md
index b610b49ca8..5b5326bfdd 100644
--- a/docs/sources/reference/components/faro/faro.receiver.md
+++ b/docs/sources/reference/components/faro/faro.receiver.md
@@ -29,21 +29,21 @@ faro.receiver "<LABEL>" {
 
 You can use the following arguments with `faro.receiver`:
 
-| Name               | Type          | Description                                  | Default  | Required |
-| ------------------ | ------------- | -------------------------------------------- | -------- | -------- |
-| `extra_log_labels` | `map(string)` | Extra labels to attach to emitted log lines. | `{}`     | no       |
+| Name               | Type          | Description                                  | Default | Required |
+| ------------------ | ------------- | -------------------------------------------- | ------- | -------- |
+| `extra_log_labels` | `map(string)` | Extra labels to attach to emitted log lines. | `{}`    | no       |
 
 ## Blocks
 
 You can use the following blocks with `faro.receiver`:
 
-| Block                                        | Description                                          | Required |
-| -------------------------------------------- | ---------------------------------------------------- | -------- |
-| [`output`][output]                           | Configures where to send collected telemetry data.   | yes      |
-| [`server`][server]                           | Configures the HTTP server.                          | no       |
-| `server` >  [`rate_limiting`][rate_limiting] | Configures rate limiting for the HTTP server.        | no       |
-| [`sourcemaps`][sourcemaps]                   | Configures sourcemap retrieval.                      | no       |
-| `sourcemaps` >  [`location`][location]       | Configures on-disk location for sourcemap retrieval. | no       |
+| Block                                       | Description                                          | Required |
+| ------------------------------------------- | ---------------------------------------------------- | -------- |
+| [`output`][output]                          | Configures where to send collected telemetry data.   | yes      |
+| [`server`][server]                          | Configures the HTTP server.                          | no       |
+| `server` > [`rate_limiting`][rate_limiting] | Configures rate limiting for the HTTP server.        | no       |
+| [`sourcemaps`][sourcemaps]                  | Configures sourcemap retrieval.                      | no       |
+| `sourcemaps` > [`location`][location]       | Configures on-disk location for sourcemap retrieval. | no       |
 
 The > symbol indicates deeper levels of nesting.
 For example, `sourcemaps` > `location` refers to a `location` block defined inside an `sourcemaps` block.
@@ -178,18 +178,18 @@ The template value is replaced with the release value provided by the [Faro Web
 
 `faro.receiver` exposes the following metrics for monitoring the component:
 
-* `faro_receiver_logs_total` (counter): Total number of ingested logs.
-* `faro_receiver_measurements_total` (counter): Total number of ingested measurements.
-* `faro_receiver_exceptions_total` (counter): Total number of ingested exceptions.
-* `faro_receiver_events_total` (counter): Total number of ingested events.
-* `faro_receiver_exporter_errors_total` (counter): Total number of errors produced by an internal exporter.
-* `faro_receiver_request_duration_seconds` (histogram): Time (in seconds) spent serving HTTP requests.
-* `faro_receiver_request_message_bytes` (histogram): Size (in bytes) of HTTP requests received from clients.
-* `faro_receiver_response_message_bytes` (histogram): Size (in bytes) of HTTP responses sent to clients.
-* `faro_receiver_inflight_requests` (gauge): Current number of inflight requests.
-* `faro_receiver_sourcemap_cache_size` (counter): Number of items in sourcemap cache per origin.
-* `faro_receiver_sourcemap_downloads_total` (counter): Total number of sourcemap downloads performed per origin and status.
-* `faro_receiver_sourcemap_file_reads_total` (counter): Total number of sourcemap retrievals using the filesystem per origin and status.
+- `faro_receiver_logs_total` (counter): Total number of ingested logs.
+- `faro_receiver_measurements_total` (counter): Total number of ingested measurements.
+- `faro_receiver_exceptions_total` (counter): Total number of ingested exceptions.
+- `faro_receiver_events_total` (counter): Total number of ingested events.
+- `faro_receiver_exporter_errors_total` (counter): Total number of errors produced by an internal exporter.
+- `faro_receiver_request_duration_seconds` (histogram): Time (in seconds) spent serving HTTP requests.
+- `faro_receiver_request_message_bytes` (histogram): Size (in bytes) of HTTP requests received from clients.
+- `faro_receiver_response_message_bytes` (histogram): Size (in bytes) of HTTP responses sent to clients.
+- `faro_receiver_inflight_requests` (gauge): Current number of inflight requests.
+- `faro_receiver_sourcemap_cache_size` (counter): Number of items in sourcemap cache per origin.
+- `faro_receiver_sourcemap_downloads_total` (counter): Total number of sourcemap downloads performed per origin and status.
+- `faro_receiver_sourcemap_file_reads_total` (counter): Total number of sourcemap retrievals using the filesystem per origin and status.
 
 ## Example
 
@@ -227,13 +227,13 @@ otelcol.exporter.otlp "traces" {
 
 Replace the following:
 
-* _`<NETWORK_ADDRESS>`_: The IP address of the network interface to listen to traffic on.
+- _`<NETWORK_ADDRESS>`_: The IP address of the network interface to listen to traffic on.
   This IP address must be reachable by browsers using the web application to instrument.
-* _`<PATH_TO_SOURCEMAPS>`_: The path on disk where sourcemaps are located.
-* _`<WEB_APP_PREFIX>`_: Prefix of the web application being instrumented.
-* `LOKI_ADDRESS`: Address of the Loki server to send logs to.
+- _`<PATH_TO_SOURCEMAPS>`_: The path on disk where sourcemaps are located.
+- _`<WEB_APP_PREFIX>`_: Prefix of the web application being instrumented.
+- `LOKI_ADDRESS`: Address of the Loki server to send logs to.
   Refer to [`loki.write`][loki.write] if you want to use authentication to send logs to the Loki server.
-* _`<OTLP_ADDRESS>`_: The address of the OTLP-compatible server to send traces to.
+- _`<OTLP_ADDRESS>`_: The address of the OTLP-compatible server to send traces to.
   Refer to[`otelcol.exporter.otlp`][otelcol.exporter.otlp] if you want to use authentication to send logs to the Loki server.
 
 [loki.write]: ../../loki/loki.write/
@@ -248,7 +248,6 @@ Replace the following:
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 - Components that export [OpenTelemetry `otelcol.Consumer`](../../../compatibility/#opentelemetry-otelcolconsumer-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/local/local.file.md b/docs/sources/reference/components/local/local.file.md
index bec308ee4f..054f94d670 100644
--- a/docs/sources/reference/components/local/local.file.md
+++ b/docs/sources/reference/components/local/local.file.md
@@ -30,7 +30,7 @@ local.file "<LABEL>" {
 You can use the following arguments with `local.file`:
 
 | Name             | Type       | Description                                              | Default      | Required |
-|------------------|------------|----------------------------------------------------------|--------------|----------|
+| ---------------- | ---------- | -------------------------------------------------------- | ------------ | -------- |
 | `filename`       | `string`   | Path of the file on disk to watch.                       |              | yes      |
 | `detector`       | `string`   | Which file change detector to use, `fsnotify` or `poll`. | `"fsnotify"` | no       |
 | `is_secret`      | `bool`     | Marks the file as containing a [secret][].               | `false`      | no       |
@@ -49,7 +49,7 @@ The `local.file` component doesn't support any blocks. You can configure this co
 The following fields are exported and can be referenced by other components:
 
 | Name      | Type                 | Description                                         |
-|-----------|----------------------|-----------------------------------------------------|
+| --------- | -------------------- | --------------------------------------------------- |
 | `content` | `string` or `secret` | The contents of the file from the most recent read. |
 
 The `content` field has the `secret` type only if the `is_secret` argument is true.
@@ -70,7 +70,7 @@ The read error is exposed as a log message and in the debug information for the
 
 ## Debug metrics
 
-* `local_file_timestamp_last_accessed_unix_seconds` (gauge): The timestamp, in Unix seconds, that the file was last successfully accessed.
+- `local_file_timestamp_last_accessed_unix_seconds` (gauge): The timestamp, in Unix seconds, that the file was last successfully accessed.
 
 ## Example
 
diff --git a/docs/sources/reference/components/local/local.file_match.md b/docs/sources/reference/components/local/local.file_match.md
index b172b19ce4..3d709cf0f8 100644
--- a/docs/sources/reference/components/local/local.file_match.md
+++ b/docs/sources/reference/components/local/local.file_match.md
@@ -26,16 +26,16 @@ local.file_match "LABEL" {
 
 You can use the following arguments with `local.file_match`:
 
-| Name                | Type                | Description                                                                                | Default | Required |
-|---------------------|---------------------|--------------------------------------------------------------------------------------------|---------|----------|
-| `path_targets`      | `list(map(string))` | Targets to expand; looks for glob patterns on the  `__path__` and `__path_exclude__` keys. |         | yes      |
-| `sync_period`       | `duration`          | How often to sync filesystem and targets.                                                  | `"10s"` | no       |
+| Name           | Type                | Description                                                                               | Default | Required |
+| -------------- | ------------------- | ----------------------------------------------------------------------------------------- | ------- | -------- |
+| `path_targets` | `list(map(string))` | Targets to expand; looks for glob patterns on the `__path__` and `__path_exclude__` keys. |         | yes      |
+| `sync_period`  | `duration`          | How often to sync filesystem and targets.                                                 | `"10s"` | no       |
 
 `path_targets` uses [doublestar][] style paths.
 
-* `/tmp/**/*.log` matches all subdirectories of `tmp` and include any files that end in `*.log`.
-* `/tmp/apache/*.log` matches only files in `/tmp/apache/` that end in `*.log`.
-* `/tmp/**` matches all subdirectories of `tmp`, `tmp` itself, and all files.
+- `/tmp/**/*.log` matches all subdirectories of `tmp` and include any files that end in `*.log`.
+- `/tmp/apache/*.log` matches only files in `/tmp/apache/` that end in `*.log`.
+- `/tmp/**` matches all subdirectories of `tmp`, `tmp` itself, and all files.
 
 ## Blocks
 
@@ -46,12 +46,12 @@ The `local.file_match` component doesn't support any blocks. You can configure t
 The following fields are exported and can be referenced by other components:
 
 | Name      | Type                | Description                                        |
-|-----------|---------------------|----------------------------------------------------|
+| --------- | ------------------- | -------------------------------------------------- |
 | `targets` | `list(map(string))` | The set of targets discovered from the filesystem. |
 
 Each target includes the following label:
 
-* `__path__`: Absolute path to the file.
+- `__path__`: Absolute path to the file.
 
 ## Component health
 
@@ -98,9 +98,9 @@ loki.write "endpoint" {
 
 Replace the following:
 
-* _`<LOKI_URL>`_: The URL of the Loki server to send logs to.
-* _`<USERNAME>`_: The username to use for authentication to the Loki API.
-* _`<PASSWORD>`_: The password to use for authentication to the Loki API.
+- _`<LOKI_URL>`_: The URL of the Loki server to send logs to.
+- _`<USERNAME>`_: The username to use for authentication to the Loki API.
+- _`<PASSWORD>`_: The password to use for authentication to the Loki API.
 
 ### Send Kubernetes Pod logs to Loki
 
@@ -150,9 +150,9 @@ loki.write "endpoint" {
 
 Replace the following:
 
-* _`<LOKI_URL>`_: The URL of the Loki server to send logs to.
-* _`<USERNAME>`_: The username to use for authentication to the Loki API.
-* _`<PASSWORD>`_: The password to use for authentication to the Loki API.
+- _`<LOKI_URL>`_: The URL of the Loki server to send logs to.
+- _`<USERNAME>`_: The username to use for authentication to the Loki API.
+- _`<PASSWORD>`_: The password to use for authentication to the Loki API.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/loki/loki.process.md b/docs/sources/reference/components/loki/loki.process.md
index c4c9a03760..424cc7fcce 100644
--- a/docs/sources/reference/components/loki/loki.process.md
+++ b/docs/sources/reference/components/loki/loki.process.md
@@ -121,10 +121,10 @@ stage.cri {}
 
 CRI specifies log lines as single space-delimited values with the following components:
 
-* `time`: The timestamp string of the log.
-* `stream`: Either `stdout` or `stderr`.
-* `flags`: CRI flags including `F` or `P`.
-* `log`: The contents of the log line.
+- `time`: The timestamp string of the log.
+- `stream`: Either `stdout` or `stderr`.
+- `flags`: CRI flags including `F` or `P`.
+- `log`: The contents of the log line.
 
 Given the following log line, the subsequent key-value pairs are created in the shared map of extracted data:
 
@@ -171,9 +171,9 @@ stage.docker {}
 
 Docker log entries are formatted as JSON with the following keys:
 
-* `log`: The content of log line.
-* `stream`: Either `stdout` or `stderr`.
-* `time`: The timestamp string of the log line.
+- `log`: The content of log line.
+- `stream`: Either `stdout` or `stderr`.
+- `time`: The timestamp string of the log line.
 
 Given the following log line, the subsequent key-value pairs are created in the shared map of extracted data:
 
@@ -205,14 +205,14 @@ The following arguments are supported:
 
 The `expression` field must be a RE2 regular expression string.
 
-* If `source` is empty or not provided, the regular expression attempts to match the log line itself.
-* If `source` is a single name, the regular expression attempts to match the corresponding value from the extracted map.
-* If `source` is a comma-separated list of names, the corresponding values from the extracted map are concatenated using `separator` and the regular expression attempts to match the concatenated string.
+- If `source` is empty or not provided, the regular expression attempts to match the log line itself.
+- If `source` is a single name, the regular expression attempts to match the corresponding value from the extracted map.
+- If `source` is a comma-separated list of names, the corresponding values from the extracted map are concatenated using `separator` and the regular expression attempts to match the concatenated string.
 
 The `value` field can only work with values from the extracted map, and must be specified together with `source`.
 
-* If `source` is a single name, the entries are dropped when there is an exact match between the corresponding value from the extracted map and the `value`.
-* If `source` is a comma-separated list of names, the entries are dropped when the `value` matches the `source` values from extracted data, concatenated using the `separator`.
+- If `source` is a single name, the entries are dropped when there is an exact match between the corresponding value from the extracted map and the `value`.
+- If `source` is a comma-separated list of names, the entries are dropped when the `value` matches the `source` values from extracted data, concatenated using the `separator`.
 
 Whenever an entry is dropped, the metric `loki_process_dropped_lines_total` is incremented.
 By default, the reason label is `"drop_stage"`, but you can provide a custom label using the `drop_counter_reason` argument.
@@ -287,14 +287,14 @@ Given the following log line:
 
 The first stage would create the following key-value pairs in the set of extracted data:
 
-* `message`: `Message type:\r\nOverwritten: new\r\nImage: C:\Users\User\alloy.exe`
-* `Overwritten`: `old`
+- `message`: `Message type:\r\nOverwritten: new\r\nImage: C:\Users\User\alloy.exe`
+- `Overwritten`: `old`
 
 The second stage parses the value of `message` from the extracted data and appends or overwrites the following key-value pairs to the set of extracted data:
 
-* `Image`: `C:\\Users\\User\\alloy.exe`
-* `Message_type`: (empty string)
-* `Overwritten`: `new`
+- `Image`: `C:\\Users\\User\\alloy.exe`
+- `Message_type`: (empty string)
+- `Overwritten`: `new`
 
 ### `stage.geoip`
 
@@ -530,7 +530,7 @@ You can use one of two options to circumvent this issue:
 
 1. An escaped double quote. For example: `http_user_agent = "\"request_User-Agent\""`
 1. A backtick quote. For example: ``http_user_agent = `"request_User-Agent"` ``
-{{< /admonition >}}
+   {{< /admonition >}}
 
 ### `stage.label_drop`
 
@@ -836,7 +836,7 @@ The following arguments are supported:
 
 | Name                | Type       | Description                                                                         | Default                  | Required |
 | ------------------- | ---------- | ----------------------------------------------------------------------------------- | ------------------------ | -------- |
-| `action`            | `string`   | The action to take. Valid actions are  `inc`, `dec`, `set`, `add`, or `sub`.        |                          | yes      |
+| `action`            | `string`   | The action to take. Valid actions are `inc`, `dec`, `set`, `add`, or `sub`.         |                          | yes      |
 | `name`              | `string`   | The metric name.                                                                    |                          | yes      |
 | `description`       | `string`   | The metric's description and help text.                                             | `""`                     | no       |
 | `max_idle_duration` | `duration` | Maximum amount of time to wait until the metric is marked as 'stale' and removed.   | `"5m"`                   | no       |
@@ -856,7 +856,7 @@ The following arguments are supported:
 
 | Name                | Type          | Description                                                                         | Default                  | Required |
 | ------------------- | ------------- | ----------------------------------------------------------------------------------- | ------------------------ | -------- |
-| `buckets`           | `list(float)` | Predefined buckets                                                                    |                          | yes      |
+| `buckets`           | `list(float)` | Predefined buckets                                                                  |                          | yes      |
 | `name`              | `string`      | The metric name.                                                                    |                          | yes      |
 | `description`       | `string`      | The metric's description and help text.                                             | `""`                     | no       |
 | `max_idle_duration` | `duration`    | Maximum amount of time to wait until the metric is marked as 'stale' and removed.   | `"5m"`                   | no       |
@@ -875,15 +875,15 @@ The `max_idle_duration` must be greater or equal to `"1s"`, and it defaults to `
 The metric values extracted from the log data are internally converted to floats.
 The supported values are the following:
 
-* Integer
-* Floating point number
-* String - Two types of string format are supported:
-  * Strings that represent floating point numbers, for example, "0.804" is converted to 0.804.
-  * Duration format strings. Valid time units are `"ns"`, `"us"`, `"ms"`, `"s"`, `"m"`, `"h"`.
+- Integer
+- Floating point number
+- String - Two types of string format are supported:
+  - Strings that represent floating point numbers, for example, "0.804" is converted to 0.804.
+  - Duration format strings. Valid time units are `"ns"`, `"us"`, `"ms"`, `"s"`, `"m"`, `"h"`.
     A value in this format is converted to a floating point number of seconds, for example, `"0.5ms"` is converted to `0.0005`.
-* Boolean:
-  * `true` is converted to `1`.
-  * `false` is converted to `0`.
+- Boolean:
+  - `true` is converted to `1`.
+  - `false` is converted to `0`.
 
 The following pipeline creates a counter which increments every time any log line is received by using the `match_all` parameter.
 The pipeline creates a second counter which adds the byte size of these log lines by using the `count_entry_bytes` parameter.
@@ -1468,10 +1468,10 @@ stage.template {
 
 ##### `Trim`, `TrimLeft`, `TrimRight`, `TrimSpace`, `TrimPrefix`, `TrimSuffix`
 
-* `Trim` returns a slice of the string `s` with all leading and trailing Unicode code points contained in `cutset` removed.
-* `TrimLeft` and `TrimRight` are the same as Trim except that they trim only leading and trailing characters, respectively.
-* `TrimSpace` returns a slice of the string s, with all leading and trailing white space removed, as defined by Unicode.
-* `TrimPrefix` and `TrimSuffix` trim the supplied prefix or suffix, respectively.
+- `Trim` returns a slice of the string `s` with all leading and trailing Unicode code points contained in `cutset` removed.
+- `TrimLeft` and `TrimRight` are the same as Trim except that they trim only leading and trailing characters, respectively.
+- `TrimSpace` returns a slice of the string s, with all leading and trailing white space removed, as defined by Unicode.
+- `TrimPrefix` and `TrimSuffix` trim the supplied prefix or suffix, respectively.
 
 The following example shows how you can use this function.
 
@@ -1637,7 +1637,7 @@ The following table shows the supported reference values to use when defining a
 | ------------------- | ------------------------------------------------------------------------------------------------------------------------ |
 | Year                | 06, 2006                                                                                                                 |
 | Month               | 1, 01, Jan, January                                                                                                      |
-| Day                 | 2, 02, _2 (two digits right justified)                                                                                   |
+| Day                 | 2, 02, \_2 (two digits right justified)                                                                                  |
 | Day of the week     | Mon, Monday                                                                                                              |
 | Hour                | 3 (12-hour), 03 (12-hour zero prefixed), 15 (24-hour)                                                                    |
 | Minute              | 4, 04                                                                                                                    |
@@ -1661,8 +1661,8 @@ The `action_on_failure` field defines what should happen when the source field d
 
 The supported actions are:
 
-* fudge (default): Change the timestamp to the last known timestamp, summing up 1 nanosecond to guarantee log entries ordering.
-* skip: Don't change the timestamp and keep the time when the log entry was scraped.
+- fudge (default): Change the timestamp to the last known timestamp, summing up 1 nanosecond to guarantee log entries ordering.
+- skip: Don't change the timestamp and keep the time when the log entry was scraped.
 
 The following stage fetches the `time` value from the shared values map, parses it as a RFC3339 format, and sets it as the log entry's timestamp.
 
@@ -1700,8 +1700,8 @@ The following fields are exported and can be referenced by other components:
 
 ## Debug metrics
 
-* `loki_process_dropped_lines_total` (counter): Number of lines dropped as part of a processing stage.
-* `loki_process_dropped_lines_by_label_total` (counter):  Number of lines dropped when `by_label_name` is non-empty in [stage.limit][].
+- `loki_process_dropped_lines_total` (counter): Number of lines dropped as part of a processing stage.
+- `loki_process_dropped_lines_by_label_total` (counter): Number of lines dropped when `by_label_name` is non-empty in [stage.limit][].
 
 ## Example
 
@@ -1720,6 +1720,7 @@ loki.process "local" {
   }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/loki/loki.relabel.md b/docs/sources/reference/components/loki/loki.relabel.md
index 2b25ee80af..9beb5398a8 100644
--- a/docs/sources/reference/components/loki/loki.relabel.md
+++ b/docs/sources/reference/components/loki/loki.relabel.md
@@ -81,11 +81,11 @@ In those cases, exported fields are kept at their last healthy values.
 
 ## Debug metrics
 
-* `loki_relabel_entries_processed` (counter): Total number of log entries processed.
-* `loki_relabel_entries_written` (counter): Total number of log entries forwarded.
-* `loki_relabel_cache_misses` (counter): Total number of cache misses.
-* `loki_relabel_cache_hits` (counter): Total number of cache hits.
-* `loki_relabel_cache_size` (gauge): Total size of relabel cache.
+- `loki_relabel_entries_processed` (counter): Total number of log entries processed.
+- `loki_relabel_entries_written` (counter): Total number of log entries forwarded.
+- `loki_relabel_cache_misses` (counter): Total number of cache misses.
+- `loki_relabel_cache_hits` (counter): Total number of cache hits.
+- `loki_relabel_cache_size` (gauge): Total size of relabel cache.
 
 ## Example
 
diff --git a/docs/sources/reference/components/loki/loki.rules.kubernetes.md b/docs/sources/reference/components/loki/loki.rules.kubernetes.md
index 7a35d73704..985d6e8492 100644
--- a/docs/sources/reference/components/loki/loki.rules.kubernetes.md
+++ b/docs/sources/reference/components/loki/loki.rules.kubernetes.md
@@ -12,16 +12,17 @@ title: loki.rules.kubernetes
 
 `loki.rules.kubernetes` discovers `PrometheusRule` Kubernetes resources and loads them into a Loki instance.
 
-* You can specify multiple `loki.rules.kubernetes` components by giving them different labels.
-* [Kubernetes label selectors][] can be used to limit the `Namespace` and `PrometheusRule` resources considered during reconciliation.
-* Compatible with the Ruler APIs of Grafana Loki, Grafana Cloud, and Grafana Enterprise Metrics.
-* Compatible with the `PrometheusRule` CRD from the [`prometheus-operator`][prometheus-operator].
-* This component accesses the Kubernetes REST API from [within a Pod][].
+- You can specify multiple `loki.rules.kubernetes` components by giving them different labels.
+- [Kubernetes label selectors][] can be used to limit the `Namespace` and `PrometheusRule` resources considered during reconciliation.
+- Compatible with the Ruler APIs of Grafana Loki, Grafana Cloud, and Grafana Enterprise Metrics.
+- Compatible with the `PrometheusRule` CRD from the [`prometheus-operator`][prometheus-operator].
+- This component accesses the Kubernetes REST API from [within a Pod][].
 
 {{< admonition type="note" >}}
 This component requires [Role-based access control (RBAC)][] to be set up in Kubernetes for {{< param "PRODUCT_NAME" >}} to access it via the Kubernetes REST API.
 
 [Role-based access control (RBAC)]: https://kubernetes.io/docs/reference/access-authn-authz/rbac/
+
 {{< /admonition >}}
 
 [Kubernetes label selectors]: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors
@@ -53,15 +54,15 @@ You can use the following arguments with `loki.rules.kubernetes`:
 | `tenant_id`             | `string`   | Loki tenant ID.                                                                 |         | no       |
 | `use_legacy_routes`     | `bool`     | Whether to use deprecated ruler API endpoints.                                  | false   | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
- [arguments]: #arguments
+[arguments]: #arguments
 
 If no `tenant_id` is provided, the component assumes that the Loki instance at `address` is running in single-tenant mode and no `X-Scope-OrgID` header is sent.
 
@@ -132,9 +133,9 @@ The following arguments are supported:
 
 The `operator` argument should be one of the following strings:
 
-* `"in"`
-* `"notin"`
-* `"exists"`
+- `"in"`
+- `"notin"`
+- `"exists"`
 
 ### `oauth2`
 
@@ -158,15 +159,15 @@ The `operator` argument should be one of the following strings:
 
 The following are exposed per discovered `PrometheusRule` resource:
 
-* The Kubernetes namespace.
-* The resource name.
-* The resource UID.
-* The number of rule groups.
+- The Kubernetes namespace.
+- The resource name.
+- The resource UID.
+- The number of rule groups.
 
 The following are exposed per discovered Loki rule namespace resource:
 
-* The namespace name.
-* The number of rule groups.
+- The namespace name.
+- The number of rule groups.
 
 Only resources managed by the component are exposed - regardless of how many actually exist.
 
@@ -220,10 +221,10 @@ loki.rules.kubernetes "default" {
 
 Replace the following:
 
-* _`<GRAFANA_CLOUD_URL>`_: The Grafana Cloud URL.
-* _`<GRAFANA_CLOUD_USER>`_: Your Grafana Cloud user name.
-* _`<GRAFANA_CLOUD_API_KEY>`_: Your Grafana Cloud API key.
-* _`<GRAFANA_CLOUD_API_KEY_PATH>`_: The path to the Grafana Cloud API key.
+- _`<GRAFANA_CLOUD_URL>`_: The Grafana Cloud URL.
+- _`<GRAFANA_CLOUD_USER>`_: Your Grafana Cloud user name.
+- _`<GRAFANA_CLOUD_API_KEY>`_: Your Grafana Cloud API key.
+- _`<GRAFANA_CLOUD_API_KEY_PATH>`_: The path to the Grafana Cloud API key.
 
 The following example is an RBAC configuration for Kubernetes. It authorizes {{< param "PRODUCT_NAME" >}} to query the Kubernetes REST API:
 
@@ -239,21 +240,21 @@ kind: ClusterRole
 metadata:
   name: alloy
 rules:
-- apiGroups: [""]
-  resources: ["namespaces"]
-  verbs: ["get", "list", "watch"]
-- apiGroups: ["monitoring.coreos.com"]
-  resources: ["prometheusrules"]
-  verbs: ["get", "list", "watch"]
+  - apiGroups: [""]
+    resources: ["namespaces"]
+    verbs: ["get", "list", "watch"]
+  - apiGroups: ["monitoring.coreos.com"]
+    resources: ["prometheusrules"]
+    verbs: ["get", "list", "watch"]
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
 metadata:
   name: alloy
 subjects:
-- kind: ServiceAccount
-  name: alloy
-  namespace: default
+  - kind: ServiceAccount
+    name: alloy
+    namespace: default
 roleRef:
   kind: ClusterRole
   name: alloy
diff --git a/docs/sources/reference/components/loki/loki.secretfilter.md b/docs/sources/reference/components/loki/loki.secretfilter.md
index e1620edd07..65c1550830 100644
--- a/docs/sources/reference/components/loki/loki.secretfilter.md
+++ b/docs/sources/reference/components/loki/loki.secretfilter.md
@@ -127,8 +127,8 @@ loki.write "local_loki" {
 
 Replace the following:
 
-* _`<PATH_TARGETS>`_: The paths to the log files to monitor.
-* _`<LOKI_ENDPOINT>`_: The URL of the Loki instance to send logs to.
+- _`<PATH_TARGETS>`_: The paths to the log files to monitor.
+- _`<LOKI_ENDPOINT>`_: The URL of the Loki instance to send logs to.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/loki/loki.source.api.md b/docs/sources/reference/components/loki/loki.source.api.md
index f871d3c2a1..4b3edc6b57 100644
--- a/docs/sources/reference/components/loki/loki.source.api.md
+++ b/docs/sources/reference/components/loki/loki.source.api.md
@@ -32,15 +32,15 @@ loki.source.api "<LABEL>" {
 
 The component starts an HTTP server on the configured port and address with the following endpoints:
 
-* `/loki/api/v1/push` - accepting `POST` requests compatible with [Loki push API][loki-push-api], for example, from another {{< param "PRODUCT_NAME" >}}'s [`loki.write`][loki.write] component.
-* `/loki/api/v1/raw` - accepting `POST` requests with newline-delimited log lines in body.
-   This can be used to send NDJSON or plain text logs.
-   This is compatible with the Promtail push API endpoint.
-   Refer to the [Promtail documentation][promtail-push-api] for more information.
-   When this endpoint is used, the incoming timestamps can't be used and the `use_incoming_timestamp = true` setting is ignored.
-* `/ready` - accepting `GET` requests. Can be used to confirm the server is reachable and healthy.
-* `/api/v1/push` - internally reroutes to `/loki/api/v1/push`.
-* `/api/v1/raw` - internally reroutes to `/loki/api/v1/raw`.
+- `/loki/api/v1/push` - accepting `POST` requests compatible with [Loki push API][loki-push-api], for example, from another {{< param "PRODUCT_NAME" >}}'s [`loki.write`][loki.write] component.
+- `/loki/api/v1/raw` - accepting `POST` requests with newline-delimited log lines in body.
+  This can be used to send NDJSON or plain text logs.
+  This is compatible with the Promtail push API endpoint.
+  Refer to the [Promtail documentation][promtail-push-api] for more information.
+  When this endpoint is used, the incoming timestamps can't be used and the `use_incoming_timestamp = true` setting is ignored.
+- `/ready` - accepting `GET` requests. Can be used to confirm the server is reachable and healthy.
+- `/api/v1/push` - internally reroutes to `/loki/api/v1/push`.
+- `/api/v1/raw` - internally reroutes to `/loki/api/v1/raw`.
 
 [promtail-push-api]: https://grafana.com/docs/loki/latest/clients/promtail/configuration/#loki_push_api
 
@@ -86,10 +86,10 @@ You can use the following block with `loki.source.api`:
 The following are some of the metrics that are exposed when this component is used.
 The metrics include labels such as `status_code` where relevant, which can be used to measure request success rates.
 
-* `loki_source_api_request_duration_seconds` (histogram): Time (in seconds) spent serving HTTP requests.
-* `loki_source_api_request_message_bytes` (histogram): Size (in bytes) of messages received in the request.
-* `loki_source_api_response_message_bytes` (histogram): Size (in bytes) of messages sent in response.
-* `loki_source_api_tcp_connections` (gauge): Current number of accepted TCP connections.
+- `loki_source_api_request_duration_seconds` (histogram): Time (in seconds) spent serving HTTP requests.
+- `loki_source_api_request_message_bytes` (histogram): Size (in bytes) of messages received in the request.
+- `loki_source_api_response_message_bytes` (histogram): Size (in bytes) of messages sent in response.
+- `loki_source_api_tcp_connections` (gauge): Current number of accepted TCP connections.
 
 ## Example
 
@@ -124,12 +124,12 @@ loki.source.api "loki_push_api" {
 
 Replace the following:
 
-* _`<USERNAME>`_: Your username.
-* _`<PASSWORD_FILE>`_: Your password file.
+- _`<USERNAME>`_: Your username.
+- _`<PASSWORD_FILE>`_: Your password file.
 
 ### Technical details
 
-`loki.source.api` filters out all labels that start with `__`, for example,  `__tenant_id__`.
+`loki.source.api` filters out all labels that start with `__`, for example, `__tenant_id__`.
 
 If you need to be able to set the tenant ID, you must either make sure the `X-Scope-OrgID` header is present or use the [`loki.process`][loki.process] component.
 
@@ -143,7 +143,6 @@ If you need to be able to set the tenant ID, you must either make sure the `X-Sc
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.awsfirehose.md b/docs/sources/reference/components/loki/loki.source.awsfirehose.md
index 56fa653b40..3d092fe9e5 100644
--- a/docs/sources/reference/components/loki/loki.source.awsfirehose.md
+++ b/docs/sources/reference/components/loki/loki.source.awsfirehose.md
@@ -16,18 +16,18 @@ The HTTP API exposed is compatible
 with the [Data Firehose HTTP Delivery API](https://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.html).
 Since the API model that Data Firehose uses to deliver data over HTTP is generic enough, the same component can be used to receive data from multiple origins:
 
-* [Amazon CloudWatch logs](https://docs.aws.amazon.com/firehose/latest/dev/writing-with-cloudwatch-logs.html)
-* [Amazon CloudWatch events](https://docs.aws.amazon.com/firehose/latest/dev/writing-with-cloudwatch-events.html)
-* Custom data through [DirectPUT requests](https://docs.aws.amazon.com/firehose/latest/dev/writing-with-sdk.html)
+- [Amazon CloudWatch logs](https://docs.aws.amazon.com/firehose/latest/dev/writing-with-cloudwatch-logs.html)
+- [Amazon CloudWatch events](https://docs.aws.amazon.com/firehose/latest/dev/writing-with-cloudwatch-events.html)
+- Custom data through [DirectPUT requests](https://docs.aws.amazon.com/firehose/latest/dev/writing-with-sdk.html)
 
 The component uses a heuristic to try to decode as much information as possible from each log record, and it falls back to writing the raw records to Loki.
 The decoding process goes as follows:
 
-* Data Firehose sends batched requests
-* Each record is treated individually
-* For each `record` received in each request:
-  * If the `record` comes from a [CloudWatch logs subscription filter](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/SubscriptionFilters.html#DestinationKinesisExample), it's decoded and each logging event is written to Loki
-  * All other records are written raw to Loki
+- Data Firehose sends batched requests
+- Each record is treated individually
+- For each `record` received in each request:
+  - If the `record` comes from a [CloudWatch logs subscription filter](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/SubscriptionFilters.html#DestinationKinesisExample), it's decoded and each logging event is written to Loki
+  - All other records are written raw to Loki
 
 The component exposes some internal labels, available for relabeling.
 The following tables describes internal labels available in records coming from any source.
@@ -63,7 +63,7 @@ loki.source.awsfirehose "<LABEL>" {
 
 The component starts an HTTP server on the configured port and address with the following endpoints:
 
-* `/awsfirehose/api/v1/push` - accepting `POST` requests compatible with [Data Firehose HTTP Specifications](https://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.html).
+- `/awsfirehose/api/v1/push` - accepting `POST` requests compatible with [Data Firehose HTTP Specifications](https://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.html).
 
 You can use the [X-Amz-Firehose-Common-Attributes](https://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.html) header to set extra static labels.
 You can configure the header in the **Parameters** section of the Data Firehose delivery stream configuration.
@@ -102,7 +102,7 @@ The `relabel_rules` field can make use of the `rules` export value from a [`loki
 You can use the following blocks with `loki.source.awsfirehose`:
 
 | Name           | Description                                        | Required |
-|----------------|----------------------------------------------------|----------|
+| -------------- | -------------------------------------------------- | -------- |
 | [`grpc`][grpc] | Configures the gRPC server that receives requests. | no       |
 | [`http`][http] | Configures the HTTP server that receives requests. | no       |
 
@@ -130,14 +130,14 @@ You can use the following blocks with `loki.source.awsfirehose`:
 The following are some of the metrics that are exposed when this component is used.
 
 {{< admonition type="note" >}}
-The metrics include labels  such as `status_code` where relevant, which you can use to measure request success rates.
+The metrics include labels such as `status_code` where relevant, which you can use to measure request success rates.
 {{< /admonition >}}
 
-* `loki_source_awsfirehose_batch_size` (histogram): Size (in units) of the number of records received per request.
-* `loki_source_awsfirehose_invalid_static_labels_errors` (counter): Count number of errors while processing Data Firehose static labels.
-* `loki_source_awsfirehose_record_errors` (counter): Count of errors while decoding an individual record.
-* `loki_source_awsfirehose_records_received` (counter): Count of records received.
-* `loki_source_awsfirehose_request_errors` (counter): Count of errors while receiving a request.
+- `loki_source_awsfirehose_batch_size` (histogram): Size (in units) of the number of records received per request.
+- `loki_source_awsfirehose_invalid_static_labels_errors` (counter): Count number of errors while processing Data Firehose static labels.
+- `loki_source_awsfirehose_record_errors` (counter): Count of errors while decoding an individual record.
+- `loki_source_awsfirehose_records_received` (counter): Count of records received.
+- `loki_source_awsfirehose_request_errors` (counter): Count of errors while receiving a request.
 
 ## Example
 
@@ -169,8 +169,8 @@ loki.source.awsfirehose "loki_fh_receiver" {
 
 Replace the following:
 
-* _`<USERNAME>`_: Your username.
-* _`<PASSWORD_FILE>`_: Your password file.
+- _`<USERNAME>`_: Your username.
+- _`<PASSWORD_FILE>`_: Your password file.
 
 As another example, if you are receiving records that originated from a CloudWatch logs subscription, you can enrich each received entry by relabeling internal labels.
 The following configuration builds upon the one above but keeps the origin log stream and group as `log_stream` and `log_group`, respectively.
@@ -214,8 +214,8 @@ loki.relabel "logging_origin" {
 
 Replace the following:
 
-* _`<USERNAME>`_: Your username.
-* _`<PASSWORD_FILE>`_: Your password file.
+- _`<USERNAME>`_: Your username.
+- _`<PASSWORD_FILE>`_: Your password file.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
@@ -225,7 +225,6 @@ Replace the following:
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.azure_event_hubs.md b/docs/sources/reference/components/loki/loki.source.azure_event_hubs.md
index c509f695cc..5d11f136ed 100644
--- a/docs/sources/reference/components/loki/loki.source.azure_event_hubs.md
+++ b/docs/sources/reference/components/loki/loki.source.azure_event_hubs.md
@@ -1,5 +1,4 @@
 ---
-
 canonical: https://grafana.com/docs/alloy/latest/reference/components/loki/loki.source.azure_event_hubs/
 aliases:
   - ../loki.source.azure_event_hubs/ # /docs/alloy/latest/reference/components/loki.source.azure_event_hubs/
@@ -142,7 +141,6 @@ loki.write "example" {
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.cloudflare.md b/docs/sources/reference/components/loki/loki.source.cloudflare.md
index 693c5d2aa7..69acbeeff5 100644
--- a/docs/sources/reference/components/loki/loki.source.cloudflare.md
+++ b/docs/sources/reference/components/loki/loki.source.cloudflare.md
@@ -1,5 +1,4 @@
 ---
-
 canonical: https://grafana.com/docs/alloy/latest/reference/components/loki/loki.source.cloudflare/
 aliases:
   - ../loki.source.cloudflare/ # /docs/alloy/latest/reference/components/loki.source.cloudflare/
@@ -46,84 +45,86 @@ You can use the following arguments with `loki.source.cloudflare`:
 By default `loki.source.cloudflare` fetches logs with the `default` set of fields.
 The following list shows the different sets of `fields_type` available for selection, and the fields they include:
 
-* `default` includes:
-{{< column-list >}}
-  * `"ClientIP"`
-  * `"ClientRequestHost"`
-  * `"ClientRequestMethod"`
-  * `"ClientRequestURI"`
-  * `"EdgeEndTimestamp"`
-  * `"EdgeResponseBytes"`
-  * `"EdgeRequestHost"`
-  * `"EdgeResponseStatus"`
-  * `"EdgeStartTimestamp"`
-  * `"RayID"`
-{{< /column-list >}}
+- `default` includes:
+  {{< column-list >}}
+
+  - `"ClientIP"`
+  - `"ClientRequestHost"`
+  - `"ClientRequestMethod"`
+  - `"ClientRequestURI"`
+  - `"EdgeEndTimestamp"`
+  - `"EdgeResponseBytes"`
+  - `"EdgeRequestHost"`
+  - `"EdgeResponseStatus"`
+  - `"EdgeStartTimestamp"`
+  - `"RayID"`
+    {{< /column-list >}}
 
   plus any extra fields provided via `additional_fields` argument.
-* `minimal` includes all `default` fields and adds:
-{{< column-list >}}
-  * `"ZoneID"`
-  * `"ClientSSLProtocol"`
-  * `"ClientRequestProtocol"`
-  * `"ClientRequestPath"`
-  * `"ClientRequestUserAgent"`
-  * `"ClientRequestReferer"`
-  * `"EdgeColoCode"`
-  * `"ClientCountry"`
-  * `"CacheCacheStatus"`
-  * `"CacheResponseStatus"`
-  * `"EdgeResponseContentType"`
-{{< /column-list >}}
-   plus any extra fields provided via `additional_fields` argument.
-* `extended` includes all `minimal` fields and adds:
-{{< column-list >}}
-  * `"ClientSSLCipher"`
-  * `"ClientASN"`
-  * `"ClientIPClass"`
-  * `"CacheResponseBytes"`
-  * `"EdgePathingOp"`
-  * `"EdgePathingSrc"`
-  * `"EdgePathingStatus"`
-  * `"ParentRayID"`
-  * `"WorkerCPUTime"`
-  * `"WorkerStatus"`
-  * `"WorkerSubrequest"`
-  * `"WorkerSubrequestCount"`
-  * `"OriginIP"`
-  * `"OriginResponseStatus"`
-  * `"OriginSSLProtocol"`
-  * `"OriginResponseHTTPExpires"`
-  * `"OriginResponseHTTPLastModified"`
- {{< /column-list >}}
-  plus any extra fields provided via `additional_fields` argument.
-* `all` includes all `extended` fields and adds:
-{{< column-list >}}
-  * `"BotScore"`
-  * `"BotScoreSrc"`
-  * `"BotTags"`
-  * `"ClientRequestBytes"`
-  * `"ClientSrcPort"`
-  * `"ClientXRequestedWith"`
-  * `"CacheTieredFill"`
-  * `"EdgeResponseCompressionRatio"`
-  * `"EdgeServerIP"`
-  * `"FirewallMatchesSources"`
-  * `"FirewallMatchesActions"`
-  * `"FirewallMatchesRuleIDs"`
-  * `"OriginResponseBytes"`
-  * `"OriginResponseTime"`
-  * `"ClientDeviceType"`
-  * `"WAFFlags"`
-  * `"WAFMatchedVar"`
-  * `"EdgeColoID"`
-  * `"RequestHeaders"`
-  * `"ResponseHeaders"`
-  * `"ClientRequestSource"`
-{{< /column-list >}}
-  plus any extra fields provided via `additional_fields` argument.
-  This is still relevant in this case if new fields are made available via Cloudflare API but aren't yet included in `all`.
-* `custom` includes only the fields defined in `additional_fields`.
+
+- `minimal` includes all `default` fields and adds:
+  {{< column-list >}}
+  - `"ZoneID"`
+  - `"ClientSSLProtocol"`
+  - `"ClientRequestProtocol"`
+  - `"ClientRequestPath"`
+  - `"ClientRequestUserAgent"`
+  - `"ClientRequestReferer"`
+  - `"EdgeColoCode"`
+  - `"ClientCountry"`
+  - `"CacheCacheStatus"`
+  - `"CacheResponseStatus"`
+  - `"EdgeResponseContentType"`
+    {{< /column-list >}}
+    plus any extra fields provided via `additional_fields` argument.
+- `extended` includes all `minimal` fields and adds:
+  {{< column-list >}}
+  - `"ClientSSLCipher"`
+  - `"ClientASN"`
+  - `"ClientIPClass"`
+  - `"CacheResponseBytes"`
+  - `"EdgePathingOp"`
+  - `"EdgePathingSrc"`
+  - `"EdgePathingStatus"`
+  - `"ParentRayID"`
+  - `"WorkerCPUTime"`
+  - `"WorkerStatus"`
+  - `"WorkerSubrequest"`
+  - `"WorkerSubrequestCount"`
+  - `"OriginIP"`
+  - `"OriginResponseStatus"`
+  - `"OriginSSLProtocol"`
+  - `"OriginResponseHTTPExpires"`
+  - `"OriginResponseHTTPLastModified"`
+    {{< /column-list >}}
+    plus any extra fields provided via `additional_fields` argument.
+- `all` includes all `extended` fields and adds:
+  {{< column-list >}}
+  - `"BotScore"`
+  - `"BotScoreSrc"`
+  - `"BotTags"`
+  - `"ClientRequestBytes"`
+  - `"ClientSrcPort"`
+  - `"ClientXRequestedWith"`
+  - `"CacheTieredFill"`
+  - `"EdgeResponseCompressionRatio"`
+  - `"EdgeServerIP"`
+  - `"FirewallMatchesSources"`
+  - `"FirewallMatchesActions"`
+  - `"FirewallMatchesRuleIDs"`
+  - `"OriginResponseBytes"`
+  - `"OriginResponseTime"`
+  - `"ClientDeviceType"`
+  - `"WAFFlags"`
+  - `"WAFMatchedVar"`
+  - `"EdgeColoID"`
+  - `"RequestHeaders"`
+  - `"ResponseHeaders"`
+  - `"ClientRequestSource"`
+    {{< /column-list >}}
+    plus any extra fields provided via `additional_fields` argument.
+    This is still relevant in this case if new fields are made available via Cloudflare API but aren't yet included in `all`.
+- `custom` includes only the fields defined in `additional_fields`.
 
 The component saves the last successfully fetched timestamp in its positions file.
 If a position is found in the file for a given zone ID, the component restarts pulling logs from that timestamp.
@@ -225,17 +226,17 @@ The `loki.source.cloudflare` component doesn't support any blocks. You can confi
 
 `loki.source.cloudflare` exposes the following debug information:
 
-* Whether the target is ready and reading logs from the API.
-* The Cloudflare zone ID.
-* The last error reported, if any.
-* The stored positions file entry, as the combination of `zone_id`, labels and last fetched timestamp.
-* The last timestamp fetched.
-* The set of fields being fetched.
+- Whether the target is ready and reading logs from the API.
+- The Cloudflare zone ID.
+- The last error reported, if any.
+- The stored positions file entry, as the combination of `zone_id`, labels and last fetched timestamp.
+- The last timestamp fetched.
+- The set of fields being fetched.
 
 ## Debug metrics
 
-* `loki_source_cloudflare_target_entries_total` (counter): Total number of successful entries sent via the cloudflare target.
-* `loki_source_cloudflare_target_last_requested_end_timestamp` (gauge): The last cloudflare request end timestamp fetched, for calculating how far behind the target is.
+- `loki_source_cloudflare_target_entries_total` (counter): Total number of successful entries sent via the cloudflare target.
+- `loki_source_cloudflare_target_last_requested_end_timestamp` (gauge): The last cloudflare request end timestamp fetched, for calculating how far behind the target is.
 
 ## Example
 
@@ -264,7 +265,6 @@ loki.write "local" {
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.docker.md b/docs/sources/reference/components/loki/loki.source.docker.md
index 1981927c74..de6de09df6 100644
--- a/docs/sources/reference/components/loki/loki.source.docker.md
+++ b/docs/sources/reference/components/loki/loki.source.docker.md
@@ -105,14 +105,14 @@ The `tls_config` block configures TLS settings for connecting to HTTPS Docker da
 
 `loki.source.docker` exposes some debug information per target:
 
-* Whether the target is ready to tail entries.
-* The labels associated with the target.
-* The most recent time a log line was read.
+- Whether the target is ready to tail entries.
+- The labels associated with the target.
+- The most recent time a log line was read.
 
 ## Debug metrics
 
-* `loki_source_docker_target_entries_total` (gauge): Total number of successful entries sent to the Docker target.
-* `loki_source_docker_target_parsing_errors_total` (gauge): Total number of parsing errors while receiving Docker messages.
+- `loki_source_docker_target_entries_total` (gauge): Total number of successful entries sent to the Docker target.
+- `loki_source_docker_target_parsing_errors_total` (gauge): Total number of parsing errors while receiving Docker messages.
 
 ## Component behavior
 
@@ -154,7 +154,6 @@ loki.write "local" {
 - Components that export [Targets](../../../compatibility/#targets-exporters)
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.file.md b/docs/sources/reference/components/loki/loki.source.file.md
index 7002c19727..a0266e35a8 100644
--- a/docs/sources/reference/components/loki/loki.source.file.md
+++ b/docs/sources/reference/components/loki/loki.source.file.md
@@ -85,9 +85,9 @@ To avoid it, pick an `initial_delay` that's long enough to avoid it.
 
 Currently supported compression formats are:
 
-* `gz` - for Gzip
-* `z` - for zlib
-* `bz2` - for bzip2
+- `gz` - for Gzip
+- `z` - for zlib
+- `bz2` - for bzip2
 
 The component can only support one compression format at a time.
 To handle multiple formats, you must create multiple components.
@@ -118,17 +118,17 @@ If file changes are detected, the poll frequency is reset to `min_poll_frequency
 
 `loki.source.file` exposes some target-level debug information per reader:
 
-* The tailed path.
-* Whether the reader is running.
-* The last recorded read offset in the positions file.
+- The tailed path.
+- Whether the reader is running.
+- The last recorded read offset in the positions file.
 
 ## Debug metrics
 
-* `loki_source_file_encoding_failures_total` (counter): Number of encoding failures.
-* `loki_source_file_file_bytes_total` (gauge): Number of bytes total.
-* `loki_source_file_files_active_total` (gauge): Number of active files.
-* `loki_source_file_read_bytes_total` (gauge): Number of bytes read.
-* `loki_source_file_read_lines_total` (counter): Number of lines read.
+- `loki_source_file_encoding_failures_total` (counter): Number of encoding failures.
+- `loki_source_file_file_bytes_total` (gauge): Number of bytes total.
+- `loki_source_file_files_active_total` (gauge): Number of active files.
+- `loki_source_file_read_bytes_total` (gauge): Number of bytes read.
+- `loki_source_file_read_lines_total` (counter): Number of lines read.
 
 ## Component behavior
 
@@ -244,7 +244,6 @@ loki.write "local" {
 - Components that export [Targets](../../../compatibility/#targets-exporters)
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.gcplog.md b/docs/sources/reference/components/loki/loki.source.gcplog.md
index b88f314c0b..1d8c16202b 100644
--- a/docs/sources/reference/components/loki/loki.source.gcplog.md
+++ b/docs/sources/reference/components/loki/loki.source.gcplog.md
@@ -122,22 +122,22 @@ The `labels` map is applied to every entry that passes through the component.
 
 `loki.source.gcplog` exposes some debug information per gcplog listener:
 
-* The configured strategy.
-* Their label set.
-* When using a `push` strategy, the listen address.
+- The configured strategy.
+- Their label set.
+- When using a `push` strategy, the listen address.
 
 ## Debug metrics
 
 When using the `pull` strategy, the component exposes the following debug metrics:
 
-* `loki_source_gcplog_pull_entries_total` (counter): Number of entries received by the gcplog target.
-* `loki_source_gcplog_pull_last_success_scrape` (gauge): Timestamp of target's last successful poll.
-* `loki_source_gcplog_pull_parsing_errors_total` (counter): Total number of parsing errors while receiving gcplog messages.
+- `loki_source_gcplog_pull_entries_total` (counter): Number of entries received by the gcplog target.
+- `loki_source_gcplog_pull_last_success_scrape` (gauge): Timestamp of target's last successful poll.
+- `loki_source_gcplog_pull_parsing_errors_total` (counter): Total number of parsing errors while receiving gcplog messages.
 
 When using the `push` strategy, the component exposes the following debug metrics:
 
-* `loki_source_gcplog_push_entries_total` (counter): Number of entries received by the gcplog target.
-* `loki_source_gcplog_push_entries_total` (counter): Number of parsing errors while receiving gcplog messages.
+- `loki_source_gcplog_push_entries_total` (counter): Number of entries received by the gcplog target.
+- `loki_source_gcplog_push_entries_total` (counter): Number of parsing errors while receiving gcplog messages.
 
 ## Example
 
@@ -185,7 +185,6 @@ loki.write "local" {
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.gelf.md b/docs/sources/reference/components/loki/loki.source.gelf.md
index bbbccd7cbb..e54adffef0 100644
--- a/docs/sources/reference/components/loki/loki.source.gelf.md
+++ b/docs/sources/reference/components/loki/loki.source.gelf.md
@@ -43,10 +43,10 @@ The `relabel_rules` argument can make use of the `rules` export from a [`loki.re
 
 Incoming messages have the following internal labels available:
 
-* `__gelf_message_facility`: The GELF facility.
-* `__gelf_message_host`: The GELF level message version sent by the client.
-* `__gelf_message_host`: The host sending the GELF message.
-* `__gelf_message_level`: The GELF level as a string.
+- `__gelf_message_facility`: The GELF facility.
+- `__gelf_message_host`: The GELF level message version sent by the client.
+- `__gelf_message_host`: The host sending the GELF message.
+- `__gelf_message_level`: The GELF level as a string.
 
 All labels starting with `__` are removed prior to forwarding log entries.
 To keep these labels, relabel them using a [`loki.relabel`][loki.relabel] component and pass its `rules` export to the `relabel_rules` argument.
@@ -63,8 +63,8 @@ The `loki.source.gelf` component doesn't support any blocks. You can configure t
 
 ## Debug Metrics
 
-* `gelf_target_entries_total` (counter): Total number of successful entries sent to the GELF target.
-* `gelf_target_parsing_errors_total` (counter): Total number of parsing errors while receiving GELF messages.
+- `gelf_target_entries_total` (counter): Total number of successful entries sent to the GELF target.
+- `gelf_target_parsing_errors_total` (counter): Total number of parsing errors while receiving GELF messages.
 
 ## Example
 
@@ -96,7 +96,6 @@ loki.write "endpoint" {
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.heroku.md b/docs/sources/reference/components/loki/loki.source.heroku.md
index ff75e8c882..30420c0d39 100644
--- a/docs/sources/reference/components/loki/loki.source.heroku.md
+++ b/docs/sources/reference/components/loki/loki.source.heroku.md
@@ -75,10 +75,10 @@ The `labels` map is applied to every message that the component reads.
 
 The following internal labels all prefixed with `__` are available but are discarded if not relabeled:
 
-* `__heroku_drain_app`
-* `__heroku_drain_host`
-* `__heroku_drain_log_id`
-* `__heroku_drain_proc`
+- `__heroku_drain_app`
+- `__heroku_drain_host`
+- `__heroku_drain_log_id`
+- `__heroku_drain_proc`
 
 All URL query parameters are translated to `__heroku_drain_param_<name>`
 
@@ -97,13 +97,13 @@ configuration.
 
 `loki.source.heroku` exposes some debug information per Heroku listener:
 
-* Whether the listener is currently running.
-* The listen address.
+- Whether the listener is currently running.
+- The listen address.
 
 ## Debug metrics
 
-* `loki_source_heroku_drain_entries_total` (counter): Number of successful entries received by the Heroku target.
-* `loki_source_heroku_drain_parsing_errors_total` (counter): Number of parsing errors while receiving Heroku messages.
+- `loki_source_heroku_drain_entries_total` (counter): Number of successful entries received by the Heroku target.
+- `loki_source_heroku_drain_parsing_errors_total` (counter): Number of parsing errors while receiving Heroku messages.
 
 ## Example
 
@@ -151,7 +151,6 @@ loki.write "local" {
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.journal.md b/docs/sources/reference/components/loki/loki.source.journal.md
index d75c744157..d2bb6a2255 100644
--- a/docs/sources/reference/components/loki/loki.source.journal.md
+++ b/docs/sources/reference/components/loki/loki.source.journal.md
@@ -17,9 +17,9 @@ You can specify multiple `loki.source.journal` components by giving them differe
 {{< admonition type="note" >}}
 Make sure that the `grafana-alloy` user is a member of the following groups:
 
-* `adm`
-* `systemd-journal`
-{{< /admonition >}}
+- `adm`
+- `systemd-journal`
+  {{< /admonition >}}
 
 ## Usage
 
@@ -76,8 +76,8 @@ The `loki.source.journal` component doesn't support any blocks. You can configur
 
 ## Debug Metrics
 
-* `loki_source_journal_target_parsing_errors_total` (counter): Total number of parsing errors while reading journal messages.
-* `loki_source_journal_target_lines_total` (counter): Total number of successful journal lines read.
+- `loki_source_journal_target_parsing_errors_total` (counter): Total number of parsing errors while reading journal messages.
+- `loki_source_journal_target_lines_total` (counter): Total number of successful journal lines read.
 
 ## Example
 
@@ -112,7 +112,6 @@ loki.write "endpoint" {
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.kafka.md b/docs/sources/reference/components/loki/loki.source.kafka.md
index c25d09a3b8..a08c7ba14e 100644
--- a/docs/sources/reference/components/loki/loki.source.kafka.md
+++ b/docs/sources/reference/components/loki/loki.source.kafka.md
@@ -34,7 +34,7 @@ loki.source.kafka "<LABEL>" {
 `loki.source.kafka` supports the following arguments:
 
 | Name                     | Type                 | Description                                              | Default               | Required |
-|--------------------------|----------------------|----------------------------------------------------------|-----------------------|----------|
+| ------------------------ | -------------------- | -------------------------------------------------------- | --------------------- | -------- |
 | `brokers`                | `list(string)`       | The list of brokers to connect to Kafka.                 |                       | yes      |
 | `forward_to`             | `list(LogsReceiver)` | List of receivers to send log entries to.                |                       | yes      |
 | `topics`                 | `list(string)`       | The list of Kafka topics to consume.                     |                       | yes      |
@@ -72,10 +72,10 @@ You can use the following blocks with `loki.source.kafka`:
 | Name                                                              | Description                                               | Required |
 | ----------------------------------------------------------------- | --------------------------------------------------------- | -------- |
 | [`authentication`][authentication]                                | Optional authentication configuration with Kafka brokers. | no       |
-| `authentication` >  [`sasl_config`][sasl_config]                  | Optional authentication configuration with Kafka brokers. | no       |
+| `authentication` > [`sasl_config`][sasl_config]                   | Optional authentication configuration with Kafka brokers. | no       |
 | `authentication` > `sasl_config` > [`oauth_config`][oauth_config] | Optional authentication configuration with Kafka brokers. | no       |
 | `authentication` > `sasl_config` > [`tls_config`][tls_config]     | Optional authentication configuration with Kafka brokers. | no       |
-| `authentication` >  [`tls_config`][tls_config]                    | Optional authentication configuration with Kafka brokers. | no       |
+| `authentication` > [`tls_config`][tls_config]                     | Optional authentication configuration with Kafka brokers. | no       |
 
 The > symbol indicates deeper levels of nesting.
 For example, `authentication` > `sasl_config` refers to a `sasl_config` block defined inside a `authentication` block.
@@ -170,7 +170,6 @@ loki.write "local" {
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.kubernetes.md b/docs/sources/reference/components/loki/loki.source.kubernetes.md
index 446afa225c..5d5d07b9cb 100644
--- a/docs/sources/reference/components/loki/loki.source.kubernetes.md
+++ b/docs/sources/reference/components/loki/loki.source.kubernetes.md
@@ -18,10 +18,10 @@ This component collects logs from Kubernetes Pods. You can't use this component
 
 This component has the following benefits over `loki.source.file`:
 
-* It works without a privileged container.
-* It works without a root user.
-* It works without needing access to the filesystem of the Kubernetes node.
-* It doesn't require a DaemonSet to collect logs, so one {{< param "PRODUCT_NAME" >}} could collect logs for the whole cluster.
+- It works without a privileged container.
+- It works without a root user.
+- It works without needing access to the filesystem of the Kubernetes node.
+- It doesn't require a DaemonSet to collect logs, so one {{< param "PRODUCT_NAME" >}} could collect logs for the whole cluster.
 
 {{< admonition type="note" >}}
 Because `loki.source.kubernetes` uses the Kubernetes API to tail logs, it uses more network traffic and CPU consumption of Kubelets than `loki.source.file`.
@@ -51,10 +51,10 @@ You can use the following arguments with `loki.source.kubernetes`:
 
 Each target in `targets` must have the following labels:
 
-* `__meta_kubernetes_namespace` or `__pod_namespace__` to specify the namespace of the Pod to tail.
-* `__meta_kubernetes_pod_container_name` or `__pod_container_name__` to specify the container within the Pod to tail.
-* `__meta_kubernetes_pod_name` or `__pod_name__` to specify the name of the Pod to tail.
-* `__meta_kubernetes_pod_uid` or `__pod_uid__` to specify the UID of the Pod to tail.
+- `__meta_kubernetes_namespace` or `__pod_namespace__` to specify the namespace of the Pod to tail.
+- `__meta_kubernetes_pod_container_name` or `__pod_container_name__` to specify the container within the Pod to tail.
+- `__meta_kubernetes_pod_name` or `__pod_name__` to specify the name of the Pod to tail.
+- `__meta_kubernetes_pod_uid` or `__pod_uid__` to specify the UID of the Pod to tail.
 
 By default, all of these labels are present when the output `discovery.kubernetes` is used.
 
@@ -105,13 +105,13 @@ The following arguments are supported:
 | `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
 | `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][client] argument
-* [`bearer_token`][client] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][client] argument
+- [`bearer_token`][client] argument
+- [`oauth2`][oauth2] block
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -143,18 +143,18 @@ If {{< param "PRODUCT_NAME" >}} is _not_ running in clustered mode, then the blo
 
 Clustering looks only at the following labels for determining the shard key:
 
-* `__meta_kubernetes_namespace`
-* `__meta_kubernetes_pod_container_name`
-* `__meta_kubernetes_pod_name`
-* `__meta_kubernetes_pod_uid`
-* `__pod_container_name__`
-* `__pod_name__`
-* `__pod_namespace__`
-* `__pod_uid__`
-* `container`
-* `job`
-* `namespace`
-* `pod`
+- `__meta_kubernetes_namespace`
+- `__meta_kubernetes_pod_container_name`
+- `__meta_kubernetes_pod_name`
+- `__meta_kubernetes_pod_uid`
+- `__pod_container_name__`
+- `__pod_name__`
+- `__pod_namespace__`
+- `__pod_uid__`
+- `container`
+- `job`
+- `namespace`
+- `pod`
 
 [using clustering]: ../../../../get-started/clustering/
 
@@ -170,10 +170,10 @@ Clustering looks only at the following labels for determining the shard key:
 
 `loki.source.kubernetes` exposes some target-level debug information per target:
 
-* The labels associated with the target.
-* The full set of labels which were found during service discovery.
-* The most recent time a log line was read and forwarded to the next components in the pipeline.
-* The most recent error from tailing, if any.
+- The labels associated with the target.
+- The full set of labels which were found during service discovery.
+- The most recent time a log line was read and forwarded to the next components in the pipeline.
+- The most recent error from tailing, if any.
 
 ## Debug metrics
 
@@ -209,7 +209,6 @@ loki.write "local" {
 - Components that export [Targets](../../../compatibility/#targets-exporters)
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.kubernetes_events.md b/docs/sources/reference/components/loki/loki.source.kubernetes_events.md
index 3172eba939..3ce80cda24 100644
--- a/docs/sources/reference/components/loki/loki.source.kubernetes_events.md
+++ b/docs/sources/reference/components/loki/loki.source.kubernetes_events.md
@@ -49,9 +49,9 @@ If an explicit list of namespaces is provided, {{< param "PRODUCT_NAME" >}} only
 
 Log lines generated by `loki.source.kubernetes_events` have the following labels:
 
-* `namespace`: Namespace of the Kubernetes object involved in the event.
-* `job`: Value specified by the `job_name` argument.
-* `instance`: Value matching the component ID.
+- `namespace`: Namespace of the Kubernetes object involved in the event.
+- `job`: Value specified by the `job_name` argument.
+- `instance`: Value matching the component ID.
 
 If `job_name` argument is the empty string, the component will fail to load.
 To remove the job label, forward the output of `loki.source.kubernetes_events` to [a `loki.relabel` component][loki.relabel].
@@ -102,13 +102,13 @@ The following arguments are supported:
 | `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
 | `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][client] argument
-* [`bearer_token`][client] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][client] argument
+- [`bearer_token`][client] argument
+- [`oauth2`][oauth2] block
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -180,7 +180,6 @@ loki.write "local" {
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.podlogs.md b/docs/sources/reference/components/loki/loki.source.podlogs.md
index 6acfcd4177..097d1a2e12 100644
--- a/docs/sources/reference/components/loki/loki.source.podlogs.md
+++ b/docs/sources/reference/components/loki/loki.source.podlogs.md
@@ -78,30 +78,30 @@ If `namespaceSelector` is left as the default value, all Namespaces are used for
 The `relabelings` field can be used to modify labels from discovered Pods.
 The following meta labels are available for relabeling:
 
-* `__meta_kubernetes_namespace`: The namespace of the Pod.
-* `__meta_kubernetes_pod_annotation_<annotationname>`: Each annotation from the Pod.
-* `__meta_kubernetes_pod_annotationpresent_<annotationname>`: `true` for each annotation from the Pod.
-* `__meta_kubernetes_pod_container_image`: The image the container is using.
-* `__meta_kubernetes_pod_container_init`: `true` if the container is an `InitContainer`.
-* `__meta_kubernetes_pod_container_name`: Name of the container.
-* `__meta_kubernetes_pod_controller_kind`: Object kind of the Pod's controller.
-* `__meta_kubernetes_pod_controller_name`: Name of the Pod's controller.
-* `__meta_kubernetes_pod_host_ip`: The current host IP of the Pod object.
-* `__meta_kubernetes_pod_ip`: The Pod IP of the Pod.
-* `__meta_kubernetes_pod_label_<labelname>`: Each label from the Pod.
-* `__meta_kubernetes_pod_labelpresent_<labelname>`: `true` for each label from the Pod.
-* `__meta_kubernetes_pod_name`: The name of the Pod.
-* `__meta_kubernetes_pod_node_name`: The name of the node the Pod is scheduled onto.
-* `__meta_kubernetes_pod_phase`: Set to `Pending`, `Running`, `Succeeded`, `Failed` or `Unknown` in the lifecycle.
-* `__meta_kubernetes_pod_ready`: Set to `true` or `false` for the Pod's ready state.
-* `__meta_kubernetes_pod_uid`: The UID of the Pod.
+- `__meta_kubernetes_namespace`: The namespace of the Pod.
+- `__meta_kubernetes_pod_annotation_<annotationname>`: Each annotation from the Pod.
+- `__meta_kubernetes_pod_annotationpresent_<annotationname>`: `true` for each annotation from the Pod.
+- `__meta_kubernetes_pod_container_image`: The image the container is using.
+- `__meta_kubernetes_pod_container_init`: `true` if the container is an `InitContainer`.
+- `__meta_kubernetes_pod_container_name`: Name of the container.
+- `__meta_kubernetes_pod_controller_kind`: Object kind of the Pod's controller.
+- `__meta_kubernetes_pod_controller_name`: Name of the Pod's controller.
+- `__meta_kubernetes_pod_host_ip`: The current host IP of the Pod object.
+- `__meta_kubernetes_pod_ip`: The Pod IP of the Pod.
+- `__meta_kubernetes_pod_label_<labelname>`: Each label from the Pod.
+- `__meta_kubernetes_pod_labelpresent_<labelname>`: `true` for each label from the Pod.
+- `__meta_kubernetes_pod_name`: The name of the Pod.
+- `__meta_kubernetes_pod_node_name`: The name of the node the Pod is scheduled onto.
+- `__meta_kubernetes_pod_phase`: Set to `Pending`, `Running`, `Succeeded`, `Failed` or `Unknown` in the lifecycle.
+- `__meta_kubernetes_pod_ready`: Set to `true` or `false` for the Pod's ready state.
+- `__meta_kubernetes_pod_uid`: The UID of the Pod.
 
 In addition to the meta labels, the following labels are exposed to tell `loki.source.podlogs` which container to tail:
 
-* `__pod_container_name__`: The container name within the Pod.
-* `__pod_name__`: The name of the Pod.
-* `__pod_namespace__`: The namespace of the Pod.
-* `__pod_uid__`: The UID of the Pod.
+- `__pod_container_name__`: The container name within the Pod.
+- `__pod_name__`: The name of the Pod.
+- `__pod_namespace__`: The namespace of the Pod.
+- `__pod_uid__`: The UID of the Pod.
 
 [LabelSelector]: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#labelselector-v1-meta
 [RelabelConfig]: https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.RelabelConfig
@@ -144,7 +144,7 @@ If the `client` block isn't provided, the default in-cluster configuration with
 The following arguments are supported:
 
 | Name                     | Type                | Description                                                                                      | Default | Required |
-|--------------------------|---------------------|--------------------------------------------------------------------------------------------------|---------|----------|
+| ------------------------ | ------------------- | ------------------------------------------------------------------------------------------------ | ------- | -------- |
 | `api_server`             | `string`            | URL of the Kubernetes API server.                                                                |         | no       |
 | `bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.                                             |         | no       |
 | `bearer_token`           | `secret`            | Bearer token to authenticate with.                                                               |         | no       |
@@ -158,11 +158,11 @@ The following arguments are supported:
 
 At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth]block
-* [`bearer_token_file`][client] argument
-* [`bearer_token`][client] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth]block
+- [`bearer_token_file`][client] argument
+- [`bearer_token`][client] argument
+- [`oauth2`][oauth2] block
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -177,7 +177,7 @@ At most, one of the following can be provided:
 ### `clustering`
 
 | Name      | Type   | Description                                         | Default | Required |
-|-----------|--------|-----------------------------------------------------|---------|----------|
+| --------- | ------ | --------------------------------------------------- | ------- | -------- |
 | `enabled` | `bool` | Distribute log collection with other cluster nodes. |         | yes      |
 
 When {{< param "PRODUCT_NAME" >}} is [using clustering][], and `enabled` is set to true, then this
@@ -189,18 +189,18 @@ If {{< param "PRODUCT_NAME" >}} is _not_ running in clustered mode, then the blo
 
 Clustering looks only at the following labels for determining the shard key:
 
-* `__pod_namespace__`
-* `__pod_name__`
-* `__pod_container_name__`
-* `__pod_uid__`
-* `__meta_kubernetes_namespace`
-* `__meta_kubernetes_pod_name`
-* `__meta_kubernetes_pod_container_name`
-* `__meta_kubernetes_pod_uid`
-* `container`
-* `pod`
-* `job`
-* `namespace`
+- `__pod_namespace__`
+- `__pod_name__`
+- `__pod_container_name__`
+- `__pod_uid__`
+- `__meta_kubernetes_namespace`
+- `__meta_kubernetes_pod_name`
+- `__meta_kubernetes_pod_container_name`
+- `__meta_kubernetes_pod_uid`
+- `container`
+- `pod`
+- `job`
+- `namespace`
 
 [using clustering]: ../../../../get-started/clustering/
 
@@ -211,17 +211,17 @@ The `match_expression` block describes a Kubernetes label match expression for `
 The following arguments are supported:
 
 | Name       | Type           | Description                        | Default | Required |
-|------------|----------------|------------------------------------|---------|----------|
+| ---------- | -------------- | ---------------------------------- | ------- | -------- |
 | `key`      | `string`       | The label name to match against.   |         | yes      |
 | `operator` | `string`       | The operator to use when matching. |         | yes      |
 | `values`   | `list(string)` | The values used when matching.     |         | no       |
 
 The `operator` argument must be one of the following strings:
 
-* `"In"`
-* `"NotIn"`
-* `"Exists"`
-* `"DoesNotExist"`
+- `"In"`
+- `"NotIn"`
+- `"Exists"`
+- `"DoesNotExist"`
 
 Both `selector` and `namespace_selector` can make use of multiple
 `match_expression` inner blocks which are treated as AND clauses.
@@ -237,7 +237,7 @@ The `selector` and `namespce_selector` blocks describe a Kubernetes label select
 The following arguments are supported:
 
 | Name           | Type          | Description                                       | Default | Required |
-|----------------|---------------|---------------------------------------------------|---------|----------|
+| -------------- | ------------- | ------------------------------------------------- | ------- | -------- |
 | `match_labels` | `map(string)` | Label keys and values used to discover resources. | `{}`    | no       |
 
 When the `match_labels` argument is empty, all resources are matched.
@@ -258,10 +258,10 @@ When the `match_labels` argument is empty, all resources are matched.
 
 `loki.source.podlogs` exposes some target-level debug information per target:
 
-* The labels associated with the target.
-* The full set of labels which were found during service discovery.
-* The most recent time a log line was read and forwarded to the next components in the pipeline.
-* The most recent error from tailing, if any.
+- The labels associated with the target.
+- The full set of labels which were found during service discovery.
+- The most recent time a log line was read and forwarded to the next components in the pipeline.
+- The most recent error from tailing, if any.
 
 ## Debug metrics
 
@@ -291,7 +291,6 @@ loki.write "local" {
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.syslog.md b/docs/sources/reference/components/loki/loki.source.syslog.md
index ba48845914..6748f324e0 100644
--- a/docs/sources/reference/components/loki/loki.source.syslog.md
+++ b/docs/sources/reference/components/loki/loki.source.syslog.md
@@ -84,7 +84,7 @@ The `labels` map is applied to every message that the component reads.
 All header fields from the parsed RFC5424 messages are brought in as internal labels, prefixed with `__syslog_`.
 
 If `label_structured_data` is set, structured data in the syslog header is also translated to internal labels in the form of `__syslog_message_sd_<ID>_<KEY>`.
-For example, a  structured data entry of `[example@99999 test="yes"]` becomes the label `__syslog_message_sd_example_99999_test` with the value `"yes"`.
+For example, a structured data entry of `[example@99999 test="yes"]` becomes the label `__syslog_message_sd_example_99999_test` with the value `"yes"`.
 
 ### `tls_config`
 
@@ -103,15 +103,15 @@ configuration.
 
 `loki.source.syslog` exposes some debug information per syslog listener:
 
-* Whether the listener is running.
-* The listen address.
-* The labels that the listener applies to incoming log entries.
+- Whether the listener is running.
+- The listen address.
+- The labels that the listener applies to incoming log entries.
 
 ## Debug metrics
 
-* `loki_source_syslog_empty_messages_total` (counter): Total number of empty messages received from the syslog component.
-* `loki_source_syslog_entries_total` (counter): Total number of successful entries sent to the syslog component.
-* `loki_source_syslog_parsing_errors_total` (counter): Total number of parsing errors while receiving syslog messages.
+- `loki_source_syslog_empty_messages_total` (counter): Total number of empty messages received from the syslog component.
+- `loki_source_syslog_entries_total` (counter): Total number of successful entries sent to the syslog component.
+- `loki_source_syslog_parsing_errors_total` (counter): Total number of parsing errors while receiving syslog messages.
 
 ## Example
 
@@ -148,7 +148,6 @@ loki.write "local" {
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.source.windowsevent.md b/docs/sources/reference/components/loki/loki.source.windowsevent.md
index c484d5bfad..f50a2cf28d 100644
--- a/docs/sources/reference/components/loki/loki.source.windowsevent.md
+++ b/docs/sources/reference/components/loki/loki.source.windowsevent.md
@@ -78,6 +78,7 @@ loki.write "endpoint" {
     }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -86,7 +87,6 @@ loki.write "endpoint" {
 
 - Components that export [Loki `LogsReceiver`](../../../compatibility/#loki-logsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/loki/loki.write.md b/docs/sources/reference/components/loki/loki.write.md
index 9406cf917d..a005e34c3a 100644
--- a/docs/sources/reference/components/loki/loki.write.md
+++ b/docs/sources/reference/components/loki/loki.write.md
@@ -88,13 +88,13 @@ The following arguments are supported:
 | `retry_on_http_429`      | `bool`              | Retry when an HTTP 429 status code is received.                                                  | `true`    | no       |
 | `tenant_id`              | `string`            | The tenant ID used by default to push logs.                                                      |           | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][endpoint] argument
-* [`bearer_token`][endpoint] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][endpoint] argument
+- [`bearer_token`][endpoint] argument
+- [`oauth2`][oauth2] block
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -155,8 +155,8 @@ To enable the WAL, you must include the `wal` block in your configuration.
 When the WAL is enabled, the log entries sent to the `loki.write` component are first written to a WAL under the `dir` directory and then read into the remote-write client.
 This process provides durability guarantees when an entry reaches this component. The client knows when to read from the WAL using the following two mechanisms:
 
-* The WAL-writer side of the `loki.write` component notifies the reader side that new data is available.
-* The WAL-reader side periodically checks if there is new data, increasing the wait time exponentially between `min_read_frequency` and `max_read_frequency`.
+- The WAL-writer side of the `loki.write` component notifies the reader side that new data is available.
+- The WAL-reader side periodically checks if there is new data, increasing the wait time exponentially between `min_read_frequency` and `max_read_frequency`.
 
 The WAL is located inside a component-specific directory relative to the storage path {{< param "PRODUCT_NAME" >}} is configured to use.
 Refer to the [`run` documentation][run] for more information about how to change the storage path.
@@ -191,14 +191,14 @@ The following fields are exported and can be referenced by other components:
 
 ## Debug metrics
 
-* `loki_write_batch_retries_total` (counter): Number of times batches have had to be retried.
-* `loki_write_dropped_bytes_total` (counter): Number of bytes dropped because failed to be sent to the ingester after all retries.
-* `loki_write_dropped_entries_total` (counter): Number of log entries dropped because they failed to be sent to the ingester after all retries.
-* `loki_write_encoded_bytes_total` (counter): Number of bytes encoded and ready to send.
-* `loki_write_request_duration_seconds` (histogram): Duration of sent requests.
-* `loki_write_sent_bytes_total` (counter): Number of bytes sent.
-* `loki_write_sent_entries_total` (counter): Number of log entries sent to the ingester.
-* `loki_write_stream_lag_seconds` (gauge): Difference between current time and last batch timestamp for successful sends.
+- `loki_write_batch_retries_total` (counter): Number of times batches have had to be retried.
+- `loki_write_dropped_bytes_total` (counter): Number of bytes dropped because failed to be sent to the ingester after all retries.
+- `loki_write_dropped_entries_total` (counter): Number of log entries dropped because they failed to be sent to the ingester after all retries.
+- `loki_write_encoded_bytes_total` (counter): Number of bytes encoded and ready to send.
+- `loki_write_request_duration_seconds` (histogram): Duration of sent requests.
+- `loki_write_sent_bytes_total` (counter): Number of bytes sent.
+- `loki_write_sent_entries_total` (counter): Number of log entries sent to the ingester.
+- `loki_write_stream_lag_seconds` (gauge): Difference between current time and last batch timestamp for successful sends.
 
 ## Examples
 
@@ -234,7 +234,7 @@ loki.write "default" {
 
 ## Technical details
 
-`loki.write` uses [snappy](https://en.wikipedia.org/wiki/Snappy_(compression)) for compression.
+`loki.write` uses [snappy](<https://en.wikipedia.org/wiki/Snappy_(compression)>) for compression.
 
 Any labels that start with `__` are removed before sending to the endpoint.
 
diff --git a/docs/sources/reference/components/mimir/mimir.rules.kubernetes.md b/docs/sources/reference/components/mimir/mimir.rules.kubernetes.md
index 2156efd5ae..279caa7c80 100644
--- a/docs/sources/reference/components/mimir/mimir.rules.kubernetes.md
+++ b/docs/sources/reference/components/mimir/mimir.rules.kubernetes.md
@@ -12,16 +12,17 @@ title: mimir.rules.kubernetes
 
 `mimir.rules.kubernetes` discovers `PrometheusRule` Kubernetes resources and loads them into a Mimir instance.
 
-* You can specify multiple `mimir.rules.kubernetes` components by giving them different labels.
-* [Kubernetes label selectors][] can be used to limit the `Namespace` and `PrometheusRule` resources considered during reconciliation.
-* Compatible with the Ruler APIs of Grafana Mimir, Grafana Cloud, and Grafana Enterprise Metrics.
-* Compatible with the `PrometheusRule` CRD from the [`prometheus-operator`][prometheus-operator].
-* This component accesses the Kubernetes REST API from [within a Pod][].
+- You can specify multiple `mimir.rules.kubernetes` components by giving them different labels.
+- [Kubernetes label selectors][] can be used to limit the `Namespace` and `PrometheusRule` resources considered during reconciliation.
+- Compatible with the Ruler APIs of Grafana Mimir, Grafana Cloud, and Grafana Enterprise Metrics.
+- Compatible with the `PrometheusRule` CRD from the [`prometheus-operator`][prometheus-operator].
+- This component accesses the Kubernetes REST API from [within a Pod][].
 
 {{< admonition type="note" >}}
 This component requires [Role-based access control (RBAC)][] to be set up in Kubernetes in order for {{< param "PRODUCT_NAME" >}} to access it via the Kubernetes REST API.
 
 [Role-based access control (RBAC)]: https://kubernetes.io/docs/reference/access-authn-authz/rbac/
+
 {{< /admonition >}}
 
 {{< admonition type="note" >}}
@@ -29,6 +30,7 @@ This component requires [Role-based access control (RBAC)][] to be set up in Kub
 When you use this component as part of a cluster of {{< param "PRODUCT_NAME" >}} instances, only a single instance from the cluster updates rules using the Mimir API.
 
 [clustered mode]: ../../../../get-started/clustering/
+
 {{< /admonition >}}
 
 [Kubernetes label selectors]: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors
@@ -67,14 +69,14 @@ You can use the following arguments with `mimir.rules.kubernetes`:
 
 At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments]argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments]argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
- [arguments]: #arguments
- [gem-path-prefix]: https://grafana.com/docs/mimir/latest/references/http-api/
+[arguments]: #arguments
+[gem-path-prefix]: https://grafana.com/docs/mimir/latest/references/http-api/
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -180,10 +182,10 @@ The following arguments are supported:
 
 The `operator` argument should be one of the following strings:
 
-* `"In"`
-* `"NotIn"`
-* `"Exists"`
-* `"DoesNotExist"`
+- `"In"`
+- `"NotIn"`
+- `"Exists"`
+- `"DoesNotExist"`
 
 The `values` argument must not be provided when `operator` is set to `"Exists"` or `"DoesNotExist"`.
 
@@ -209,15 +211,15 @@ The `values` argument must not be provided when `operator` is set to `"Exists"`
 
 The following are exposed per discovered `PrometheusRule` resource:
 
-* The Kubernetes namespace.
-* The resource name.
-* The resource UID.
-* The number of rule groups.
+- The Kubernetes namespace.
+- The resource name.
+- The resource UID.
+- The number of rule groups.
 
 The following are exposed per discovered Mimir rule namespace resource:
 
-* The namespace name.
-* The number of rule groups.
+- The namespace name.
+- The number of rule groups.
 
 Only resources managed by the component are exposed, regardless of how many actually exist.
 
@@ -303,21 +305,21 @@ kind: ClusterRole
 metadata:
   name: alloy
 rules:
-- apiGroups: [""]
-  resources: ["namespaces"]
-  verbs: ["get", "list", "watch"]
-- apiGroups: ["monitoring.coreos.com"]
-  resources: ["prometheusrules"]
-  verbs: ["get", "list", "watch"]
+  - apiGroups: [""]
+    resources: ["namespaces"]
+    verbs: ["get", "list", "watch"]
+  - apiGroups: ["monitoring.coreos.com"]
+    resources: ["prometheusrules"]
+    verbs: ["get", "list", "watch"]
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
 metadata:
   name: alloy
 subjects:
-- kind: ServiceAccount
-  name: alloy
-  namespace: default
+  - kind: ServiceAccount
+    name: alloy
+    namespace: default
 roleRef:
   kind: ClusterRole
   name: alloy
diff --git a/docs/sources/reference/components/otelcol/otelcol.auth.basic.md b/docs/sources/reference/components/otelcol/otelcol.auth.basic.md
index 814773ba6e..a2e90799fd 100644
--- a/docs/sources/reference/components/otelcol/otelcol.auth.basic.md
+++ b/docs/sources/reference/components/otelcol/otelcol.auth.basic.md
@@ -33,19 +33,19 @@ otelcol.auth.basic "LABEL" {
 
 `otelcol.auth.basic` supports the following arguments:
 
-Name       | Type     | Description                                        | Default | Required
------------|----------|----------------------------------------------------|---------|---------
-`username` | `string` | Username to use for basic authentication requests. |         | yes
-`password` | `secret` | Password to use for basic authentication requests. |         | yes
+| Name       | Type     | Description                                        | Default | Required |
+| ---------- | -------- | -------------------------------------------------- | ------- | -------- |
+| `username` | `string` | Username to use for basic authentication requests. |         | yes      |
+| `password` | `secret` | Password to use for basic authentication requests. |         | yes      |
 
 ## Blocks
 
 The following blocks are supported inside the definition of
 `otelcol.auth.basic`:
 
-Hierarchy | Block      | Description                          | Required
-----------|------------|--------------------------------------|---------
-debug_metrics  | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [debug_metrics]: #debug_metrics-block
 
@@ -57,9 +57,9 @@ debug_metrics  | [debug_metrics][] | Configures the metrics that this component
 
 The following fields are exported and can be referenced by other components:
 
-Name      | Type                       | Description
-----------|----------------------------|----------------------------------------------------------------
-`handler` | `capsule(otelcol.Handler)` | A value that other components can use to authenticate requests.
+| Name      | Type                       | Description                                                     |
+| --------- | -------------------------- | --------------------------------------------------------------- |
+| `handler` | `capsule(otelcol.Handler)` | A value that other components can use to authenticate requests. |
 
 ## Component health
 
diff --git a/docs/sources/reference/components/otelcol/otelcol.auth.bearer.md b/docs/sources/reference/components/otelcol/otelcol.auth.bearer.md
index f0bcd4e1ef..b85aed5391 100644
--- a/docs/sources/reference/components/otelcol/otelcol.auth.bearer.md
+++ b/docs/sources/reference/components/otelcol/otelcol.auth.bearer.md
@@ -32,10 +32,10 @@ otelcol.auth.bearer "LABEL" {
 
 `otelcol.auth.bearer` supports the following arguments:
 
-Name     | Type     | Description                                      | Default  | Required
----------|----------|--------------------------------------------------|----------|---------
-`token`  | `secret` | Bearer token to use for authenticating requests. |          | yes
-`scheme` | `string` | Authentication scheme name.                      | "Bearer" | no
+| Name     | Type     | Description                                      | Default  | Required |
+| -------- | -------- | ------------------------------------------------ | -------- | -------- |
+| `token`  | `secret` | Bearer token to use for authenticating requests. |          | yes      |
+| `scheme` | `string` | Authentication scheme name.                      | "Bearer" | no       |
 
 When sending the token, the value of `scheme` is prepended to the `token` value.
 The string is then sent out as either a header (in case of HTTP) or as metadata (in case of gRPC).
@@ -45,9 +45,9 @@ The string is then sent out as either a header (in case of HTTP) or as metadata
 The following blocks are supported inside the definition of
 `otelcol.auth.bearer`:
 
-Hierarchy | Block      | Description                          | Required
-----------|------------|--------------------------------------|---------
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [debug_metrics]: #debug_metrics-block
 
@@ -59,9 +59,9 @@ debug_metrics | [debug_metrics][] | Configures the metrics that this component g
 
 The following fields are exported and can be referenced by other components:
 
-Name      | Type                       | Description
-----------|----------------------------|----------------------------------------------------------------
-`handler` | `capsule(otelcol.Handler)` | A value that other components can use to authenticate requests.
+| Name      | Type                       | Description                                                     |
+| --------- | -------------------------- | --------------------------------------------------------------- |
+| `handler` | `capsule(otelcol.Handler)` | A value that other components can use to authenticate requests. |
 
 ## Component health
 
@@ -97,7 +97,7 @@ otelcol.auth.bearer "creds" {
 
 The example below configures [otelcol.exporter.otlphttp][] to use a bearer token authentication.
 
-If we assume that the value of the `API_KEY` environment variable is `SECRET_API_KEY`, then 
+If we assume that the value of the `API_KEY` environment variable is `SECRET_API_KEY`, then
 the `Authorization` HTTP header is set to `MyScheme SECRET_API_KEY`.
 
 ```alloy
diff --git a/docs/sources/reference/components/otelcol/otelcol.auth.headers.md b/docs/sources/reference/components/otelcol/otelcol.auth.headers.md
index 526e1036f7..31e70b2341 100644
--- a/docs/sources/reference/components/otelcol/otelcol.auth.headers.md
+++ b/docs/sources/reference/components/otelcol/otelcol.auth.headers.md
@@ -39,10 +39,10 @@ through inner blocks.
 The following blocks are supported inside the definition of
 `otelcol.auth.headers`:
 
-Hierarchy | Block      | Description                          | Required
-----------|------------|--------------------------------------|---------
-header    | [header][] | Custom header to attach to requests. | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| header        | [header][]        | Custom header to attach to requests.                                       | no       |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [header]: #header-block
 [debug_metrics]: #debug_metrics-block
@@ -52,18 +52,19 @@ debug_metrics | [debug_metrics][] | Configures the metrics that this component g
 The `header` block defines a custom header to attach to requests. It is valid
 to provide multiple `header` blocks to set more than one header.
 
-Name           | Type                 | Description                             | Default  | Required
----------------|----------------------|-----------------------------------------|----------|---------
-`key`          | `string`             | Name of the header to set.              |          | yes
-`value`        | `string` or `secret` | Value of the header.                    |          | no
-`from_context` | `string`             | Metadata name to get header value from. |          | no
-`action`       | `string`             | An action to perform on the header      | "upsert" | no
+| Name           | Type                 | Description                             | Default  | Required |
+| -------------- | -------------------- | --------------------------------------- | -------- | -------- |
+| `key`          | `string`             | Name of the header to set.              |          | yes      |
+| `value`        | `string` or `secret` | Value of the header.                    |          | no       |
+| `from_context` | `string`             | Metadata name to get header value from. |          | no       |
+| `action`       | `string`             | An action to perform on the header      | "upsert" | no       |
 
 The supported values for `action` are:
-* `insert`: Inserts the new header if it does not exist.
-* `update`: Updates the header value if it exists.
-* `upsert`: Inserts a header if it does not exist and updates the header if it exists.
-* `delete`: Deletes the header.
+
+- `insert`: Inserts the new header if it does not exist.
+- `update`: Updates the header value if it exists.
+- `upsert`: Inserts a header if it does not exist and updates the header if it exists.
+- `delete`: Deletes the header.
 
 Exactly one of `value` or `from_context` must be provided for each `header`
 block.
@@ -72,9 +73,10 @@ The `value` attribute sets the value of the header directly.
 Alternatively, `from_context` can be used to dynamically retrieve the header value from request metadata.
 
 For `from_context` to work, other components in the pipeline also need to be configured appropriately:
-* If an `otelcol.processor.batch` is present in the pipeline, it must be configured to preserve client metadata. 
+
+- If an `otelcol.processor.batch` is present in the pipeline, it must be configured to preserve client metadata.
   Do this by adding the value that `from_context` needs to the `metadata_keys` of the batch processor.
-* `otelcol` receivers must be configured with `include_metadata` set to `true` so that metadata keys are available to the pipeline.
+- `otelcol` receivers must be configured with `include_metadata` set to `true` so that metadata keys are available to the pipeline.
 
 ### debug_metrics block
 
@@ -84,9 +86,9 @@ For `from_context` to work, other components in the pipeline also need to be con
 
 The following fields are exported and can be referenced by other components:
 
-Name | Type | Description
----- | ---- | -----------
-`handler` | `capsule(otelcol.Handler)` | A value that other components can use to authenticate requests.
+| Name      | Type                       | Description                                                     |
+| --------- | -------------------------- | --------------------------------------------------------------- |
+| `handler` | `capsule(otelcol.Handler)` | A value that other components can use to authenticate requests. |
 
 ## Component health
 
diff --git a/docs/sources/reference/components/otelcol/otelcol.auth.oauth2.md b/docs/sources/reference/components/otelcol/otelcol.auth.oauth2.md
index f2e8a7014b..f3232cfa92 100644
--- a/docs/sources/reference/components/otelcol/otelcol.auth.oauth2.md
+++ b/docs/sources/reference/components/otelcol/otelcol.auth.oauth2.md
@@ -14,7 +14,6 @@ The authorization tokens can be used by HTTP and gRPC based OpenTelemetry export
 This component can fetch and refresh expired tokens automatically.
 Refer to the [OAuth 2.0 Authorization Framework](https://datatracker.ietf.org/doc/html/rfc6749#section-4.4) for more information about the Auth 2.0 Client Credentials flow.
 
-
 {{< admonition type="note" >}}
 `otelcol.auth.oauth2` is a wrapper over the upstream OpenTelemetry Collector `oauth2client` extension.
 Bug reports or feature requests will be redirected to the upstream repository, if necessary.
@@ -34,16 +33,16 @@ otelcol.auth.oauth2 "LABEL" {
 
 ## Arguments
 
-Name                 | Type                | Description                                                                        | Default | Required
--------------------- | ------------------- | ---------------------------------------------------------------------------------- | ------- | --------
-`client_id`          | `string`            | The client identifier issued to the client.                                        |         | no
-`client_id_file`     | `string`            | The file path to retrieve the client identifier issued to the client.              |         | no
-`client_secret`      | `secret`            | The secret string associated with the client identifier.                           |         | no
-`client_secret_file` | `secret`            | The file path to retrieve the secret string associated with the client identifier. |         | no
-`token_url`          | `string`            | The server endpoint URL from which to get tokens.                                  |         | yes
-`endpoint_params`    | `map(list(string))` | Additional parameters that are sent to the token endpoint.                         | `{}`    | no
-`scopes`             | `list(string)`      | Requested permissions associated for the client.                                   | `[]`    | no
-`timeout`            | `duration`          | The timeout on the client connecting to `token_url`.                               | `"0s"`  | no
+| Name                 | Type                | Description                                                                        | Default | Required |
+| -------------------- | ------------------- | ---------------------------------------------------------------------------------- | ------- | -------- |
+| `client_id`          | `string`            | The client identifier issued to the client.                                        |         | no       |
+| `client_id_file`     | `string`            | The file path to retrieve the client identifier issued to the client.              |         | no       |
+| `client_secret`      | `secret`            | The secret string associated with the client identifier.                           |         | no       |
+| `client_secret_file` | `secret`            | The file path to retrieve the secret string associated with the client identifier. |         | no       |
+| `token_url`          | `string`            | The server endpoint URL from which to get tokens.                                  |         | yes      |
+| `endpoint_params`    | `map(list(string))` | Additional parameters that are sent to the token endpoint.                         | `{}`    | no       |
+| `scopes`             | `list(string)`      | Requested permissions associated for the client.                                   | `[]`    | no       |
+| `timeout`            | `duration`          | The timeout on the client connecting to `token_url`.                               | `"0s"`  | no       |
 
 The `timeout` argument is used both for requesting initial tokens and for refreshing tokens. `"0s"` implies no timeout.
 
@@ -57,10 +56,10 @@ If both are set, `client_secret_file` also takes precedence.
 
 The following blocks are supported inside the definition of `otelcol.auth.oauth2`:
 
-Hierarchy | Block   | Description                        | Required
-----------|---------|------------------------------------|---------
-tls       | [tls][] | TLS settings for the token client. | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| tls           | [tls][]           | TLS settings for the token client.                                         | no       |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [tls]: #tls-block
 [debug_metrics]: #debug_metrics-block
@@ -79,9 +78,9 @@ The `tls` block configures TLS settings used for connecting to the token client.
 
 The following fields are exported and can be referenced by other components:
 
-Name      | Type                       | Description
-----------|----------------------------|----------------------------------------------------------------
-`handler` | `capsule(otelcol.Handler)` | A value that other components can use to authenticate requests.
+| Name      | Type                       | Description                                                     |
+| --------- | -------------------------- | --------------------------------------------------------------- |
+| `handler` | `capsule(otelcol.Handler)` | A value that other components can use to authenticate requests. |
 
 ## Component health
 
@@ -111,6 +110,7 @@ otelcol.auth.oauth2 "creds" {
 ```
 
 Here is another example with some optional attributes specified:
+
 ```alloy
 otelcol.exporter.otlp "example" {
   client {
diff --git a/docs/sources/reference/components/otelcol/otelcol.auth.sigv4.md b/docs/sources/reference/components/otelcol/otelcol.auth.sigv4.md
index d8f8070a35..b066587e53 100644
--- a/docs/sources/reference/components/otelcol/otelcol.auth.sigv4.md
+++ b/docs/sources/reference/components/otelcol/otelcol.auth.sigv4.md
@@ -25,6 +25,7 @@ different labels.
 {{< param "PRODUCT_NAME" >}} must have valid AWS credentials as used by the [AWS SDK for Go][].
 
 [AWS SDK for Go]: https://aws.github.io/aws-sdk-go-v2/docs/configuring-sdk/#specifying-credentials
+
 {{< /admonition >}}
 
 ## Usage
@@ -36,17 +37,17 @@ otelcol.auth.sigv4 "LABEL" {
 
 ## Arguments
 
-Name      | Type     | Description                   | Default | Required
-----------|----------|-------------------------------|---------|---------
-`region`  | `string` | The AWS region to sign with.  | ""      | no
-`service` | `string` | The AWS service to sign with. | ""      | no
+| Name      | Type     | Description                   | Default | Required |
+| --------- | -------- | ----------------------------- | ------- | -------- |
+| `region`  | `string` | The AWS region to sign with.  | ""      | no       |
+| `service` | `string` | The AWS service to sign with. | ""      | no       |
 
 If `region` and `service` are left empty, their values are inferred from the URL of the exporter
 using the following rules:
 
-* If the exporter URL starts with `aps-workspaces` and `service` is empty, `service` will be set to `aps`.
-* If the exporter URL starts with `search-` and `service` is empty, `service` will be set to `es`.
-* If the exporter URL starts with either `aps-workspaces` or `search-` and `region` is empty, `region` will be set to the value between the first and second `.` character in the exporter URL.
+- If the exporter URL starts with `aps-workspaces` and `service` is empty, `service` will be set to `aps`.
+- If the exporter URL starts with `search-` and `service` is empty, `service` will be set to `es`.
+- If the exporter URL starts with either `aps-workspaces` or `search-` and `region` is empty, `region` will be set to the value between the first and second `.` character in the exporter URL.
 
 If none of the above rules apply, then `region` and `service` must be specified.
 
@@ -59,10 +60,10 @@ A list of valid AWS regions can be found on Amazon's documentation for [Regions,
 The following blocks are supported inside the definition of
 `otelcol.auth.sigv4`:
 
-Hierarchy   | Block           | Description                        | Required
-------------|-----------------|------------------------------------|---------
-assume_role | [assume_role][] | Configuration for assuming a role. | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| assume_role   | [assume_role][]   | Configuration for assuming a role.                                         | no       |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [assume_role]: #assume_role-block
 [debug_metrics]: #debug_metrics-block
@@ -71,11 +72,11 @@ debug_metrics | [debug_metrics][] | Configures the metrics that this component g
 
 The `assume_role` block specifies the configuration needed to assume a role.
 
-Name           | Type     | Description                                                     | Default | Required
----------------|----------|-----------------------------------------------------------------|---------|---------
-`arn`          | `string` | The Amazon Resource Name (ARN) of a role to assume.             | ""      | no
-`session_name` | `string` | The name of a role session.                                     | ""      | no
-`sts_region`   | `string` | The AWS region where STS is used to assume the configured role. | ""      | no
+| Name           | Type     | Description                                                     | Default | Required |
+| -------------- | -------- | --------------------------------------------------------------- | ------- | -------- |
+| `arn`          | `string` | The Amazon Resource Name (ARN) of a role to assume.             | ""      | no       |
+| `session_name` | `string` | The name of a role session.                                     | ""      | no       |
+| `sts_region`   | `string` | The AWS region where STS is used to assume the configured role. | ""      | no       |
 
 If the `assume_role` block is specified in the config and `sts_region` is not set, then `sts_region` will default to the value for `region`.
 
@@ -89,9 +90,9 @@ For cross region authentication, `region` and `sts_region` can be set different
 
 The following fields are exported and can be referenced by other components:
 
-Name      | Type                       | Description
-----------|----------------------------|----------------------------------------------------------------
-`handler` | `capsule(otelcol.Handler)` | A value that other components can use to authenticate requests.
+| Name      | Type                       | Description                                                     |
+| --------- | -------------------------- | --------------------------------------------------------------- |
+| `handler` | `capsule(otelcol.Handler)` | A value that other components can use to authenticate requests. |
 
 ## Component health
 
diff --git a/docs/sources/reference/components/otelcol/otelcol.connector.host_info.md b/docs/sources/reference/components/otelcol/otelcol.connector.host_info.md
index 7ef63e4a17..a18e4d31c5 100644
--- a/docs/sources/reference/components/otelcol/otelcol.connector.host_info.md
+++ b/docs/sources/reference/components/otelcol/otelcol.connector.host_info.md
@@ -34,10 +34,10 @@ otelcol.connector.host_info "LABEL" {
 The following blocks are supported inside the definition of
 `otelcol.connector.host_info`:
 
-| Hierarchy | Block      | Description                                       | Required |
-| --------- | ---------- | ------------------------------------------------- | -------- |
-| output    | [output][] | Configures where to send received telemetry data. | yes      |
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| output        | [output][]        | Configures where to send received telemetry data.                          | yes      |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [output]: #output-block
 [debug_metrics]: #debug_metrics-block
diff --git a/docs/sources/reference/components/otelcol/otelcol.connector.servicegraph.md b/docs/sources/reference/components/otelcol/otelcol.connector.servicegraph.md
index 7026b3854e..3260945fd4 100644
--- a/docs/sources/reference/components/otelcol/otelcol.connector.servicegraph.md
+++ b/docs/sources/reference/components/otelcol/otelcol.connector.servicegraph.md
@@ -25,11 +25,11 @@ This component is based on [Grafana Tempo's service graph processor](https://git
 
 Service graphs are useful for a number of use-cases:
 
-* Infer the topology of a distributed system. As distributed systems grow, they become more complex.
+- Infer the topology of a distributed system. As distributed systems grow, they become more complex.
   Service graphs can help you understand the structure of the system.
-* Provide a high level overview of the health of your system.
+- Provide a high level overview of the health of your system.
   Service graphs show error rates, latencies, and other relevant data.
-* Provide a historic view of a system’s topology.
+- Provide a historic view of a system’s topology.
   Distributed systems change very frequently,
   and service graphs offer a way of seeing how these systems have evolved over time.
 
@@ -55,46 +55,47 @@ otelcol.connector.servicegraph "LABEL" {
 
 `otelcol.connector.servicegraph` supports the following arguments:
 
-Name                        | Type             | Description                                                         | Default | Required
-----------------------------|------------------|-------------------------------------------------------------------- |---------|---------
-`latency_histogram_buckets` | `list(duration)` | Buckets for latency histogram metrics.                              | `["2ms", "4ms", "6ms", "8ms", "10ms", "50ms", "100ms", "200ms", "400ms", "800ms", "1s", "1400ms", "2s", "5s", "10s", "15s"]` | no
-`dimensions`                | `list(string)`   | A list of dimensions to add with the default dimensions.            | `[]`         | no
-`cache_loop`                | `duration`       | Configures how often to delete series which have not been updated.  | `"1m"`       | no
-`store_expiration_loop`     | `duration`       | The time to expire old entries from the store periodically.         | `"2s"`       | no
-`metrics_flush_interval`    | `duration`       | The interval at which metrics are flushed to downstream components. | `"0s"`       | no
-`database_name_attribute`   | `string`         | The attribute name used to identify the database name from span attributes. | `"db.name"`  | no
+| Name                        | Type             | Description                                                                 | Default                                                                                                                      | Required |
+| --------------------------- | ---------------- | --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -------- |
+| `latency_histogram_buckets` | `list(duration)` | Buckets for latency histogram metrics.                                      | `["2ms", "4ms", "6ms", "8ms", "10ms", "50ms", "100ms", "200ms", "400ms", "800ms", "1s", "1400ms", "2s", "5s", "10s", "15s"]` | no       |
+| `dimensions`                | `list(string)`   | A list of dimensions to add with the default dimensions.                    | `[]`                                                                                                                         | no       |
+| `cache_loop`                | `duration`       | Configures how often to delete series which have not been updated.          | `"1m"`                                                                                                                       | no       |
+| `store_expiration_loop`     | `duration`       | The time to expire old entries from the store periodically.                 | `"2s"`                                                                                                                       | no       |
+| `metrics_flush_interval`    | `duration`       | The interval at which metrics are flushed to downstream components.         | `"0s"`                                                                                                                       | no       |
+| `database_name_attribute`   | `string`         | The attribute name used to identify the database name from span attributes. | `"db.name"`                                                                                                                  | no       |
 
 Service graphs work by inspecting traces and looking for spans with parent-children relationship that represent a request.
 `otelcol.connector.servicegraph` uses OpenTelemetry semantic conventions to detect a myriad of requests.
 The following requests are currently supported:
 
-* A direct request between two services, where the outgoing and the incoming span
+- A direct request between two services, where the outgoing and the incoming span
   must have a [Span Kind][] value of `client` and `server` respectively.
-* A request across a messaging system, where the outgoing and the incoming span
+- A request across a messaging system, where the outgoing and the incoming span
   must have a [Span Kind][] value of `producer` and `consumer` respectively.
-* A database request, where spans have a [Span Kind][] with a value of `client`,
+- A database request, where spans have a [Span Kind][] with a value of `client`,
   as well as an attribute with a key of `db.name`.
 
 Every span which can be paired up to form a request is kept in an in-memory store:
-* If the TTL of the span expires before it can be paired, it is deleted from the store.
+
+- If the TTL of the span expires before it can be paired, it is deleted from the store.
   TTL is configured in the [store][] block.
-* If the span is paired prior to its expiration, a metric is recorded and the span is deleted from the store.
+- If the span is paired prior to its expiration, a metric is recorded and the span is deleted from the store.
 
 The following metrics are emitted by the processor:
 
-| Metric                                      | Type      | Labels                          | Description                                                  |
-|---------------------------------------------|-----------|---------------------------------|--------------------------------------------------------------|
-| traces_service_graph_request_total          | Counter   | client, server, connection_type | Total count of requests between two nodes                    |
-| traces_service_graph_request_failed_total   | Counter   | client, server, connection_type | Total count of failed requests between two nodes             |
-| traces_service_graph_request_server_seconds | Histogram | client, server, connection_type | Time for a request between two nodes as seen from the server |
-| traces_service_graph_request_client_seconds | Histogram | client, server, connection_type | Time for a request between two nodes as seen from the client |
-| traces_service_graph_unpaired_spans_total   | Counter   | client, server, connection_type | Total count of unpaired spans                                |
-| traces_service_graph_dropped_spans_total    | Counter   | client, server, connection_type | Total count of dropped spans                                 |
+| Metric                                    | Type      | Labels                          | Description                                                               |
+| ----------------------------------------- | --------- | ------------------------------- | ------------------------------------------------------------------------- |
+| traces_service_graph_request_total        | Counter   | client, server, connection_type | Total count of requests between two nodes                                 |
+| traces_service_graph_request_failed_total | Counter   | client, server, connection_type | Total count of failed requests between two nodes                          |
+| traces_service_graph_request_server       | Histogram | client, server, connection_type | Number of seconds for a request between two nodes as seen from the server |
+| traces_service_graph_request_client       | Histogram | client, server, connection_type | Number of seconds for a request between two nodes as seen from the client |
+| traces_service_graph_unpaired_spans_total | Counter   | client, server, connection_type | Total count of unpaired spans                                             |
+| traces_service_graph_dropped_spans_total  | Counter   | client, server, connection_type | Total count of dropped spans                                              |
 
 Duration is measured both from the client and the server sides.
 
 The `latency_histogram_buckets` argument controls the buckets for
-`traces_service_graph_request_server_seconds` and `traces_service_graph_request_client_seconds`.
+`traces_service_graph_request_server` and `traces_service_graph_request_client`.
 
 Each emitted metrics series have a `client` and a `server` label corresponding with the service doing the request and the service receiving the request.
 The value of the label is derived from the `service.name` resource attribute of the two spans.
@@ -102,10 +103,11 @@ The value of the label is derived from the `service.name` resource attribute of
 The `connection_type` label may not be set. If it is set, its value will be either `messaging_system` or `database`.
 
 Additional labels can be included using the `dimensions` configuration option:
-* Those labels will have a prefix to mark where they originate (client or server span kinds).
+
+- Those labels will have a prefix to mark where they originate (client or server span kinds).
   The `client_` prefix relates to the dimensions coming from spans with a [Span Kind][] of `client`.
   The `server_` prefix relates to the dimensions coming from spans with a [Span Kind][] of `server`.
-* Firstly the resource attributes will be searched. If the attribute is not found, the span attributes will be searched.
+- Firstly the resource attributes will be searched. If the attribute is not found, the span attributes will be searched.
 
 When `metrics_flush_interval` is set to `0s`, metrics will be flushed on every received batch of traces.
 
@@ -116,11 +118,11 @@ When `metrics_flush_interval` is set to `0s`, metrics will be flushed on every r
 The following blocks are supported inside the definition of
 `otelcol.connector.servicegraph`:
 
-Hierarchy | Block      | Description                               | Required
-----------|------------|-------------------------------------------|---------
-store     | [store][]  | Configures the in-memory store for spans. | no
-output    | [output][] | Configures where to send telemetry data.  | yes
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| store         | [store][]         | Configures the in-memory store for spans.                                  | no       |
+| output        | [output][]        | Configures where to send telemetry data.                                   | yes      |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [store]: #store-block
 [output]: #output-block
@@ -130,10 +132,10 @@ debug_metrics | [debug_metrics][] | Configures the metrics that this component g
 
 The `store` block configures the in-memory store for spans.
 
-Name        | Type       | Description                                   | Default | Required
-------------|------------|-----------------------------------------------|---------|---------
-`max_items` | `number`   | Maximum number of items to keep in the store. | `1000`  | no
-`ttl`       | `duration` | The time to live for spans in the store.      | `"2s"`  | no
+| Name        | Type       | Description                                   | Default | Required |
+| ----------- | ---------- | --------------------------------------------- | ------- | -------- |
+| `max_items` | `number`   | Maximum number of items to keep in the store. | `1000`  | no       |
+| `ttl`       | `duration` | The time to live for spans in the store.      | `"2s"`  | no       |
 
 ### output block
 
@@ -147,9 +149,9 @@ Name        | Type       | Description                                   | Defau
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` traces telemetry data. It does not accept metrics and logs.
 
diff --git a/docs/sources/reference/components/otelcol/otelcol.connector.spanlogs.md b/docs/sources/reference/components/otelcol/otelcol.connector.spanlogs.md
index 6afb4ba0e4..8933b5a75c 100644
--- a/docs/sources/reference/components/otelcol/otelcol.connector.spanlogs.md
+++ b/docs/sources/reference/components/otelcol/otelcol.connector.spanlogs.md
@@ -17,6 +17,7 @@ This allows you to automatically build a mechanism for trace discovery.
 It is based on the `automatic_logging` component in the [traces][] subsystem of Grafana Agent Static.
 
 [traces]: https://grafana.com/docs/agent/latest/static/configuration/traces-config
+
 {{< /admonition >}}
 
 You can specify multiple `otelcol.connector.spanlogs` components by giving them different labels.
@@ -277,6 +278,7 @@ For an input trace like this...
   ]
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/otelcol/otelcol.exporter.awss3.md b/docs/sources/reference/components/otelcol/otelcol.exporter.awss3.md
index 64422f417e..8c20efcb00 100644
--- a/docs/sources/reference/components/otelcol/otelcol.exporter.awss3.md
+++ b/docs/sources/reference/components/otelcol/otelcol.exporter.awss3.md
@@ -35,30 +35,30 @@ otelcol.exporter.awss3 "<LABEL>" {
 
 Replace the following:
 
-* _`<LABEL>`_: The label for the `otelcol.exporter.awss3` component.
-* _`<REGION>`_: The AWS region.
-* _`<BUCKET_NAME>`_: The S3 bucket.
-* _`<PREFIX>`_: The prefix for the S3 key.
+- _`<LABEL>`_: The label for the `otelcol.exporter.awss3` component.
+- _`<REGION>`_: The AWS region.
+- _`<BUCKET_NAME>`_: The S3 bucket.
+- _`<PREFIX>`_: The prefix for the S3 key.
 
 ## Arguments
 
 `otelcol.exporter.awss3` supports the following arguments:
 
-Name       | Type       | Description                                      | Default | Required
------------|------------|--------------------------------------------------|---------|---------
-`encoding` | `string`   | Encoding extension to use to marshal data. Overrides the `marshaler` configuration option if set. | `""`  | no
-`encoding_file_ext` | `string` | File format extension suffix when using the `encoding` configuration option. It can be left empty if a suffix shouldn't be appended. | `""` | no
+| Name                | Type     | Description                                                                                                                          | Default | Required |
+| ------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------- | -------- |
+| `encoding`          | `string` | Encoding extension to use to marshal data. Overrides the `marshaler` configuration option if set.                                    | `""`    | no       |
+| `encoding_file_ext` | `string` | File format extension suffix when using the `encoding` configuration option. It can be left empty if a suffix shouldn't be appended. | `""`    | no       |
 
 ## Blocks
 
 The following blocks are supported inside the definition of
 `otelcol.exporter.awss3`:
 
-Hierarchy              | Block                | Description                                                                          | Required
------------------------|----------------------|--------------------------------------------------------------------------------------|---------
-s3_uploader            | [s3_uploader][]      | Configures the AWS S3 bucket details to send telemetry data to.                      | yes
-marshaler              | [marshaler][]        | Marshaler used to produce output data.                                               | no
-debug_metrics          | [debug_metrics][]    | Configures the metrics that this component generates to monitor its state.           | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| s3_uploader   | [s3_uploader][]   | Configures the AWS S3 bucket details to send telemetry data to.            | yes      |
+| marshaler     | [marshaler][]     | Marshaler used to produce output data.                                     | no       |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [s3_uploader]: #s3_uploader-block
 [marshaler]: #marshaler-block
@@ -70,18 +70,18 @@ The `s3_uploader` block configures the AWS S3 bucket details used by the compone
 
 The following arguments are supported:
 
-Name                  | Type                       | Description                                                                      | Default      | Required
-----------------------|----------------------------|----------------------------------------------------------------------------------|--------------|---------
-`region`              | `string`                   | The AWS region.                                                                      | `"us-east-1"`| no
-`s3_bucket`           | `string`                   | The S3 bucket.                                                                        |              | yes
-`s3_prefix`           | `string`                   | Prefix for the S3 key (root directory inside the bucket).                            |              | yes
-`s3_partition`        | `string`                   | Time granularity of S3 key: hour or minute.                                       | `"minute"`   | no
-`role_arn`            | `string`                   | The Role ARN to be assumed.                                                       |              | no
-`file_prefix`         | `string`                   | The file prefix defined by the user.                                                      |              | no
-`endpoint`            | `string`                   | Overrides the endpoint used by the exporter instead of constructing it from `region` and `s3_bucket`. |      | no
-`s3_force_path_style` | `boolean`                  |  Set this to `true` to force the request to use [path-style requests](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html#path-style-access) | `false`             | no
-`disable_ssl`         | `boolean`                  |  Set this to `true` to disable SSL when sending requests.           |              | `false`
-`compression`         | `string`                   | How should the file be compressed? `none`, `gzip`                                                    | `none`      | no
+| Name                  | Type      | Description                                                                                                                                                       | Default       | Required |
+| --------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | -------- |
+| `region`              | `string`  | The AWS region.                                                                                                                                                   | `"us-east-1"` | no       |
+| `s3_bucket`           | `string`  | The S3 bucket.                                                                                                                                                    |               | yes      |
+| `s3_prefix`           | `string`  | Prefix for the S3 key (root directory inside the bucket).                                                                                                         |               | yes      |
+| `s3_partition`        | `string`  | Time granularity of S3 key: hour or minute.                                                                                                                       | `"minute"`    | no       |
+| `role_arn`            | `string`  | The Role ARN to be assumed.                                                                                                                                       |               | no       |
+| `file_prefix`         | `string`  | The file prefix defined by the user.                                                                                                                              |               | no       |
+| `endpoint`            | `string`  | Overrides the endpoint used by the exporter instead of constructing it from `region` and `s3_bucket`.                                                             |               | no       |
+| `s3_force_path_style` | `boolean` | Set this to `true` to force the request to use [path-style requests](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html#path-style-access) | `false`       | no       |
+| `disable_ssl`         | `boolean` | Set this to `true` to disable SSL when sending requests.                                                                                                          |               | `false`  |
+| `compression`         | `string`  | How should the file be compressed? `none`, `gzip`                                                                                                                 | `none`        | no       |
 
 [path-style requests]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html#path-style-access
 
@@ -98,9 +98,9 @@ Marshaler determines the format of data sent to AWS S3. Currently, the following
 
 The following arguments are supported:
 
-Name                    | Type       | Description                                                                                | Default | Required
-------------------------|------------|--------------------------------------------------------------------------------------------|---------|---------
-`type`                  | `string`   | Marshaler used to produce output data.                                                      | `"otlp_json"`   | no
+| Name   | Type     | Description                            | Default       | Required |
+| ------ | -------- | -------------------------------------- | ------------- | -------- |
+| `type` | `string` | Marshaler used to produce output data. | `"otlp_json"` | no       |
 
 ### debug_metrics block
 
@@ -123,9 +123,9 @@ Refer to the Open Telemetry [encoding extensions][encoding] documentation for mo
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics,
 logs, or traces).
@@ -142,15 +142,15 @@ information.
 
 ## Debug metrics
 
-* `otelcol_exporter_sent_spans_total` (counter): Number of spans successfully sent to destination.
-* `otelcol_exporter_send_failed_spans_total` (counter): Number of spans in failed attempts to send to destination.
-* `otelcol_exporter_queue_capacity` (gauge): Fixed capacity of the retry queue (in batches).
-* `otelcol_exporter_queue_size` (gauge): Current size of the retry queue (in batches).
-* `rpc_client_duration_milliseconds` (histogram): Measures the duration of inbound RPC.
-* `rpc_client_request_size_bytes` (histogram): Measures size of RPC request messages (uncompressed).
-* `rpc_client_requests_per_rpc` (histogram): Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs.
-* `rpc_client_response_size_bytes` (histogram): Measures size of RPC response messages (uncompressed).
-* `rpc_client_responses_per_rpc` (histogram): Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs.
+- `otelcol_exporter_sent_spans_total` (counter): Number of spans successfully sent to destination.
+- `otelcol_exporter_send_failed_spans_total` (counter): Number of spans in failed attempts to send to destination.
+- `otelcol_exporter_queue_capacity` (gauge): Fixed capacity of the retry queue (in batches).
+- `otelcol_exporter_queue_size` (gauge): Current size of the retry queue (in batches).
+- `rpc_client_duration_milliseconds` (histogram): Measures the duration of inbound RPC.
+- `rpc_client_request_size_bytes` (histogram): Measures size of RPC request messages (uncompressed).
+- `rpc_client_requests_per_rpc` (histogram): Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs.
+- `rpc_client_response_size_bytes` (histogram): Measures size of RPC response messages (uncompressed).
+- `rpc_client_responses_per_rpc` (histogram): Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs.
 
 ## Example
 
diff --git a/docs/sources/reference/components/otelcol/otelcol.exporter.datadog.md b/docs/sources/reference/components/otelcol/otelcol.exporter.datadog.md
index d552bdfd67..7e3e0f38e7 100644
--- a/docs/sources/reference/components/otelcol/otelcol.exporter.datadog.md
+++ b/docs/sources/reference/components/otelcol/otelcol.exporter.datadog.md
@@ -6,7 +6,6 @@ aliases:
 title: otelcol.exporter.datadog
 ---
 
-
 <span class="badge docs-labels__stage docs-labels__item">Community</span>
 
 # otelcol.exporter.datadog
@@ -16,7 +15,7 @@ title: otelcol.exporter.datadog
 `otelcol.exporter.datadog` accepts metrics and traces telemetry data from other `otelcol` components and sends it to Datadog.
 
 {{< admonition type="note" >}}
-`otelcol.exporter.datadog` is a wrapper over the upstream OpenTelemetry Collector `datadog` exporter from the `otelcol-contrib`  distribution.
+`otelcol.exporter.datadog` is a wrapper over the upstream OpenTelemetry Collector `datadog` exporter from the `otelcol-contrib` distribution.
 Bug reports or feature requests will be redirected to the upstream repository, if necessary.
 {{< /admonition >}}
 
@@ -36,33 +35,33 @@ otelcol.exporter.datadog "LABEL" {
 
 The following arguments are supported:
 
-Name            | Type     | Description                                                                      | Default | Required
-----------------|----------|----------------------------------------------------------------------------------|---------|---------
-`hostname`      | `string` | The fallback hostname used for payloads without hostname-identifying attributes. |         | no
-`only_metadata` | `bool`   | Whether to send only metadata.                                                   | `false` | no
+| Name            | Type     | Description                                                                      | Default | Required |
+| --------------- | -------- | -------------------------------------------------------------------------------- | ------- | -------- |
+| `hostname`      | `string` | The fallback hostname used for payloads without hostname-identifying attributes. |         | no       |
+| `only_metadata` | `bool`   | Whether to send only metadata.                                                   | `false` | no       |
 
-If `hostname` is unset, the hostname is determined automatically. For more information, refer to the Datadog [Fallback hostname logic](https://docs.datadoghq.com/opentelemetry/schema_semantics/hostname/?tab=datadogexporter#fallback-hostname-logic) documentation. 
+If `hostname` is unset, the hostname is determined automatically. For more information, refer to the Datadog [Fallback hostname logic](https://docs.datadoghq.com/opentelemetry/schema_semantics/hostname/?tab=datadogexporter#fallback-hostname-logic) documentation.
 This option will **NOT** change the hostname applied to metrics or traces if they already have hostname-identifying attributes.
 
 ## Blocks
 
 The following blocks are supported inside the definition of `otelcol.exporter.datadog`:
 
-Hierarchy            | Block                | Description                                                                | Required
----------------------|----------------------|----------------------------------------------------------------------------|---------
-api                  | [api][]              | Configures authentication with Datadog                                     | yes
-traces               | [traces][]           | Trace exporter specific configuration.                                     | no
-logs               | [logs][]           | Logs exporter specific configuration.                                     | no
-metrics              | [metrics][]          | Metric exporter specific configuration.                                    | no
-metrics > exporter   | [exporter][]         | Metric Exporter specific configuation.                                     | no
-metrics > histograms | [histograms][]       | Histograms specific configuration.                                         | no
-metrics > sums       | [sums][]             | Sums specific configuration                                                | no
-metrics > summaries  | [summaries][]        | Summaries specific configuration                                           | no
-host_metadata        | [host_metadata][]    | Host metadata specific configuration.                                      | no
-client               | [client][]           | Configures the HTTP client used to send telemetry data.                    | no
-retry_on_failure     | [retry_on_failure][] | Configures retry mechanism for failed requests.                            | no
-queue                | [queue][]            | Configures batching of data before sending.                                | no
-debug_metrics        | [debug_metrics][]    | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy            | Block                | Description                                                                | Required |
+| -------------------- | -------------------- | -------------------------------------------------------------------------- | -------- |
+| api                  | [api][]              | Configures authentication with Datadog                                     | yes      |
+| traces               | [traces][]           | Trace exporter specific configuration.                                     | no       |
+| logs                 | [logs][]             | Logs exporter specific configuration.                                      | no       |
+| metrics              | [metrics][]          | Metric exporter specific configuration.                                    | no       |
+| metrics > exporter   | [exporter][]         | Metric Exporter specific configuation.                                     | no       |
+| metrics > histograms | [histograms][]       | Histograms specific configuration.                                         | no       |
+| metrics > sums       | [sums][]             | Sums specific configuration                                                | no       |
+| metrics > summaries  | [summaries][]        | Summaries specific configuration                                           | no       |
+| host_metadata        | [host_metadata][]    | Host metadata specific configuration.                                      | no       |
+| client               | [client][]           | Configures the HTTP client used to send telemetry data.                    | no       |
+| retry_on_failure     | [retry_on_failure][] | Configures retry mechanism for failed requests.                            | no       |
+| queue                | [queue][]            | Configures batching of data before sending.                                | no       |
+| debug_metrics        | [debug_metrics][]    | Configures the metrics that this component generates to monitor its state. | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `metrics > summaries` refers to a `summaries` block defined inside a `metrics` block.
 
@@ -88,11 +87,11 @@ to Datadog. If you do not provide the `api` block, you can't send telemetry to D
 
 The following arguments are supported:
 
-Name                  | Type     | Description                                           | Default           | Required
-----------------------|----------|-------------------------------------------------------|-------------------|---------
-`api_key`             | `secret` | API Key for Datadog                                   |                   | yes
-`site`                | `string` | The site of the Datadog intake to send Agent data to. | `"datadoghq.com"` | no
-`fail_on_invalid_key` | `bool`   | Whether to exit at startup on an invalid API key      | `false`           | no
+| Name                  | Type     | Description                                           | Default           | Required |
+| --------------------- | -------- | ----------------------------------------------------- | ----------------- | -------- |
+| `api_key`             | `secret` | API Key for Datadog                                   |                   | yes      |
+| `site`                | `string` | The site of the Datadog intake to send Agent data to. | `"datadoghq.com"` | no       |
+| `fail_on_invalid_key` | `bool`   | Whether to exit at startup on an invalid API key      | `false`           | no       |
 
 ### traces block
 
@@ -100,17 +99,17 @@ The `traces` block configures the trace exporter settings.
 
 The following arguments are supported:
 
-Name                             | Type           | Description                                                                                        | Default                               | Required
----------------------------------|----------------|----------------------------------------------------------------------------------------------------|---------------------------------------|---------
-`endpoint`                       | `string`       | The host of the Datadog intake server to send traces to.                                           | `"https://trace.agent.datadoghq.com"` | no
-`ignore_resources`               | `list(string)` | A blocklist of regular expressions can be provided to disable traces based on their resource name. |                                       | no
-`span_name_remappings`           | `map(string)`  | A map of Datadog span operation name keys and preferred name values to update those names to.      |                                       | no
-`span_name_as_resource_name`     | `bool`         | Use OpenTelemetry semantic convention for span naming                                              | `true`                                | no
-`compute_stats_by_span_kind`     | `bool`         | Enables APM stats computation based on `span.kind`                                                 | `true`                                | no
-`compute_top_level_by_span_kind` | `bool`         | Enables top-level span identification based on `span.kind`                                         | `false`                               | no
-`peer_tags_aggregation`          | `bool`         | Enables aggregation of peer related tags in Datadog exporter                                       | `false`                               | no
-`peer_tags`                      | `list(string)` | List of supplementary peer tags that go beyond the defaults.                                       |                                       | no
-`trace_buffer`                   | `number`       | Specifies the number of outgoing trace payloads to buffer before dropping                          | `10`                                  | no
+| Name                             | Type           | Description                                                                                        | Default                               | Required |
+| -------------------------------- | -------------- | -------------------------------------------------------------------------------------------------- | ------------------------------------- | -------- |
+| `endpoint`                       | `string`       | The host of the Datadog intake server to send traces to.                                           | `"https://trace.agent.datadoghq.com"` | no       |
+| `ignore_resources`               | `list(string)` | A blocklist of regular expressions can be provided to disable traces based on their resource name. |                                       | no       |
+| `span_name_remappings`           | `map(string)`  | A map of Datadog span operation name keys and preferred name values to update those names to.      |                                       | no       |
+| `span_name_as_resource_name`     | `bool`         | Use OpenTelemetry semantic convention for span naming                                              | `true`                                | no       |
+| `compute_stats_by_span_kind`     | `bool`         | Enables APM stats computation based on `span.kind`                                                 | `true`                                | no       |
+| `compute_top_level_by_span_kind` | `bool`         | Enables top-level span identification based on `span.kind`                                         | `false`                               | no       |
+| `peer_tags_aggregation`          | `bool`         | Enables aggregation of peer related tags in Datadog exporter                                       | `false`                               | no       |
+| `peer_tags`                      | `list(string)` | List of supplementary peer tags that go beyond the defaults.                                       |                                       | no       |
+| `trace_buffer`                   | `number`       | Specifies the number of outgoing trace payloads to buffer before dropping                          | `10`                                  | no       |
 
 If `compute_stats_by_span_kind` is disabled, only top-level and measured spans will have stats computed.
 If you are sending OTel traces and want stats on non-top-level spans, this flag must be set to `true`.
@@ -126,13 +125,12 @@ The `logs` block configures the logs exporter settings.
 
 The following arguments are supported:
 
-Name                             | Type           | Description                                                                                        | Default                               | Required
----------------------------------|----------------|----------------------------------------------------------------------------------------------------|---------------------------------------|---------
-`endpoint`                       | `string`       | The host of the Datadog intake server to send logs to.                                           | `"https://http-intake.logs.datadoghq.com"` | no                                         `false`                                    | no   |
-`use_compression`                | `bool`         | Available when sending logs via HTTPS. Compresses logs if enabled. |                               `true`	                                  | no
-`compression_level`              | `int`          | The compression_level parameter accepts values from 0 (no compression) to 9 (maximum compression but higher resource usage). Only used if `use_compression` is set to `true`.                                                         | `6`                                        | no
-`batch_wait`                     | `int`         | The maximum time in seconds the logs agent waits to fill each batch of logs before sending.                                                                                                               | `5`                                | no
-
+| Name                | Type     | Description                                                                                                                                                                   | Default                                    | Required   |
+| ------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | ---------- | --- |
+| `endpoint`          | `string` | The host of the Datadog intake server to send logs to.                                                                                                                        | `"https://http-intake.logs.datadoghq.com"` | no `false` | no  |
+| `use_compression`   | `bool`   | Available when sending logs via HTTPS. Compresses logs if enabled.                                                                                                            | `true`                                     | no         |
+| `compression_level` | `int`    | The compression_level parameter accepts values from 0 (no compression) to 9 (maximum compression but higher resource usage). Only used if `use_compression` is set to `true`. | `6`                                        | no         |
+| `batch_wait`        | `int`    | The maximum time in seconds the logs agent waits to fill each batch of logs before sending.                                                                                   | `5`                                        | no         |
 
 If `use_compression` is disabled, `compression_level` has no effect.
 
@@ -140,19 +138,18 @@ If `endpoint` is unset, the value is obtained through the `site` parameter in th
 
 [api]: #api-block
 
-
 ### metrics block
 
 The `metrics` block configures Metric specific exporter settings.
 
 The following arguments are supported:
 
-Name        | Type     | Description                                                             | Default                       | Required
-------------|----------|-------------------------------------------------------------------------|-------------------------------|---------
-`delta_ttl` | `number` | The number of seconds values are kept in memory for calculating deltas. | `3600`                        | no
-`endpoint`  | `string` | The host of the Datadog intake server to send metrics to.               | `"https://api.datadoghq.com"` | no
+| Name        | Type     | Description                                                             | Default                       | Required |
+| ----------- | -------- | ----------------------------------------------------------------------- | ----------------------------- | -------- |
+| `delta_ttl` | `number` | The number of seconds values are kept in memory for calculating deltas. | `3600`                        | no       |
+| `endpoint`  | `string` | The host of the Datadog intake server to send metrics to.               | `"https://api.datadoghq.com"` | no       |
 
-Any of the subset of resource attributes in the [semantic mapping list](https://docs.datadoghq.com/opentelemetry/guide/semantic_mapping/)  are converted to Datadog conventions and set to to metric tags whether `resource_attributes_as_tags` is enabled or not.
+Any of the subset of resource attributes in the [semantic mapping list](https://docs.datadoghq.com/opentelemetry/guide/semantic_mapping/) are converted to Datadog conventions and set to to metric tags whether `resource_attributes_as_tags` is enabled or not.
 
 If `endpoint` is unset, the value is obtained through the `site` parameter in the [api][] section.
 
@@ -164,11 +161,10 @@ The `exporter` block configures the metric exporter settings.
 
 The following arguments are supported:
 
-Name                                     | Type   | Description                                                                          | Default | Required
------------------------------------------|--------|--------------------------------------------------------------------------------------|---------|---------
-`resource_attributes_as_tags`            | `bool` | Set to `true` to add resource attributes of a metric to its metric tags.             | `false` | no
-`instrumentation_scope_metadata_as_tags` | `bool` | Set to `true` to add metadata about the instrumentation scope that created a metric. | `false` | no
-
+| Name                                     | Type   | Description                                                                          | Default | Required |
+| ---------------------------------------- | ------ | ------------------------------------------------------------------------------------ | ------- | -------- |
+| `resource_attributes_as_tags`            | `bool` | Set to `true` to add resource attributes of a metric to its metric tags.             | `false` | no       |
+| `instrumentation_scope_metadata_as_tags` | `bool` | Set to `true` to add metadata about the instrumentation scope that created a metric. | `false` | no       |
 
 ### histograms block
 
@@ -176,10 +172,10 @@ The `histograms` block configures the histogram settings.
 
 The following arguments are supported:
 
-Name                       | Type     | Description                                                               | Default           | Required
----------------------------|----------|---------------------------------------------------------------------------|-------------------|---------
-`mode`                     | `string` | How to report histograms.                                                 | `"distributions"` | no
-`send_aggregation_metrics` | `bool`   | Whether to report sum, count, min, and max as separate histogram metrics. | `false`           | no
+| Name                       | Type     | Description                                                               | Default           | Required |
+| -------------------------- | -------- | ------------------------------------------------------------------------- | ----------------- | -------- |
+| `mode`                     | `string` | How to report histograms.                                                 | `"distributions"` | no       |
+| `send_aggregation_metrics` | `bool`   | Whether to report sum, count, min, and max as separate histogram metrics. | `false`           | no       |
 
 Valid values for `mode` are:
 
@@ -193,10 +189,10 @@ The `sums` block configures the sums settings.
 
 The following arguments are supported:
 
-Name                                 | Type     | Description                                                    | Default      | Required
--------------------------------------|----------|----------------------------------------------------------------|--------------|---------
-`cumulative_monotonic_mode`          | `string` | How to report cumulative monotonic sums.                       | `"to_delta"` | no
-`initial_cumulative_monotonic_value` | `string` | How to report the initial value for cumulative monotonic sums. | `"auto"`     | no
+| Name                                 | Type     | Description                                                    | Default      | Required |
+| ------------------------------------ | -------- | -------------------------------------------------------------- | ------------ | -------- |
+| `cumulative_monotonic_mode`          | `string` | How to report cumulative monotonic sums.                       | `"to_delta"` | no       |
+| `initial_cumulative_monotonic_value` | `string` | How to report the initial value for cumulative monotonic sums. | `"auto"`     | no       |
 
 Valid values for `cumulative_monotonic_mode` are:
 
@@ -215,9 +211,9 @@ The `summaries` block configures the summary settings.
 
 The following arguments are supported:
 
-Name   | Type     | Description              | Default    | Required
--------|----------|--------------------------|------------|---------
-`mode` | `string` | How to report summaries. | `"gauges"` | no
+| Name   | Type     | Description              | Default    | Required |
+| ------ | -------- | ------------------------ | ---------- | -------- |
+| `mode` | `string` | How to report summaries. | `"gauges"` | no       |
 
 Valid values for `mode` are:
 
@@ -231,17 +227,17 @@ Host metadata is the information used to populate the infrastructure list and th
 
 The following arguments are supported:
 
-Name              | Type           | Description                                                | Default              | Required
-------------------|----------------|------------------------------------------------------------|----------------------|---------
-`enabled`         | `bool`         | Enable the host metadata functionality                     | `true`               | no
-`hostname_source` | `string`       | Source for the hostname of host metadata.                  | `"config_or_system"` | no
-`tags`            | `list(string)` | List of host tags to be sent as part of the host metadata. |                      | no
+| Name              | Type           | Description                                                | Default              | Required |
+| ----------------- | -------------- | ---------------------------------------------------------- | -------------------- | -------- |
+| `enabled`         | `bool`         | Enable the host metadata functionality                     | `true`               | no       |
+| `hostname_source` | `string`       | Source for the hostname of host metadata.                  | `"config_or_system"` | no       |
+| `tags`            | `list(string)` | List of host tags to be sent as part of the host metadata. |                      | no       |
 
 By default, the exporter will only send host metadata for a single host, whose name is chosen according to `host_metadata::hostname_source`.
 
 Valid values for `hostname_source` are:
 
-- `"first_resource"` picks the host metadata hostname from the resource attributes on the first OTLP payload that gets to the exporter. 
+- `"first_resource"` picks the host metadata hostname from the resource attributes on the first OTLP payload that gets to the exporter.
   If the first payload lacks hostname-like attributes, it will fallback to 'config_or_system' behavior. **Do not use this hostname source if receiving data from multiple hosts**.
 - `"config_or_system"` picks the host metadata hostname from the 'hostname' setting, falling back to system and cloud provider APIs.
 
@@ -252,17 +248,17 @@ Not all fields are supported by the Datadog Exporter.
 
 The following arguments are supported:
 
-Name                      | Type       | Description                                                                 | Default | Required
---------------------------|------------|-----------------------------------------------------------------------------|---------|---------
-`read_buffer_size`        | `string`   | Size of the read buffer the HTTP client uses for reading server responses.  |         | no
-`write_buffer_size`       | `string`   | Size of the write buffer the HTTP client uses for writing requests.         |         | no
-`timeout`                 | `duration` | Time to wait before marking a request as failed.                            | `"15s"` | no
-`max_idle_conns`          | `int`      | Limits the number of idle HTTP connections the client can keep open.        | `100`   | no
-`max_idle_conns_per_host` | `int`      | Limits the number of idle HTTP connections the host can keep open.          | `5`     | no
-`max_conns_per_host`      | `int`      | Limits the total (dialing,active, and idle) number of connections per host. |         | no
-`idle_conn_timeout`       | `duration` | Time to wait before an idle connection closes itself.                       | `"45s"` | no
-`disable_keep_alives`     | `bool`     | Disable HTTP keep-alive.                                                    |         | no
-`insecure_skip_verify`    | `boolean`  | Ignores insecure server TLS certificates.                                   |         | no
+| Name                      | Type       | Description                                                                 | Default | Required |
+| ------------------------- | ---------- | --------------------------------------------------------------------------- | ------- | -------- |
+| `read_buffer_size`        | `string`   | Size of the read buffer the HTTP client uses for reading server responses.  |         | no       |
+| `write_buffer_size`       | `string`   | Size of the write buffer the HTTP client uses for writing requests.         |         | no       |
+| `timeout`                 | `duration` | Time to wait before marking a request as failed.                            | `"15s"` | no       |
+| `max_idle_conns`          | `int`      | Limits the number of idle HTTP connections the client can keep open.        | `100`   | no       |
+| `max_idle_conns_per_host` | `int`      | Limits the number of idle HTTP connections the host can keep open.          | `5`     | no       |
+| `max_conns_per_host`      | `int`      | Limits the total (dialing,active, and idle) number of connections per host. |         | no       |
+| `idle_conn_timeout`       | `duration` | Time to wait before an idle connection closes itself.                       | `"45s"` | no       |
+| `disable_keep_alives`     | `bool`     | Disable HTTP keep-alive.                                                    |         | no       |
+| `insecure_skip_verify`    | `boolean`  | Ignores insecure server TLS certificates.                                   |         | no       |
 
 ### retry_on_failure block
 
@@ -284,9 +280,9 @@ The `queue` block configures an in-memory buffer of batches before data is sent
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value other components can use to send telemetry data to.
+| Name    | Type               | Description                                                 |
+| ------- | ------------------ | ----------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics, logs, or traces).
 
@@ -303,6 +299,7 @@ information.
 ## Example
 
 ### Forward Prometheus Metrics
+
 This example forwards Prometheus metrics from {{< param "PRODUCT_NAME" >}} through a receiver for conversion to Open Telemetry format before finally sending them to Datadog.
 If you are using the US Datadog APIs, the `api` field is required for the exporter to function.
 
diff --git a/docs/sources/reference/components/otelcol/otelcol.exporter.debug.md b/docs/sources/reference/components/otelcol/otelcol.exporter.debug.md
index 0f4743cd10..b9d23db4a6 100644
--- a/docs/sources/reference/components/otelcol/otelcol.exporter.debug.md
+++ b/docs/sources/reference/components/otelcol/otelcol.exporter.debug.md
@@ -12,7 +12,7 @@ title: otelcol.exporter.debug
 You can control the verbosity of the logs.
 
 {{< admonition type="note" >}}
-`otelcol.exporter.debug` is a wrapper over the upstream OpenTelemetry Collector `debug` exporter. 
+`otelcol.exporter.debug` is a wrapper over the upstream OpenTelemetry Collector `debug` exporter.
 If necessary, bug reports or feature requests are redirected to the upstream repository.
 {{< /admonition >}}
 
@@ -28,24 +28,27 @@ otelcol.exporter.debug "LABEL" { }
 
 `otelcol.exporter.debug` supports the following arguments:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`verbosity`           | `string` | Verbosity of the generated logs. | `"basic"` | no
-`sampling_initial`    | `int`    | Number of messages initially logged each second. | `2` | no
-`sampling_thereafter` | `int`    | Sampling rate after the initial messages are logged. | `1` | no
-`use_internal_logger` | `bool`   | Whether to use the internal logger or print directly to `stdout`. | `true` | no
+| Name                  | Type     | Description                                                       | Default   | Required |
+| --------------------- | -------- | ----------------------------------------------------------------- | --------- | -------- |
+| `verbosity`           | `string` | Verbosity of the generated logs.                                  | `"basic"` | no       |
+| `sampling_initial`    | `int`    | Number of messages initially logged each second.                  | `2`       | no       |
+| `sampling_thereafter` | `int`    | Sampling rate after the initial messages are logged.              | `1`       | no       |
+| `use_internal_logger` | `bool`   | Whether to use the internal logger or print directly to `stdout`. | `true`    | no       |
 
 The `verbosity` argument must be one of:
-* `"basic"`: A single-line summary of received data is logged to stderr, with a total count of telemetry records for every batch of received logs, metrics, or traces.
-* `"normal"`: Produces the same output as `"basic"` verbosity.
-* `"detailed"`: All details of every telemetry record are logged to stderr, typically writing multiple lines for every telemetry record.
+
+- `"basic"`: A single-line summary of received data is logged to stderr, with a total count of telemetry records for every batch of received logs, metrics, or traces.
+- `"normal"`: Produces the same output as `"basic"` verbosity.
+- `"detailed"`: All details of every telemetry record are logged to stderr, typically writing multiple lines for every telemetry record.
 
 The following example shows `"basic"` and `"normal"` output:
+
 ```
 ts=2024-06-13T11:24:13.782957Z level=info msg=TracesExporter component_path=/ component_id=otelcol.exporter.debug.default "resource spans": 1, spans: 2
 ```
 
 The following example shows `"detailed"` output:
+
 ```
 ts=2024-06-13T11:24:13.782957Z level=info msg=TracesExporter component_path=/ component_id=otelcol.exporter.debug.default "resource spans"=1 spans=2
 ts=2024-06-13T11:24:13.783101Z level=info msg="ResourceSpans #0
@@ -97,9 +100,9 @@ Multiline logs may also be harder to parse.
 The following blocks are supported inside the definition of
 `otelcol.exporter.debug`:
 
-Hierarchy     | Block             | Description                                                                | Required
---------------|-------------------|----------------------------------------------------------------------------|---------
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `client > tls`
 refers to a `tls` block defined inside a `client` block.
@@ -114,9 +117,9 @@ refers to a `tls` block defined inside a `client` block.
 
 The following fields are exported and can be referenced by other components:
 
-Name | Type | Description
----- | ---- | -----------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics,
 logs, or traces).
@@ -149,6 +152,7 @@ otelcol.receiver.otlp "default" {
 
 otelcol.exporter.debug "default" {}
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -162,4 +166,4 @@ Connecting some components may not be sensible or components may require further
 Refer to the linked documentation for more details.
 {{< /admonition >}}
 
-<!-- END GENERATED COMPATIBLE COMPONENTS -->
\ No newline at end of file
+<!-- END GENERATED COMPATIBLE COMPONENTS -->
diff --git a/docs/sources/reference/components/otelcol/otelcol.exporter.kafka.md b/docs/sources/reference/components/otelcol/otelcol.exporter.kafka.md
index cfbcad4c06..899b749325 100644
--- a/docs/sources/reference/components/otelcol/otelcol.exporter.kafka.md
+++ b/docs/sources/reference/components/otelcol/otelcol.exporter.kafka.md
@@ -8,14 +8,14 @@ title: otelcol.exporter.kafka
 
 # otelcol.exporter.kafka
 
-`otelcol.exporter.kafka` accepts logs, metrics, and traces telemetry data from 
+`otelcol.exporter.kafka` accepts logs, metrics, and traces telemetry data from
 other `otelcol` components and sends it to Kafka.
 
 It is important to use `otelcol.exporter.kafka` together with `otelcol.processor.batch`
 to make sure `otelcol.exporter.kafka` doesn't slow down due to sending Kafka a huge number of small payloads.
 
 {{< admonition type="note" >}}
-`otelcol.exporter.kafka` is a wrapper over the upstream OpenTelemetry Collector `kafka` exporter from the `otelcol-contrib`  distribution.
+`otelcol.exporter.kafka` is a wrapper over the upstream OpenTelemetry Collector `kafka` exporter from the `otelcol-contrib` distribution.
 Bug reports or feature requests will be redirected to the upstream repository, if necessary.
 {{< /admonition >}}
 
@@ -34,24 +34,24 @@ otelcol.exporter.kafka "LABEL" {
 
 The following arguments are supported:
 
-Name                                       | Type            | Description                                                                         | Default              | Required
------------------------------------------- | --------------- | ----------------------------------------------------------------------------------- | -------------------- | --------
-`protocol_version`                         | `string`        | Kafka protocol version to use.                                                      |                      | yes
-`brokers`                                  | `list(string)`  | Kafka brokers to connect to.                                                        | `["localhost:9092"]` | no
-`topic`                                    | `string`        | Kafka topic to send to.                                                             |  _See below_         | no
-`topic_from_attribute`                     | `string`        | A resource attribute whose value should be used as the message's topic.             |  `""`                | no
-`encoding`                                 | `string`        | Encoding of payload read from Kafka.                                                | `"otlp_proto"`       | no
-`client_id`                                | `string`        | Consumer client ID to use. The ID will be used for all produce requests.            | `"sarama"`           | no
-`timeout`                                  | `duration`      | The timeout for every attempt to send data to the backend.                          | `"5s"`               | no
-`resolve_canonical_bootstrap_servers_only` | `bool`          | Whether to resolve then reverse-lookup broker IPs during startup.                   | `"false"`            | no
-`partition_traces_by_id`                   | `bool`          | Whether to include the trace ID as the message key in trace messages sent to Kafka. | `"false"`            | no
-`partition_metrics_by_resource_attributes` | `bool`          | Whether to include the hash of sorted resource attributes as the message partitioning key in metric messages sent to Kafka. | `"false"`            | no
+| Name                                       | Type           | Description                                                                                                                 | Default              | Required |
+| ------------------------------------------ | -------------- | --------------------------------------------------------------------------------------------------------------------------- | -------------------- | -------- |
+| `protocol_version`                         | `string`       | Kafka protocol version to use.                                                                                              |                      | yes      |
+| `brokers`                                  | `list(string)` | Kafka brokers to connect to.                                                                                                | `["localhost:9092"]` | no       |
+| `topic`                                    | `string`       | Kafka topic to send to.                                                                                                     | _See below_          | no       |
+| `topic_from_attribute`                     | `string`       | A resource attribute whose value should be used as the message's topic.                                                     | `""`                 | no       |
+| `encoding`                                 | `string`       | Encoding of payload read from Kafka.                                                                                        | `"otlp_proto"`       | no       |
+| `client_id`                                | `string`       | Consumer client ID to use. The ID will be used for all produce requests.                                                    | `"sarama"`           | no       |
+| `timeout`                                  | `duration`     | The timeout for every attempt to send data to the backend.                                                                  | `"5s"`               | no       |
+| `resolve_canonical_bootstrap_servers_only` | `bool`         | Whether to resolve then reverse-lookup broker IPs during startup.                                                           | `"false"`            | no       |
+| `partition_traces_by_id`                   | `bool`         | Whether to include the trace ID as the message key in trace messages sent to Kafka.                                         | `"false"`            | no       |
+| `partition_metrics_by_resource_attributes` | `bool`         | Whether to include the hash of sorted resource attributes as the message partitioning key in metric messages sent to Kafka. | `"false"`            | no       |
 
 If `topic` is not set, different topics will be used for different telemetry signals:
 
-* Metrics will be sent to an `otlp_metrics` topic.
-* Traces will be sent to an `otlp_spans` topic.
-* Logs will be sent to an `otlp_logs` topic.
+- Metrics will be sent to an `otlp_metrics` topic.
+- Traces will be sent to an `otlp_spans` topic.
+- Logs will be sent to an `otlp_logs` topic.
 
 If topic is set, the same topic will be used for all telemetry signals - metrics, logs, and traces.
 
@@ -59,16 +59,17 @@ When `topic_from_attribute` is set, it will take precedence over `topic`.
 
 The `encoding` argument determines how to encode messages sent to Kafka.
 `encoding` must be one of the following strings:
-* Encodings which work for traces, logs, and metrics:
-  * `"otlp_proto"`: Encode messages as OTLP protobuf. 
-  * `"otlp_json"`: Encode messages as OTLP JSON.
-* Encodings which work only for traces:
-  * `"jaeger_proto"`: The payload is serialized to a single Jaeger proto `Span`, and keyed by TraceID.
-  * `"jaeger_json"`: The payload is serialized to a single Jaeger JSON Span using `jsonpb`, and keyed by TraceID.
-  * `"zipkin_proto"`: The payload is serialized to Zipkin v2 proto Span.
-  * `"zipkin_json"`: The payload is serialized to Zipkin v2 JSON Span.
-* Encodings which work only for logs:
-  * `"raw"`: If the log record body is a byte array, it is sent as is. Otherwise, it is serialized to JSON. Resource and record attributes are discarded.
+
+- Encodings which work for traces, logs, and metrics:
+  - `"otlp_proto"`: Encode messages as OTLP protobuf.
+  - `"otlp_json"`: Encode messages as OTLP JSON.
+- Encodings which work only for traces:
+  - `"jaeger_proto"`: The payload is serialized to a single Jaeger proto `Span`, and keyed by TraceID.
+  - `"jaeger_json"`: The payload is serialized to a single Jaeger JSON Span using `jsonpb`, and keyed by TraceID.
+  - `"zipkin_proto"`: The payload is serialized to Zipkin v2 proto Span.
+  - `"zipkin_json"`: The payload is serialized to Zipkin v2 JSON Span.
+- Encodings which work only for logs:
+  - `"raw"`: If the log record body is a byte array, it is sent as is. Otherwise, it is serialized to JSON. Resource and record attributes are discarded.
 
 `partition_traces_by_id` does not have any effect on Jaeger encoding exporters since Jaeger exporters include trace ID as the message key by default.
 
@@ -76,22 +77,22 @@ The `encoding` argument determines how to encode messages sent to Kafka.
 
 The following blocks are supported inside the definition of `otelcol.exporter.kafka`:
 
-Hierarchy                        | Block               | Description                                                                 | Required
--------------------------------- | ------------------- | --------------------------------------------------------------------------- | --------
-authentication                   | [authentication][]   | Configures authentication for connecting to Kafka brokers.                  | no
-authentication > plaintext       | [plaintext][]        | Authenticates against Kafka brokers with plaintext.                         | no
-authentication > sasl            | [sasl][]             | Authenticates against Kafka brokers with SASL.                              | no
-authentication > sasl > aws_msk  | [aws_msk][]          | Additional SASL parameters when using AWS_MSK_IAM.                          | no
-authentication > tls             | [tls][]              | Configures TLS for connecting to the Kafka brokers.                         | no
-authentication > kerberos        | [kerberos][]         | Authenticates against Kafka brokers with Kerberos.                          | no
-metadata                         | [metadata][]         | Configures how to retrieve metadata from Kafka brokers.                     | no
-metadata > retry                 | [retry][]            | Configures how to retry metadata retrieval.                                 | no
-retry_on_failure                 | [retry_on_failure][] | Configures retry mechanism for failed requests.                             | no
-sending_queue                    | [sending_queue][]    | Configures batching of data before sending.                                 | no
-producer                         | [producer][]         | Kafka producer configuration,                                               | no
-debug_metrics                    | [debug_metrics][]    | Configures the metrics which this component generates to monitor its state. | no
-
-The `>` symbol indicates deeper levels of nesting. 
+| Hierarchy                       | Block                | Description                                                                 | Required |
+| ------------------------------- | -------------------- | --------------------------------------------------------------------------- | -------- |
+| authentication                  | [authentication][]   | Configures authentication for connecting to Kafka brokers.                  | no       |
+| authentication > plaintext      | [plaintext][]        | Authenticates against Kafka brokers with plaintext.                         | no       |
+| authentication > sasl           | [sasl][]             | Authenticates against Kafka brokers with SASL.                              | no       |
+| authentication > sasl > aws_msk | [aws_msk][]          | Additional SASL parameters when using AWS_MSK_IAM.                          | no       |
+| authentication > tls            | [tls][]              | Configures TLS for connecting to the Kafka brokers.                         | no       |
+| authentication > kerberos       | [kerberos][]         | Authenticates against Kafka brokers with Kerberos.                          | no       |
+| metadata                        | [metadata][]         | Configures how to retrieve metadata from Kafka brokers.                     | no       |
+| metadata > retry                | [retry][]            | Configures how to retry metadata retrieval.                                 | no       |
+| retry_on_failure                | [retry_on_failure][] | Configures retry mechanism for failed requests.                             | no       |
+| sending_queue                   | [sending_queue][]    | Configures batching of data before sending.                                 | no       |
+| producer                        | [producer][]         | Kafka producer configuration,                                               | no       |
+| debug_metrics                   | [debug_metrics][]    | Configures the metrics which this component generates to monitor its state. | no       |
+
+The `>` symbol indicates deeper levels of nesting.
 For example, `authentication > tls` refers to a `tls` block defined inside an `authentication` block.
 
 [authentication]: #authentication-block
@@ -161,12 +162,12 @@ The `producer` block configures how to retry retrieving metadata when retrieval
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`max_message_bytes` | `number` | The maximum permitted size of a message in bytes. | `1000000` | no
-`required_acks` | `number` | Controls when a message is regarded as transmitted.   | `1` | no
-`compression` | `string` | Time to wait between retries. | `"none"` | no
-`flush_max_messages` | `number` | Time to wait between retries. | `0` | no
+| Name                 | Type     | Description                                         | Default   | Required |
+| -------------------- | -------- | --------------------------------------------------- | --------- | -------- |
+| `max_message_bytes`  | `number` | The maximum permitted size of a message in bytes.   | `1000000` | no       |
+| `required_acks`      | `number` | Controls when a message is regarded as transmitted. | `1`       | no       |
+| `compression`        | `string` | Time to wait between retries.                       | `"none"`  | no       |
+| `flush_max_messages` | `number` | Time to wait between retries.                       | `0`       | no       |
 
 Refer to the [sarama documentation][RequiredAcks] for more information on `required_acks`.
 
@@ -184,9 +185,9 @@ Refer to the [Sarama documentation][CompressionCodec] for more information.
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics, logs, or traces).
 
diff --git a/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md b/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md
index 67c5f6aab0..2c3d73f843 100644
--- a/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md
+++ b/docs/sources/reference/components/otelcol/otelcol.exporter.loadbalancing.md
@@ -32,9 +32,9 @@ which choose a backend based on the view of the full trace.
 When a list of backends is updated, some of the signals will be rerouted to different backends.
 Around R/N of the "routes" will be rerouted differently, where:
 
-* A "route" is either a trace ID or a service name mapped to a certain backend.
-* "R" is the total number of routes.
-* "N" is the total number of backends.
+- A "route" is either a trace ID or a service name mapped to a certain backend.
+- "R" is the total number of routes.
+- "N" is the total number of backends.
 
 This should be stable enough for most cases, and the larger the number of backends, the less disruption it should cause.
 
@@ -57,36 +57,37 @@ otelcol.exporter.loadbalancing "LABEL" {
 
 `otelcol.exporter.loadbalancing` supports the following arguments:
 
-Name          | Type     | Description                          | Default     | Required
---------------|----------|--------------------------------------|-------------|---------
-`routing_key` | `string` | Routing strategy for load balancing. | `"traceID"` | no
+| Name          | Type     | Description                          | Default     | Required |
+| ------------- | -------- | ------------------------------------ | ----------- | -------- |
+| `routing_key` | `string` | Routing strategy for load balancing. | `"traceID"` | no       |
 
 The `routing_key` attribute determines how to route signals across endpoints. Its value could be one of the following:
-* `"service"`: spans with the same `service.name` will be exported to the same backend.
-This is useful when using processors like the span metrics, so all spans for each service are sent to consistent {{< param "PRODUCT_NAME" >}} instances
-for metric collection. Otherwise, metrics for the same services would be sent to different instances, making aggregations inaccurate.
-* `"traceID"`: spans belonging to the same traceID will be exported to the same backend.
+
+- `"service"`: spans with the same `service.name` will be exported to the same backend.
+  This is useful when using processors like the span metrics, so all spans for each service are sent to consistent {{< param "PRODUCT_NAME" >}} instances
+  for metric collection. Otherwise, metrics for the same services would be sent to different instances, making aggregations inaccurate.
+- `"traceID"`: spans belonging to the same traceID will be exported to the same backend.
 
 ## Blocks
 
 The following blocks are supported inside the definition of
 `otelcol.exporter.loadbalancing`:
 
-Hierarchy                            | Block             | Description                                                                | Required
--------------------------------------|-------------------|----------------------------------------------------------------------------|---------
-resolver                             | [resolver][]      | Configures discovering the endpoints to export to.                         | yes
-resolver > static                    | [static][]        | Static list of endpoints to export to.                                     | no
-resolver > dns                       | [dns][]           | DNS-sourced list of endpoints to export to.                                | no
-resolver > kubernetes                | [kubernetes][]    | Kubernetes-sourced list of endpoints to export to.                         | no
-resolver > aws_cloud_map             | [aws_cloud_map][] | AWS CloudMap-sourced list of endpoints to export to.                       | no
-protocol                             | [protocol][]      | Protocol settings. Only OTLP is supported at the moment.                   | no
-protocol > otlp                      | [otlp][]          | Configures an OTLP exporter.                                               | no
-protocol > otlp > client             | [client][]        | Configures the exporter gRPC client.                                       | no
-protocol > otlp > client > tls       | [tls][]           | Configures TLS for the gRPC client.                                        | no
-protocol > otlp > client > keepalive | [keepalive][]     | Configures keepalive settings for the gRPC client.                         | no
-protocol > otlp > queue              | [queue][]         | Configures batching of data before sending.                                | no
-protocol > otlp > retry              | [retry][]         | Configures retry mechanism for failed requests.                            | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy                            | Block             | Description                                                                | Required |
+| ------------------------------------ | ----------------- | -------------------------------------------------------------------------- | -------- |
+| resolver                             | [resolver][]      | Configures discovering the endpoints to export to.                         | yes      |
+| resolver > static                    | [static][]        | Static list of endpoints to export to.                                     | no       |
+| resolver > dns                       | [dns][]           | DNS-sourced list of endpoints to export to.                                | no       |
+| resolver > kubernetes                | [kubernetes][]    | Kubernetes-sourced list of endpoints to export to.                         | no       |
+| resolver > aws_cloud_map             | [aws_cloud_map][] | AWS CloudMap-sourced list of endpoints to export to.                       | no       |
+| protocol                             | [protocol][]      | Protocol settings. Only OTLP is supported at the moment.                   | no       |
+| protocol > otlp                      | [otlp][]          | Configures an OTLP exporter.                                               | no       |
+| protocol > otlp > client             | [client][]        | Configures the exporter gRPC client.                                       | no       |
+| protocol > otlp > client > tls       | [tls][]           | Configures TLS for the gRPC client.                                        | no       |
+| protocol > otlp > client > keepalive | [keepalive][]     | Configures keepalive settings for the gRPC client.                         | no       |
+| protocol > otlp > queue              | [queue][]         | Configures batching of data before sending.                                | no       |
+| protocol > otlp > retry              | [retry][]         | Configures retry mechanism for failed requests.                            | no       |
+| debug_metrics                        | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `resolver > static`
 refers to a `static` block defined inside a `resolver` block.
@@ -118,9 +119,9 @@ The `static` block configures a list of endpoints which this exporter will send
 
 The following arguments are supported:
 
-Name        | Type           | Description                     | Default | Required
-------------|----------------|---------------------------------|---------|---------
-`hostnames` | `list(string)` | List of endpoints to export to. |         | yes
+| Name        | Type           | Description                     | Default | Required |
+| ----------- | -------------- | ------------------------------- | ------- | -------- |
+| `hostnames` | `list(string)` | List of endpoints to export to. |         | yes      |
 
 ### dns block
 
@@ -130,12 +131,12 @@ as the endpoint to which to export data to.
 
 The following arguments are supported:
 
-Name       | Type       | Description                                                           | Default  | Required
------------|------------|-----------------------------------------------------------------------|----------|---------
-`hostname` | `string`   | DNS hostname to resolve.                                              |          | yes
-`interval` | `duration` | Resolver interval.                                                    | `"5s"`   | no
-`timeout`  | `duration` | Resolver timeout.                                                     | `"1s"`   | no
-`port`     | `string`   | Port to be used with the IP addresses resolved from the DNS hostname. | `"4317"` | no
+| Name       | Type       | Description                                                           | Default  | Required |
+| ---------- | ---------- | --------------------------------------------------------------------- | -------- | -------- |
+| `hostname` | `string`   | DNS hostname to resolve.                                              |          | yes      |
+| `interval` | `duration` | Resolver interval.                                                    | `"5s"`   | no       |
+| `timeout`  | `duration` | Resolver timeout.                                                     | `"1s"`   | no       |
+| `port`     | `string`   | Port to be used with the IP addresses resolved from the DNS hostname. | `"4317"` | no       |
 
 ### kubernetes block
 
@@ -145,11 +146,11 @@ The `kubernetes` resolver has a much faster response time than the `dns` resolve
 
 The following arguments are supported:
 
-Name      | Type           | Description                                                 | Default  | Required
-----------|----------------|-------------------------------------------------------------|----------|---------
-`service` | `string`       | Kubernetes service to resolve.                              |          | yes
-`ports`   | `list(number)` | Ports to use with the IP addresses resolved from `service`. | `[4317]` | no
-`timeout` | `duration`     | Resolver timeout.                                           | `"1s"`   | no
+| Name      | Type           | Description                                                 | Default  | Required |
+| --------- | -------------- | ----------------------------------------------------------- | -------- | -------- |
+| `service` | `string`       | Kubernetes service to resolve.                              |          | yes      |
+| `ports`   | `list(number)` | Ports to use with the IP addresses resolved from `service`. | `[4317]` | no       |
+| `timeout` | `duration`     | Resolver timeout.                                           | `"1s"`   | no       |
 
 If no namespace is specified inside `service`, an attempt will be made to infer the namespace for this {{< param "PRODUCT_NAME" >}}.
 If this fails, the `default` namespace will be used.
@@ -165,27 +166,28 @@ The `aws_cloud_map` block allows users to use `otelcol.exporter.loadbalancing` w
 
 The following arguments are supported:
 
-Name            | Type       | Description                                                                        | Default     | Required
-----------------|------------|------------------------------------------------------------------------------------|-------------|---------
-`namespace`     | `string`   | The CloudMap namespace where the service is registered.                            |             | yes
-`service_name`  | `string`   | The name of the service which was specified when registering the instance.         |             | yes
-`interval`      | `duration` | Resolver interval.                                                                 | `"30s"`     | no
-`timeout`       | `duration` | Resolver timeout.                                                                  | `"5s"`      | no
-`health_status` | `string`   | Ports to use with the IP addresses resolved from `service`.                        | `"HEALTHY"` | no
-`port`          | `number`   | Port to be used for exporting the traces to the addresses resolved from `service`. | `null`      | no
+| Name            | Type       | Description                                                                        | Default     | Required |
+| --------------- | ---------- | ---------------------------------------------------------------------------------- | ----------- | -------- |
+| `namespace`     | `string`   | The CloudMap namespace where the service is registered.                            |             | yes      |
+| `service_name`  | `string`   | The name of the service which was specified when registering the instance.         |             | yes      |
+| `interval`      | `duration` | Resolver interval.                                                                 | `"30s"`     | no       |
+| `timeout`       | `duration` | Resolver timeout.                                                                  | `"5s"`      | no       |
+| `health_status` | `string`   | Ports to use with the IP addresses resolved from `service`.                        | `"HEALTHY"` | no       |
+| `port`          | `number`   | Port to be used for exporting the traces to the addresses resolved from `service`. | `null`      | no       |
 
 `health_status` can be set to either of:
-* `HEALTHY`: Only return instances that are healthy.
-* `UNHEALTHY`: Only return instances that are unhealthy.
-* `ALL`: Return all instances, regardless of their health status.
-* `HEALTHY_OR_ELSE_ALL`: Returns healthy instances, unless none are reporting a healthy state. 
+
+- `HEALTHY`: Only return instances that are healthy.
+- `UNHEALTHY`: Only return instances that are unhealthy.
+- `ALL`: Return all instances, regardless of their health status.
+- `HEALTHY_OR_ELSE_ALL`: Returns healthy instances, unless none are reporting a healthy state.
   In that case, return all instances. This is also called failing open.
 
 If `port` is not set, a default port defined in CloudMap will be used.
 
 {{< admonition type="note" >}}
 The `aws_cloud_map` resolver returns a maximum of 100 hosts.
-A [feature request](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/29771) 
+A [feature request](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/29771)
 aims cover pagination for this scenario.
 {{< /admonition >}}
 
@@ -205,16 +207,16 @@ The endpoints used by the client block are the ones from the `resolver` block
 
 The following arguments are supported:
 
-Name                | Type                       | Description                                                                      | Default       | Required
---------------------|----------------------------|----------------------------------------------------------------------------------|---------------|---------
-`compression`       | `string`                   | Compression mechanism to use for requests.                                       | `"gzip"`      | no
-`read_buffer_size`  | `string`                   | Size of the read buffer the gRPC client to use for reading server responses.     |               | no
-`write_buffer_size` | `string`                   | Size of the write buffer the gRPC client to use for writing requests.            | `"512KiB"`    | no
-`wait_for_ready`    | `boolean`                  | Waits for gRPC connection to be in the `READY` state before sending data.        | `false`       | no
-`headers`           | `map(string)`              | Additional headers to send with the request.                                     | `{}`          | no
-`balancer_name`     | `string`                   | Which gRPC client-side load balancer to use for requests.                        | `round_robin` | no
-`authority`         | `string`                   | Overrides the default `:authority` header in gRPC requests from the gRPC client. |               | no
-`auth`              | `capsule(otelcol.Handler)` | Handler from an `otelcol.auth` component to use for authenticating requests.     |               | no
+| Name                | Type                       | Description                                                                      | Default       | Required |
+| ------------------- | -------------------------- | -------------------------------------------------------------------------------- | ------------- | -------- |
+| `compression`       | `string`                   | Compression mechanism to use for requests.                                       | `"gzip"`      | no       |
+| `read_buffer_size`  | `string`                   | Size of the read buffer the gRPC client to use for reading server responses.     |               | no       |
+| `write_buffer_size` | `string`                   | Size of the write buffer the gRPC client to use for writing requests.            | `"512KiB"`    | no       |
+| `wait_for_ready`    | `boolean`                  | Waits for gRPC connection to be in the `READY` state before sending data.        | `false`       | no       |
+| `headers`           | `map(string)`              | Additional headers to send with the request.                                     | `{}`          | no       |
+| `balancer_name`     | `string`                   | Which gRPC client-side load balancer to use for requests.                        | `round_robin` | no       |
+| `authority`         | `string`                   | Overrides the default `:authority` header in gRPC requests from the gRPC client. |               | no       |
+| `auth`              | `capsule(otelcol.Handler)` | Handler from an `otelcol.auth` component to use for authenticating requests.     |               | no       |
 
 {{< docs/shared lookup="reference/components/otelcol-compression-field.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -224,8 +226,8 @@ Name                | Type                       | Description
 
 You can configure an HTTP proxy with the following environment variables:
 
-* `HTTPS_PROXY`
-* `NO_PROXY`
+- `HTTPS_PROXY`
+- `NO_PROXY`
 
 The `HTTPS_PROXY` environment variable specifies a URL to use for proxying
 requests. Connections to the proxy are established via [the `HTTP CONNECT`
@@ -257,11 +259,11 @@ connections.
 
 The following arguments are supported:
 
-Name                    | Type       | Description                                                                                | Default | Required
-------------------------|------------|--------------------------------------------------------------------------------------------|---------|---------
-`ping_wait`             | `duration` | How often to ping the server after no activity.                                            |         | no
-`ping_response_timeout` | `duration` | Time to wait before closing inactive connections if the server does not respond to a ping. |         | no
-`ping_without_stream`   | `boolean`  | Send pings even if there is no active stream request.                                      |         | no
+| Name                    | Type       | Description                                                                                | Default | Required |
+| ----------------------- | ---------- | ------------------------------------------------------------------------------------------ | ------- | -------- |
+| `ping_wait`             | `duration` | How often to ping the server after no activity.                                            |         | no       |
+| `ping_response_timeout` | `duration` | Time to wait before closing inactive connections if the server does not respond to a ping. |         | no       |
+| `ping_without_stream`   | `boolean`  | Send pings even if there is no active stream request.                                      |         | no       |
 
 ### queue block
 
@@ -283,13 +285,14 @@ The `retry` block configures how failed requests to the gRPC server are retried.
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` OTLP-formatted data for telemetry signals of these types:
-* logs
-* traces
+
+- logs
+- traces
 
 ## Choose a load balancing strategy
 
@@ -302,10 +305,13 @@ The use of `otelcol.exporter.loadbalancing` is only necessary for [stateful comp
 [stateful-and-stateless-components]: ../../../../set-up/deploy/#stateful-and-stateless-components
 
 ### otelcol.processor.tail_sampling
+
 <!-- TODO: Add a picture of the architecture?  -->
+
 All spans for a given trace ID must go to the same tail sampling {{< param "PRODUCT_NAME" >}} instance.
-* This can be done by configuring `otelcol.exporter.loadbalancing` with `routing_key = "traceID"`.
-* If you do not configure `routing_key = "traceID"`, the sampling decision may be incorrect.
+
+- This can be done by configuring `otelcol.exporter.loadbalancing` with `routing_key = "traceID"`.
+- If you do not configure `routing_key = "traceID"`, the sampling decision may be incorrect.
   The tail sampler must have a full view of the trace when making a sampling decision.
   For example, a `rate_limiting` tail sampling strategy may incorrectly pass through
   more spans than expected if the spans for the same trace are spread out to more than
@@ -314,27 +320,31 @@ All spans for a given trace ID must go to the same tail sampling {{< param "PROD
 <!-- Make "rate limiting" a URL to the tail sampler doc -->
 
 ### otelcol.connector.spanmetrics
+
 All spans for a given `service.name` must go to the same spanmetrics {{< param "PRODUCT_NAME" >}}.
-* This can be done by configuring `otelcol.exporter.loadbalancing` with `routing_key = "service"`.
-* If you do not configure `routing_key = "service"`, metrics generated from spans might be incorrect.
-For example, if similar spans for the same `service.name` end up on different {{< param "PRODUCT_NAME" >}} instances, the two {{< param "PRODUCT_NAME" >}}s will have identical metric series for calculating span latency, errors, and number of requests.
-When both {{< param "PRODUCT_NAME" >}} instances attempt to write the metrics to a database such as Mimir, the series may clash with each other.
-At best, this will lead to an error in {{< param "PRODUCT_NAME" >}} and a rejected write to the metrics database.
-At worst, it could lead to inaccurate data due to overlapping samples for the metric series.
+
+- This can be done by configuring `otelcol.exporter.loadbalancing` with `routing_key = "service"`.
+- If you do not configure `routing_key = "service"`, metrics generated from spans might be incorrect.
+  For example, if similar spans for the same `service.name` end up on different {{< param "PRODUCT_NAME" >}} instances, the two {{< param "PRODUCT_NAME" >}}s will have identical metric series for calculating span latency, errors, and number of requests.
+  When both {{< param "PRODUCT_NAME" >}} instances attempt to write the metrics to a database such as Mimir, the series may clash with each other.
+  At best, this will lead to an error in {{< param "PRODUCT_NAME" >}} and a rejected write to the metrics database.
+  At worst, it could lead to inaccurate data due to overlapping samples for the metric series.
 
 However, there are ways to scale `otelcol.connector.spanmetrics` without the need for a load balancer:
+
 1. Each {{< param "PRODUCT_NAME" >}} could add an attribute such as `collector.id` in order to make its series unique.
    Then, for example, you could use a `sum by` PromQL query to aggregate the metrics from different {{< param "PRODUCT_NAME" >}}s.
    Unfortunately, an extra `collector.id` attribute has a downside that the metrics stored in the database will have higher {{< term "cardinality" >}}cardinality{{< /term >}}.
 2. Spanmetrics could be generated in the backend database instead of in {{< param "PRODUCT_NAME" >}}.
-    For example, span metrics can be [generated][tempo-spanmetrics] in Grafana Cloud by the Tempo traces database.
+   For example, span metrics can be [generated][tempo-spanmetrics] in Grafana Cloud by the Tempo traces database.
 
 [tempo-spanmetrics]: https://grafana.com/docs/tempo/latest/metrics-generator/span_metrics/
 
 ### otelcol.connector.servicegraph
+
 It is challenging to scale `otelcol.connector.servicegraph` over multiple {{< param "PRODUCT_NAME" >}} instances.
 For `otelcol.connector.servicegraph` to work correctly, each "client" span must be paired with a "server" span to calculate metrics such as span duration.
-If a "client" span goes to one {{< param "PRODUCT_NAME" >}}, but a "server" span goes to another {{< param "PRODUCT_NAME" >}},  then no single {{< param "PRODUCT_NAME" >}} will be able to pair the spans and a metric won't be generated.
+If a "client" span goes to one {{< param "PRODUCT_NAME" >}}, but a "server" span goes to another {{< param "PRODUCT_NAME" >}}, then no single {{< param "PRODUCT_NAME" >}} will be able to pair the spans and a metric won't be generated.
 
 `otelcol.exporter.loadbalancing` can solve this problem partially if it is configured with `routing_key = "traceID"`.
 Each {{< param "PRODUCT_NAME" >}} will then be able to calculate a service graph for each "client"/"server" pair in a trace.
@@ -352,13 +362,15 @@ For example, service graphs can be [generated][tempo-servicegraphs] in Grafana C
 [adaptive-metrics]: https://grafana.com/docs/grafana-cloud/cost-management-and-billing/reduce-costs/metrics-costs/control-metrics-usage-via-adaptive-metrics/
 
 ### Mixing stateful components
+
 <!-- TODO: Add a picture of the architecture?  -->
+
 Different {{< param "PRODUCT_NAME" >}} components may require a different `routing_key` for `otelcol.exporter.loadbalancing`.
 For example, `otelcol.processor.tail_sampling` requires `routing_key = "traceID"` whereas `otelcol.connector.spanmetrics` requires `routing_key = "service"`.
 To load balance both types of components, two different sets of load balancers have to be set up:
 
-* One set of `otelcol.exporter.loadbalancing` with `routing_key = "traceID"`, sending spans to {{< param "PRODUCT_NAME" >}}s doing tail sampling and no span metrics.
-* Another set of `otelcol.exporter.loadbalancing` with `routing_key = "service"`, sending spans to {{< param "PRODUCT_NAME" >}}s doing span metrics and no service graphs.
+- One set of `otelcol.exporter.loadbalancing` with `routing_key = "traceID"`, sending spans to {{< param "PRODUCT_NAME" >}}s doing tail sampling and no span metrics.
+- Another set of `otelcol.exporter.loadbalancing` with `routing_key = "service"`, sending spans to {{< param "PRODUCT_NAME" >}}s doing span metrics and no service graphs.
 
 Unfortunately, this can also lead to side effects.
 For example, if `otelcol.connector.spanmetrics` is configured to generate exemplars, the tail sampling {{< param "PRODUCT_NAME" >}}s might drop the trace that the exemplar points to.
@@ -435,14 +447,15 @@ otelcol.exporter.loadbalancing "default" {
 ```
 
 The following example shows a Kubernetes configuration that configures two sets of {{< param "PRODUCT_NAME" >}}s:
-* A pool of load-balancer {{< param "PRODUCT_NAME" >}}s:
-  * Spans are received from instrumented applications via `otelcol.receiver.otlp`
-  * Spans are exported via `otelcol.exporter.loadbalancing`.
-* A pool of sampling {{< param "PRODUCT_NAME" >}}s:
-  * The sampling {{< param "PRODUCT_NAME" >}}s run behind a headless service to enable the load-balancer {{< param "PRODUCT_NAME" >}}s to discover them.
-  * Spans are received from the load-balancer {{< param "PRODUCT_NAME" >}}s via `otelcol.receiver.otlp`
-  * Traces are sampled via `otelcol.processor.tail_sampling`.
-  * The traces are exported via `otelcol.exporter.otlp` to an OTLP-compatible database such as Tempo.
+
+- A pool of load-balancer {{< param "PRODUCT_NAME" >}}s:
+  - Spans are received from instrumented applications via `otelcol.receiver.otlp`
+  - Spans are exported via `otelcol.exporter.loadbalancing`.
+- A pool of sampling {{< param "PRODUCT_NAME" >}}s:
+  - The sampling {{< param "PRODUCT_NAME" >}}s run behind a headless service to enable the load-balancer {{< param "PRODUCT_NAME" >}}s to discover them.
+  - Spans are received from the load-balancer {{< param "PRODUCT_NAME" >}}s via `otelcol.receiver.otlp`
+  - Traces are sampled via `otelcol.processor.tail_sampling`.
+  - The traces are exported via `otelcol.exporter.otlp` to an OTLP-compatible database such as Tempo.
 
 {{< collapse title="Example Kubernetes configuration" >}}
 
@@ -470,12 +483,12 @@ spec:
         name: k6-trace-generator
     spec:
       containers:
-      - env:
-        - name: ENDPOINT
-          value: alloy-traces-lb.grafana-cloud-monitoring.svc.cluster.local:9411
-        image: ghcr.io/grafana/xk6-client-tracing:v0.0.2
-        imagePullPolicy: IfNotPresent
-        name: k6-trace-generator
+        - env:
+            - name: ENDPOINT
+              value: alloy-traces-lb.grafana-cloud-monitoring.svc.cluster.local:9411
+          image: ghcr.io/grafana/xk6-client-tracing:v0.0.2
+          imagePullPolicy: IfNotPresent
+          name: k6-trace-generator
 ---
 apiVersion: v1
 kind: Service
@@ -485,10 +498,10 @@ metadata:
 spec:
   clusterIP: None
   ports:
-  - name: alloy-traces-otlp-grpc
-    port: 9411
-    protocol: TCP
-    targetPort: 9411
+    - name: alloy-traces-otlp-grpc
+      port: 9411
+      protocol: TCP
+      targetPort: 9411
   selector:
     name: alloy-traces-lb
   type: ClusterIP
@@ -511,28 +524,28 @@ spec:
         name: alloy-traces-lb
     spec:
       containers:
-      - args:
-        - run
-        - /etc/alloy/alloy_lb.alloy
-        command:
-        - /bin/alloy
-        image: grafana/alloy:v1.0
-        imagePullPolicy: IfNotPresent
-        name: alloy-traces
-        ports:
-        - containerPort: 9411
-          name: otlp-grpc
-          protocol: TCP
-        - containerPort: 34621
-          name: alloy-lb
-          protocol: TCP
-        volumeMounts:
-        - mountPath: /etc/alloy
+        - args:
+            - run
+            - /etc/alloy/alloy_lb.alloy
+          command:
+            - /bin/alloy
+          image: grafana/alloy:v1.0
+          imagePullPolicy: IfNotPresent
           name: alloy-traces
+          ports:
+            - containerPort: 9411
+              name: otlp-grpc
+              protocol: TCP
+            - containerPort: 34621
+              name: alloy-lb
+              protocol: TCP
+          volumeMounts:
+            - mountPath: /etc/alloy
+              name: alloy-traces
       volumes:
-      - configMap:
+        - configMap:
+            name: alloy-traces
           name: alloy-traces
-        name: alloy-traces
 ---
 apiVersion: v1
 kind: Service
@@ -542,10 +555,10 @@ metadata:
 spec:
   clusterIP: None
   ports:
-  - name: alloy-lb
-    port: 34621
-    protocol: TCP
-    targetPort: alloy-lb
+    - name: alloy-lb
+      port: 34621
+      protocol: TCP
+      targetPort: alloy-lb
   selector:
     name: alloy-traces-sampling
   type: ClusterIP
@@ -568,28 +581,28 @@ spec:
         name: alloy-traces-sampling
     spec:
       containers:
-      - args:
-        - run
-        - /etc/alloy/alloy_sampling.alloy
-        command:
-        - /bin/alloy
-        image: grafana/alloy:v1.0
-        imagePullPolicy: IfNotPresent
-        name: alloy-traces
-        ports:
-        - containerPort: 9411
-          name: otlp-grpc
-          protocol: TCP
-        - containerPort: 34621
-          name: alloy-lb
-          protocol: TCP
-        volumeMounts:
-        - mountPath: /etc/alloy
+        - args:
+            - run
+            - /etc/alloy/alloy_sampling.alloy
+          command:
+            - /bin/alloy
+          image: grafana/alloy:v1.0
+          imagePullPolicy: IfNotPresent
           name: alloy-traces
+          ports:
+            - containerPort: 9411
+              name: otlp-grpc
+              protocol: TCP
+            - containerPort: 34621
+              name: alloy-lb
+              protocol: TCP
+          volumeMounts:
+            - mountPath: /etc/alloy
+              name: alloy-traces
       volumes:
-      - configMap:
+        - configMap:
+            name: alloy-traces
           name: alloy-traces
-        name: alloy-traces
 ---
 apiVersion: v1
 kind: ConfigMap
@@ -655,12 +668,14 @@ data:
       password = "pass"
     }
 ```
+
 {{< /collapse >}}
 
 You must fill in the correct OTLP credentials prior to running the example.
 You can use [k3d][] to start the example:
 
 <!-- TODO: Link to the k3d page -->
+
 ```bash
 k3d cluster create alloy-lb-test
 kubectl apply -f kubernetes_config.yaml
@@ -676,7 +691,7 @@ k3d cluster delete alloy-lb-test
 
 ### Kubernetes resolver
 
-When you configure `otelcol.exporter.loadbalancing`  with a `kubernetes` resolver, the Kubernetes API notifies {{< param "PRODUCT_NAME" >}} whenever a new pod is added or removed from the service.
+When you configure `otelcol.exporter.loadbalancing` with a `kubernetes` resolver, the Kubernetes API notifies {{< param "PRODUCT_NAME" >}} whenever a new pod is added or removed from the service.
 Spans are exported to the addresses from the Kubernetes API, combined with all the possible `ports`.
 
 ```alloy
@@ -696,18 +711,20 @@ otelcol.exporter.loadbalancing "default" {
 ```
 
 The following example shows a Kubernetes configuration that sets up two sets of {{< param "PRODUCT_NAME" >}}s:
-* A pool of load-balancer {{< param "PRODUCT_NAME" >}}s:
-  * Spans are received from instrumented applications via `otelcol.receiver.otlp`
-  * Spans are exported via `otelcol.exporter.loadbalancing`.
-  * The load-balancer {{< param "PRODUCT_NAME" >}}s will get notified by the Kubernetes API any time a pod
+
+- A pool of load-balancer {{< param "PRODUCT_NAME" >}}s:
+  - Spans are received from instrumented applications via `otelcol.receiver.otlp`
+  - Spans are exported via `otelcol.exporter.loadbalancing`.
+  - The load-balancer {{< param "PRODUCT_NAME" >}}s will get notified by the Kubernetes API any time a pod
     is added or removed from the pool of sampling {{< param "PRODUCT_NAME" >}}s.
-* A pool of sampling {{< param "PRODUCT_NAME" >}}s:
-  * The sampling {{< param "PRODUCT_NAME" >}}s do not need to run behind a headless service.
-  * Spans are received from the load-balancer {{< param "PRODUCT_NAME" >}}s via `otelcol.receiver.otlp`
-  * Traces are sampled via `otelcol.processor.tail_sampling`.
-  * The traces are exported via `otelcol.exporter.otlp` to a an OTLP-compatible database such as Tempo.
+- A pool of sampling {{< param "PRODUCT_NAME" >}}s:
+  - The sampling {{< param "PRODUCT_NAME" >}}s do not need to run behind a headless service.
+  - Spans are received from the load-balancer {{< param "PRODUCT_NAME" >}}s via `otelcol.receiver.otlp`
+  - Traces are sampled via `otelcol.processor.tail_sampling`.
+  - The traces are exported via `otelcol.exporter.otlp` to a an OTLP-compatible database such as Tempo.
 
 <!-- TODO: In the k8s config, why does the LB service has to be headless? -->
+
 {{< collapse title="Example Kubernetes configuration" >}}
 
 ```yaml
@@ -728,14 +745,14 @@ metadata:
   name: alloy-traces-role
   namespace: grafana-cloud-monitoring
 rules:
-- apiGroups:
-  - ""
-  resources:
-  - endpoints
-  verbs:
-  - list
-  - watch
-  - get
+  - apiGroups:
+      - ""
+    resources:
+      - endpoints
+    verbs:
+      - list
+      - watch
+      - get
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: RoleBinding
@@ -747,9 +764,9 @@ roleRef:
   kind: Role
   name: alloy-traces-role
 subjects:
-- kind: ServiceAccount
-  name: alloy-traces
-  namespace: grafana-cloud-monitoring
+  - kind: ServiceAccount
+    name: alloy-traces
+    namespace: grafana-cloud-monitoring
 ---
 apiVersion: apps/v1
 kind: Deployment
@@ -769,12 +786,12 @@ spec:
         name: k6-trace-generator
     spec:
       containers:
-      - env:
-        - name: ENDPOINT
-          value: alloy-traces-lb.grafana-cloud-monitoring.svc.cluster.local:9411
-        image: ghcr.io/grafana/xk6-client-tracing:v0.0.2
-        imagePullPolicy: IfNotPresent
-        name: k6-trace-generator
+        - env:
+            - name: ENDPOINT
+              value: alloy-traces-lb.grafana-cloud-monitoring.svc.cluster.local:9411
+          image: ghcr.io/grafana/xk6-client-tracing:v0.0.2
+          imagePullPolicy: IfNotPresent
+          name: k6-trace-generator
 ---
 apiVersion: v1
 kind: Service
@@ -784,10 +801,10 @@ metadata:
 spec:
   clusterIP: None
   ports:
-  - name: alloy-traces-otlp-grpc
-    port: 9411
-    protocol: TCP
-    targetPort: 9411
+    - name: alloy-traces-otlp-grpc
+      port: 9411
+      protocol: TCP
+      targetPort: 9411
   selector:
     name: alloy-traces-lb
   type: ClusterIP
@@ -810,26 +827,26 @@ spec:
         name: alloy-traces-lb
     spec:
       containers:
-      - args:
-        - run
-        - /etc/alloy/alloy_lb.alloy
-        command:
-        - /bin/alloy
-        image: grafana/alloy:v1.0
-        imagePullPolicy: IfNotPresent
-        name: alloy-traces
-        ports:
-        - containerPort: 9411
-          name: otlp-grpc
-          protocol: TCP
-        volumeMounts:
-        - mountPath: /etc/alloy
+        - args:
+            - run
+            - /etc/alloy/alloy_lb.alloy
+          command:
+            - /bin/alloy
+          image: grafana/alloy:v1.0
+          imagePullPolicy: IfNotPresent
           name: alloy-traces
+          ports:
+            - containerPort: 9411
+              name: otlp-grpc
+              protocol: TCP
+          volumeMounts:
+            - mountPath: /etc/alloy
+              name: alloy-traces
       serviceAccount: alloy-traces
       volumes:
-      - configMap:
+        - configMap:
+            name: alloy-traces
           name: alloy-traces
-        name: alloy-traces
 ---
 apiVersion: v1
 kind: Service
@@ -838,10 +855,10 @@ metadata:
   namespace: grafana-cloud-monitoring
 spec:
   ports:
-  - name: alloy-lb
-    port: 34621
-    protocol: TCP
-    targetPort: alloy-lb
+    - name: alloy-lb
+      port: 34621
+      protocol: TCP
+      targetPort: alloy-lb
   selector:
     name: alloy-traces-sampling
   type: ClusterIP
@@ -864,25 +881,25 @@ spec:
         name: alloy-traces-sampling
     spec:
       containers:
-      - args:
-        - run
-        - /etc/alloy/alloy_sampling.alloy
-        command:
-        - /bin/alloy
-        image: grafana/alloy:v1.0
-        imagePullPolicy: IfNotPresent
-        name: alloy-traces
-        ports:
-        - containerPort: 34621
-          name: alloy-lb
-          protocol: TCP
-        volumeMounts:
-        - mountPath: /etc/alloy
+        - args:
+            - run
+            - /etc/alloy/alloy_sampling.alloy
+          command:
+            - /bin/alloy
+          image: grafana/alloy:v1.0
+          imagePullPolicy: IfNotPresent
           name: alloy-traces
+          ports:
+            - containerPort: 34621
+              name: alloy-lb
+              protocol: TCP
+          volumeMounts:
+            - mountPath: /etc/alloy
+              name: alloy-traces
       volumes:
-      - configMap:
+        - configMap:
+            name: alloy-traces
           name: alloy-traces
-        name: alloy-traces
 ---
 apiVersion: v1
 kind: ConfigMap
diff --git a/docs/sources/reference/components/otelcol/otelcol.exporter.loki.md b/docs/sources/reference/components/otelcol/otelcol.exporter.loki.md
index 9097c01f69..69edfaf6c5 100644
--- a/docs/sources/reference/components/otelcol/otelcol.exporter.loki.md
+++ b/docs/sources/reference/components/otelcol/otelcol.exporter.loki.md
@@ -18,9 +18,10 @@ to `loki` components.
 
 The attributes of the OTLP log are not converted to Loki attributes by default.
 To convert them, the OTLP log should contain special "hint" attributes:
-* To convert OTLP resource attributes to Loki labels,
+
+- To convert OTLP resource attributes to Loki labels,
   use the `loki.resource.labels` hint attribute.
-* To convert OTLP log attributes to Loki labels,
+- To convert OTLP log attributes to Loki labels,
   use the `loki.attribute.labels` hint attribute.
 
 Labels will be translated to a [Prometheus format][], which is more constrained than the OTLP format.
@@ -42,17 +43,17 @@ otelcol.exporter.loki "LABEL" {
 
 `otelcol.exporter.loki` supports the following arguments:
 
-Name         | Type             | Description                           | Default | Required
--------------|------------------|---------------------------------------|---------|---------
-`forward_to` | `list(receiver)` | Where to forward converted Loki logs. |         | yes
+| Name         | Type             | Description                           | Default | Required |
+| ------------ | ---------------- | ------------------------------------- | ------- | -------- |
+| `forward_to` | `list(receiver)` | Where to forward converted Loki logs. |         | yes      |
 
 ## Exported fields
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for logs. Other telemetry signals are ignored.
 
@@ -99,13 +100,14 @@ loki.write "local" {
 ### Converting OTLP attributes to Loki labels
 
 The example below will convert the following attributes to Loki labels:
-* The `service.name` and `service.namespace` OTLP resource attributes.
-* The `event.domain` and `event.name` OTLP log attributes.
+
+- The `service.name` and `service.namespace` OTLP resource attributes.
+- The `event.domain` and `event.name` OTLP log attributes.
 
 Labels will be translated to a [Prometheus format][]. For example:
 
 | OpenTelemetry Attribute | Prometheus Label                                      |
-|-------------------------|-------------------------------------------------------|
+| ----------------------- | ----------------------------------------------------- |
 | `name`                  | `name`                                                |
 | `host.name`             | `host_name`                                           |
 | `host_name`             | `host_name`                                           |
diff --git a/docs/sources/reference/components/otelcol/otelcol.exporter.otlp.md b/docs/sources/reference/components/otelcol/otelcol.exporter.otlp.md
index d956b453a4..8a74fe7702 100644
--- a/docs/sources/reference/components/otelcol/otelcol.exporter.otlp.md
+++ b/docs/sources/reference/components/otelcol/otelcol.exporter.otlp.md
@@ -32,23 +32,23 @@ otelcol.exporter.otlp "LABEL" {
 
 `otelcol.exporter.otlp` supports the following arguments:
 
-Name      | Type       | Description                                      | Default | Required
-----------|------------|--------------------------------------------------|---------|---------
-`timeout` | `duration` | Time to wait before marking a request as failed. | `"5s"`  | no
+| Name      | Type       | Description                                      | Default | Required |
+| --------- | ---------- | ------------------------------------------------ | ------- | -------- |
+| `timeout` | `duration` | Time to wait before marking a request as failed. | `"5s"`  | no       |
 
 ## Blocks
 
 The following blocks are supported inside the definition of
 `otelcol.exporter.otlp`:
 
-Hierarchy          | Block                | Description                                                                | Required
--------------------|----------------------|----------------------------------------------------------------------------|---------
-client             | [client][]           | Configures the gRPC server to send telemetry data to.                      | yes
-client > tls       | [tls][]              | Configures TLS for the gRPC client.                                        | no
-client > keepalive | [keepalive][]        | Configures keepalive settings for the gRPC client.                         | no
-sending_queue      | [sending_queue][]    | Configures batching of data before sending.                                | no
-retry_on_failure   | [retry_on_failure][] | Configures retry mechanism for failed requests.                            | no
-debug_metrics      | [debug_metrics][]    | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy          | Block                | Description                                                                | Required |
+| ------------------ | -------------------- | -------------------------------------------------------------------------- | -------- |
+| client             | [client][]           | Configures the gRPC server to send telemetry data to.                      | yes      |
+| client > tls       | [tls][]              | Configures TLS for the gRPC client.                                        | no       |
+| client > keepalive | [keepalive][]        | Configures keepalive settings for the gRPC client.                         | no       |
+| sending_queue      | [sending_queue][]    | Configures batching of data before sending.                                | no       |
+| retry_on_failure   | [retry_on_failure][] | Configures retry mechanism for failed requests.                            | no       |
+| debug_metrics      | [debug_metrics][]    | Configures the metrics that this component generates to monitor its state. | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `client > tls`
 refers to a `tls` block defined inside a `client` block.
@@ -66,17 +66,17 @@ The `client` block configures the gRPC client used by the component.
 
 The following arguments are supported:
 
-Name                | Type                       | Description                                                                      | Default       | Required
---------------------|----------------------------|----------------------------------------------------------------------------------|---------------|---------
-`endpoint`          | `string`                   | `host:port` to send telemetry data to.                                           |               | yes
-`compression`       | `string`                   | Compression mechanism to use for requests.                                       | `"gzip"`      | no
-`read_buffer_size`  | `string`                   | Size of the read buffer the gRPC client to use for reading server responses.     |               | no
-`write_buffer_size` | `string`                   | Size of the write buffer the gRPC client to use for writing requests.            | `"512KiB"`    | no
-`wait_for_ready`    | `boolean`                  | Waits for gRPC connection to be in the `READY` state before sending data.        | `false`       | no
-`headers`           | `map(string)`              | Additional headers to send with the request.                                     | `{}`          | no
-`balancer_name`     | `string`                   | Which gRPC client-side load balancer to use for requests.                        | `round_robin` | no
-`authority`         | `string`                   | Overrides the default `:authority` header in gRPC requests from the gRPC client. |               | no
-`auth`              | `capsule(otelcol.Handler)` | Handler from an `otelcol.auth` component to use for authenticating requests.     |               | no
+| Name                | Type                       | Description                                                                      | Default       | Required |
+| ------------------- | -------------------------- | -------------------------------------------------------------------------------- | ------------- | -------- |
+| `endpoint`          | `string`                   | `host:port` to send telemetry data to.                                           |               | yes      |
+| `compression`       | `string`                   | Compression mechanism to use for requests.                                       | `"gzip"`      | no       |
+| `read_buffer_size`  | `string`                   | Size of the read buffer the gRPC client to use for reading server responses.     |               | no       |
+| `write_buffer_size` | `string`                   | Size of the write buffer the gRPC client to use for writing requests.            | `"512KiB"`    | no       |
+| `wait_for_ready`    | `boolean`                  | Waits for gRPC connection to be in the `READY` state before sending data.        | `false`       | no       |
+| `headers`           | `map(string)`              | Additional headers to send with the request.                                     | `{}`          | no       |
+| `balancer_name`     | `string`                   | Which gRPC client-side load balancer to use for requests.                        | `round_robin` | no       |
+| `authority`         | `string`                   | Overrides the default `:authority` header in gRPC requests from the gRPC client. |               | no       |
+| `auth`              | `capsule(otelcol.Handler)` | Handler from an `otelcol.auth` component to use for authenticating requests.     |               | no       |
 
 {{< docs/shared lookup="reference/components/otelcol-compression-field.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -86,8 +86,8 @@ Name                | Type                       | Description
 
 An HTTP proxy can be configured through the following environment variables:
 
-* `HTTPS_PROXY`
-* `NO_PROXY`
+- `HTTPS_PROXY`
+- `NO_PROXY`
 
 The `HTTPS_PROXY` environment variable specifies a URL to use for proxying
 requests. Connections to the proxy are established via [the `HTTP CONNECT`
@@ -118,6 +118,7 @@ server.
 Sending sensitive credentials over insecure non-TLS connections is supported by non-gRPC exporters such as [otelcol.exporter.otlphttp][].
 
 [otelcol.exporter.otlphttp]: ../otelcol.exporter.otlphttp/
+
 {{< /admonition >}}
 
 ### keepalive block
@@ -126,11 +127,11 @@ The `keepalive` block configures keepalive settings for gRPC client connections.
 
 The following arguments are supported:
 
-Name                    | Type       | Description                                                                                | Default | Required
-------------------------|------------|--------------------------------------------------------------------------------------------|---------|---------
-`ping_wait`             | `duration` | How often to ping the server after no activity.                                            |         | no
-`ping_response_timeout` | `duration` | Time to wait before closing inactive connections if the server does not respond to a ping. |         | no
-`ping_without_stream`   | `boolean`  | Send pings even if there is no active stream request.                                      |         | no
+| Name                    | Type       | Description                                                                                | Default | Required |
+| ----------------------- | ---------- | ------------------------------------------------------------------------------------------ | ------- | -------- |
+| `ping_wait`             | `duration` | How often to ping the server after no activity.                                            |         | no       |
+| `ping_response_timeout` | `duration` | Time to wait before closing inactive connections if the server does not respond to a ping. |         | no       |
+| `ping_without_stream`   | `boolean`  | Send pings even if there is no active stream request.                                      |         | no       |
 
 ### sending_queue block
 
@@ -153,9 +154,9 @@ The `retry_on_failure` block configures how failed requests to the gRPC server a
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics,
 logs, or traces).
@@ -172,15 +173,15 @@ information.
 
 ## Debug metrics
 
-* `otelcol_exporter_sent_spans_total` (counter): Number of spans successfully sent to destination.
-* `otelcol_exporter_send_failed_spans_total` (counter): Number of spans in failed attempts to send to destination.
-* `otelcol_exporter_queue_capacity` (gauge): Fixed capacity of the retry queue (in batches)
-* `otelcol_exporter_queue_size` (gauge): Current size of the retry queue (in batches)
-* `rpc_client_duration_milliseconds` (histogram): Measures the duration of inbound RPC.
-* `rpc_client_request_size_bytes` (histogram): Measures size of RPC request messages (uncompressed).
-* `rpc_client_requests_per_rpc` (histogram): Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs.
-* `rpc_client_response_size_bytes` (histogram): Measures size of RPC response messages (uncompressed).
-* `rpc_client_responses_per_rpc` (histogram): Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs.
+- `otelcol_exporter_sent_spans_total` (counter): Number of spans successfully sent to destination.
+- `otelcol_exporter_send_failed_spans_total` (counter): Number of spans in failed attempts to send to destination.
+- `otelcol_exporter_queue_capacity` (gauge): Fixed capacity of the retry queue (in batches)
+- `otelcol_exporter_queue_size` (gauge): Current size of the retry queue (in batches)
+- `rpc_client_duration_milliseconds` (histogram): Measures the duration of inbound RPC.
+- `rpc_client_request_size_bytes` (histogram): Measures size of RPC request messages (uncompressed).
+- `rpc_client_requests_per_rpc` (histogram): Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs.
+- `rpc_client_response_size_bytes` (histogram): Measures size of RPC response messages (uncompressed).
+- `rpc_client_responses_per_rpc` (histogram): Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs.
 
 ## Examples
 
@@ -218,6 +219,7 @@ otelcol.auth.basic "grafana_cloud_traces" {
     password = sys.env("GRAFANA_CLOUD_API_KEY")
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/otelcol/otelcol.exporter.otlphttp.md b/docs/sources/reference/components/otelcol/otelcol.exporter.otlphttp.md
index c6dd0c857a..dae3702be0 100644
--- a/docs/sources/reference/components/otelcol/otelcol.exporter.otlphttp.md
+++ b/docs/sources/reference/components/otelcol/otelcol.exporter.otlphttp.md
@@ -31,12 +31,12 @@ otelcol.exporter.otlphttp "LABEL" {
 
 `otelcol.exporter.otlphttp` supports the following arguments:
 
-Name               | Type     | Description                                                               | Default                           | Required
--------------------|----------|---------------------------------------------------------------------------|-----------------------------------|---------
-`metrics_endpoint` | `string` | The endpoint to send metrics to.                                          | `client.endpoint + "/v1/metrics"` | no
-`logs_endpoint`    | `string` | The endpoint to send logs to.                                             | `client.endpoint + "/v1/logs"`    | no
-`traces_endpoint`  | `string` | The endpoint to send traces to.                                           | `client.endpoint + "/v1/traces"`  | no
-`encoding`         | `string` | The encoding to use for messages. Should be either `"proto"` or `"json"`. | `"proto"`                         | no
+| Name               | Type     | Description                                                               | Default                           | Required |
+| ------------------ | -------- | ------------------------------------------------------------------------- | --------------------------------- | -------- |
+| `metrics_endpoint` | `string` | The endpoint to send metrics to.                                          | `client.endpoint + "/v1/metrics"` | no       |
+| `logs_endpoint`    | `string` | The endpoint to send logs to.                                             | `client.endpoint + "/v1/logs"`    | no       |
+| `traces_endpoint`  | `string` | The endpoint to send traces to.                                           | `client.endpoint + "/v1/traces"`  | no       |
+| `encoding`         | `string` | The encoding to use for messages. Should be either `"proto"` or `"json"`. | `"proto"`                         | no       |
 
 The default value depends on the `endpoint` field set in the required `client` block.
 If set, these arguments override the `client.endpoint` field for the corresponding signal.
@@ -45,14 +45,14 @@ If set, these arguments override the `client.endpoint` field for the correspondi
 
 The following blocks are supported inside the definition of `otelcol.exporter.otlphttp`:
 
-Hierarchy        | Block                | Description                                                                | Required
------------------|----------------------|----------------------------------------------------------------------------|---------
-client           | [client][]           | Configures the HTTP server to send telemetry data to.                      | yes
-client > tls     | [tls][]              | Configures TLS for the HTTP client.                                        | no
-client > cookies | [cookies][]          | Store cookies from server responses and reuse them in subsequent requests. | no
-sending_queue    | [sending_queue][]    | Configures batching of data before sending.                                | no
-retry_on_failure | [retry_on_failure][] | Configures retry mechanism for failed requests.                            | no
-debug_metrics    | [debug_metrics][]    | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy        | Block                | Description                                                                | Required |
+| ---------------- | -------------------- | -------------------------------------------------------------------------- | -------- |
+| client           | [client][]           | Configures the HTTP server to send telemetry data to.                      | yes      |
+| client > tls     | [tls][]              | Configures TLS for the HTTP client.                                        | no       |
+| client > cookies | [cookies][]          | Store cookies from server responses and reuse them in subsequent requests. | no       |
+| sending_queue    | [sending_queue][]    | Configures batching of data before sending.                                | no       |
+| retry_on_failure | [retry_on_failure][] | Configures retry mechanism for failed requests.                            | no       |
+| debug_metrics    | [debug_metrics][]    | Configures the metrics that this component generates to monitor its state. | no       |
 
 The `>` symbol indicates deeper levels of nesting.
 For example, `client > tls` refers to a `tls` block defined inside a `client` block.
@@ -70,27 +70,28 @@ The `client` block configures the HTTP client used by the component.
 
 The following arguments are supported:
 
-Name                      | Type                       | Description                                                                                                        | Default    | Required
---------------------------|----------------------------|--------------------------------------------------------------------------------------------------------------------|------------|---------
-`endpoint`                | `string`                   | The target URL to send telemetry data to.                                                                          |            | yes
-`proxy_url`               | `string`                   | HTTP proxy to send requests through.                                                                               |            |
-`read_buffer_size`        | `string`                   | Size of the read buffer the HTTP client uses for reading server responses.                                         | `0`        | no
-`write_buffer_size`       | `string`                   | Size of the write buffer the HTTP client uses for writing requests.                                                | `"512KiB"` | no
-`timeout`                 | `duration`                 | Time to wait before marking a request as failed.                                                                   | `"30s"`    | no
-`headers`                 | `map(string)`              | Additional headers to send with the request.                                                                       | `{}`       | no
-`compression`             | `string`                   | Compression mechanism to use for requests.                                                                         | `"gzip"`   | no
-`max_idle_conns`          | `int`                      | Limits the number of idle HTTP connections the client can keep open.                                               | `100`      | no
-`max_idle_conns_per_host` | `int`                      | Limits the number of idle HTTP connections the host can keep open.                                                 | `0`        | no
-`max_conns_per_host`      | `int`                      | Limits the total (dialing,active, and idle) number of connections per host.                                        | `0`        | no
-`idle_conn_timeout`       | `duration`                 | Time to wait before an idle connection closes itself.                                                              | `"90s"`    | no
-`disable_keep_alives`     | `bool`                     | Disable HTTP keep-alive.                                                                                           | `false`    | no
-`http2_read_idle_timeout` | `duration`                 | Timeout after which a health check using ping frame will be carried out if no frame is received on the connection. | `0s`       | no
-`http2_ping_timeout`      | `duration`                 | Timeout after which the connection will be closed if a response to Ping isn't received.                            | `15s`      | no
-`auth`                    | `capsule(otelcol.Handler)` | Handler from an `otelcol.auth` component to use for authenticating requests.                                       |            | no
+| Name                      | Type                       | Description                                                                                                        | Default    | Required |
+| ------------------------- | -------------------------- | ------------------------------------------------------------------------------------------------------------------ | ---------- | -------- |
+| `endpoint`                | `string`                   | The target URL to send telemetry data to.                                                                          |            | yes      |
+| `proxy_url`               | `string`                   | HTTP proxy to send requests through.                                                                               |            |
+| `read_buffer_size`        | `string`                   | Size of the read buffer the HTTP client uses for reading server responses.                                         | `0`        | no       |
+| `write_buffer_size`       | `string`                   | Size of the write buffer the HTTP client uses for writing requests.                                                | `"512KiB"` | no       |
+| `timeout`                 | `duration`                 | Time to wait before marking a request as failed.                                                                   | `"30s"`    | no       |
+| `headers`                 | `map(string)`              | Additional headers to send with the request.                                                                       | `{}`       | no       |
+| `compression`             | `string`                   | Compression mechanism to use for requests.                                                                         | `"gzip"`   | no       |
+| `max_idle_conns`          | `int`                      | Limits the number of idle HTTP connections the client can keep open.                                               | `100`      | no       |
+| `max_idle_conns_per_host` | `int`                      | Limits the number of idle HTTP connections the host can keep open.                                                 | `0`        | no       |
+| `max_conns_per_host`      | `int`                      | Limits the total (dialing,active, and idle) number of connections per host.                                        | `0`        | no       |
+| `idle_conn_timeout`       | `duration`                 | Time to wait before an idle connection closes itself.                                                              | `"90s"`    | no       |
+| `disable_keep_alives`     | `bool`                     | Disable HTTP keep-alive.                                                                                           | `false`    | no       |
+| `http2_read_idle_timeout` | `duration`                 | Timeout after which a health check using ping frame will be carried out if no frame is received on the connection. | `0s`       | no       |
+| `http2_ping_timeout`      | `duration`                 | Timeout after which the connection will be closed if a response to Ping isn't received.                            | `15s`      | no       |
+| `auth`                    | `capsule(otelcol.Handler)` | Handler from an `otelcol.auth` component to use for authenticating requests.                                       |            | no       |
 
 When setting `headers`, note that:
-  - Certain headers such as `Content-Length` and `Connection` are automatically written when needed and values in `headers` may be ignored.
-  - The `Host` header is automatically derived from the `endpoint` value. However, this automatic assignment can be overridden by explicitly setting a `Host` header in `headers`.
+
+- Certain headers such as `Content-Length` and `Connection` are automatically written when needed and values in `headers` may be ignored.
+- The `Host` header is automatically derived from the `endpoint` value. However, this automatic assignment can be overridden by explicitly setting a `Host` header in `headers`.
 
 Setting `disable_keep_alives` to `true` will result in significant overhead establishing a new HTTP or HTTPS connection for every request.
 Before enabling this option, consider whether changes to idle connection settings can achieve your goal.
@@ -109,9 +110,9 @@ This could be useful in situations such as load balancers relying on cookies for
 
 The following arguments are supported:
 
-Name      | Type   | Description                               | Default    | Required
-----------|--------|-------------------------------------------|------------|---------
-`enabled` | `bool` | The target URL to send telemetry data to. | `false`    | no
+| Name      | Type   | Description                               | Default | Required |
+| --------- | ------ | ----------------------------------------- | ------- | -------- |
+| `enabled` | `bool` | The target URL to send telemetry data to. | `false` | no       |
 
 ### tls block
 
@@ -139,9 +140,9 @@ The `retry_on_failure` block configures how failed requests to the HTTP server a
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics, logs, or traces).
 
@@ -168,6 +169,7 @@ otelcol.exporter.otlphttp "tempo" {
     }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/otelcol/otelcol.exporter.prometheus.md b/docs/sources/reference/components/otelcol/otelcol.exporter.prometheus.md
index ae29f26d36..05f306999e 100644
--- a/docs/sources/reference/components/otelcol/otelcol.exporter.prometheus.md
+++ b/docs/sources/reference/components/otelcol/otelcol.exporter.prometheus.md
@@ -18,6 +18,7 @@ and forwards the resulting metrics to `prometheus` components.
 Conversion of metrics are done according to the OpenTelemetry [Metrics Data Model][] specification.
 
 [Metrics Data Model]: https://opentelemetry.io/docs/reference/specification/metrics/data-model/
+
 {{< /admonition >}}
 
 Multiple `otelcol.exporter.prometheus` components can be specified by giving them
@@ -35,22 +36,22 @@ otelcol.exporter.prometheus "LABEL" {
 
 `otelcol.exporter.prometheus` supports the following arguments:
 
-Name                               | Type                    | Description                                                       | Default | Required
------------------------------------|-------------------------|-------------------------------------------------------------------|---------|---------
-`include_target_info`              | `boolean`               | Whether to include `target_info` metrics.                         | `true`  | no
-`include_scope_info`               | `boolean`               | Whether to include `otel_scope_info` metrics.                     | `false` | no
-`include_scope_labels`             | `boolean`               | Whether to include additional OTLP labels in all metrics.         | `true`  | no
-`add_metric_suffixes`              | `boolean`               | Whether to add type and unit suffixes to metrics names.           | `true`  | no
-`gc_frequency`                     | `duration`              | How often to clean up stale metrics from memory.                  | `"5m"`  | no
-`forward_to`                       | `list(MetricsReceiver)` | Where to forward converted Prometheus metrics.                    |         | yes
-`resource_to_telemetry_conversion` | `boolean`               | Whether to convert OTel resource attributes to Prometheus labels. | `false` | no
+| Name                               | Type                    | Description                                                       | Default | Required |
+| ---------------------------------- | ----------------------- | ----------------------------------------------------------------- | ------- | -------- |
+| `include_target_info`              | `boolean`               | Whether to include `target_info` metrics.                         | `true`  | no       |
+| `include_scope_info`               | `boolean`               | Whether to include `otel_scope_info` metrics.                     | `false` | no       |
+| `include_scope_labels`             | `boolean`               | Whether to include additional OTLP labels in all metrics.         | `true`  | no       |
+| `add_metric_suffixes`              | `boolean`               | Whether to add type and unit suffixes to metrics names.           | `true`  | no       |
+| `gc_frequency`                     | `duration`              | How often to clean up stale metrics from memory.                  | `"5m"`  | no       |
+| `forward_to`                       | `list(MetricsReceiver)` | Where to forward converted Prometheus metrics.                    |         | yes      |
+| `resource_to_telemetry_conversion` | `boolean`               | Whether to convert OTel resource attributes to Prometheus labels. | `false` | no       |
 
 By default, OpenTelemetry resources are converted into `target_info` metrics.
 OpenTelemetry instrumentation scopes are converted into `otel_scope_info`
 metrics. Set the `include_scope_info` and `include_target_info` arguments to
 `false`, respectively, to disable the custom metrics.
 
-When `include_scope_labels` is `true`  the `otel_scope_name` and
+When `include_scope_labels` is `true` the `otel_scope_name` and
 `otel_scope_version` labels are added to every converted metric sample.
 
 When `include_target_info` is true, OpenTelemetry Collector resources are converted into `target_info` metrics.
@@ -63,6 +64,7 @@ to convert OTLP resource attributes to OTLP metric datapoint attributes before u
 See [Creating Prometheus labels from OTLP resource attributes][] for an example.
 
 [Creating Prometheus labels from OTLP resource attributes]: #creating-prometheus-labels-from-otlp-resource-attributes
+
 {{< /admonition >}}
 
 ## Blocks
@@ -70,9 +72,9 @@ See [Creating Prometheus labels from OTLP resource attributes][] for an example.
 The following blocks are supported inside the definition of
 `otelcol.exporter.prometheus`:
 
-Hierarchy | Block      | Description                          | Required
-----------|------------|--------------------------------------|---------
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [debug_metrics]: #debug_metrics-block
 
@@ -84,9 +86,9 @@ debug_metrics | [debug_metrics][] | Configures the metrics that this component g
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for metrics. Other telemetry signals are ignored.
 
@@ -95,12 +97,13 @@ are forwarded to the `forward_to` argument.
 
 The following are dropped during the conversion process:
 
-* Metrics that use the delta aggregation temporality.
+- Metrics that use the delta aggregation temporality.
   {{< admonition type="note" >}}
   Prometheus does not natively support delta metrics.
   If your {{< param "PRODUCT_NAME" >}} instance ingests delta OTLP metrics, you can convert them to cumulative OTLP metrics with [`otelcol.processor.deltatocumulative`][otelcol.processor.deltatocumulative] before you use `otelcol.exporter.prometheus`.
 
   [otelcol.processor.deltatocumulative]: ../otelcol.processor.deltatocumulative
+
   {{< /admonition >}}
 
 ## Component health
@@ -202,4 +205,4 @@ Connecting some components may not be sensible or components may require further
 Refer to the linked documentation for more details.
 {{< /admonition >}}
 
-<!-- END GENERATED COMPATIBLE COMPONENTS -->
\ No newline at end of file
+<!-- END GENERATED COMPATIBLE COMPONENTS -->
diff --git a/docs/sources/reference/components/otelcol/otelcol.extension.jaeger_remote_sampling.md b/docs/sources/reference/components/otelcol/otelcol.extension.jaeger_remote_sampling.md
index 481789ca7b..11efc01512 100644
--- a/docs/sources/reference/components/otelcol/otelcol.extension.jaeger_remote_sampling.md
+++ b/docs/sources/reference/components/otelcol/otelcol.extension.jaeger_remote_sampling.md
@@ -35,21 +35,21 @@ otelcol.extension.jaeger_remote_sampling "LABEL" {
 The following blocks are supported inside the definition of
 `otelcol.extension.jaeger_remote_sampling`:
 
-Hierarchy                             | Block                  | Description                                                                      | Required
---------------------------------------|------------------------|----------------------------------------------------------------------------------|---------
-http                                  | [http][]               | Configures the http server to serve Jaeger remote sampling.                      | no
-http > tls                            | [tls][]                | Configures TLS for the HTTP server.                                              | no
-http > cors                           | [cors][]               | Configures CORS for the HTTP server.                                             | no
-grpc                                  | [grpc][]               | Configures the grpc server to serve Jaeger remote sampling.                      | no
-grpc > tls                            | [tls][]                | Configures TLS for the gRPC server.                                              | no
-grpc > keepalive                      | [keepalive][]          | Configures keepalive settings for the configured server.                         | no
-grpc > keepalive > server_parameters  | [server_parameters][]  | Server parameters used to configure keepalive settings.                          | no
-grpc > keepalive > enforcement_policy | [enforcement_policy][] | Enforcement policy for keepalive settings.                                       | no
-source                                | [source][]             | Configures the Jaeger remote sampling document.                                  | yes
-source > remote                       | [remote][]             | Configures the gRPC client used to retrieve the Jaeger remote sampling document. | no
-source > remote > tls                 | [tls_client][]                | Configures TLS for the gRPC client.                                              | no
-source > remote > keepalive           | [keepalive][]          | Configures keepalive settings for the gRPC client.                               | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy                             | Block                  | Description                                                                      | Required |
+| ------------------------------------- | ---------------------- | -------------------------------------------------------------------------------- | -------- |
+| http                                  | [http][]               | Configures the http server to serve Jaeger remote sampling.                      | no       |
+| http > tls                            | [tls][]                | Configures TLS for the HTTP server.                                              | no       |
+| http > cors                           | [cors][]               | Configures CORS for the HTTP server.                                             | no       |
+| grpc                                  | [grpc][]               | Configures the grpc server to serve Jaeger remote sampling.                      | no       |
+| grpc > tls                            | [tls][]                | Configures TLS for the gRPC server.                                              | no       |
+| grpc > keepalive                      | [keepalive][]          | Configures keepalive settings for the configured server.                         | no       |
+| grpc > keepalive > server_parameters  | [server_parameters][]  | Server parameters used to configure keepalive settings.                          | no       |
+| grpc > keepalive > enforcement_policy | [enforcement_policy][] | Enforcement policy for keepalive settings.                                       | no       |
+| source                                | [source][]             | Configures the Jaeger remote sampling document.                                  | yes      |
+| source > remote                       | [remote][]             | Configures the gRPC client used to retrieve the Jaeger remote sampling document. | no       |
+| source > remote > tls                 | [tls_client][]         | Configures TLS for the gRPC client.                                              | no       |
+| source > remote > keepalive           | [keepalive][]          | Configures keepalive settings for the gRPC client.                               | no       |
+| debug_metrics                         | [debug_metrics][]      | Configures the metrics that this component generates to monitor its state.       | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `grpc > tls`
 refers to a `tls` block defined inside a `grpc` block.
@@ -73,12 +73,12 @@ The `http` block configures an HTTP server which serves the Jaeger remote sampli
 
 The following arguments are supported:
 
-Name                     | Type           | Description                                                     | Default          | Required
--------------------------|----------------|-----------------------------------------------------------------|------------------|---------
-`endpoint`               | `string`       | `host:port` to listen for traffic on.                           | `"0.0.0.0:5778"` | no
-`max_request_body_size`  | `string`       | Maximum request body size the server will allow.                | `20MiB`          | no
-`include_metadata`       | `boolean`      | Propagate incoming connection metadata to downstream consumers. |                  | no
-`compression_algorithms` | `list(string)` | A list of compression algorithms the server can accept.         | `["", "gzip", "zstd", "zlib", "snappy", "deflate", "lz4"]` | no
+| Name                     | Type           | Description                                                     | Default                                                    | Required |
+| ------------------------ | -------------- | --------------------------------------------------------------- | ---------------------------------------------------------- | -------- |
+| `endpoint`               | `string`       | `host:port` to listen for traffic on.                           | `"0.0.0.0:5778"`                                           | no       |
+| `max_request_body_size`  | `string`       | Maximum request body size the server will allow.                | `20MiB`                                                    | no       |
+| `include_metadata`       | `boolean`      | Propagate incoming connection metadata to downstream consumers. |                                                            | no       |
+| `compression_algorithms` | `list(string)` | A list of compression algorithms the server can accept.         | `["", "gzip", "zstd", "zlib", "snappy", "deflate", "lz4"]` | no       |
 
 ### tls block
 
@@ -93,38 +93,38 @@ The `cors` block configures CORS settings for an HTTP server.
 
 The following arguments are supported:
 
-Name              | Type           | Description                                              | Default                | Required
-------------------|----------------|----------------------------------------------------------|------------------------|---------
-`allowed_origins` | `list(string)` | Allowed values for the `Origin` header.                  |                        | no
-`allowed_headers` | `list(string)` | Accepted headers from CORS requests.                     | `["X-Requested-With"]` | no
-`max_age`         | `number`       | Configures the `Access-Control-Max-Age` response header. |                        | no
+| Name              | Type           | Description                                              | Default                | Required |
+| ----------------- | -------------- | -------------------------------------------------------- | ---------------------- | -------- |
+| `allowed_origins` | `list(string)` | Allowed values for the `Origin` header.                  |                        | no       |
+| `allowed_headers` | `list(string)` | Accepted headers from CORS requests.                     | `["X-Requested-With"]` | no       |
+| `max_age`         | `number`       | Configures the `Access-Control-Max-Age` response header. |                        | no       |
 
 The `allowed_headers` specifies which headers are acceptable from a CORS
 request. The following headers are always implicitly allowed:
 
-* `Accept`
-* `Accept-Language`
-* `Content-Type`
-* `Content-Language`
+- `Accept`
+- `Accept-Language`
+- `Content-Type`
+- `Content-Language`
 
 If `allowed_headers` includes `"*"`, all headers will be permitted.
 
 ### grpc block
 
 The `grpc` block configures a gRPC server which serves the Jaeger remote
- sampling document.
+sampling document.
 
 The following arguments are supported:
 
-Name                     | Type      | Description                                                                | Default           | Required
--------------------------|-----------|----------------------------------------------------------------------------|-------------------|---------
-`endpoint`               | `string`  | `host:port` to listen for traffic on.                                      | `"0.0.0.0:14250"` | no
-`transport`              | `string`  | Transport to use for the gRPC server.                                      | `"tcp"`           | no
-`max_recv_msg_size`      | `string`  | Maximum size of messages the server will accept.                           | `"4MiB"`          | no
-`max_concurrent_streams` | `number`  | Limit the number of concurrent streaming RPC calls.                        |                   | no
-`read_buffer_size`       | `string`  | Size of the read buffer the gRPC server will use for reading from clients. | `"512KiB"`        | no
-`write_buffer_size`      | `string`  | Size of the write buffer the gRPC server will use for writing to clients.  |                   | no
-`include_metadata`       | `boolean` | Propagate incoming connection metadata to downstream consumers.            |                   | no
+| Name                     | Type      | Description                                                                | Default           | Required |
+| ------------------------ | --------- | -------------------------------------------------------------------------- | ----------------- | -------- |
+| `endpoint`               | `string`  | `host:port` to listen for traffic on.                                      | `"0.0.0.0:14250"` | no       |
+| `transport`              | `string`  | Transport to use for the gRPC server.                                      | `"tcp"`           | no       |
+| `max_recv_msg_size`      | `string`  | Maximum size of messages the server will accept.                           | `"4MiB"`          | no       |
+| `max_concurrent_streams` | `number`  | Limit the number of concurrent streaming RPC calls.                        |                   | no       |
+| `read_buffer_size`       | `string`  | Size of the read buffer the gRPC server will use for reading from clients. | `"512KiB"`        | no       |
+| `write_buffer_size`      | `string`  | Size of the write buffer the gRPC server will use for writing to clients.  |                   | no       |
+| `include_metadata`       | `boolean` | Propagate incoming connection metadata to downstream consumers.            |                   | no       |
 
 ### keepalive block
 
@@ -141,13 +141,13 @@ servers.
 
 The following arguments are supported:
 
-Name                       | Type       | Description                                                                          | Default      | Required
----------------------------|------------|--------------------------------------------------------------------------------------|--------------|---------
-`max_connection_idle`      | `duration` | Maximum age for idle connections.                                                    | `"infinity"` | no
-`max_connection_age`       | `duration` | Maximum age for non-idle connections.                                                | `"infinity"` | no
-`max_connection_age_grace` | `duration` | Time to wait before forcibly closing connections.                                    | `"infinity"` | no
-`time`                     | `duration` | How often to ping inactive clients to check for liveness.                            | `"2h"`       | no
-`timeout`                  | `duration` | Time to wait before closing inactive clients that do not respond to liveness checks. | `"20s"`      | no
+| Name                       | Type       | Description                                                                          | Default      | Required |
+| -------------------------- | ---------- | ------------------------------------------------------------------------------------ | ------------ | -------- |
+| `max_connection_idle`      | `duration` | Maximum age for idle connections.                                                    | `"infinity"` | no       |
+| `max_connection_age`       | `duration` | Maximum age for non-idle connections.                                                | `"infinity"` | no       |
+| `max_connection_age_grace` | `duration` | Time to wait before forcibly closing connections.                                    | `"infinity"` | no       |
+| `time`                     | `duration` | How often to ping inactive clients to check for liveness.                            | `"2h"`       | no       |
+| `timeout`                  | `duration` | Time to wait before closing inactive clients that do not respond to liveness checks. | `"20s"`      | no       |
 
 ### enforcement_policy block
 
@@ -157,10 +157,10 @@ configured policy.
 
 The following arguments are supported:
 
-Name                    | Type       | Description                                                             | Default | Required
-------------------------|------------|-------------------------------------------------------------------------|---------|---------
-`min_time`              | `duration` | Minimum time clients should wait before sending a keepalive ping.       | `"5m"`  | no
-`permit_without_stream` | `boolean`  | Allow clients to send keepalive pings when there are no active streams. | `false` | no
+| Name                    | Type       | Description                                                             | Default | Required |
+| ----------------------- | ---------- | ----------------------------------------------------------------------- | ------- | -------- |
+| `min_time`              | `duration` | Minimum time clients should wait before sending a keepalive ping.       | `"5m"`  | no       |
+| `permit_without_stream` | `boolean`  | Allow clients to send keepalive pings when there are no active streams. | `false` | no       |
 
 ### source block
 
@@ -169,11 +169,11 @@ that is served by the servers specified in the `grpc` and `http` blocks.
 
 The following arguments are supported:
 
-Name              | Type       | Description                                                                     | Default | Required
-------------------|------------|---------------------------------------------------------------------------------|---------|---------
-`file`            | `string`   | A local file containing a Jaeger remote sampling document.                      | `""`    | no
-`reload_interval` | `duration` | The interval at which to reload the specified file. Leave at 0 to never reload. | `0`     | no
-`content`         | `string`   | A string containing the Jaeger remote sampling contents directly.               | `""`    | no
+| Name              | Type       | Description                                                                     | Default | Required |
+| ----------------- | ---------- | ------------------------------------------------------------------------------- | ------- | -------- |
+| `file`            | `string`   | A local file containing a Jaeger remote sampling document.                      | `""`    | no       |
+| `reload_interval` | `duration` | The interval at which to reload the specified file. Leave at 0 to never reload. | `0`     | no       |
+| `content`         | `string`   | A string containing the Jaeger remote sampling contents directly.               | `""`    | no       |
 
 Exactly one of the `file` argument, `content` argument or `remote` block must be specified.
 
@@ -183,16 +183,16 @@ The `remote` block configures the gRPC client used by the component.
 
 The following arguments are supported:
 
-Name                | Type                       | Description                                                                      | Default       | Required
---------------------|----------------------------|----------------------------------------------------------------------------------|---------------|---------
-`endpoint`          | `string`                   | `host:port` to send telemetry data to.                                           |               | yes
-`compression`       | `string`                   | Compression mechanism to use for requests.                                       | `"gzip"`      | no
-`read_buffer_size`  | `string`                   | Size of the read buffer the gRPC client to use for reading server responses.     |               | no
-`write_buffer_size` | `string`                   | Size of the write buffer the gRPC client to use for writing requests.            | `"512KiB"`    | no
-`wait_for_ready`    | `boolean`                  | Waits for gRPC connection to be in the `READY` state before sending data.        | `false`       | no
-`headers`           | `map(string)`              | Additional headers to send with the request.                                     | `{}`          | no
-`authority`         | `string`                   | Overrides the default `:authority` header in gRPC requests from the gRPC client. |               | no
-`auth`              | `capsule(otelcol.Handler)` | Handler from an `otelcol.auth` component to use for authenticating requests.     |               | no
+| Name                | Type                       | Description                                                                      | Default    | Required |
+| ------------------- | -------------------------- | -------------------------------------------------------------------------------- | ---------- | -------- |
+| `endpoint`          | `string`                   | `host:port` to send telemetry data to.                                           |            | yes      |
+| `compression`       | `string`                   | Compression mechanism to use for requests.                                       | `"gzip"`   | no       |
+| `read_buffer_size`  | `string`                   | Size of the read buffer the gRPC client to use for reading server responses.     |            | no       |
+| `write_buffer_size` | `string`                   | Size of the write buffer the gRPC client to use for writing requests.            | `"512KiB"` | no       |
+| `wait_for_ready`    | `boolean`                  | Waits for gRPC connection to be in the `READY` state before sending data.        | `false`    | no       |
+| `headers`           | `map(string)`              | Additional headers to send with the request.                                     | `{}`       | no       |
+| `authority`         | `string`                   | Overrides the default `:authority` header in gRPC requests from the gRPC client. |            | no       |
+| `auth`              | `capsule(otelcol.Handler)` | Handler from an `otelcol.auth` component to use for authenticating requests.     |            | no       |
 
 {{< docs/shared lookup="reference/components/otelcol-compression-field.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -202,8 +202,8 @@ Name                | Type                       | Description
 
 An HTTP proxy can be configured through the following environment variables:
 
-* `HTTPS_PROXY`
-* `NO_PROXY`
+- `HTTPS_PROXY`
+- `NO_PROXY`
 
 The `HTTPS_PROXY` environment variable specifies a URL to use for proxying
 requests. Connections to the proxy are established via [the `HTTP CONNECT`
@@ -236,11 +236,11 @@ connections.
 
 The following arguments are supported:
 
-Name                    | Type       | Description                                                                                | Default | Required
-------------------------|------------|--------------------------------------------------------------------------------------------|---------|---------
-`ping_wait`             | `duration` | How often to ping the server after no activity.                                            |         | no
-`ping_response_timeout` | `duration` | Time to wait before closing inactive connections if the server does not respond to a ping. |         | no
-`ping_without_stream`   | `boolean`  | Send pings even if there is no active stream request.                                      |         | no
+| Name                    | Type       | Description                                                                                | Default | Required |
+| ----------------------- | ---------- | ------------------------------------------------------------------------------------------ | ------- | -------- |
+| `ping_wait`             | `duration` | How often to ping the server after no activity.                                            |         | no       |
+| `ping_response_timeout` | `duration` | Time to wait before closing inactive connections if the server does not respond to a ping. |         | no       |
+| `ping_without_stream`   | `boolean`  | Send pings even if there is no active stream request.                                      |         | no       |
 
 ### debug_metrics block
 
@@ -276,7 +276,6 @@ otelcol.extension.jaeger_remote_sampling "example" {
 
 ### Serving from another component
 
-
 This example uses the output of a component to determine what sampling
 rules to serve:
 
diff --git a/docs/sources/reference/components/otelcol/otelcol.processor.attributes.md b/docs/sources/reference/components/otelcol/otelcol.processor.attributes.md
index 62fb97dc97..0138ddbe7c 100644
--- a/docs/sources/reference/components/otelcol/otelcol.processor.attributes.md
+++ b/docs/sources/reference/components/otelcol/otelcol.processor.attributes.md
@@ -40,23 +40,23 @@ otelcol.processor.attributes "LABEL" {
 The following blocks are supported inside the definition of
 `otelcol.processor.attributes`:
 
-Hierarchy              | Block            | Description                                                        | Required
------------------------|------------------|--------------------------------------------------------------------|---------
-output                 | [output][]       | Configures where to send received telemetry data.                  | yes
-action                 | [action][]       | Actions to take on the attributes of incoming metrics/logs/traces. | no
-include                | [include][]      | Filter for data included in this processor's actions.              | no
-include > regexp       | [regexp][]       | Regex cache settings.                                              | no
-include > attribute    | [attribute][]    | A list of attributes to match against.                             | no
-include > resource     | [resource][]     | A list of items to match the resources against.                    | no
-include > library      | [library][]      | A list of items to match the implementation library against.       | no
-include > log_severity | [library][]      | How to match against a log record's SeverityNumber, if defined.    | no
-exclude                | [exclude][]      | Filter for data excluded from this processor's actions             | no
-exclude > regexp       | [regexp][]       | Regex cache settings.                                              | no
-exclude > attribute    | [attribute][]    | A list of attributes to match against.                             | no
-exclude > resource     | [resource][]     | A list of items to match the resources against.                    | no
-exclude > library      | [library][]      | A list of items to match the implementation library against.       | no
-exclude > log_severity | [log_severity][] | How to match against a log record's SeverityNumber, if defined.    | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy              | Block             | Description                                                                | Required |
+| ---------------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| output                 | [output][]        | Configures where to send received telemetry data.                          | yes      |
+| action                 | [action][]        | Actions to take on the attributes of incoming metrics/logs/traces.         | no       |
+| include                | [include][]       | Filter for data included in this processor's actions.                      | no       |
+| include > regexp       | [regexp][]        | Regex cache settings.                                                      | no       |
+| include > attribute    | [attribute][]     | A list of attributes to match against.                                     | no       |
+| include > resource     | [resource][]      | A list of items to match the resources against.                            | no       |
+| include > library      | [library][]       | A list of items to match the implementation library against.               | no       |
+| include > log_severity | [library][]       | How to match against a log record's SeverityNumber, if defined.            | no       |
+| exclude                | [exclude][]       | Filter for data excluded from this processor's actions                     | no       |
+| exclude > regexp       | [regexp][]        | Regex cache settings.                                                      | no       |
+| exclude > attribute    | [attribute][]     | A list of attributes to match against.                                     | no       |
+| exclude > resource     | [resource][]      | A list of items to match the resources against.                            | no       |
+| exclude > library      | [library][]       | A list of items to match the implementation library against.               | no       |
+| exclude > log_severity | [log_severity][]  | How to match against a log record's SeverityNumber, if defined.            | no       |
+| debug_metrics          | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `include > attribute`
 refers to an `attribute` block defined inside an `include` block.
@@ -80,69 +80,69 @@ The `action` block configures how to modify the span, log, or metric.
 
 The following attributes are supported:
 
-Name             | Type     | Description                                                             | Default | Required
------------------|----------|-------------------------------------------------------------------------|---------|---------
-`key`            | `string` | The attribute that the action relates to.                               |         | yes
-`action`         | `string` | The type of action performed.                                           |         | yes
-`value`          | `any`    | The value to populate for the key.                                      |         | no
-`pattern`        | `string` | A regex pattern.                                                        | `""`    | no
-`from_attribute` | `string` | The attribute from the input data used to populate the attribute value. | `""`    | no
-`from_context`   | `string` | The context value used to populate the attribute value.                 | `""`    | no
-`converted_type` | `string` | The type to convert the attribute value to.                             | `""`    | no
+| Name             | Type     | Description                                                             | Default | Required |
+| ---------------- | -------- | ----------------------------------------------------------------------- | ------- | -------- |
+| `key`            | `string` | The attribute that the action relates to.                               |         | yes      |
+| `action`         | `string` | The type of action performed.                                           |         | yes      |
+| `value`          | `any`    | The value to populate for the key.                                      |         | no       |
+| `pattern`        | `string` | A regex pattern.                                                        | `""`    | no       |
+| `from_attribute` | `string` | The attribute from the input data used to populate the attribute value. | `""`    | no       |
+| `from_context`   | `string` | The context value used to populate the attribute value.                 | `""`    | no       |
+| `converted_type` | `string` | The type to convert the attribute value to.                             | `""`    | no       |
 
 The `value` data type must be either a number, string, or boolean.
 
 The supported values for `action` are:
 
-* `insert`: Inserts a new attribute in input data where the key does not already exist.
+- `insert`: Inserts a new attribute in input data where the key does not already exist.
 
-    * The `key` attribute is required. It specifies the attribute to act upon.
-    * One of the `value`, `from_attribute` or `from_context` attributes is required.
+  - The `key` attribute is required. It specifies the attribute to act upon.
+  - One of the `value`, `from_attribute` or `from_context` attributes is required.
 
-* `update`: Updates an attribute in input data where the key does exist.
+- `update`: Updates an attribute in input data where the key does exist.
 
-    * The `key`attribute is required. It specifies the attribute to act upon.
-    * One of the `value`, `from_attribute` or `from_context` attributes is required.
+  - The `key`attribute is required. It specifies the attribute to act upon.
+  - One of the `value`, `from_attribute` or `from_context` attributes is required.
 
-* `upsert`: Either inserts a new attribute in input data where the key does not already exist
-   or updates an attribute in input data where the key does exist.
+- `upsert`: Either inserts a new attribute in input data where the key does not already exist
+  or updates an attribute in input data where the key does exist.
 
-    * The `key`attribute is required. It specifies the attribute to act upon.
-    * One of the `value`, `from_attribute` or `from_context`attributes is required:
-        * `value` specifies the value to populate for the key.
-        * `from_attribute` specifies the attribute from the input data to use to populate
-        the value. If the attribute doesn't exist, no action is performed.
-        * `from_context` specifies the context value used to populate the attribute value.
-        If the key is prefixed with `metadata.`, the values are searched
-        in the receiver's transport protocol for additional information like gRPC Metadata or HTTP Headers.
-        If the key is prefixed with `auth.`, the values are searched
-        in the authentication information set by the server authenticator.
-        Refer to the server authenticator's documentation part of your pipeline
-        for more information about which attributes are available.
-        If the key is `client.address`, the value will be set to the client address.
-        If the key doesn't exist, no action is performed.
-        If the key has multiple values the values will be joined with a `;` separator.
+  - The `key`attribute is required. It specifies the attribute to act upon.
+  - One of the `value`, `from_attribute` or `from_context`attributes is required:
+    - `value` specifies the value to populate for the key.
+    - `from_attribute` specifies the attribute from the input data to use to populate
+      the value. If the attribute doesn't exist, no action is performed.
+    - `from_context` specifies the context value used to populate the attribute value.
+      If the key is prefixed with `metadata.`, the values are searched
+      in the receiver's transport protocol for additional information like gRPC Metadata or HTTP Headers.
+      If the key is prefixed with `auth.`, the values are searched
+      in the authentication information set by the server authenticator.
+      Refer to the server authenticator's documentation part of your pipeline
+      for more information about which attributes are available.
+      If the key is `client.address`, the value will be set to the client address.
+      If the key doesn't exist, no action is performed.
+      If the key has multiple values the values will be joined with a `;` separator.
 
-* `hash`: Hashes (SHA1) an existing attribute value.
+- `hash`: Hashes (SHA1) an existing attribute value.
 
-    * The `key` attribute and/or the `pattern` attributes is required.
+  - The `key` attribute and/or the `pattern` attributes is required.
 
-* `extract`: Extracts values using a regular expression rule from the input key to target keys specified in the rule.
+- `extract`: Extracts values using a regular expression rule from the input key to target keys specified in the rule.
   If a target key already exists, it will be overridden. Note: It behaves similarly to the Span Processor `to_attributes`
   setting with the existing attribute as the source.
 
-    * The `key` attribute is required. It specifies the attribute to extract values from. The value of `key` is NOT altered.
-    * The `pattern` attribute is required. It is the regex pattern used to extract attributes from the value of `key`.
-      The submatchers must be named. If attributes already exist, they will be overwritten.
+  - The `key` attribute is required. It specifies the attribute to extract values from. The value of `key` is NOT altered.
+  - The `pattern` attribute is required. It is the regex pattern used to extract attributes from the value of `key`.
+    The submatchers must be named. If attributes already exist, they will be overwritten.
 
-* `convert`: Converts an existing attribute to a specified type.
+- `convert`: Converts an existing attribute to a specified type.
 
-    * The `key` attribute is required. It specifies the attribute to act upon.
-    * The `converted_type` attribute is required and must be one of int, double or string.
+  - The `key` attribute is required. It specifies the attribute to act upon.
+  - The `converted_type` attribute is required and must be one of int, double or string.
 
-* `delete`: Deletes an attribute from the input data.
+- `delete`: Deletes an attribute from the input data.
 
-    * The `key` attribute and/or the `pattern` attribute is required. It specifies the attribute to act upon.
+  - The `key` attribute and/or the `pattern` attribute is required. It specifies the attribute to act upon.
 
 ### include block
 
@@ -151,11 +151,12 @@ The `include` block provides an option to include data being fed into the [actio
 {{< docs/shared lookup="reference/components/match-properties-block.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
 One of the following is also required:
-* For spans, one of `services`, `span_names`, `span_kinds`, [attribute][], [resource][], or [library][] must be specified
+
+- For spans, one of `services`, `span_names`, `span_kinds`, [attribute][], [resource][], or [library][] must be specified
   with a non-empty value for a valid configuration. The `log_bodies`, `log_severity_texts`, `log_severity`, and `metric_names` attributes are invalid.
-* For logs, one of `log_bodies`, `log_severity_texts`, `log_severity`, [attribute][], [resource][], or [library][] must be
+- For logs, one of `log_bodies`, `log_severity_texts`, `log_severity`, [attribute][], [resource][], or [library][] must be
   specified with a non-empty value for a valid configuration. The `span_names`, `span_kinds`, `metric_names`, and `services` attributes are invalid.
-* For metrics, `metric_names` must be specified with a valid non-empty value for a valid configuration. The `span_names`,
+- For metrics, `metric_names` must be specified with a valid non-empty value for a valid configuration. The `span_names`,
   `span_kinds`, `log_bodies`, `log_severity_texts`, `log_severity`, `services`, [attribute][], [resource][], and [library][] attributes are invalid.
 
 If the configuration includes filters which are specific to a particular signal type, it is best to include only that signal type in the component's output.
@@ -171,16 +172,18 @@ If you would like to not propagate certain signals to downstream components,
 consider a processor such as [otelcol.processor.tail_sampling][].
 
 [otelcol.processor.tail_sampling]: ../otelcol.processor.tail_sampling/
+
 {{< /admonition >}}
 
 {{< docs/shared lookup="reference/components/match-properties-block.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
 One of the following is also required:
-* For spans, one of `services`, `span_names`, `span_kinds`, [attribute][], [resource][], or [library][] must be specified 
+
+- For spans, one of `services`, `span_names`, `span_kinds`, [attribute][], [resource][], or [library][] must be specified
   with a non-empty value for a valid configuration. The `log_bodies`, `log_severity_texts`, `log_severity`, and `metric_names` attributes are invalid.
-* For logs, one of `log_bodies`, `log_severity_texts`, `log_severity`, [attribute][], [resource][], or [library][] must be 
+- For logs, one of `log_bodies`, `log_severity_texts`, `log_severity`, [attribute][], [resource][], or [library][] must be
   specified with a non-empty value for a valid configuration. The `span_names`, `span_kinds`, `metric_names`, and `services` attributes are invalid.
-* For metrics, `metric_names` must be specified with a valid non-empty value for a valid configuration. The `span_names`, 
+- For metrics, `metric_names` must be specified with a valid non-empty value for a valid configuration. The `span_names`,
   `span_kinds`, `log_bodies`, `log_severity_texts`, `log_severity`, `services`, [attribute][], [resource][], and [library][] attributes are invalid.
 
 If the configuration includes filters which are specific to a particular signal type, it is best to include only that signal type in the component's output.
@@ -218,9 +221,9 @@ For example, adding a `span_names` filter could cause the component to error if
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics, logs, or traces).
 
@@ -342,12 +345,14 @@ otelcol.exporter.otlp "default" {
 ### Excluding spans based on attributes
 
 For example, the following spans match the properties and won't be processed by the processor:
-* Span1 Name: "svcB", Attributes: {env: "dev", test_request: 123, credit_card: 1234}
-* Span2 Name: "svcA", Attributes: {env: "dev", test_request: false}
+
+- Span1 Name: "svcB", Attributes: {env: "dev", test_request: 123, credit_card: 1234}
+- Span2 Name: "svcA", Attributes: {env: "dev", test_request: false}
 
 The following spans do not match the properties and the processor actions are applied to it:
-* Span3 Name: "svcB", Attributes: {env: 1, test_request: "dev", credit_card: 1234}
-* Span4 Name: "svcC", Attributes: {env: "dev", test_request: false}
+
+- Span3 Name: "svcB", Attributes: {env: 1, test_request: "dev", credit_card: 1234}
+- Span4 Name: "svcC", Attributes: {env: "dev", test_request: false}
 
 Note that due to the presence of the `services` attribute, this configuration works only for
 trace signals. This is why only traces are configured in the `output` block.
@@ -443,10 +448,10 @@ otelcol.processor.attributes "default" {
 
 ### Including and excluding spans based on regex and services
 
-This processor will remove the "token" attribute and will obfuscate the "password" attribute 
+This processor will remove the "token" attribute and will obfuscate the "password" attribute
 in spans where the service name matches `"auth.*"` and where the span name does not match `"login.*"`.
 
-Note that due to the presence of the `services` and `span_names` attributes, this configuration 
+Note that due to the presence of the `services` and `span_names` attributes, this configuration
 works only for trace signals. This is why only traces are configured in the `output` block.
 
 ```alloy
@@ -492,11 +497,11 @@ matches a regex pattern.
 ```alloy
 otelcol.processor.attributes "default" {
     include {
-        // "match_type" of "regexp" defines that the "value" attributes 
+        // "match_type" of "regexp" defines that the "value" attributes
         // in the "attribute" blocks are regexp-es.
         match_type = "regexp"
 
-        // This attribute ('db.statement') must exist in the span and match 
+        // This attribute ('db.statement') must exist in the span and match
         // the regex ('SELECT \* FROM USERS.*') for a match.
         attribute {
             key = "db.statement"
@@ -521,7 +526,7 @@ otelcol.processor.attributes "default" {
 ### Including spans based on regex of log body
 
 This processor will remove the "token" attribute and will obfuscate the "password"
-attribute in spans where the log body matches "AUTH.*".
+attribute in spans where the log body matches "AUTH.\*".
 
 Note that due to the presence of the `log_bodies` attribute, this configuration works only for
 log signals. This is why only logs are configured in the `output` block.
@@ -551,7 +556,7 @@ otelcol.processor.attributes "default" {
 ### Including spans based on regex of log severity
 
 The following demonstrates how to process logs that have a severity level which is equal to or higher than
-the level specified in the `log_severity` block. This processor will remove the "token" attribute and will 
+the level specified in the `log_severity` block. This processor will remove the "token" attribute and will
 obfuscate the "password" attribute in logs where the severity is at least "INFO".
 
 Note that due to the presence of the `log_severity` attribute, this configuration works only for
@@ -639,6 +644,7 @@ otelcol.processor.attributes "default" {
     }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -656,4 +662,4 @@ Connecting some components may not be sensible or components may require further
 Refer to the linked documentation for more details.
 {{< /admonition >}}
 
-<!-- END GENERATED COMPATIBLE COMPONENTS -->
\ No newline at end of file
+<!-- END GENERATED COMPATIBLE COMPONENTS -->
diff --git a/docs/sources/reference/components/otelcol/otelcol.processor.batch.md b/docs/sources/reference/components/otelcol/otelcol.processor.batch.md
index f6a25dee02..b272978861 100644
--- a/docs/sources/reference/components/otelcol/otelcol.processor.batch.md
+++ b/docs/sources/reference/components/otelcol/otelcol.processor.batch.md
@@ -40,33 +40,35 @@ otelcol.processor.batch "LABEL" {
 
 `otelcol.processor.batch` supports the following arguments:
 
-Name                         | Type           | Description                                                             | Default   | Required
------------------------------|----------------|-------------------------------------------------------------------------|-----------|---------
-`timeout`                    | `duration`     | How long to wait before flushing the batch.                             | `"200ms"` | no
-`send_batch_size`            | `number`       | Amount of data to buffer before flushing the batch.                     | `8192`    | no
-`send_batch_max_size`        | `number`       | Upper limit of a batch size.                                            | `0`       | no
-`metadata_keys`              | `list(string)` | Creates a different batcher for each key/value combination of metadata. | `[]`      | no
-`metadata_cardinality_limit` | `number`       | Limit of the unique metadata key/value combinations.                    | `1000`    | no
+| Name                         | Type           | Description                                                             | Default   | Required |
+| ---------------------------- | -------------- | ----------------------------------------------------------------------- | --------- | -------- |
+| `timeout`                    | `duration`     | How long to wait before flushing the batch.                             | `"200ms"` | no       |
+| `send_batch_size`            | `number`       | Amount of data to buffer before flushing the batch.                     | `8192`    | no       |
+| `send_batch_max_size`        | `number`       | Upper limit of a batch size.                                            | `0`       | no       |
+| `metadata_keys`              | `list(string)` | Creates a different batcher for each key/value combination of metadata. | `[]`      | no       |
+| `metadata_cardinality_limit` | `number`       | Limit of the unique metadata key/value combinations.                    | `1000`    | no       |
 
 `otelcol.processor.batch` accumulates data into a batch until one of the
 following events happens:
 
-* The duration specified by `timeout` elapses since the time the last batch was
+- The duration specified by `timeout` elapses since the time the last batch was
   sent.
 
-* The number of spans, log lines, or metric samples processed is greater than
+- The number of spans, log lines, or metric samples processed is greater than
   or equal to the number specified by `send_batch_size`.
 
 Logs, traces, and metrics are processed independently.
 For example, if `send_batch_size` is set to `1000`:
-* The processor may, at the same time, buffer 1,000 spans,
+
+- The processor may, at the same time, buffer 1,000 spans,
   1,000 log lines, and 1,000 metric samples before flushing them.
-* If there are enough spans for a batch of spans (1,000 or more), but not enough for a
+- If there are enough spans for a batch of spans (1,000 or more), but not enough for a
   batch of metric samples (less than 1,000) then only the spans will be flushed.
 
 Use `send_batch_max_size` to limit the amount of data contained in a single batch:
-* When set to `0`, batches can be any size.
-* When set to a non-zero value, `send_batch_max_size` must be greater than or equal to `send_batch_size`.
+
+- When set to `0`, batches can be any size.
+- When set to a non-zero value, `send_batch_max_size` must be greater than or equal to `send_batch_size`.
   Every batch will contain up to the `send_batch_max_size` number of spans, log lines, or metric samples.
   The excess spans, log lines, or metric samples will not be lost - instead, they will be added to
   the next batch.
@@ -74,9 +76,10 @@ Use `send_batch_max_size` to limit the amount of data contained in a single batc
 For example, assume `send_batch_size` is set to the default `8192` and there
 are currently 8,000 batched spans. If the batch processor receives 8,000 more
 spans at once, its behavior depends on how `send_batch_max_size` is configured:
-* If `send_batch_max_size` is set to `0`, the total batch size would be 16,000
+
+- If `send_batch_max_size` is set to `0`, the total batch size would be 16,000
   which would then be flushed as a single batch.
-* If `send_batch_max_size` is set to `10000`, then the total batch size will be
+- If `send_batch_max_size` is set to `10000`, then the total batch size will be
   10,000 and the remaining 6,000 spans will be flushed in a subsequent batch.
 
 `metadata_cardinality_limit` applies for the lifetime of the process.
@@ -97,10 +100,10 @@ which defaults to 1000 to limit memory impact.
 The following blocks are supported inside the definition of
 `otelcol.processor.batch`:
 
-Hierarchy | Block      | Description                                       | Required
-----------|------------|---------------------------------------------------|---------
-output    | [output][] | Configures where to send received telemetry data. | yes
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| output        | [output][]        | Configures where to send received telemetry data.                          | yes      |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [output]: #output-block
 [debug_metrics]: #debug_metrics-block
@@ -117,9 +120,9 @@ debug_metrics | [debug_metrics][] | Configures the metrics that this component g
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics,
 logs, or traces).
@@ -136,11 +139,11 @@ information.
 
 ## Debug metrics
 
-* `otelcol_processor_batch_batch_send_size_bytes` (histogram): Number of bytes in batch that was sent.
-* `otelcol_processor_batch_batch_send_size` (histogram): Number of units in the batch.
-* `otelcol_processor_batch_metadata_cardinality` (gauge): Number of distinct metadata value combinations being processed.
-* `otelcol_processor_batch_timeout_trigger_send_total` (counter): Number of times the batch was sent due to a timeout trigger.
-* `otelcol_processor_batch_batch_size_trigger_send_total` (counter): Number of times the batch was sent due to a size trigger.
+- `otelcol_processor_batch_batch_send_size_bytes` (histogram): Number of bytes in batch that was sent.
+- `otelcol_processor_batch_batch_send_size` (histogram): Number of units in the batch.
+- `otelcol_processor_batch_metadata_cardinality` (gauge): Number of distinct metadata value combinations being processed.
+- `otelcol_processor_batch_timeout_trigger_send_total` (counter): Number of times the batch was sent due to a timeout trigger.
+- `otelcol_processor_batch_batch_size_trigger_send_total` (counter): Number of times the batch was sent due to a size trigger.
 
 ## Examples
 
diff --git a/docs/sources/reference/components/otelcol/otelcol.processor.deltatocumulative.md b/docs/sources/reference/components/otelcol/otelcol.processor.deltatocumulative.md
index d67850b33b..cbdbcaa086 100644
--- a/docs/sources/reference/components/otelcol/otelcol.processor.deltatocumulative.md
+++ b/docs/sources/reference/components/otelcol/otelcol.processor.deltatocumulative.md
@@ -35,9 +35,9 @@ otelcol.processor.deltatocumulative "LABEL" {
 
 `otelcol.processor.deltatocumulative` supports the following arguments:
 
-| Name          | Type       | Description                                                         | Default       | Required |
-| ------------- | ---------- | ------------------------------------------------------------------- | ------------- | -------- |
-| `max_stale`   | `duration` | How long to wait for a new sample before marking a stream as stale. | `"5m"`        | no       |
+| Name          | Type       | Description                                                         | Default               | Required |
+| ------------- | ---------- | ------------------------------------------------------------------- | --------------------- | -------- |
+| `max_stale`   | `duration` | How long to wait for a new sample before marking a stream as stale. | `"5m"`                | no       |
 | `max_streams` | `number`   | Upper limit of streams to track. Set to `0` to disable.             | `9223372036854775807` | no       |
 
 `otelcol.processor.deltatocumulative` tracks incoming metric streams.
diff --git a/docs/sources/reference/components/otelcol/otelcol.processor.discovery.md b/docs/sources/reference/components/otelcol/otelcol.processor.discovery.md
index 532c7026bf..1ea3247a05 100644
--- a/docs/sources/reference/components/otelcol/otelcol.processor.discovery.md
+++ b/docs/sources/reference/components/otelcol/otelcol.processor.discovery.md
@@ -21,24 +21,27 @@ Multiple `otelcol.processor.discovery` components can be specified by giving the
 {{< admonition type="note" >}}
 It can be difficult to follow [OpenTelemetry semantic conventions][OTEL sem conv] when
 adding resource attributes via `otelcol.processor.discovery`:
-* `discovery.relabel` and most `discovery.*` processes such as `discovery.kubernetes`
+
+- `discovery.relabel` and most `discovery.*` processes such as `discovery.kubernetes`
   can only emit [Prometheus-compatible labels][Prometheus data model].
-* Prometheus labels use underscores (`_`) in labels names, whereas
+- Prometheus labels use underscores (`_`) in labels names, whereas
   [OpenTelemetry semantic conventions][OTEL sem conv] use dots (`.`).
-* Although `otelcol.processor.discovery` is able to work with non-Prometheus labels
+- Although `otelcol.processor.discovery` is able to work with non-Prometheus labels
   such as ones containing dots, the fact that `discovery.*` components are generally
   only compatible with Prometheus naming conventions makes it hard to follow OpenTelemetry
   semantic conventions in `otelcol.processor.discovery`.
 
 If your use case is to add resource attributes which contain Kubernetes metadata, consider using `otelcol.processor.k8sattributes` instead.
 
-------
+---
+
 The main use case for `otelcol.processor.discovery` is for users who migrate to {{< param "PRODUCT_NAME" >}}
 from Grafana Agent Static mode `prom_sd_operation_type`/`prom_sd_pod_associations` [configuration options][Traces].
 
 [Prometheus data model]: https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels
 [OTEL sem conv]: https://github.com/open-telemetry/semantic-conventions/blob/main/docs/README.md
 [Traces]: https://grafana.com/docs/agent/latest/static/configuration/traces-config/
+
 {{< /admonition >}}
 
 ## Usage
@@ -56,30 +59,33 @@ otelcol.processor.discovery "LABEL" {
 
 `otelcol.processor.discovery` supports the following arguments:
 
-Name               | Type                | Description                                                           | Default                                                         | Required
--------------------|---------------------|-----------------------------------------------------------------------|-----------------------------------------------------------------|---------
-`targets`          | `list(map(string))` | List of target labels to apply to the spans.                          |                                                                 | yes
-`operation_type`   | `string`            | Configures whether to update a span's attribute if it already exists. | `upsert`                                                        | no
-`pod_associations` | `list(string)`      | Configures how to decide the hostname of the span.                    | `["ip", "net.host.ip", "k8s.pod.ip", "hostname", "connection"]` | no
+| Name               | Type                | Description                                                           | Default                                                         | Required |
+| ------------------ | ------------------- | --------------------------------------------------------------------- | --------------------------------------------------------------- | -------- |
+| `targets`          | `list(map(string))` | List of target labels to apply to the spans.                          |                                                                 | yes      |
+| `operation_type`   | `string`            | Configures whether to update a span's attribute if it already exists. | `upsert`                                                        | no       |
+| `pod_associations` | `list(string)`      | Configures how to decide the hostname of the span.                    | `["ip", "net.host.ip", "k8s.pod.ip", "hostname", "connection"]` | no       |
 
 `targets` could come from `discovery.*` components:
+
 1. The `__address__` label will be matched against the IP address of incoming spans.
-   * If `__address__` contains a port, it is ignored.
+   - If `__address__` contains a port, it is ignored.
 2. If a match is found, then relabeling rules are applied.
-   * Note that labels starting with `__` will not be added to the spans.
+   - Note that labels starting with `__` will not be added to the spans.
 
 The supported values for `operation_type` are:
-* `insert`: Inserts a new resource attribute if the key does not already exist.
-* `update`: Updates a resource attribute if the key already exists.
-* `upsert`: Either inserts a new resource attribute if the key does not already exist,
-   or updates a resource attribute if the key does exist.
+
+- `insert`: Inserts a new resource attribute if the key does not already exist.
+- `update`: Updates a resource attribute if the key already exists.
+- `upsert`: Either inserts a new resource attribute if the key does not already exist,
+  or updates a resource attribute if the key does exist.
 
 The supported values for `pod_associations` are:
-* `ip`: The hostname will be sourced from an `ip` resource attribute.
-* `net.host.ip`: The hostname will be sourced from a `net.host.ip` resource attribute.
-* `k8s.pod.ip`: The hostname will be sourced from a `k8s.pod.ip` resource attribute.
-* `hostname`: The hostname will be sourced from a `host.name` resource attribute.
-* `connection`: The hostname will be sourced from the context from the incoming requests (gRPC and HTTP).
+
+- `ip`: The hostname will be sourced from an `ip` resource attribute.
+- `net.host.ip`: The hostname will be sourced from a `net.host.ip` resource attribute.
+- `k8s.pod.ip`: The hostname will be sourced from a `k8s.pod.ip` resource attribute.
+- `hostname`: The hostname will be sourced from a `host.name` resource attribute.
+- `connection`: The hostname will be sourced from the context from the incoming requests (gRPC and HTTP).
 
 If multiple `pod_associations` methods are enabled, the order of evaluation is honored.
 For example, when `pod_associations` is `["ip", "net.host.ip"]`, `"net.host.ip"` may be matched
@@ -90,9 +96,9 @@ only if `"ip"` hasn't already matched.
 The following blocks are supported inside the definition of
 `otelcol.processor.discovery`:
 
-Hierarchy | Block      | Description                                       | Required
-----------|------------|---------------------------------------------------|---------
-output    | [output][] | Configures where to send received telemetry data. | yes
+| Hierarchy | Block      | Description                                       | Required |
+| --------- | ---------- | ------------------------------------------------- | -------- |
+| output    | [output][] | Configures where to send received telemetry data. | yes      |
 
 [output]: #output-block
 
@@ -104,12 +110,13 @@ output    | [output][] | Configures where to send received telemetry data. | yes
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` OTLP-formatted data for telemetry signals of these types:
-* traces
+
+- traces
 
 ## Component health
 
@@ -124,6 +131,7 @@ information.
 ## Examples
 
 ### Basic usage
+
 ```alloy
 discovery.http "dynamic_targets" {
     url              = "https://example.com/scrape_targets"
diff --git a/docs/sources/reference/components/otelcol/otelcol.processor.filter.md b/docs/sources/reference/components/otelcol/otelcol.processor.filter.md
index e376f6bea1..d9eee9de39 100644
--- a/docs/sources/reference/components/otelcol/otelcol.processor.filter.md
+++ b/docs/sources/reference/components/otelcol/otelcol.processor.filter.md
@@ -14,22 +14,25 @@ If any of the OTTL statements evaluates to true, the telemetry data is dropped.
 
 OTTL statements consist of [OTTL Converter functions][], which act on paths.
 A path is a reference to a telemetry data such as:
-* Resource attributes.
-* Instrumentation scope name.
-* Span attributes.
+
+- Resource attributes.
+- Instrumentation scope name.
+- Span attributes.
 
 In addition to the [standard OTTL Converter functions][OTTL Converter functions], the following metrics-only functions are used exclusively by the processor:
-* [HasAttrKeyOnDataPoint][]
-* [HasAttrOnDataPoint][]
+
+- [HasAttrKeyOnDataPoint][]
+- [HasAttrOnDataPoint][]
 
 [OTTL][] statements used in `otelcol.processor.filter` mostly contain constructs such as:
-* [Booleans][OTTL booleans]:
-  * `not true`
-  * `not IsMatch(name, "http_.*")`
-* [Math expressions][OTTL math expressions]:
-  * `1 + 1`
-  * `end_time_unix_nano - start_time_unix_nano`
-  * `sum([1, 2, 3, 4]) + (10 / 1) - 1`
+
+- [Booleans][OTTL booleans]:
+  - `not true`
+  - `not IsMatch(name, "http_.*")`
+- [Math expressions][OTTL math expressions]:
+  - `1 + 1`
+  - `end_time_unix_nano - start_time_unix_nano`
+  - `sum([1, 2, 3, 4]) + (10 / 1) - 1`
 
 {{< admonition type="note" >}}
 Raw {{< param "PRODUCT_NAME" >}} syntax strings can be used to write OTTL statements.
@@ -53,6 +56,7 @@ Exercise caution when using `otelcol.processor.filter`:
   if the log references the dropped span.
 
 [Orphaned Telemetry]: https://github.com/open-telemetry/opentelemetry-collector/blob/v0.85.0/docs/standard-warnings.md#orphaned-telemetry
+
 {{< /admonition >}}
 
 ## Usage
@@ -71,27 +75,28 @@ otelcol.processor.filter "LABEL" {
 
 `otelcol.processor.filter` supports the following arguments:
 
-Name         | Type     | Description                                                        | Default       | Required
------------- | -------- | ------------------------------------------------------------------ | ------------- | --------
-`error_mode` | `string` | How to react to errors if they occur while processing a statement. | `"propagate"` | no
+| Name         | Type     | Description                                                        | Default       | Required |
+| ------------ | -------- | ------------------------------------------------------------------ | ------------- | -------- |
+| `error_mode` | `string` | How to react to errors if they occur while processing a statement. | `"propagate"` | no       |
 
 The supported values for `error_mode` are:
-* `ignore`: Ignore errors returned by conditions, log them, and continue on to the next condition. This is the recommended mode.
-* `silent`: Ignore errors returned by conditions, do not log them, and continue on to the next condition.
-* `propagate`: Return the error up the pipeline. This will result in the payload being dropped from {{< param "PRODUCT_NAME" >}}.
+
+- `ignore`: Ignore errors returned by conditions, log them, and continue on to the next condition. This is the recommended mode.
+- `silent`: Ignore errors returned by conditions, do not log them, and continue on to the next condition.
+- `propagate`: Return the error up the pipeline. This will result in the payload being dropped from {{< param "PRODUCT_NAME" >}}.
 
 ## Blocks
 
 The following blocks are supported inside the definition of
 `otelcol.processor.filter`:
 
-Hierarchy | Block       | Description                                       | Required
---------- | ----------- | ------------------------------------------------- | --------
-traces    | [traces][]  | Statements which filter traces.                   | no
-metrics   | [metrics][] | Statements which filter metrics.                  | no
-logs      | [logs][]    | Statements which filter logs.                     | no
-output    | [output][]  | Configures where to send received telemetry data. | yes
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| traces        | [traces][]        | Statements which filter traces.                                            | no       |
+| metrics       | [metrics][]       | Statements which filter metrics.                                           | no       |
+| logs          | [logs][]          | Statements which filter logs.                                              | no       |
+| output        | [output][]        | Configures where to send received telemetry data.                          | yes      |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [traces]: #traces-block
 [metrics]: #metrics-block
@@ -99,22 +104,23 @@ debug_metrics | [debug_metrics][] | Configures the metrics that this component g
 [output]: #output-block
 [debug_metrics]: #debug_metrics-block
 
-
 ### traces block
 
 The `traces` block specifies statements that filter trace telemetry signals.
 Only one `traces` block can be specified.
 
-Name        | Type           | Description                                         | Default | Required
------------ | -------------- | --------------------------------------------------- | ------- | --------
-`span`      | `list(string)` | List of OTTL statements filtering OTLP spans.       |         | no
-`spanevent` | `list(string)` | List of OTTL statements filtering OTLP span events. |         | no
+| Name        | Type           | Description                                         | Default | Required |
+| ----------- | -------------- | --------------------------------------------------- | ------- | -------- |
+| `span`      | `list(string)` | List of OTTL statements filtering OTLP spans.       |         | no       |
+| `spanevent` | `list(string)` | List of OTTL statements filtering OTLP span events. |         | no       |
 
 The syntax of OTTL statements depends on the OTTL context. See the OpenTelemetry documentation for more information:
-* [OTTL span context][]
-* [OTTL spanevent context][]
+
+- [OTTL span context][]
+- [OTTL spanevent context][]
 
 Statements are checked in order from "high level" to "low level" telemetry, in this order:
+
 1. `span`
 2. `spanevent`
 
@@ -128,16 +134,18 @@ If all span events for a span are dropped, the span will be left intact.
 The `metrics` block specifies statements that filter metric telemetry signals.
 Only one `metrics` blocks can be specified.
 
-Name        | Type           | Description                                               | Default | Required
------------ | -------------- | --------------------------------------------------------- | ------- | --------
-`metric`    | `list(string)` | List of OTTL statements filtering OTLP metric.            |         | no
-`datapoint` | `list(string)` | List of OTTL statements filtering OTLP metric datapoints. |         | no
+| Name        | Type           | Description                                               | Default | Required |
+| ----------- | -------------- | --------------------------------------------------------- | ------- | -------- |
+| `metric`    | `list(string)` | List of OTTL statements filtering OTLP metric.            |         | no       |
+| `datapoint` | `list(string)` | List of OTTL statements filtering OTLP metric datapoints. |         | no       |
 
 The syntax of OTTL statements depends on the OTTL context. See the OpenTelemetry documentation for more information:
-* [OTTL metric context][]
-* [OTTL datapoint context][]
+
+- [OTTL metric context][]
+- [OTTL datapoint context][]
 
 Statements are checked in order from "high level" to "low level" telemetry, in this order:
+
 1. `metric`
 2. `datapoint`
 
@@ -151,12 +159,13 @@ If all datapoints for a metric are dropped, the metric will also be dropped.
 The `logs` block specifies statements that filter log telemetry signals.
 Only `logs` blocks can be specified.
 
-Name            | Type           | Description                                    | Default | Required
---------------- | -------------- | ---------------------------------------------- | ------- | --------
-`log_record`    | `list(string)` | List of OTTL statements filtering OTLP metric. |         | no
+| Name         | Type           | Description                                    | Default | Required |
+| ------------ | -------------- | ---------------------------------------------- | ------- | -------- |
+| `log_record` | `list(string)` | List of OTTL statements filtering OTLP metric. |         | no       |
 
 The syntax of OTTL statements depends on the OTTL context. See the OpenTelemetry documentation for more information:
-* [OTTL log context][]
+
+- [OTTL log context][]
 
 Only one of the statements inside the list of statements has to be satisfied.
 
@@ -172,9 +181,9 @@ Only one of the statements inside the list of statements has to be satisfied.
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics,
 logs, or traces).
@@ -220,8 +229,9 @@ otelcol.processor.filter "default" {
 ### Drop metrics based on either of two criteria
 
 This example drops metrics which satisfy at least one of two OTTL statements:
-* The metric name is `my.metric` and there is a `my_label` resource attribute with a value of `abc123 `.
-* The metric is a histogram.
+
+- The metric name is `my.metric` and there is a `my_label` resource attribute with a value of `abc123 `.
+- The metric is a histogram.
 
 ```alloy
 otelcol.processor.filter "default" {
@@ -270,8 +280,6 @@ otelcol.processor.filter "default" {
 ```
 
 [escaped]: ../../../../get-started/configuration-syntax/expressions/types_and_values/#strings
-
-
 [OTTL]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/<OTEL_VERSION>/pkg/ottl/README.md
 [OTTL span context]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/<OTEL_VERSION>/pkg/ottl/contexts/ottlspan/README.md
 [OTTL spanevent context]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/<OTEL_VERSION>/pkg/ottl/contexts/ottlspanevent/README.md
@@ -283,6 +291,7 @@ otelcol.processor.filter "default" {
 [HasAttrOnDataPoint]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/<OTEL_VERSION>/processor/filterprocessor/README.md#hasattrondatapoint
 [OTTL booleans]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/<OTEL_VERSION>/pkg/ottl#booleans
 [OTTL math expressions]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/<OTEL_VERSION>/pkg/ottl#math-expressions
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/otelcol/otelcol.processor.groupbyattrs.md b/docs/sources/reference/components/otelcol/otelcol.processor.groupbyattrs.md
index ccc9b2151e..e245ce5773 100644
--- a/docs/sources/reference/components/otelcol/otelcol.processor.groupbyattrs.md
+++ b/docs/sources/reference/components/otelcol/otelcol.processor.groupbyattrs.md
@@ -36,21 +36,21 @@ otelcol.processor.groupbyattrs "LABEL" {
 
 The following arguments are supported:
 
-| Name            | Type              | Description                                                                             | Default | Required |
-|-----------------|-------------------|-----------------------------------------------------------------------------------------|---------|----------|
-| `keys`          | `list(string)`    | Keys that will be used to group the spans, log records, or metric data points together. | `[]`    | no       |
+| Name   | Type           | Description                                                                             | Default | Required |
+| ------ | -------------- | --------------------------------------------------------------------------------------- | ------- | -------- |
+| `keys` | `list(string)` | Keys that will be used to group the spans, log records, or metric data points together. | `[]`    | no       |
 
-`keys` is a string array that is used for grouping the data. 
+`keys` is a string array that is used for grouping the data.
 If it is empty, the processor performs compaction and reassociates all spans with matching Resource and InstrumentationLibrary.
 
 ## Blocks
 
 The following blocks are supported inside the definition of `otelcol.processor.groupbyattrs`:
 
-Hierarchy | Block       | Description                                       | Required
---------- | ----------- | ------------------------------------------------- | --------
-output    | [output][]  | Configures where to send received telemetry data. | yes
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| output        | [output][]        | Configures where to send received telemetry data.                          | yes      |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [output]: #output-block
 [debug_metrics]: #debug_metrics-block
@@ -68,7 +68,7 @@ debug_metrics | [debug_metrics][] | Configures the metrics that this component g
 The following fields are exported and can be referenced by other components:
 
 | Name    | Type               | Description                                                   |
-|---------|--------------------|---------------------------------------------------------------|
+| ------- | ------------------ | ------------------------------------------------------------- |
 | `input` | `otelcol.Consumer` | Accepts `otelcol.Consumer` data for metrics, logs, or traces. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics,
@@ -164,7 +164,7 @@ This output demonstrates how `otelcol.processor.groupbyattrs` works in various s
 ### Compaction
 
 Sometimes telemetry data can become fragmented due to multiple duplicated ResourceSpans/ResourceLogs/ResourceMetrics objects.
-This leads to additional memory consumption, increased processing costs, inefficient serialization and increase of the export requests. 
+This leads to additional memory consumption, increased processing costs, inefficient serialization and increase of the export requests.
 In such situations, `otelcol.processor.groupbyattrs` can be used to compact the data with matching Resource and InstrumentationLibrary properties.
 
 For example, consider this input data:
@@ -177,24 +177,25 @@ Resource {host.name="localhost"}
   InstrumentationLibrary {name="OtherLibrary"}
   Spans
     Span {span_id=2, ...}
-    
+
 Resource {host.name="localhost"}
   InstrumentationLibrary {name="MyLibrary"}
   Spans
     Span {span_id=3, ...}
-    
+
 Resource {host.name="localhost"}
   InstrumentationLibrary {name="MyLibrary"}
   Spans
     Span {span_id=4, ...}
-    
+
 Resource {host.name="otherhost"}
   InstrumentationLibrary {name="MyLibrary"}
   Spans
     Span {span_id=5, ...}
 ```
 
-You can use `otelcol.processor.groupbyattrs` with its default configuration to compact the data: 
+You can use `otelcol.processor.groupbyattrs` with its default configuration to compact the data:
+
 ```alloy
 otelcol.processor.groupbyattrs "default" {
   output {
@@ -221,7 +222,9 @@ Resource {host.name="otherhost"}
   Spans
     Span {span_id=5, ...}
 ```
+
 [otelcol.processor.batch]: ../otelcol.processor.batch/
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/otelcol/otelcol.processor.k8sattributes.md b/docs/sources/reference/components/otelcol/otelcol.processor.k8sattributes.md
index cecc3826c2..2b2857003c 100644
--- a/docs/sources/reference/components/otelcol/otelcol.processor.k8sattributes.md
+++ b/docs/sources/reference/components/otelcol/otelcol.processor.k8sattributes.md
@@ -34,48 +34,49 @@ otelcol.processor.k8sattributes "LABEL" {
 
 The following arguments are supported:
 
-Name          | Type     | Description                                                               | Default          | Required
---------------|----------|---------------------------------------------------------------------------|------------------|---------
-`auth_type`   | `string` | Authentication method when connecting to the Kubernetes API.              | `serviceAccount` | no
-`passthrough` | `bool`   | Passthrough signals as-is, only adding a `k8s.pod.ip` resource attribute. | `false`          | no
+| Name          | Type     | Description                                                               | Default          | Required |
+| ------------- | -------- | ------------------------------------------------------------------------- | ---------------- | -------- |
+| `auth_type`   | `string` | Authentication method when connecting to the Kubernetes API.              | `serviceAccount` | no       |
+| `passthrough` | `bool`   | Passthrough signals as-is, only adding a `k8s.pod.ip` resource attribute. | `false`          | no       |
 
 The supported values for `auth_type` are:
-* `none`: No authentication is required.
-* `serviceAccount`: Use the built-in service account that Kubernetes automatically provisions for each pod.
-* `kubeConfig`: Use local credentials like those used by kubectl.
-* `tls`: Use client TLS authentication.
+
+- `none`: No authentication is required.
+- `serviceAccount`: Use the built-in service account that Kubernetes automatically provisions for each pod.
+- `kubeConfig`: Use local credentials like those used by kubectl.
+- `tls`: Use client TLS authentication.
 
 Setting `passthrough` to `true` enables the "passthrough mode" of `otelcol.processor.k8sattributes`:
-* Only a `k8s.pod.ip` resource attribute will be added.
-* No other metadata will be added.
-* The Kubernetes API will not be accessed.
-* To correctly detect the pod IPs, {{< param "PRODUCT_NAME" >}} must receive spans directly from services.
-* The `passthrough` setting is useful when configuring {{< param "PRODUCT_NAME" >}} as a Kubernetes Deployment.
-A {{< param "PRODUCT_NAME" >}} running as a Deployment cannot detect the IP addresses of pods generating telemetry
-data without any of the well-known IP attributes. If the Deployment {{< param "PRODUCT_NAME" >}} receives telemetry from
-{{< param "PRODUCT_NAME" >}}s deployed as DaemonSet, then some of those attributes might be missing. As a workaround,
-you can configure the DaemonSet {{< param "PRODUCT_NAME" >}}s with `passthrough` set to `true`.
+
+- Only a `k8s.pod.ip` resource attribute will be added.
+- No other metadata will be added.
+- The Kubernetes API will not be accessed.
+- To correctly detect the pod IPs, {{< param "PRODUCT_NAME" >}} must receive spans directly from services.
+- The `passthrough` setting is useful when configuring {{< param "PRODUCT_NAME" >}} as a Kubernetes Deployment.
+  A {{< param "PRODUCT_NAME" >}} running as a Deployment cannot detect the IP addresses of pods generating telemetry
+  data without any of the well-known IP attributes. If the Deployment {{< param "PRODUCT_NAME" >}} receives telemetry from
+  {{< param "PRODUCT_NAME" >}}s deployed as DaemonSet, then some of those attributes might be missing. As a workaround,
+  you can configure the DaemonSet {{< param "PRODUCT_NAME" >}}s with `passthrough` set to `true`.
 
 ## Blocks
 
 The following blocks are supported inside the definition of
 `otelcol.processor.k8sattributes`:
 
-Hierarchy                | Block               | Description                                               | Required
--------------------------|---------------------|-----------------------------------------------------------|---------
-output                   | [output][]          | Configures where to send received telemetry data.         | yes
-extract                  | [extract][]         | Rules for extracting data from Kubernetes.                | no
-extract > annotation     | [annotation][]      | Creating resource attributes from Kubernetes annotations. | no
-extract > label          | [extract_label][]   | Creating resource attributes from Kubernetes labels.      | no
-filter                   | [filter][]          | Filters the data loaded from Kubernetes.                  | no
-filter > field           | [field][]           | Filter pods by generic Kubernetes fields.                 | no
-filter > label           | [filter_label][]    | Filter pods by Kubernetes labels.                         | no
-pod_association          | [pod_association][] | Rules to associate pod metadata with telemetry signals.   | no
-pod_association > source | [source][]          | Source information to identify a pod.                     | no
-exclude                  | [exclude][]         | Exclude pods from being processed.                        | no
-exclude > pod            | [pod][]             | Pod information.                                          | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
-
+| Hierarchy                | Block               | Description                                                                | Required |
+| ------------------------ | ------------------- | -------------------------------------------------------------------------- | -------- |
+| output                   | [output][]          | Configures where to send received telemetry data.                          | yes      |
+| extract                  | [extract][]         | Rules for extracting data from Kubernetes.                                 | no       |
+| extract > annotation     | [annotation][]      | Creating resource attributes from Kubernetes annotations.                  | no       |
+| extract > label          | [extract_label][]   | Creating resource attributes from Kubernetes labels.                       | no       |
+| filter                   | [filter][]          | Filters the data loaded from Kubernetes.                                   | no       |
+| filter > field           | [field][]           | Filter pods by generic Kubernetes fields.                                  | no       |
+| filter > label           | [filter_label][]    | Filter pods by Kubernetes labels.                                          | no       |
+| pod_association          | [pod_association][] | Rules to associate pod metadata with telemetry signals.                    | no       |
+| pod_association > source | [source][]          | Source information to identify a pod.                                      | no       |
+| exclude                  | [exclude][]         | Exclude pods from being processed.                                         | no       |
+| exclude > pod            | [pod][]             | Pod information.                                                           | no       |
+| debug_metrics            | [debug_metrics][]   | Configures the metrics that this component generates to monitor its state. | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `extract > annotation`
 refers to an `annotation` block defined inside an `extract` block.
@@ -99,43 +100,43 @@ The `extract` block configures which metadata, annotations, and labels to extrac
 
 The following attributes are supported:
 
-Name       | Type           | Description                          | Default     | Required
------------|----------------|--------------------------------------|-------------|---------
-`metadata` | `list(string)` | Pre-configured metadata keys to add. | _See below_ | no
+| Name       | Type           | Description                          | Default     | Required |
+| ---------- | -------------- | ------------------------------------ | ----------- | -------- |
+| `metadata` | `list(string)` | Pre-configured metadata keys to add. | _See below_ | no       |
 
 The currently supported `metadata` keys are:
 
-* `k8s.pod.name`
-* `k8s.pod.uid`
-* `k8s.deployment.name`
-* `k8s.node.name`
-* `k8s.namespace.name`
-* `k8s.pod.start_time`
-* `k8s.replicaset.name`
-* `k8s.replicaset.uid`
-* `k8s.daemonset.name`
-* `k8s.daemonset.uid`
-* `k8s.job.name`
-* `k8s.job.uid`
-* `k8s.cronjob.name`
-* `k8s.statefulset.name`
-* `k8s.statefulset.uid`
-* `k8s.container.name`
-* `container.image.name`
-* `container.image.tag`
-* `container.id`
+- `k8s.pod.name`
+- `k8s.pod.uid`
+- `k8s.deployment.name`
+- `k8s.node.name`
+- `k8s.namespace.name`
+- `k8s.pod.start_time`
+- `k8s.replicaset.name`
+- `k8s.replicaset.uid`
+- `k8s.daemonset.name`
+- `k8s.daemonset.uid`
+- `k8s.job.name`
+- `k8s.job.uid`
+- `k8s.cronjob.name`
+- `k8s.statefulset.name`
+- `k8s.statefulset.uid`
+- `k8s.container.name`
+- `container.image.name`
+- `container.image.tag`
+- `container.id`
 
 By default, if `metadata` is not specified, the following fields are extracted and added to spans, metrics, and logs as resource attributes:
 
-* `k8s.pod.name`
-* `k8s.pod.uid`
-* `k8s.pod.start_time`
-* `k8s.namespace.name`
-* `k8s.node.name`
-* `k8s.deployment.name` (if the pod is controlled by a deployment)
-* `k8s.container.name` (requires an additional attribute to be set: `container.id`)
-* `container.image.name` (requires one of the following additional attributes to be set: `container.id` or `k8s.container.name`)
-* `container.image.tag` (requires one of the following additional attributes to be set: `container.id` or `k8s.container.name`)
+- `k8s.pod.name`
+- `k8s.pod.uid`
+- `k8s.pod.start_time`
+- `k8s.namespace.name`
+- `k8s.node.name`
+- `k8s.deployment.name` (if the pod is controlled by a deployment)
+- `k8s.container.name` (requires an additional attribute to be set: `container.id`)
+- `container.image.name` (requires one of the following additional attributes to be set: `container.id` or `k8s.container.name`)
+- `container.image.tag` (requires one of the following additional attributes to be set: `container.id` or `k8s.container.name`)
 
 ### annotation block
 
@@ -155,10 +156,10 @@ The `filter` block configures which nodes to get data from and which fields and
 
 The following attributes are supported:
 
-Name        | Type     | Description                                                             | Default | Required
-------------|----------|-------------------------------------------------------------------------|---------|---------
-`node`      | `string` | Configures a Kubernetes node name or host name.                         | `""`    | no
-`namespace` | `string` | Filters all pods by the provided namespace. All other pods are ignored. | `""`    | no
+| Name        | Type     | Description                                                             | Default | Required |
+| ----------- | -------- | ----------------------------------------------------------------------- | ------- | -------- |
+| `node`      | `string` | Configures a Kubernetes node name or host name.                         | `""`    | no       |
+| `namespace` | `string` | Filters all pods by the provided namespace. All other pods are ignored. | `""`    | no       |
 
 If `node` is specified, then any pods not running on the specified node will be ignored by `otelcol.processor.k8sattributes`.
 
@@ -184,6 +185,7 @@ fully through child blocks.
 The `pod_association` block can be repeated multiple times, to configure additional rules.
 
 Example:
+
 ```alloy
 pod_association {
     source {
@@ -213,11 +215,10 @@ pod to be associated with the telemetry signal.
 
 The following attributes are supported:
 
-Name   | Type     | Description                                                                      | Default | Required
--------|----------|----------------------------------------------------------------------------------|---------|---------
-`from` | `string` | The association method. Currently supports `resource_attribute` and `connection` |         | yes
-`name` | `string` | Name represents extracted key name. For example, `ip`, `pod_uid`, `k8s.pod.ip`   |         | no
-
+| Name   | Type     | Description                                                                      | Default | Required |
+| ------ | -------- | -------------------------------------------------------------------------------- | ------- | -------- |
+| `from` | `string` | The association method. Currently supports `resource_attribute` and `connection` |         | yes      |
+| `name` | `string` | Name represents extracted key name. For example, `ip`, `pod_uid`, `k8s.pod.ip`   |         | no       |
 
 ### exclude block
 
@@ -233,9 +234,9 @@ The `pod` block configures a pod to be excluded from the processor.
 
 The following attributes are supported:
 
-Name   | Type     | Description         | Default | Required
--------|----------|---------------------|---------|---------
-`name` | `string` | The name of the pod |         | yes
+| Name   | Type     | Description         | Default | Required |
+| ------ | -------- | ------------------- | ------- | -------- |
+| `name` | `string` | The name of the pod |         | yes      |
 
 ### output block
 
@@ -249,9 +250,9 @@ Name   | Type     | Description         | Default | Required
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics, logs, or traces).
 
@@ -268,14 +269,15 @@ information.
 ## Examples
 
 ### Basic usage
+
 In most cases, this is enough to get started. It'll add these resource attributes to all logs, metrics, and traces:
 
-* `k8s.namespace.name`
-* `k8s.pod.name`
-* `k8s.pod.uid`
-* `k8s.pod.start_time`
-* `k8s.deployment.name`
-* `k8s.node.name`
+- `k8s.namespace.name`
+- `k8s.pod.name`
+- `k8s.pod.uid`
+- `k8s.pod.start_time`
+- `k8s.deployment.name`
+- `k8s.node.name`
 
 Example:
 
@@ -416,6 +418,7 @@ prometheus.remote_write "mimir" {
   }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/otelcol/otelcol.processor.memory_limiter.md b/docs/sources/reference/components/otelcol/otelcol.processor.memory_limiter.md
index 5f42f1195b..7d66fbe24b 100644
--- a/docs/sources/reference/components/otelcol/otelcol.processor.memory_limiter.md
+++ b/docs/sources/reference/components/otelcol/otelcol.processor.memory_limiter.md
@@ -48,13 +48,13 @@ otelcol.processor.memory_limiter "LABEL" {
 
 `otelcol.processor.memory_limiter` supports the following arguments:
 
-Name                     | Type       | Description                                                                            | Default        | Required
--------------------------|------------|----------------------------------------------------------------------------------------|----------------|---------
-`check_interval`         | `duration` | How often to check memory usage.                                                       |                | yes
-`limit`                  | `string`   | Maximum amount of memory targeted to be allocated by the process heap.                 | `"0MiB"`       | no
-`spike_limit`            | `string`   | Maximum spike expected between the measurements of memory usage.                       | 20% of `limit` | no
-`limit_percentage`       | `int`      | Maximum amount of total available memory targeted to be allocated by the process heap. | `0`            | no
-`spike_limit_percentage` | ` int`     | Maximum spike expected between the measurements of memory usage.                       | `0`            | no
+| Name                     | Type       | Description                                                                            | Default        | Required |
+| ------------------------ | ---------- | -------------------------------------------------------------------------------------- | -------------- | -------- |
+| `check_interval`         | `duration` | How often to check memory usage.                                                       |                | yes      |
+| `limit`                  | `string`   | Maximum amount of memory targeted to be allocated by the process heap.                 | `"0MiB"`       | no       |
+| `spike_limit`            | `string`   | Maximum spike expected between the measurements of memory usage.                       | 20% of `limit` | no       |
+| `limit_percentage`       | `int`      | Maximum amount of total available memory targeted to be allocated by the process heap. | `0`            | no       |
+| `spike_limit_percentage` | ` int`     | Maximum spike expected between the measurements of memory usage.                       | `0`            | no       |
 
 The arguments must define either `limit` or the `limit_percentage,
 spike_limit_percentage` pair, but not both.
@@ -75,10 +75,10 @@ The `limit` and `spike_limit` values must be larger than 1 MiB.
 The following blocks are supported inside the definition of
 `otelcol.processor.memory_limiter`:
 
-Hierarchy | Block      | Description                                       | Required
-----------|------------|---------------------------------------------------|---------
-output    | [output][] | Configures where to send received telemetry data. | yes
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| output        | [output][]        | Configures where to send received telemetry data.                          | yes      |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [output]: #output-block
 [debug_metrics]: #debug_metrics-block
@@ -95,9 +95,9 @@ debug_metrics | [debug_metrics][] | Configures the metrics that this component g
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics,
 logs, or traces).
@@ -111,6 +111,7 @@ configuration.
 
 `otelcol.processor.memory_limiter` does not expose any component-specific debug
 information.
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -128,4 +129,4 @@ Connecting some components may not be sensible or components may require further
 Refer to the linked documentation for more details.
 {{< /admonition >}}
 
-<!-- END GENERATED COMPATIBLE COMPONENTS -->
\ No newline at end of file
+<!-- END GENERATED COMPATIBLE COMPONENTS -->
diff --git a/docs/sources/reference/components/otelcol/otelcol.processor.probabilistic_sampler.md b/docs/sources/reference/components/otelcol/otelcol.processor.probabilistic_sampler.md
index 805c3904c9..8cd54ee7fb 100644
--- a/docs/sources/reference/components/otelcol/otelcol.processor.probabilistic_sampler.md
+++ b/docs/sources/reference/components/otelcol/otelcol.processor.probabilistic_sampler.md
@@ -10,13 +10,13 @@ title: otelcol.processor.probabilistic_sampler
 
 `otelcol.processor.probabilistic_sampler` accepts logs and traces data from other otelcol components and applies probabilistic sampling based on configuration options.
 
-<!-- 
+<!--
 The next few paragraphs were copied from the OTel docs:
 https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/probabilisticsamplerprocessor/README.md
 -->
 
 The probabilistic sampler processor supports several modes of sampling for spans and log records.  
-Sampling is performed on a per-request basis, considering individual items statelessly. 
+Sampling is performed on a per-request basis, considering individual items statelessly.
 For whole trace sampling, see `otelcol.processor.tail_sampling`.
 
 For trace spans, this sampler supports probabilistic sampling based on a configured sampling percentage applied to the TraceID.
@@ -48,16 +48,16 @@ otelcol.processor.probabilistic_sampler "LABEL" {
 
 `otelcol.processor.probabilistic_sampler` supports the following arguments:
 
-Name                  | Type      | Description                                                                                                          | Default          | Required
-----------------------|-----------|----------------------------------------------------------------------------------------------------------------------|------------------|---------
-`mode`                | `string`  | Sampling mode.                                                                                                       | `"proportional"` | no
-`hash_seed`           | `uint32`  | An integer used to compute the hash algorithm.                                                                       | `0`              | no
-`sampling_percentage` | `float32` | Percentage of traces or logs sampled.                                                                                | `0`              | no
-`sampling_precision`  | `int`     | The number of hexadecimal digits used to encode the sampling threshold.                                              | `4`              | no
-`fail_closed`         | `bool`    | Whether to reject items with sampling-related errors.                                                                | `true`           | no
-`attribute_source`    | `string`  | Defines where to look for the attribute in `from_attribute`.                                                         | `"traceID"`      | no
-`from_attribute`      | `string`  | The name of a log record attribute used for sampling purposes.                                                       | `""`             | no
-`sampling_priority`   | `string`  | The name of a log record attribute used to set a different sampling priority from the `sampling_percentage` setting. | `""`             | no
+| Name                  | Type      | Description                                                                                                          | Default          | Required |
+| --------------------- | --------- | -------------------------------------------------------------------------------------------------------------------- | ---------------- | -------- |
+| `mode`                | `string`  | Sampling mode.                                                                                                       | `"proportional"` | no       |
+| `hash_seed`           | `uint32`  | An integer used to compute the hash algorithm.                                                                       | `0`              | no       |
+| `sampling_percentage` | `float32` | Percentage of traces or logs sampled.                                                                                | `0`              | no       |
+| `sampling_precision`  | `int`     | The number of hexadecimal digits used to encode the sampling threshold.                                              | `4`              | no       |
+| `fail_closed`         | `bool`    | Whether to reject items with sampling-related errors.                                                                | `true`           | no       |
+| `attribute_source`    | `string`  | Defines where to look for the attribute in `from_attribute`.                                                         | `"traceID"`      | no       |
+| `from_attribute`      | `string`  | The name of a log record attribute used for sampling purposes.                                                       | `""`             | no       |
+| `sampling_priority`   | `string`  | The name of a log record attribute used to set a different sampling priority from the `sampling_percentage` setting. | `""`             | no       |
 
 You can set `mode` to `"proportional"`, `"equalizing"`, or `"hash_seed"`.
 The default is `"proportional"` unless either `hash_seed` is configured or `attribute_source` is set to `record`.
@@ -79,6 +79,7 @@ It is also possible to leverage a different `hash_seed` at different collector t
 `sampling_priority` (logs only) determines the name of a log record attribute used to set a different sampling priority from the `sampling_percentage` setting. 0 means to never sample the log record, and greater than or equal to 100 means to always sample the log record.
 
 The `probabilistic_sampler` supports two types of sampling for traces:
+
 1. `sampling.priority` [semantic convention](https://github.com/opentracing/specification/blob/master/semantic_conventions.md#span-tags-table) as defined by OpenTracing.
 2. Trace ID hashing.
 
@@ -94,9 +95,9 @@ The `probabilistic_sampler` supports sampling logs according to their trace ID,
 The following blocks are supported inside the definition of
 `otelcol.processor.probabilistic_sampler`:
 
-Hierarchy | Block      | Description                          | Required
-----------|------------|--------------------------------------|---------
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 [debug_metrics]: #debug_metrics-block
 
@@ -108,13 +109,14 @@ debug_metrics | [debug_metrics][] | Configures the metrics that this component g
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` OTLP-formatted data for any telemetry signal of these types:
-* logs
-* traces
+
+- logs
+- traces
 
 ## Component health
 
@@ -179,6 +181,7 @@ otelcol.processor.probabilistic_sampler "default" {
   }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/otelcol/otelcol.processor.resourcedetection.md b/docs/sources/reference/components/otelcol/otelcol.processor.resourcedetection.md
index 6431608b51..d3884ad707 100644
--- a/docs/sources/reference/components/otelcol/otelcol.processor.resourcedetection.md
+++ b/docs/sources/reference/components/otelcol/otelcol.processor.resourcedetection.md
@@ -37,28 +37,29 @@ otelcol.processor.resourcedetection "LABEL" {
 
 `otelcol.processor.resourcedetection` supports the following arguments:
 
-Name        | Type           | Description                                                                         | Default   | Required
------------ | -------------- | ----------------------------------------------------------------------------------- |---------- | --------
-`detectors` | `list(string)` | An ordered list of named detectors used to detect resource information.             | `["env"]` | no
-`override`  | `bool`         | Configures whether existing resource attributes should be overridden or preserved.  | `true`    | no
-`timeout`   | `duration`     | Timeout by which all specified detectors must complete.                             | `"5s"`    | no
+| Name        | Type           | Description                                                                        | Default   | Required |
+| ----------- | -------------- | ---------------------------------------------------------------------------------- | --------- | -------- |
+| `detectors` | `list(string)` | An ordered list of named detectors used to detect resource information.            | `["env"]` | no       |
+| `override`  | `bool`         | Configures whether existing resource attributes should be overridden or preserved. | `true`    | no       |
+| `timeout`   | `duration`     | Timeout by which all specified detectors must complete.                            | `"5s"`    | no       |
 
 `detectors` could contain the following values:
-* `env`
-* `ec2`
-* `ecs`
-* `eks`
-* `elasticbeanstalk`
-* `lambda`
-* `azure`
-* `aks`
-* `consul`
-* `docker`
-* `gcp`
-* `heroku`
-* `system`
-* `openshift`
-* `kubernetes_node`
+
+- `env`
+- `ec2`
+- `ecs`
+- `eks`
+- `elasticbeanstalk`
+- `lambda`
+- `azure`
+- `aks`
+- `consul`
+- `docker`
+- `gcp`
+- `heroku`
+- `system`
+- `openshift`
+- `kubernetes_node`
 
 `env` is the only detector that is not configured through a block.
 The `env` detector reads resource information from the `OTEL_RESOURCE_ATTRIBUTES` environment variable.
@@ -73,34 +74,35 @@ If multiple detectors are inserting the same attribute name, the first detector
 For example, if you had `detectors = ["eks", "ec2"]` then `cloud.platform` will be `aws_eks` instead of `ec2`.
 
 The following order is recommended for AWS:
-  1. [lambda][]
-  1. [elasticbeanstalk][]
-  1. [eks][]
-  1. [ecs][]
-  1. [ec2][]
+
+1. [lambda][]
+1. [elasticbeanstalk][]
+1. [eks][]
+1. [ecs][]
+1. [ec2][]
 
 ## Blocks
 
 The following blocks are supported inside the definition of `otelcol.processor.resourcedetection`:
 
-Hierarchy         | Block                 | Description                                       | Required
------------------ | --------------------- | ------------------------------------------------- | --------
-output            | [output][]            | Configures where to send received telemetry data. | yes
-ec2               | [ec2][]               |                                                   | no
-ecs               | [ecs][]               |                                                   | no
-eks               | [eks][]               |                                                   | no
-elasticbeanstalk  | [elasticbeanstalk][]  |                                                   | no
-lambda            | [lambda][]            |                                                   | no
-azure             | [azure][]             |                                                   | no
-aks               | [aks][]               |                                                   | no
-consul            | [consul][]            |                                                   | no
-docker            | [docker][]            |                                                   | no
-gcp               | [gcp][]               |                                                   | no
-heroku            | [heroku][]            |                                                   | no
-system            | [system][]            |                                                   | no
-openshift         | [openshift][]         |                                                   | no
-kubernetes_node   | [kubernetes_node][]   |                                                   | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy        | Block                | Description                                                                | Required |
+| ---------------- | -------------------- | -------------------------------------------------------------------------- | -------- |
+| output           | [output][]           | Configures where to send received telemetry data.                          | yes      |
+| ec2              | [ec2][]              |                                                                            | no       |
+| ecs              | [ecs][]              |                                                                            | no       |
+| eks              | [eks][]              |                                                                            | no       |
+| elasticbeanstalk | [elasticbeanstalk][] |                                                                            | no       |
+| lambda           | [lambda][]           |                                                                            | no       |
+| azure            | [azure][]            |                                                                            | no       |
+| aks              | [aks][]              |                                                                            | no       |
+| consul           | [consul][]           |                                                                            | no       |
+| docker           | [docker][]           |                                                                            | no       |
+| gcp              | [gcp][]              |                                                                            | no       |
+| heroku           | [heroku][]           |                                                                            | no       |
+| system           | [system][]           |                                                                            | no       |
+| openshift        | [openshift][]        |                                                                            | no       |
+| kubernetes_node  | [kubernetes_node][]  |                                                                            | no       |
+| debug_metrics    | [debug_metrics][]    | Configures the metrics that this component generates to monitor its state. | no       |
 
 [output]: #output
 [debug_metrics]: #debug_metrics-block
@@ -134,9 +136,9 @@ The `ec2` block reads resource information from the [EC2 instance metadata API][
 
 The `ec2` block supports the following attributes:
 
-Attribute   | Type           | Description                                                                 | Default     | Required
------------ |----------------| --------------------------------------------------------------------------- |-------------| --------
-`tags`      | `list(string)` | A list of regular expressions to match against tag keys of an EC2 instance. | `[]`        | no
+| Attribute | Type           | Description                                                                 | Default | Required |
+| --------- | -------------- | --------------------------------------------------------------------------- | ------- | -------- |
+| `tags`    | `list(string)` | A list of regular expressions to match against tag keys of an EC2 instance. | `[]`    | no       |
 
 If you are using a proxy server on your EC2 instance, it's important that you exempt requests for instance metadata as described in the [AWS cli user guide][].
 Failing to do so can result in proxied or missing instance data.
@@ -153,25 +155,25 @@ To fetch EC2 tags, the IAM role assigned to the EC2 instance must have a policy
 
 The `ec2` block supports the following blocks:
 
-Block                                            | Description                                  | Required
--------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#ec2--resource_attributes) | Configures which resource attributes to add. | no
+| Block                                            | Description                                  | Required |
+| ------------------------------------------------ | -------------------------------------------- | -------- |
+| [resource_attributes](#ec2--resource_attributes) | Configures which resource attributes to add. | no       |
 
 ##### ec2 > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                                   | Description                                                                                         | Required
---------------------------------------- | --------------------------------------------------------------------------------------------------- | --------
-[cloud.account.id][res-attr-cfg]        | Toggles the `cloud.account.id` resource attribute. <br> Sets `enabled` to `true` by default.        | no
-[cloud.availability_zone][res-attr-cfg] | Toggles the `cloud.availability_zone` resource attribute. <br> Sets `enabled` to `true` by default. | no
-[cloud.platform][res-attr-cfg]          | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.          | no
-[cloud.provider][res-attr-cfg]          | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.          | no
-[cloud.region][res-attr-cfg]            | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default.            | no
-[host.id][res-attr-cfg]                 | Toggles the `host.id` resource attribute. <br> Sets `enabled` to `true` by default.                 | no
-[host.image.id][res-attr-cfg]           | Toggles the `host.image.id` resource attribute. <br> Sets `enabled` to `true` by default.           | no
-[host.name][res-attr-cfg]               | Toggles the `host.name` resource attribute. <br> Sets `enabled` to `true` by default.               | no
-[host.type][res-attr-cfg]               | Toggles the `host.type` resource attribute. <br> Sets `enabled` to `true` by default.               | no
+| Block                                   | Description                                                                                         | Required |
+| --------------------------------------- | --------------------------------------------------------------------------------------------------- | -------- |
+| [cloud.account.id][res-attr-cfg]        | Toggles the `cloud.account.id` resource attribute. <br> Sets `enabled` to `true` by default.        | no       |
+| [cloud.availability_zone][res-attr-cfg] | Toggles the `cloud.availability_zone` resource attribute. <br> Sets `enabled` to `true` by default. | no       |
+| [cloud.platform][res-attr-cfg]          | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.          | no       |
+| [cloud.provider][res-attr-cfg]          | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.          | no       |
+| [cloud.region][res-attr-cfg]            | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default.            | no       |
+| [host.id][res-attr-cfg]                 | Toggles the `host.id` resource attribute. <br> Sets `enabled` to `true` by default.                 | no       |
+| [host.image.id][res-attr-cfg]           | Toggles the `host.image.id` resource attribute. <br> Sets `enabled` to `true` by default.           | no       |
+| [host.name][res-attr-cfg]               | Toggles the `host.name` resource attribute. <br> Sets `enabled` to `true` by default.               | no       |
+| [host.type][res-attr-cfg]               | Toggles the `host.type` resource attribute. <br> Sets `enabled` to `true` by default.               | no       |
 
 ### ecs
 
@@ -181,31 +183,31 @@ The `ecs` block queries the [Task Metadata Endpoint][] (TMDE) to record informat
 
 The `ecs` block supports the following blocks:
 
-Block                                            | Description                                  | Required
--------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#ecs--resource_attributes) | Configures which resource attributes to add. | no
+| Block                                            | Description                                  | Required |
+| ------------------------------------------------ | -------------------------------------------- | -------- |
+| [resource_attributes](#ecs--resource_attributes) | Configures which resource attributes to add. | no       |
 
 #### ecs > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                                   | Description                                                                                         | Required
---------------------------------------- | --------------------------------------------------------------------------------------------------- | --------
-[aws.ecs.cluster.arn][res-attr-cfg]     | Toggles the `aws.ecs.cluster.arn` resource attribute. <br> Sets `enabled` to `true` by default.     | no
-[aws.ecs.launchtype][res-attr-cfg]      | Toggles the `aws.ecs.launchtype` resource attribute. <br> Sets `enabled` to `true` by default.      | no
-[aws.ecs.task.arn][res-attr-cfg]        | Toggles the `aws.ecs.task.arn` resource attribute. <br> Sets `enabled` to `true` by default.        | no
-[aws.ecs.task.family][res-attr-cfg]     | Toggles the `aws.ecs.task.family` resource attribute. <br> Sets `enabled` to `true` by default.     | no
-[aws.ecs.task.id][res-attr-cfg]         | Toggles the `aws.ecs.task.id` resource attribute. <br> Sets `enabled` to `true` by default.         | no
-[aws.ecs.task.revision][res-attr-cfg]   | Toggles the `aws.ecs.task.revision` resource attribute. <br> Sets `enabled` to `true` by default.   | no
-[aws.log.group.arns][res-attr-cfg]      | Toggles the `aws.log.group.arns` resource attribute. <br> Sets `enabled` to `true` by default.      | no
-[aws.log.group.names][res-attr-cfg]     | Toggles the `aws.log.group.names` resource attribute. <br> Sets `enabled` to `true` by default.     | no
-[aws.log.stream.arns][res-attr-cfg]     | Toggles the `aws.log.stream.arns` resource attribute. <br> Sets `enabled` to `true` by default.     | no
-[aws.log.stream.names][res-attr-cfg]    | Toggles the `aws.log.stream.names` resource attribute. <br> Sets `enabled` to `true` by default.    | no
-[cloud.account.id][res-attr-cfg]        | Toggles the `cloud.account.id` resource attribute. <br> Sets `enabled` to `true` by default.        | no
-[cloud.availability_zone][res-attr-cfg] | Toggles the `cloud.availability_zone` resource attribute. <br> Sets `enabled` to `true` by default. | no
-[cloud.platform][res-attr-cfg]          | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.          | no
-[cloud.provider][res-attr-cfg]          | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.          | no
-[cloud.region][res-attr-cfg]            | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default.            | no
+| Block                                   | Description                                                                                         | Required |
+| --------------------------------------- | --------------------------------------------------------------------------------------------------- | -------- |
+| [aws.ecs.cluster.arn][res-attr-cfg]     | Toggles the `aws.ecs.cluster.arn` resource attribute. <br> Sets `enabled` to `true` by default.     | no       |
+| [aws.ecs.launchtype][res-attr-cfg]      | Toggles the `aws.ecs.launchtype` resource attribute. <br> Sets `enabled` to `true` by default.      | no       |
+| [aws.ecs.task.arn][res-attr-cfg]        | Toggles the `aws.ecs.task.arn` resource attribute. <br> Sets `enabled` to `true` by default.        | no       |
+| [aws.ecs.task.family][res-attr-cfg]     | Toggles the `aws.ecs.task.family` resource attribute. <br> Sets `enabled` to `true` by default.     | no       |
+| [aws.ecs.task.id][res-attr-cfg]         | Toggles the `aws.ecs.task.id` resource attribute. <br> Sets `enabled` to `true` by default.         | no       |
+| [aws.ecs.task.revision][res-attr-cfg]   | Toggles the `aws.ecs.task.revision` resource attribute. <br> Sets `enabled` to `true` by default.   | no       |
+| [aws.log.group.arns][res-attr-cfg]      | Toggles the `aws.log.group.arns` resource attribute. <br> Sets `enabled` to `true` by default.      | no       |
+| [aws.log.group.names][res-attr-cfg]     | Toggles the `aws.log.group.names` resource attribute. <br> Sets `enabled` to `true` by default.     | no       |
+| [aws.log.stream.arns][res-attr-cfg]     | Toggles the `aws.log.stream.arns` resource attribute. <br> Sets `enabled` to `true` by default.     | no       |
+| [aws.log.stream.names][res-attr-cfg]    | Toggles the `aws.log.stream.names` resource attribute. <br> Sets `enabled` to `true` by default.    | no       |
+| [cloud.account.id][res-attr-cfg]        | Toggles the `cloud.account.id` resource attribute. <br> Sets `enabled` to `true` by default.        | no       |
+| [cloud.availability_zone][res-attr-cfg] | Toggles the `cloud.availability_zone` resource attribute. <br> Sets `enabled` to `true` by default. | no       |
+| [cloud.platform][res-attr-cfg]          | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.          | no       |
+| [cloud.provider][res-attr-cfg]          | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.          | no       |
+| [cloud.region][res-attr-cfg]            | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default.            | no       |
 
 ### eks
 
@@ -213,23 +215,24 @@ The `eks` block adds resource attributes for Amazon EKS.
 
 The `eks` block supports the following blocks:
 
-Block                                            | Description                                  | Required
--------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#eks--resource_attributes) | Configures which resource attributes to add. | no
+| Block                                            | Description                                  | Required |
+| ------------------------------------------------ | -------------------------------------------- | -------- |
+| [resource_attributes](#eks--resource_attributes) | Configures which resource attributes to add. | no       |
 
 #### eks > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                            | Description                                                                                    | Required
--------------------------------- | ---------------------------------------------------------------------------------------------- | --------
-[cloud.platform][res-attr-cfg]   | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.     | no
-[cloud.provider][res-attr-cfg]   | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.     | no
-[k8s.cluster.name][res-attr-cfg] | Toggles the `k8s.cluster.name` resource attribute. <br> Sets `enabled` to `false` by default.  | no
+| Block                            | Description                                                                                   | Required |
+| -------------------------------- | --------------------------------------------------------------------------------------------- | -------- |
+| [cloud.platform][res-attr-cfg]   | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.    | no       |
+| [cloud.provider][res-attr-cfg]   | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.    | no       |
+| [k8s.cluster.name][res-attr-cfg] | Toggles the `k8s.cluster.name` resource attribute. <br> Sets `enabled` to `false` by default. | no       |
 
 Example values:
-* `cloud.provider`: `"aws"`
-* `cloud.platform`: `"aws_eks"`
+
+- `cloud.provider`: `"aws"`
+- `cloud.platform`: `"aws_eks"`
 
 ### elasticbeanstalk
 
@@ -239,25 +242,26 @@ The `elasticbeanstalk` block reads the AWS X-Ray configuration file available on
 
 The `elasticbeanstalk` block supports the following blocks:
 
-Block                                                         | Description                                  | Required
---------------------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#elasticbeanstalk--resource_attributes) | Configures which resource attributes to add. | no
+| Block                                                         | Description                                  | Required |
+| ------------------------------------------------------------- | -------------------------------------------- | -------- |
+| [resource_attributes](#elasticbeanstalk--resource_attributes) | Configures which resource attributes to add. | no       |
 
 #### elasticbeanstalk > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                             | Description                                                                                   | Required
---------------------------------- | --------------------------------------------------------------------------------------------- | --------
-[cloud.platform][res-attr-cfg]    | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.    | no
-[cloud.provider][res-attr-cfg]    | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.    | no
-[deployment.envir][res-attr-cfg]  | Toggles the `deployment.envir` resource attribute. <br> Sets `enabled` to `true` by default.  | no
-[service.instance][res-attr-cfg]  | Toggles the `service.instance` resource attribute. <br> Sets `enabled` to `true` by default.  | no
-[service.version][res-attr-cfg]   | Toggles the `service.version` resource attribute. <br> Sets `enabled` to `true` by default.   | no
+| Block                            | Description                                                                                  | Required |
+| -------------------------------- | -------------------------------------------------------------------------------------------- | -------- |
+| [cloud.platform][res-attr-cfg]   | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.   | no       |
+| [cloud.provider][res-attr-cfg]   | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.   | no       |
+| [deployment.envir][res-attr-cfg] | Toggles the `deployment.envir` resource attribute. <br> Sets `enabled` to `true` by default. | no       |
+| [service.instance][res-attr-cfg] | Toggles the `service.instance` resource attribute. <br> Sets `enabled` to `true` by default. | no       |
+| [service.version][res-attr-cfg]  | Toggles the `service.version` resource attribute. <br> Sets `enabled` to `true` by default.  | no       |
 
 Example values:
-* `cloud.provider`: `"aws"`
-* `cloud.platform`: `"aws_elastic_beanstalk"`
+
+- `cloud.provider`: `"aws"`
+- `cloud.platform`: `"aws_elastic_beanstalk"`
 
 ### lambda
 
@@ -267,40 +271,43 @@ The `lambda` block uses the AWS Lambda [runtime environment variables][lambda-en
 
 The `lambda` block supports the following blocks:
 
-Block                                               | Description                                  | Required
-----------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#lambda--resource_attributes) | Configures which resource attributes to add. | no
+| Block                                               | Description                                  | Required |
+| --------------------------------------------------- | -------------------------------------------- | -------- |
+| [resource_attributes](#lambda--resource_attributes) | Configures which resource attributes to add. | no       |
 
 #### lambda > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                                 | Description                                                                                         | Required
-------------------------------------- | --------------------------------------------------------------------------------------------------- | --------
-[aws.log.group.names][res-attr-cfg]   | Toggles the `aws.log.group.names` resource attribute. <br> Sets `enabled` to `true` by default.     | no
-[aws.log.stream.names][res-attr-cfg]  | Toggles the `aws.log.stream.names` resource attribute. <br> Sets `enabled` to `true` by default.    | no
-[cloud.platform][res-attr-cfg]        | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.          | no
-[cloud.provider][res-attr-cfg]        | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.          | no
-[cloud.region][res-attr-cfg]          | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default.            | no
-[faas.instance][res-attr-cfg]         | Toggles the `faas.instance` resource attribute. <br> Sets `enabled` to `true` by default.           | no
-[faas.max_memory][res-attr-cfg]       | Toggles the `faas.max_memory` resource attribute. <br> Sets `enabled` to `true` by default.         | no
-[faas.name][res-attr-cfg]             | Toggles the `faas.name` resource attribute. <br> Sets `enabled` to `true` by default.               | no
-[faas.version][res-attr-cfg]          | Toggles the `faas.version` resource attribute. <br> Sets `enabled` to `true` by default.            | no
+| Block                                | Description                                                                                      | Required |
+| ------------------------------------ | ------------------------------------------------------------------------------------------------ | -------- |
+| [aws.log.group.names][res-attr-cfg]  | Toggles the `aws.log.group.names` resource attribute. <br> Sets `enabled` to `true` by default.  | no       |
+| [aws.log.stream.names][res-attr-cfg] | Toggles the `aws.log.stream.names` resource attribute. <br> Sets `enabled` to `true` by default. | no       |
+| [cloud.platform][res-attr-cfg]       | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.       | no       |
+| [cloud.provider][res-attr-cfg]       | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.       | no       |
+| [cloud.region][res-attr-cfg]         | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default.         | no       |
+| [faas.instance][res-attr-cfg]        | Toggles the `faas.instance` resource attribute. <br> Sets `enabled` to `true` by default.        | no       |
+| [faas.max_memory][res-attr-cfg]      | Toggles the `faas.max_memory` resource attribute. <br> Sets `enabled` to `true` by default.      | no       |
+| [faas.name][res-attr-cfg]            | Toggles the `faas.name` resource attribute. <br> Sets `enabled` to `true` by default.            | no       |
+| [faas.version][res-attr-cfg]         | Toggles the `faas.version` resource attribute. <br> Sets `enabled` to `true` by default.         | no       |
 
 [Cloud semantic conventions][]:
-* `cloud.provider`: `"aws"`
-* `cloud.platform`: `"aws_lambda"`
-* `cloud.region`: `$AWS_REGION`
+
+- `cloud.provider`: `"aws"`
+- `cloud.platform`: `"aws_lambda"`
+- `cloud.region`: `$AWS_REGION`
 
 [Function as a Service semantic conventions][] and [AWS Lambda semantic conventions][]:
-* `faas.name`: `$AWS_LAMBDA_FUNCTION_NAME`
-* `faas.version`: `$AWS_LAMBDA_FUNCTION_VERSION`
-* `faas.instance`: `$AWS_LAMBDA_LOG_STREAM_NAME`
-* `faas.max_memory`: `$AWS_LAMBDA_FUNCTION_MEMORY_SIZE`
+
+- `faas.name`: `$AWS_LAMBDA_FUNCTION_NAME`
+- `faas.version`: `$AWS_LAMBDA_FUNCTION_VERSION`
+- `faas.instance`: `$AWS_LAMBDA_LOG_STREAM_NAME`
+- `faas.max_memory`: `$AWS_LAMBDA_FUNCTION_MEMORY_SIZE`
 
 [AWS Logs semantic conventions][]:
-* `aws.log.group.names`: `$AWS_LAMBDA_LOG_GROUP_NAME`
-* `aws.log.stream.names`: `$AWS_LAMBDA_LOG_STREAM_NAME`
+
+- `aws.log.group.names`: `$AWS_LAMBDA_LOG_GROUP_NAME`
+- `aws.log.stream.names`: `$AWS_LAMBDA_LOG_STREAM_NAME`
 
 [Cloud semantic conventions]: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/semantic_conventions/cloud.md
 [Function as a Service semantic conventions]: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/semantic_conventions/faas.md
@@ -315,38 +322,37 @@ The `azure` block queries the [Azure Instance Metadata Service][] to retrieve va
 
 The `azure` block supports the following blocks:
 
-Block                                              | Description                                  | Required
----------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#azure--resource_attributes) | Configures which resource attributes to add. | no
-
+| Block                                              | Description                                  | Required |
+| -------------------------------------------------- | -------------------------------------------- | -------- |
+| [resource_attributes](#azure--resource_attributes) | Configures which resource attributes to add. | no       |
 
 The `azure` block supports the following attributes:
 
-
-Attribute    | Type           | Description                                                                         | Default | Required
--------------|----------------|-------------------------------------------------------------------------------------|---------|---------
-`tags` | `list(string)` | A list of regex's to match tag keys to add as resource attributes can be specified. | `[]`    | no
+| Attribute | Type           | Description                                                                         | Default | Required |
+| --------- | -------------- | ----------------------------------------------------------------------------------- | ------- | -------- |
+| `tags`    | `list(string)` | A list of regex's to match tag keys to add as resource attributes can be specified. | `[]`    | no       |
 
 #### azure > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                                    | Description                                                                                          | Required
------------------------------------------|------------------------------------------------------------------------------------------------------|---------
-[azure.resourcegroup.name][res-attr-cfg] | Toggles the `azure.resourcegroup.name` resource attribute. <br> Sets `enabled` to `true` by default. | no
-[azure.vm.name][res-attr-cfg]            | Toggles the `azure.vm.name` resource attribute. <br> Sets `enabled` to `true` by default.            | no
-[azure.vm.scaleset.name][res-attr-cfg]   | Toggles the `azure.vm.scaleset.name` resource attribute. <br> Sets `enabled` to `true` by default.   | no
-[azure.vm.size][res-attr-cfg]            | Toggles the `azure.vm.size` resource attribute. <br> Sets `enabled` to `true` by default.            | no
-[cloud.account.id][res-attr-cfg]         | Toggles the `cloud.account.id` resource attribute. <br> Sets `enabled` to `true` by default.         | no
-[cloud.platform][res-attr-cfg]           | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.           | no
-[cloud.provider][res-attr-cfg]           | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.           | no
-[cloud.region][res-attr-cfg]             | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default.             | no
-[host.id][res-attr-cfg]                  | Toggles the `host.id` resource attribute. <br> Sets `enabled` to `true` by default.                  | no
-[host.name][res-attr-cfg]                | Toggles the `host.name` resource attribute. <br> Sets `enabled` to `true` by default.                | no
+| Block                                    | Description                                                                                          | Required |
+| ---------------------------------------- | ---------------------------------------------------------------------------------------------------- | -------- |
+| [azure.resourcegroup.name][res-attr-cfg] | Toggles the `azure.resourcegroup.name` resource attribute. <br> Sets `enabled` to `true` by default. | no       |
+| [azure.vm.name][res-attr-cfg]            | Toggles the `azure.vm.name` resource attribute. <br> Sets `enabled` to `true` by default.            | no       |
+| [azure.vm.scaleset.name][res-attr-cfg]   | Toggles the `azure.vm.scaleset.name` resource attribute. <br> Sets `enabled` to `true` by default.   | no       |
+| [azure.vm.size][res-attr-cfg]            | Toggles the `azure.vm.size` resource attribute. <br> Sets `enabled` to `true` by default.            | no       |
+| [cloud.account.id][res-attr-cfg]         | Toggles the `cloud.account.id` resource attribute. <br> Sets `enabled` to `true` by default.         | no       |
+| [cloud.platform][res-attr-cfg]           | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.           | no       |
+| [cloud.provider][res-attr-cfg]           | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.           | no       |
+| [cloud.region][res-attr-cfg]             | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default.             | no       |
+| [host.id][res-attr-cfg]                  | Toggles the `host.id` resource attribute. <br> Sets `enabled` to `true` by default.                  | no       |
+| [host.name][res-attr-cfg]                | Toggles the `host.name` resource attribute. <br> Sets `enabled` to `true` by default.                | no       |
 
 Example values:
-* `cloud.provider`: `"azure"`
-* `cloud.platform`: `"azure_vm"`
+
+- `cloud.provider`: `"azure"`
+- `cloud.platform`: `"azure_vm"`
 
 ### aks
 
@@ -354,32 +360,34 @@ The `aks` block adds resource attributes related to Azure AKS.
 
 The `aks` block supports the following blocks:
 
-Block                                            | Description                                  | Required
--------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#aks--resource_attributes) | Configures which resource attributes to add. | no
+| Block                                            | Description                                  | Required |
+| ------------------------------------------------ | -------------------------------------------- | -------- |
+| [resource_attributes](#aks--resource_attributes) | Configures which resource attributes to add. | no       |
 
 #### aks > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                            | Description                                                                                    | Required
--------------------------------- | ---------------------------------------------------------------------------------------------- | --------
-[cloud.platform][res-attr-cfg]   | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.     | no
-[cloud.provider][res-attr-cfg]   | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.     | no
-[k8s.cluster.name][res-attr-cfg] | Toggles the `k8s.cluster.name` resource attribute. <br> Sets `enabled` to `false` by default.  | no
+| Block                            | Description                                                                                   | Required |
+| -------------------------------- | --------------------------------------------------------------------------------------------- | -------- |
+| [cloud.platform][res-attr-cfg]   | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.    | no       |
+| [cloud.provider][res-attr-cfg]   | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.    | no       |
+| [k8s.cluster.name][res-attr-cfg] | Toggles the `k8s.cluster.name` resource attribute. <br> Sets `enabled` to `false` by default. | no       |
 
 Example values:
-* `cloud.provider`: `"azure"`
-* `cloud.platform`: `"azure_vm"`
+
+- `cloud.provider`: `"azure"`
+- `cloud.platform`: `"azure_vm"`
 
 Azure AKS cluster name is derived from the Azure Instance Metadata Service's (IMDS) infrastructure resource group field.
 This field contains the resource group and name of the cluster, separated by underscores. For example: `MC_<resource group>_<cluster name>_<location>`.
 
 Example:
-  - Resource group: `my-resource-group`
-  - Cluster name: `my-cluster`
-  - Location: `eastus`
-  - Generated name: `MC_my-resource-group_my-cluster_eastus`
+
+- Resource group: `my-resource-group`
+- Cluster name: `my-cluster`
+- Location: `eastus`
+- Generated name: `MC_my-resource-group_my-cluster_eastus`
 
 The cluster name is detected if it does not contain underscores and if a custom infrastructure resource group name was not used.
 
@@ -392,13 +400,13 @@ The `consul` block queries a Consul agent and reads its configuration endpoint t
 
 The `consul` block supports the following attributes:
 
-Attribute    | Type           | Description                                                                       | Default | Required
--------------|----------------|-----------------------------------------------------------------------------------|---------|---------
-`address`    | `string`       | The address of the Consul server                                                  | `""`    | no
-`datacenter` | `string`       | Datacenter to use. If not provided, the default agent datacenter is used.         | `""`    | no
-`token`      | `secret`       | A per-request ACL token which overrides the Consul agent's default (empty) token. | `""`    | no
-`namespace`  | `string`       | The name of the namespace to send along for the request.                          | `""`    | no
-`meta`       | `list(string)` | Allowlist of [Consul Metadata][] keys to use as resource attributes.              | `[]`    | no
+| Attribute    | Type           | Description                                                                       | Default | Required |
+| ------------ | -------------- | --------------------------------------------------------------------------------- | ------- | -------- |
+| `address`    | `string`       | The address of the Consul server                                                  | `""`    | no       |
+| `datacenter` | `string`       | Datacenter to use. If not provided, the default agent datacenter is used.         | `""`    | no       |
+| `token`      | `secret`       | A per-request ACL token which overrides the Consul agent's default (empty) token. | `""`    | no       |
+| `namespace`  | `string`       | The name of the namespace to send along for the request.                          | `""`    | no       |
+| `meta`       | `list(string)` | Allowlist of [Consul Metadata][] keys to use as resource attributes.              | `[]`    | no       |
 
 `token` is only required if [Consul's ACL System][] is enabled.
 
@@ -407,19 +415,19 @@ Attribute    | Type           | Description
 
 The `consul` block supports the following blocks:
 
-Block                                               | Description                                  | Required
-----------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#consul--resource_attributes) | Configures which resource attributes to add. | no
+| Block                                               | Description                                  | Required |
+| --------------------------------------------------- | -------------------------------------------- | -------- |
+| [resource_attributes](#consul--resource_attributes) | Configures which resource attributes to add. | no       |
 
 #### consul > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                        | Description                                                                              | Required
------------------------------|------------------------------------------------------------------------------------------|---------
-[cloud.region][res-attr-cfg] | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default. | no
-[host.id][res-attr-cfg]      | Toggles the `host.id` resource attribute. <br> Sets `enabled` to `true` by default.      | no
-[host.name][res-attr-cfg]    | Toggles the `host.name` resource attribute. <br> Sets `enabled` to `true` by default.    | no
+| Block                        | Description                                                                              | Required |
+| ---------------------------- | ---------------------------------------------------------------------------------------- | -------- |
+| [cloud.region][res-attr-cfg] | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default. | no       |
+| [host.id][res-attr-cfg]      | Toggles the `host.id` resource attribute. <br> Sets `enabled` to `true` by default.      | no       |
+| [host.name][res-attr-cfg]    | Toggles the `host.name` resource attribute. <br> Sets `enabled` to `true` by default.    | no       |
 
 ### docker
 
@@ -430,18 +438,18 @@ Docker detection does not work on MacOS.
 
 The `docker` block supports the following blocks:
 
-Block                                               | Description                                  | Required
-----------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#docker--resource_attributes) | Configures which resource attributes to add. | no
+| Block                                               | Description                                  | Required |
+| --------------------------------------------------- | -------------------------------------------- | -------- |
+| [resource_attributes](#docker--resource_attributes) | Configures which resource attributes to add. | no       |
 
 #### docker > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                     | Description                                                                           | Required
---------------------------|---------------------------------------------------------------------------------------|---------
-[host.name][res-attr-cfg] | Toggles the `host.name` resource attribute. <br> Sets `enabled` to `true` by default. | no
-[os.type][res-attr-cfg]   | Toggles the `os.type` resource attribute. <br> Sets `enabled` to `true` by default.   | no
+| Block                     | Description                                                                           | Required |
+| ------------------------- | ------------------------------------------------------------------------------------- | -------- |
+| [host.name][res-attr-cfg] | Toggles the `host.name` resource attribute. <br> Sets `enabled` to `true` by default. | no       |
+| [os.type][res-attr-cfg]   | Toggles the `os.type` resource attribute. <br> Sets `enabled` to `true` by default.   | no       |
 
 ### gcp
 
@@ -455,61 +463,62 @@ Use the `gcp` detector regardless of the GCP platform {{< param "PRODUCT_NAME" >
 
 The `gcp` block supports the following blocks:
 
-Block                                            | Description                                  | Required
--------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#gcp--resource_attributes) | Configures which resource attributes to add. | no
+| Block                                            | Description                                  | Required |
+| ------------------------------------------------ | -------------------------------------------- | -------- |
+| [resource_attributes](#gcp--resource_attributes) | Configures which resource attributes to add. | no       |
 
 #### gcp > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                                        | Description                                                                                              | Required
----------------------------------------------|----------------------------------------------------------------------------------------------------------|---------
-[cloud.account.id][res-attr-cfg]             | Toggles the `cloud.account.id` resource attribute. <br> Sets `enabled` to `true` by default.             | no
-[cloud.availability_zone][res-attr-cfg]      | Toggles the `cloud.availability_zone` resource attribute. <br> Sets `enabled` to `true` by default.      | no
-[cloud.platform][res-attr-cfg]               | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.               | no
-[cloud.provider][res-attr-cfg]               | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.               | no
-[cloud.region][res-attr-cfg]                 | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default.                 | no
-[faas.id][res-attr-cfg]                      | Toggles the `faas.id` resource attribute. <br> Sets `enabled` to `true` by default.                      | no
-[faas.instance][res-attr-cfg]                | Toggles the `faas.instance` resource attribute. <br> Sets `enabled` to `true` by default.                | no
-[faas.name][res-attr-cfg]                    | Toggles the `faas.name` resource attribute. <br> Sets `enabled` to `true` by default.                    | no
-[faas.version][res-attr-cfg]                 | Toggles the `faas.version` resource attribute. <br> Sets `enabled` to `true` by default.                 | no
-[gcp.cloud_run.job.execution][res-attr-cfg]  | Toggles the `gcp.cloud_run.job.execution` resource attribute. <br> Sets `enabled` to `true` by default.  | no
-[gcp.cloud_run.job.task_index][res-attr-cfg] | Toggles the `gcp.cloud_run.job.task_index` resource attribute. <br> Sets `enabled` to `true` by default. | no
-[gcp.gce.instance.hostname][res-attr-cfg]    | Toggles the `gcp.gce.instance.hostname` resource attribute. <br> Sets `enabled` to `false` by default.   | no
-[gcp.gce.instance.name][res-attr-cfg]        | Toggles the `gcp.gce.instance.name` resource attribute. <br> Sets `enabled` to `false` by default.       | no
-[host.id][res-attr-cfg]                      | Toggles the `host.id` resource attribute. <br> Sets `enabled` to `true` by default.                      | no
-[host.name][res-attr-cfg]                    | Toggles the `host.name` resource attribute. <br> Sets `enabled` to `true` by default.                    | no
-[host.type][res-attr-cfg]                    | Toggles the `host.type` resource attribute. <br> Sets `enabled` to `true` by default.                    | no
-[k8s.cluster.name][res-attr-cfg]             | Toggles the `k8s.cluster.name` resource attribute. <br> Sets `enabled` to `true` by default.             | no
+| Block                                        | Description                                                                                              | Required |
+| -------------------------------------------- | -------------------------------------------------------------------------------------------------------- | -------- |
+| [cloud.account.id][res-attr-cfg]             | Toggles the `cloud.account.id` resource attribute. <br> Sets `enabled` to `true` by default.             | no       |
+| [cloud.availability_zone][res-attr-cfg]      | Toggles the `cloud.availability_zone` resource attribute. <br> Sets `enabled` to `true` by default.      | no       |
+| [cloud.platform][res-attr-cfg]               | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.               | no       |
+| [cloud.provider][res-attr-cfg]               | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.               | no       |
+| [cloud.region][res-attr-cfg]                 | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default.                 | no       |
+| [faas.id][res-attr-cfg]                      | Toggles the `faas.id` resource attribute. <br> Sets `enabled` to `true` by default.                      | no       |
+| [faas.instance][res-attr-cfg]                | Toggles the `faas.instance` resource attribute. <br> Sets `enabled` to `true` by default.                | no       |
+| [faas.name][res-attr-cfg]                    | Toggles the `faas.name` resource attribute. <br> Sets `enabled` to `true` by default.                    | no       |
+| [faas.version][res-attr-cfg]                 | Toggles the `faas.version` resource attribute. <br> Sets `enabled` to `true` by default.                 | no       |
+| [gcp.cloud_run.job.execution][res-attr-cfg]  | Toggles the `gcp.cloud_run.job.execution` resource attribute. <br> Sets `enabled` to `true` by default.  | no       |
+| [gcp.cloud_run.job.task_index][res-attr-cfg] | Toggles the `gcp.cloud_run.job.task_index` resource attribute. <br> Sets `enabled` to `true` by default. | no       |
+| [gcp.gce.instance.hostname][res-attr-cfg]    | Toggles the `gcp.gce.instance.hostname` resource attribute. <br> Sets `enabled` to `false` by default.   | no       |
+| [gcp.gce.instance.name][res-attr-cfg]        | Toggles the `gcp.gce.instance.name` resource attribute. <br> Sets `enabled` to `false` by default.       | no       |
+| [host.id][res-attr-cfg]                      | Toggles the `host.id` resource attribute. <br> Sets `enabled` to `true` by default.                      | no       |
+| [host.name][res-attr-cfg]                    | Toggles the `host.name` resource attribute. <br> Sets `enabled` to `true` by default.                    | no       |
+| [host.type][res-attr-cfg]                    | Toggles the `host.type` resource attribute. <br> Sets `enabled` to `true` by default.                    | no       |
+| [k8s.cluster.name][res-attr-cfg]             | Toggles the `k8s.cluster.name` resource attribute. <br> Sets `enabled` to `true` by default.             | no       |
 
 #### Google Compute Engine (GCE) metadata
 
-* `cloud.provider`: `"gcp"`
-* `cloud.platform`: `"gcp_compute_engine"`
-* `cloud.account.id`: project id
-* `cloud.region`: e.g. `"us-central1"`
-* `cloud.availability_zone`: e.g. `"us-central1-c"`
-* `host.id`: instance id
-* `host.name`: instance name
-* `host.type`: machine type
-* (optional) `gcp.gce.instance.hostname`
-* (optional) `gcp.gce.instance.name`
+- `cloud.provider`: `"gcp"`
+- `cloud.platform`: `"gcp_compute_engine"`
+- `cloud.account.id`: project id
+- `cloud.region`: e.g. `"us-central1"`
+- `cloud.availability_zone`: e.g. `"us-central1-c"`
+- `host.id`: instance id
+- `host.name`: instance name
+- `host.type`: machine type
+- (optional) `gcp.gce.instance.hostname`
+- (optional) `gcp.gce.instance.name`
 
 #### Google Kubernetes Engine (GKE) metadata
 
-* `cloud.provider`: `"gcp"`
-* `cloud.platform`: `"gcp_kubernetes_engine"`
-* `cloud.account.id`: project id
-* `cloud.region`: only for regional GKE clusters; e.g. `"us-central1"`
-* `cloud.availability_zone`: only for zonal GKE clusters; e.g. `"us-central1-c"`
-* `k8s.cluster.name`
-* `host.id`: instance id
-* `host.name`: instance name; only when workload identity is disabled
+- `cloud.provider`: `"gcp"`
+- `cloud.platform`: `"gcp_kubernetes_engine"`
+- `cloud.account.id`: project id
+- `cloud.region`: only for regional GKE clusters; e.g. `"us-central1"`
+- `cloud.availability_zone`: only for zonal GKE clusters; e.g. `"us-central1-c"`
+- `k8s.cluster.name`
+- `host.id`: instance id
+- `host.name`: instance name; only when workload identity is disabled
 
 One known issue happens when GKE workload identity is enabled. The GCE metadata endpoints won't be available,
 and the GKE resource detector won't be able to determine `host.name`.
 If this happens, you can set `host.name` from one of the following resources:
+
 - Get the `node.name` through the [downward API][] with the `env` detector.
 - Get the Kubernetes node name from the Kubernetes API (with `k8s.io/client-go`).
 
@@ -517,45 +526,45 @@ If this happens, you can set `host.name` from one of the following resources:
 
 #### Google Cloud Run Services metadata
 
-* `cloud.provider`: `"gcp"`
-* `cloud.platform`: `"gcp_cloud_run"`
-* `cloud.account.id`: project id
-* `cloud.region`: e.g. `"us-central1"`
-* `faas.id`: instance id
-* `faas.name`: service name
-* `faas.version`: service revision
+- `cloud.provider`: `"gcp"`
+- `cloud.platform`: `"gcp_cloud_run"`
+- `cloud.account.id`: project id
+- `cloud.region`: e.g. `"us-central1"`
+- `faas.id`: instance id
+- `faas.name`: service name
+- `faas.version`: service revision
 
 #### Cloud Run Jobs metadata
 
-* `cloud.provider`: `"gcp"`
-* `cloud.platform`: `"gcp_cloud_run"`
-* `cloud.account.id`: project id
-* `cloud.region`: e.g. `"us-central1"`
-* `faas.id`: instance id
-* `faas.name`: service name
-* `gcp.cloud_run.job.execution`: e.g. `"my-service-ajg89"`
-* `gcp.cloud_run.job.task_index`: e.g. `"0"`
+- `cloud.provider`: `"gcp"`
+- `cloud.platform`: `"gcp_cloud_run"`
+- `cloud.account.id`: project id
+- `cloud.region`: e.g. `"us-central1"`
+- `faas.id`: instance id
+- `faas.name`: service name
+- `gcp.cloud_run.job.execution`: e.g. `"my-service-ajg89"`
+- `gcp.cloud_run.job.task_index`: e.g. `"0"`
 
 #### Google Cloud Functions metadata
 
-* `cloud.provider`: `"gcp"`
-* `cloud.platform`: `"gcp_cloud_functions"`
-* `cloud.account.id`: project id
-* `cloud.region`: e.g. `"us-central1"`
-* `faas.id`: instance id
-* `faas.name`: function name
-* `faas.version`: function version
+- `cloud.provider`: `"gcp"`
+- `cloud.platform`: `"gcp_cloud_functions"`
+- `cloud.account.id`: project id
+- `cloud.region`: e.g. `"us-central1"`
+- `faas.id`: instance id
+- `faas.name`: function name
+- `faas.version`: function version
 
 #### Google App Engine metadata
 
-* `cloud.provider`: `"gcp"`
-* `cloud.platform`: `"gcp_app_engine"`
-* `cloud.account.id`: project id
-* `cloud.region`: e.g. `"us-central1"`
-* `cloud.availability_zone`: e.g. `"us-central1-c"`
-* `faas.id`: instance id
-* `faas.name`: service name
-* `faas.version`: service version
+- `cloud.provider`: `"gcp"`
+- `cloud.platform`: `"gcp_app_engine"`
+- `cloud.account.id`: project id
+- `cloud.region`: e.g. `"us-central1"`
+- `cloud.availability_zone`: e.g. `"us-central1-c"`
+- `faas.id`: instance id
+- `faas.name`: service name
+- `faas.version`: service version
 
 ### heroku
 
@@ -563,30 +572,30 @@ The `heroku` block adds resource attributes derived from [Heroku dyno metadata][
 
 The `heroku` block supports the following blocks:
 
-Block                                               | Description                                  | Required
-----------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#heroku--resource_attributes) | Configures which resource attributes to add. | no
+| Block                                               | Description                                  | Required |
+| --------------------------------------------------- | -------------------------------------------- | -------- |
+| [resource_attributes](#heroku--resource_attributes) | Configures which resource attributes to add. | no       |
 
 #### heroku > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                                             | Description                                                                                                   | Required
---------------------------------------------------|---------------------------------------------------------------------------------------------------------------|---------
-[cloud.provider][res-attr-cfg]                    | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.                    | no
-[heroku.app.id][res-attr-cfg]                     | Toggles the `heroku.app.id` resource attribute. <br> Sets `enabled` to `true` by default.                     | no
-[heroku.dyno.id][res-attr-cfg]                    | Toggles the `heroku.dyno.id` resource attribute. <br> Sets `enabled` to `true` by default.                    | no
-[heroku.release.commit][res-attr-cfg]             | Toggles the `heroku.release.commit` resource attribute. <br> Sets `enabled` to `true` by default.             | no
-[heroku.release.creation_timestamp][res-attr-cfg] | Toggles the `heroku.release.creation_timestamp` resource attribute. <br> Sets `enabled` to `true` by default. | no
-[service.instance.id][res-attr-cfg]               | Toggles the `service.instance.id` resource attribute. <br> Sets `enabled` to `true` by default.               | no
-[service.name][res-attr-cfg]                      | Toggles the `service.name` resource attribute. <br> Sets `enabled` to `true` by default.                      | no
-[service.version][res-attr-cfg]                   | Toggles the `service.version` resource attribute. <br> Sets `enabled` to `true` by default.                   | no
+| Block                                             | Description                                                                                                   | Required |
+| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | -------- |
+| [cloud.provider][res-attr-cfg]                    | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.                    | no       |
+| [heroku.app.id][res-attr-cfg]                     | Toggles the `heroku.app.id` resource attribute. <br> Sets `enabled` to `true` by default.                     | no       |
+| [heroku.dyno.id][res-attr-cfg]                    | Toggles the `heroku.dyno.id` resource attribute. <br> Sets `enabled` to `true` by default.                    | no       |
+| [heroku.release.commit][res-attr-cfg]             | Toggles the `heroku.release.commit` resource attribute. <br> Sets `enabled` to `true` by default.             | no       |
+| [heroku.release.creation_timestamp][res-attr-cfg] | Toggles the `heroku.release.creation_timestamp` resource attribute. <br> Sets `enabled` to `true` by default. | no       |
+| [service.instance.id][res-attr-cfg]               | Toggles the `service.instance.id` resource attribute. <br> Sets `enabled` to `true` by default.               | no       |
+| [service.name][res-attr-cfg]                      | Toggles the `service.name` resource attribute. <br> Sets `enabled` to `true` by default.                      | no       |
+| [service.version][res-attr-cfg]                   | Toggles the `service.version` resource attribute. <br> Sets `enabled` to `true` by default.                   | no       |
 
 When [Heroku dyno metadata][] is active, Heroku applications publish information through environment variables.
 We map these environment variables to resource attributes as follows:
 
 | Dyno metadata environment variable | Resource attribute                  |
-|------------------------------------|-------------------------------------|
+| ---------------------------------- | ----------------------------------- |
 | `HEROKU_APP_ID`                    | `heroku.app.id`                     |
 | `HEROKU_APP_NAME`                  | `service.name`                      |
 | `HEROKU_DYNO_ID`                   | `service.instance.id`               |
@@ -610,47 +619,48 @@ Use the [Docker](#docker) detector if running {{< param "PRODUCT_NAME" >}} as a
 
 The `system` block supports the following attributes:
 
-Attribute          | Type            | Description                                                                 | Default         | Required
------------------- | --------------- | --------------------------------------------------------------------------- |---------------- | --------
-`hostname_sources` | `list(string)`  | A priority list of sources from which the hostname will be fetched.         | `["dns", "os"]` | no
+| Attribute          | Type           | Description                                                         | Default         | Required |
+| ------------------ | -------------- | ------------------------------------------------------------------- | --------------- | -------- |
+| `hostname_sources` | `list(string)` | A priority list of sources from which the hostname will be fetched. | `["dns", "os"]` | no       |
 
 The valid options for `hostname_sources` are:
-* `"dns"`: Uses multiple sources to get the fully qualified domain name.
-Firstly, it looks up the host name in the local machine's `hosts` file. If that fails, it looks up the CNAME.
-Lastly, if that fails, it does a reverse DNS query. Note: this hostname source may produce unreliable results on Windows.
-To produce a FQDN, Windows hosts might have better results using the "lookup" hostname source, which is mentioned below.
-* `"os"`: Provides the hostname provided by the local machine's kernel.
-* `"cname"`: Provides the canonical name, as provided by `net.LookupCNAME` in the Go standard library.
-Note: this hostname source may produce unreliable results on Windows.
-* `"lookup"`: Does a reverse DNS lookup of the current host's IP address.
+
+- `"dns"`: Uses multiple sources to get the fully qualified domain name.
+  Firstly, it looks up the host name in the local machine's `hosts` file. If that fails, it looks up the CNAME.
+  Lastly, if that fails, it does a reverse DNS query. Note: this hostname source may produce unreliable results on Windows.
+  To produce a FQDN, Windows hosts might have better results using the "lookup" hostname source, which is mentioned below.
+- `"os"`: Provides the hostname provided by the local machine's kernel.
+- `"cname"`: Provides the canonical name, as provided by `net.LookupCNAME` in the Go standard library.
+  Note: this hostname source may produce unreliable results on Windows.
+- `"lookup"`: Does a reverse DNS lookup of the current host's IP address.
 
 In case of an error in fetching a hostname from a source, the next source from the list of `hostname_sources` will be considered.
 
 The `system` block supports the following blocks:
 
-Block                                               | Description                                  | Required
-----------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#system--resource_attributes) | Configures which resource attributes to add. | no
+| Block                                               | Description                                  | Required |
+| --------------------------------------------------- | -------------------------------------------- | -------- |
+| [resource_attributes](#system--resource_attributes) | Configures which resource attributes to add. | no       |
 
 #### system > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                                  | Description                                                                                         | Required
----------------------------------------|-----------------------------------------------------------------------------------------------------|---------
-[host.arch][res-attr-cfg]              | Toggles the `host.arch` resource attribute. <br> Sets `enabled` to `false` by default.              | no
-[host.cpu.cache.l2.size][res-attr-cfg] | Toggles the `host.cpu.cache.l2.size` resource attribute. <br> Sets `enabled` to `false` by default. | no
-[host.cpu.family][res-attr-cfg]        | Toggles the `host.cpu.family` resource attribute. <br> Sets `enabled` to `false` by default.        | no
-[host.cpu.model.id][res-attr-cfg]      | Toggles the `host.cpu.model.id` resource attribute. <br> Sets `enabled` to `false` by default.      | no
-[host.cpu.model.name][res-attr-cfg]    | Toggles the `host.cpu.model.name` resource attribute. <br> Sets `enabled` to `false` by default.    | no
-[host.cpu.stepping][res-attr-cfg]      | Toggles the `host.cpu.stepping` resource attribute. <br> Sets `enabled` to `false` by default.      | no
-[host.cpu.vendor.id][res-attr-cfg]     | Toggles the `host.cpu.vendor.id` resource attribute. <br> Sets `enabled` to `false` by default.     | no
-[host.id][res-attr-cfg]                | Toggles the `host.id` resource attribute. <br> Sets `enabled` to `false` by default.                | no
-[host.ip][res-attr-cfg]                | Toggles the `host.ip` resource attribute. <br> Sets `enabled` to `false` by default.                | no
-[host.mac][res-attr-cfg]               | Toggles the `host.mac` resource attribute. <br> Sets `enabled` to `false` by default.                | no
-[host.name][res-attr-cfg]              | Toggles the `host.name` resource attribute. <br> Sets `enabled` to `true` by default.               | no
-[os.description][res-attr-cfg]         | Toggles the `os.description` resource attribute. <br> Sets `enabled` to `false` by default.         | no
-[os.type][res-attr-cfg]                | Toggles the `os.type` resource attribute. <br> Sets `enabled` to `true` by default.                 | no
+| Block                                  | Description                                                                                         | Required |
+| -------------------------------------- | --------------------------------------------------------------------------------------------------- | -------- |
+| [host.arch][res-attr-cfg]              | Toggles the `host.arch` resource attribute. <br> Sets `enabled` to `false` by default.              | no       |
+| [host.cpu.cache.l2.size][res-attr-cfg] | Toggles the `host.cpu.cache.l2.size` resource attribute. <br> Sets `enabled` to `false` by default. | no       |
+| [host.cpu.family][res-attr-cfg]        | Toggles the `host.cpu.family` resource attribute. <br> Sets `enabled` to `false` by default.        | no       |
+| [host.cpu.model.id][res-attr-cfg]      | Toggles the `host.cpu.model.id` resource attribute. <br> Sets `enabled` to `false` by default.      | no       |
+| [host.cpu.model.name][res-attr-cfg]    | Toggles the `host.cpu.model.name` resource attribute. <br> Sets `enabled` to `false` by default.    | no       |
+| [host.cpu.stepping][res-attr-cfg]      | Toggles the `host.cpu.stepping` resource attribute. <br> Sets `enabled` to `false` by default.      | no       |
+| [host.cpu.vendor.id][res-attr-cfg]     | Toggles the `host.cpu.vendor.id` resource attribute. <br> Sets `enabled` to `false` by default.     | no       |
+| [host.id][res-attr-cfg]                | Toggles the `host.id` resource attribute. <br> Sets `enabled` to `false` by default.                | no       |
+| [host.ip][res-attr-cfg]                | Toggles the `host.ip` resource attribute. <br> Sets `enabled` to `false` by default.                | no       |
+| [host.mac][res-attr-cfg]               | Toggles the `host.mac` resource attribute. <br> Sets `enabled` to `false` by default.               | no       |
+| [host.name][res-attr-cfg]              | Toggles the `host.name` resource attribute. <br> Sets `enabled` to `true` by default.               | no       |
+| [os.description][res-attr-cfg]         | Toggles the `os.description` resource attribute. <br> Sets `enabled` to `false` by default.         | no       |
+| [os.type][res-attr-cfg]                | Toggles the `os.type` resource attribute. <br> Sets `enabled` to `true` by default.                 | no       |
 
 ### openshift
 
@@ -658,10 +668,10 @@ The `openshift` block queries the OpenShift and Kubernetes APIs to retrieve vari
 
 The `openshift` block supports the following attributes:
 
-Attribute  | Type      | Description                                             | Default     | Required
----------- |---------- | ------------------------------------------------------- |-------------| --------
-`address`  | `string`  | Address of the OpenShift API server.                    | _See below_ | no
-`token`    | `string`  | Token used to identify against the OpenShift API server.| ""          | no
+| Attribute | Type     | Description                                              | Default     | Required |
+| --------- | -------- | -------------------------------------------------------- | ----------- | -------- |
+| `address` | `string` | Address of the OpenShift API server.                     | _See below_ | no       |
+| `token`   | `string` | Token used to identify against the OpenShift API server. | ""          | no       |
 
 The "get", "watch", and "list" permissions are required:
 
@@ -670,9 +680,9 @@ kind: ClusterRole
 metadata:
   name: alloy
 rules:
-- apiGroups: ["config.openshift.io"]
-  resources: ["infrastructures", "infrastructures/status"]
-  verbs: ["get", "watch", "list"]
+  - apiGroups: ["config.openshift.io"]
+    resources: ["infrastructures", "infrastructures/status"]
+    verbs: ["get", "watch", "list"]
 ```
 
 By default, the API address is determined from the environment variables `KUBERNETES_SERVICE_HOST`,
@@ -682,10 +692,10 @@ The determination of the API address, `ca_file`, and the service token is skippe
 
 The `openshift` block supports the following blocks:
 
-Block                                                  | Description                                             | Required
--------------------------------------------------------|---------------------------------------------------------|---------
-[resource_attributes](#openshift--resource_attributes) | Configures which resource attributes to add.            | no
-[tls](#openshift--tls)                                 | TLS settings for the connection with the OpenShift API. | yes
+| Block                                                  | Description                                             | Required |
+| ------------------------------------------------------ | ------------------------------------------------------- | -------- |
+| [resource_attributes](#openshift--resource_attributes) | Configures which resource attributes to add.            | no       |
+| [tls](#openshift--tls)                                 | TLS settings for the connection with the OpenShift API. | yes      |
 
 #### openshift > tls
 
@@ -698,12 +708,12 @@ server.
 
 The `resource_attributes` block supports the following blocks:
 
-Block                             | Description                                                                                   | Required
---------------------------------- | --------------------------------------------------------------------------------------------- | --------
-[cloud.platform][res-attr-cfg]    | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.    | no
-[cloud.provider][res-attr-cfg]    | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.    | no
-[cloud.region][res-attr-cfg]      | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default.      | no
-[k8s.cluster.name][res-attr-cfg]  | Toggles the `k8s.cluster.name` resource attribute. <br> Sets `enabled` to `true` by default.  | no
+| Block                            | Description                                                                                  | Required |
+| -------------------------------- | -------------------------------------------------------------------------------------------- | -------- |
+| [cloud.platform][res-attr-cfg]   | Toggles the `cloud.platform` resource attribute. <br> Sets `enabled` to `true` by default.   | no       |
+| [cloud.provider][res-attr-cfg]   | Toggles the `cloud.provider` resource attribute. <br> Sets `enabled` to `true` by default.   | no       |
+| [cloud.region][res-attr-cfg]     | Toggles the `cloud.region` resource attribute. <br> Sets `enabled` to `true` by default.     | no       |
+| [k8s.cluster.name][res-attr-cfg] | Toggles the `k8s.cluster.name` resource attribute. <br> Sets `enabled` to `true` by default. | no       |
 
 ### kubernetes_node
 
@@ -711,11 +721,11 @@ The `kubernetes_node` block queries the Kubernetes API server to retrieve variou
 
 The `kubernetes_node` block supports the following attributes:
 
-Attribute           | Type     | Description                                                               | Default           | Required
-------------------- |--------- | ------------------------------------------------------------------------- |------------------ | --------
-`auth_type`         | `string` | Configures how to authenticate to the K8s API server.                     | `"none"`          | no
-`context`           | `string` | Override the current context when `auth_type` is set to `"kubeConfig"`.   | `""`              | no
-`node_from_env_var` | `string` | The name of an environment variable from which to retrieve the node name. | `"K8S_NODE_NAME"` | no
+| Attribute           | Type     | Description                                                               | Default           | Required |
+| ------------------- | -------- | ------------------------------------------------------------------------- | ----------------- | -------- |
+| `auth_type`         | `string` | Configures how to authenticate to the K8s API server.                     | `"none"`          | no       |
+| `context`           | `string` | Override the current context when `auth_type` is set to `"kubeConfig"`.   | `""`              | no       |
+| `node_from_env_var` | `string` | The name of an environment variable from which to retrieve the node name. | `"K8S_NODE_NAME"` | no       |
 
 The "get" and "list" permissions are required:
 
@@ -730,24 +740,25 @@ rules:
 ```
 
 `auth_type` can be set to one of the following:
-* `none`: no authentication.
-* `serviceAccount`: use the standard service account token provided to the {{< param "PRODUCT_NAME" >}} pod.
-* `kubeConfig`: use credentials from `~/.kube/config`.
+
+- `none`: no authentication.
+- `serviceAccount`: use the standard service account token provided to the {{< param "PRODUCT_NAME" >}} pod.
+- `kubeConfig`: use credentials from `~/.kube/config`.
 
 The `kubernetes_node` block supports the following blocks:
 
-Block                                                        | Description                                  | Required
--------------------------------------------------------------|----------------------------------------------|---------
-[resource_attributes](#kubernetes_node--resource_attributes) | Configures which resource attributes to add. | no
+| Block                                                        | Description                                  | Required |
+| ------------------------------------------------------------ | -------------------------------------------- | -------- |
+| [resource_attributes](#kubernetes_node--resource_attributes) | Configures which resource attributes to add. | no       |
 
 #### kubernetes_node > resource_attributes
 
 The `resource_attributes` block supports the following blocks:
 
-Block                          | Description                                                                                | Required
------------------------------- | ------------------------------------------------------------------------------------------ | --------
-[k8s.node.name][res-attr-cfg]  | Toggles the `k8s.node.name` resource attribute. <br> Sets `enabled` to `true` by default.  | no
-[k8s.node.uid][res-attr-cfg]   | Toggles the `k8s.node.uid` resource attribute. <br> Sets `enabled` to `true` by default.   | no
+| Block                         | Description                                                                               | Required |
+| ----------------------------- | ----------------------------------------------------------------------------------------- | -------- |
+| [k8s.node.name][res-attr-cfg] | Toggles the `k8s.node.name` resource attribute. <br> Sets `enabled` to `true` by default. | no       |
+| [k8s.node.uid][res-attr-cfg]  | Toggles the `k8s.node.uid` resource attribute. <br> Sets `enabled` to `true` by default.  | no       |
 
 ## Common configuration
 
@@ -760,9 +771,9 @@ For example, some resource attributes have `enabled` set to `true` by default, w
 
 The following attributes are supported:
 
-Attribute |  Type   | Description                                                                         | Default      | Required
---------- | ------- | ----------------------------------------------------------------------------------- |------------- | --------
-`enabled` | `bool`  | Toggles whether to add the resource attribute to the span, log, or metric resource. | _See below_  | no
+| Attribute | Type   | Description                                                                         | Default     | Required |
+| --------- | ------ | ----------------------------------------------------------------------------------- | ----------- | -------- |
+| `enabled` | `bool` | Toggles whether to add the resource attribute to the span, log, or metric resource. | _See below_ | no       |
 
 To see the default value for `enabled`, refer to the tables in the sections above which list the resource attributes blocks.
 The "Description" column will state either...
@@ -777,14 +788,15 @@ The "Description" column will state either...
 
 The following fields are exported and can be referenced by other components:
 
-Name | Type | Description
----- | ---- | -----------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` OTLP-formatted data for any telemetry signal of these types:
-* logs
-* metrics
-* traces
+
+- logs
+- metrics
+- traces
 
 ## Component health
 
@@ -899,11 +911,11 @@ otelcol.processor.resourcedetection "default" {
 You need to add this to your workload:
 
 ```yaml
-        env:
-          - name: K8S_NODE_NAME
-            valueFrom:
-              fieldRef:
-                fieldPath: spec.nodeName
+env:
+  - name: K8S_NODE_NAME
+    valueFrom:
+      fieldRef:
+        fieldPath: spec.nodeName
 ```
 
 ### kubernetes_node with a custom environment variable
@@ -928,12 +940,13 @@ otelcol.processor.resourcedetection "default" {
 You need to add this to your workload:
 
 ```yaml
-        env:
-          - name: my_custom_var
-            valueFrom:
-              fieldRef:
-                fieldPath: spec.nodeName
+env:
+  - name: my_custom_var
+    valueFrom:
+      fieldRef:
+        fieldPath: spec.nodeName
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/otelcol/otelcol.processor.span.md b/docs/sources/reference/components/otelcol/otelcol.processor.span.md
index 7bd79f6ad2..b34a7c1c25 100644
--- a/docs/sources/reference/components/otelcol/otelcol.processor.span.md
+++ b/docs/sources/reference/components/otelcol/otelcol.processor.span.md
@@ -37,23 +37,23 @@ otelcol.processor.span "LABEL" {
 The following blocks are supported inside the definition of
 `otelcol.processor.span`:
 
-Hierarchy            | Block             | Description                                                  | Required
----------------------|-------------------|--------------------------------------------------------------|---------
-output               | [output][]        | Configures where to send received telemetry data.            | yes
-name                 | [name][]          | Configures how to rename a span and add attributes.          | no
-name > to_attributes | [to-attributes][] | Configuration to create attributes from a span name.         | no
-status               | [status][]        | Specifies a status which should be set for this span.        | no
-include              | [include][]       | Filter for data included in this processor's actions.        | no
-include > regexp     | [regexp][]        | Regex cache settings.                                        | no
-include > attribute  | [attribute][]     | A list of attributes to match against.                       | no
-include > resource   | [resource][]      | A list of items to match the resources against.              | no
-include > library    | [library][]       | A list of items to match the implementation library against. | no
-exclude              | [exclude][]       | Filter for data excluded from this processor's actions       | no
-exclude > regexp     | [regexp][]        | Regex cache settings.                                        | no
-exclude > attribute  | [attribute][]     | A list of attributes to match against.                       | no
-exclude > resource   | [resource][]      | A list of items to match the resources against.              | no
-exclude > library    | [library][]       | A list of items to match the implementation library against. | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy            | Block             | Description                                                                | Required |
+| -------------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| output               | [output][]        | Configures where to send received telemetry data.                          | yes      |
+| name                 | [name][]          | Configures how to rename a span and add attributes.                        | no       |
+| name > to_attributes | [to-attributes][] | Configuration to create attributes from a span name.                       | no       |
+| status               | [status][]        | Specifies a status which should be set for this span.                      | no       |
+| include              | [include][]       | Filter for data included in this processor's actions.                      | no       |
+| include > regexp     | [regexp][]        | Regex cache settings.                                                      | no       |
+| include > attribute  | [attribute][]     | A list of attributes to match against.                                     | no       |
+| include > resource   | [resource][]      | A list of items to match the resources against.                            | no       |
+| include > library    | [library][]       | A list of items to match the implementation library against.               | no       |
+| exclude              | [exclude][]       | Filter for data excluded from this processor's actions                     | no       |
+| exclude > regexp     | [regexp][]        | Regex cache settings.                                                      | no       |
+| exclude > attribute  | [attribute][]     | A list of attributes to match against.                                     | no       |
+| exclude > resource   | [resource][]      | A list of items to match the resources against.                            | no       |
+| exclude > library    | [library][]       | A list of items to match the implementation library against.               | no       |
+| debug_metrics        | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `include > attribute`
 refers to an `attribute` block defined inside an `include` block.
@@ -78,20 +78,21 @@ The `name` block configures how to rename a span and add attributes.
 
 The following attributes are supported:
 
-Name              | Type           | Description                                                      | Default | Required
-------------------|----------------|------------------------------------------------------------------|---------|---------
-`from_attributes` | `list(string)` | Attribute keys to pull values from, to generate a new span name. | `[]`    | no
-`separator` | `string` | Separates attributes values in the new span name. | `""` | no
+| Name              | Type           | Description                                                      | Default | Required |
+| ----------------- | -------------- | ---------------------------------------------------------------- | ------- | -------- |
+| `from_attributes` | `list(string)` | Attribute keys to pull values from, to generate a new span name. | `[]`    | no       |
+| `separator`       | `string`       | Separates attributes values in the new span name.                | `""`    | no       |
 
 Firstly `from_attributes` rules are applied, then [to-attributes][] are applied.
 At least one of these 2 fields must be set.
 
 `from_attributes` represents the attribute keys to pull the values from to
 generate the new span name:
-* All attribute keys are required in the span to rename a span.
-If any attribute is missing from the span, no rename will occur.
-* The new span name is constructed in order of the `from_attributes`
-specified in the configuration.
+
+- All attribute keys are required in the span to rename a span.
+  If any attribute is missing from the span, no rename will occur.
+- The new span name is constructed in order of the `from_attributes`
+  specified in the configuration.
 
 `separator` is the string used to separate attributes values in the new
 span name. If no value is set, no separator is used between attribute
@@ -104,12 +105,13 @@ The `to_attributes` block configures how to create attributes from a span name.
 
 The following attributes are supported:
 
-Name                | Type           | Description                                                          | Default | Required
---------------------|----------------|----------------------------------------------------------------------|---------|---------
-`rules`             | `list(string)` | A list of regex rules to extract attribute values from span name.    |         | yes
-`break_after_match` | `bool`         | Configures if processing of rules should stop after the first match. | `false` | no
+| Name                | Type           | Description                                                          | Default | Required |
+| ------------------- | -------------- | -------------------------------------------------------------------- | ------- | -------- |
+| `rules`             | `list(string)` | A list of regex rules to extract attribute values from span name.    |         | yes      |
+| `break_after_match` | `bool`         | Configures if processing of rules should stop after the first match. | `false` | no       |
 
 Each rule in the `rules` list is a regex pattern string.
+
 1. The span name is checked against each regex in the list.
 2. If it matches, then all named subexpressions of the regex are extracted as attributes and are added to the span.
 3. Each subexpression name becomes an attribute name and the subexpression matched portion becomes the attribute value.
@@ -128,15 +130,16 @@ The `status` block specifies a status which should be set for this span.
 
 The following attributes are supported:
 
-Name          | Type     | Description                                       | Default | Required
---------------|----------|---------------------------------------------------|---------|---------
-`code`        | `string` | A status code.                                    |         | yes
-`description` | `string` | An optional field documenting Error status codes. | `""`    | no
+| Name          | Type     | Description                                       | Default | Required |
+| ------------- | -------- | ------------------------------------------------- | ------- | -------- |
+| `code`        | `string` | A status code.                                    |         | yes      |
+| `description` | `string` | An optional field documenting Error status codes. | `""`    | no       |
 
 The supported values for `code` are:
-* `Ok`
-* `Error`
-* `Unset`
+
+- `Ok`
+- `Error`
+- `Unset`
 
 `description` should only be specified if `code` is set to `Error`.
 
@@ -147,12 +150,12 @@ The `include` block provides an option to include data being fed into the
 
 The following arguments are supported:
 
-Name         | Type           | Description                                          | Default | Required
--------------|----------------|------------------------------------------------------|---------|---------
-`match_type` | `string`       | Controls how items to match against are interpreted. |         | yes
-`services`   | `list(string)` | A list of items to match the service name against.   | `[]`    | no
-`span_names` | `list(string)` | A list of items to match the span name against.      | `[]`    | no
-`span_kinds` | `list(string)` | A list of items to match the span kind against.      | `[]`    | no
+| Name         | Type           | Description                                          | Default | Required |
+| ------------ | -------------- | ---------------------------------------------------- | ------- | -------- |
+| `match_type` | `string`       | Controls how items to match against are interpreted. |         | yes      |
+| `services`   | `list(string)` | A list of items to match the service name against.   | `[]`    | no       |
+| `span_names` | `list(string)` | A list of items to match the span name against.      | `[]`    | no       |
+| `span_kinds` | `list(string)` | A list of items to match the span kind against.      | `[]`    | no       |
 
 `match_type` is required and must be set to either `"regexp"` or `"strict"`.
 
@@ -168,12 +171,12 @@ The `exclude` block provides an option to exclude data from being fed into the
 
 The following arguments are supported:
 
-Name         | Type           | Description                                          | Default | Required
--------------|----------------|------------------------------------------------------|---------|---------
-`match_type` | `string`       | Controls how items to match against are interpreted. |         | yes
-`services`   | `list(string)` | A list of items to match the service name against.   | `[]`    | no
-`span_names` | `list(string)` | A list of items to match the span name against.      | `[]`    | no
-`span_kinds` | `list(string)` | A list of items to match the span kind against.      | `[]`    | no
+| Name         | Type           | Description                                          | Default | Required |
+| ------------ | -------------- | ---------------------------------------------------- | ------- | -------- |
+| `match_type` | `string`       | Controls how items to match against are interpreted. |         | yes      |
+| `services`   | `list(string)` | A list of items to match the service name against.   | `[]`    | no       |
+| `span_names` | `list(string)` | A list of items to match the span name against.      | `[]`    | no       |
+| `span_kinds` | `list(string)` | A list of items to match the span kind against.      | `[]`    | no       |
 
 `match_type` is required and must be set to either `"regexp"` or `"strict"`.
 
@@ -210,9 +213,9 @@ with a non-empty value for a valid configuration.
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` OTLP-formatted data for traces telemetry signals.
 Logs and metrics are not supported.
@@ -250,6 +253,7 @@ otelcol.processor.span "default" {
 
 For a span with the following attributes key/value pairs, the above
 configuration will change the span name to `"location::get::1234"`:
+
 ```json
 {
   "db.svc": "location",
@@ -261,6 +265,7 @@ configuration will change the span name to `"location::get::1234"`:
 For a span with the following attributes key/value pairs, the above
 configuration will not change the span name.
 This is because the attribute key `operation` isn't set:
+
 ```json
 {
   "db.svc": "location",
@@ -284,6 +289,7 @@ otelcol.processor.span "default" {
 
 For a span with the following attributes key/value pairs, the above
 configuration will change the span name to `"locationget1234"`:
+
 ```json
 {
   "db.svc": "location",
@@ -295,6 +301,7 @@ configuration will change the span name to `"locationget1234"`:
 ### Renaming a span name and adding attributes
 
 Example input and output using the configuration below:
+
 1. Let's assume input span name is `/api/v1/document/12345678/update`
 2. The span name will be changed to `/api/v1/document/{documentId}/update`
 3. A new attribute `"documentId"="12345678"` will be added to the span.
@@ -318,6 +325,7 @@ otelcol.processor.span "default" {
 This example renames the span name to `{operation_website}`
 and adds the attribute `{Key: operation_website, Value: <old span name> }`
 if the span has the following properties:
+
 - Service name contains the word `banks`.
 - The span name contains `/` anywhere in the string.
 - The span name is not `donot/change`.
@@ -385,6 +393,7 @@ otelcol.processor.span "default" {
   }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/otelcol/otelcol.processor.transform.md b/docs/sources/reference/components/otelcol/otelcol.processor.transform.md
index b833ecc6d0..35d3b117ea 100644
--- a/docs/sources/reference/components/otelcol/otelcol.processor.transform.md
+++ b/docs/sources/reference/components/otelcol/otelcol.processor.transform.md
@@ -12,49 +12,55 @@ title: otelcol.processor.transform
 components and modifies it using the [OpenTelemetry Transformation Language (OTTL)][OTTL].
 OTTL statements consist of [OTTL functions][], which act on paths.
 A path is a reference to a telemetry data such as:
-* Resource attributes.
-* Instrumentation scope name.
-* Span attributes.
+
+- Resource attributes.
+- Instrumentation scope name.
+- Span attributes.
 
 In addition to the [standard OTTL functions][OTTL functions],
 there is also a set of metrics-only functions:
-* [convert_sum_to_gauge][]
-* [convert_gauge_to_sum][]
-* [convert_summary_count_val_to_sum][]
-* [convert_summary_sum_val_to_sum][]
-* [copy_metric][]
-* [scale_metric][]
-* [aggregate_on_attributes][]
-* [convert_exponential_histogram_to_histogram][]
-* [aggregate_on_attribute_value][]
+
+- [convert_sum_to_gauge][]
+- [convert_gauge_to_sum][]
+- [convert_summary_count_val_to_sum][]
+- [convert_summary_sum_val_to_sum][]
+- [copy_metric][]
+- [scale_metric][]
+- [aggregate_on_attributes][]
+- [convert_exponential_histogram_to_histogram][]
+- [aggregate_on_attribute_value][]
 
 [OTTL][] statements can also contain constructs such as:
-* [Booleans][OTTL booleans]:
-  * `not true`
-  * `not IsMatch(name, "http_.*")`
-* [Boolean Expressions][OTTL boolean expressions] consisting of a `where` followed by one or more boolean values:
-  * `set(attributes["whose_fault"], "ours") where attributes["http.status"] == 500`
-  * `set(attributes["whose_fault"], "theirs") where attributes["http.status"] == 400 or attributes["http.status"] == 404`
-* [Math expressions][OTTL math expressions]:
-  * `1 + 1`
-  * `end_time_unix_nano - start_time_unix_nano`
-  * `sum([1, 2, 3, 4]) + (10 / 1) - 1`
+
+- [Booleans][OTTL booleans]:
+  - `not true`
+  - `not IsMatch(name, "http_.*")`
+- [Boolean Expressions][OTTL boolean expressions] consisting of a `where` followed by one or more boolean values:
+  - `set(attributes["whose_fault"], "ours") where attributes["http.status"] == 500`
+  - `set(attributes["whose_fault"], "theirs") where attributes["http.status"] == 400 or attributes["http.status"] == 404`
+- [Math expressions][OTTL math expressions]:
+  - `1 + 1`
+  - `end_time_unix_nano - start_time_unix_nano`
+  - `sum([1, 2, 3, 4]) + (10 / 1) - 1`
 
 {{< admonition type="note" >}}
 There are two ways of inputting strings in {{< param "PRODUCT_NAME" >}} configuration files:
-* Using quotation marks ([normal {{< param "PRODUCT_NAME" >}} syntax strings][strings]). Characters such as `\` and
+
+- Using quotation marks ([normal {{< param "PRODUCT_NAME" >}} syntax strings][strings]). Characters such as `\` and
   `"` must be escaped by preceding them with a `\` character.
-* Using backticks ([raw {{< param "PRODUCT_NAME" >}} syntax strings][raw-strings]). No characters must be escaped.
+- Using backticks ([raw {{< param "PRODUCT_NAME" >}} syntax strings][raw-strings]). No characters must be escaped.
   However, it's not possible to have backticks inside the string.
 
 For example, the OTTL statement `set(description, "Sum") where type == "Sum"` can be written as:
-* A normal {{< param "PRODUCT_NAME" >}} syntax string: `"set(description, \"Sum\") where type == \"Sum\""`.
-* A raw {{< param "PRODUCT_NAME" >}} syntax string: ``` `set(description, "Sum") where type == "Sum"` ```.
+
+- A normal {{< param "PRODUCT_NAME" >}} syntax string: `"set(description, \"Sum\") where type == \"Sum\""`.
+- A raw {{< param "PRODUCT_NAME" >}} syntax string: `` `set(description, "Sum") where type == "Sum"` ``.
 
 Raw strings are generally more convenient for writing OTTL statements.
 
 [strings]: ../../../../get-started/configuration-syntax/expressions/types_and_values/#strings
 [raw-strings]: ../../../../get-started/configuration-syntax/expressions/types_and_values/#raw-strings
+
 {{< /admonition >}}
 
 {{< admonition type="note" >}}
@@ -70,7 +76,7 @@ Some specific risks are given below, but this is not an exhaustive list.
 It is important to understand your data before using this processor.
 
 - [Unsound Transformations][]: Transformations between metric data types are not defined in the [metrics data model][].
-To use these functions, you must understand the incoming data and know that it can be meaningfully converted to a new metric data type or can be used to create new metrics.
+  To use these functions, you must understand the incoming data and know that it can be meaningfully converted to a new metric data type or can be used to create new metrics.
   - Although OTTL allows you to use the `set` function with `metric.data_type`,
     its implementation in the transform processor is a [no-op][].
     To modify a data type, you must use a specific function such as `convert_gauge_to_sum`.
@@ -80,10 +86,10 @@ To use these functions, you must understand the incoming data and know that it c
 - [Orphaned Telemetry][]: The processor allows you to modify `span_id`, `trace_id`, and `parent_span_id` for traces and `span_id`, and `trace_id` logs.
   Modifying these fields could lead to orphaned spans or logs.
 
-[Unsound Transformations]: https://github.com/open-telemetry/opentelemetry-collector/blob/{{< param "OTEL_VERSION" >}}/docs/standard-warnings.md#unsound-transformations
+[Unsound Transformations]: https://github.com/open-telemetry/opentelemetry-collector/blob/{{< param "OTEL*VERSION" >}}/docs/standard-warnings.md#unsound-transformations
 [Identity Conflict]: https://github.com/open-telemetry/opentelemetry-collector/blob/{{< param "OTEL_VERSION" >}}/docs/standard-warnings.md#identity-conflict
 [Orphaned Telemetry]: https://github.com/open-telemetry/opentelemetry-collector/blob/{{< param "OTEL_VERSION" >}}/docs/standard-warnings.md#orphaned-telemetry
-[no-op]: https://en.wikipedia.org/wiki/NOP_(code)
+[no-op]: https://en.wikipedia.org/wiki/NOP*(code)
 [metrics data model]: https://github.com/open-telemetry/opentelemetry-specification/blob/main//specification/metrics/data-model.md
 {{< /admonition >}}
 
@@ -103,34 +109,34 @@ otelcol.processor.transform "LABEL" {
 
 `otelcol.processor.transform` supports the following arguments:
 
-Name         | Type     | Description                                                        | Default       | Required
--------------|----------|--------------------------------------------------------------------|---------------|---------
-`error_mode` | `string` | How to react to errors if they occur while processing a statement. | `"propagate"` | no
+| Name         | Type     | Description                                                        | Default       | Required |
+| ------------ | -------- | ------------------------------------------------------------------ | ------------- | -------- |
+| `error_mode` | `string` | How to react to errors if they occur while processing a statement. | `"propagate"` | no       |
 
 The supported values for `error_mode` are:
-* `ignore`: Ignore errors returned by conditions, log them, and continue on to the next condition. This is the recommended mode.
-* `silent`: Ignore errors returned by conditions, do not log them, and continue on to the next condition.
-* `propagate`: Return the error up the pipeline. This will result in the payload being dropped from {{< param "PRODUCT_NAME" >}}.
+
+- `ignore`: Ignore errors returned by conditions, log them, and continue on to the next condition. This is the recommended mode.
+- `silent`: Ignore errors returned by conditions, do not log them, and continue on to the next condition.
+- `propagate`: Return the error up the pipeline. This will result in the payload being dropped from {{< param "PRODUCT_NAME" >}}.
 
 ## Blocks
 
 The following blocks are supported inside the definition of
 `otelcol.processor.transform`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-trace_statements | [trace_statements][] | Statements which transform traces. | no
-metric_statements | [metric_statements][] | Statements which transform metrics. | no
-log_statements | [log_statements][] | Statements which transform logs. | no
-output | [output][] | Configures where to send received telemetry data. | yes
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
+| Hierarchy         | Block                 | Description                                                                | Required |
+| ----------------- | --------------------- | -------------------------------------------------------------------------- | -------- |
+| trace_statements  | [trace_statements][]  | Statements which transform traces.                                         | no       |
+| metric_statements | [metric_statements][] | Statements which transform metrics.                                        | no       |
+| log_statements    | [log_statements][]    | Statements which transform logs.                                           | no       |
+| output            | [output][]            | Configures where to send received telemetry data.                          | yes      |
+| debug_metrics     | [debug_metrics][]     | Configures the metrics that this component generates to monitor its state. | no       |
 
 [trace_statements]: #trace_statements-block
 [metric_statements]: #metric_statements-block
 [log_statements]: #log_statements-block
 [output]: #output-block
 [debug_metrics]: #debug_metrics-block
-
 [OTTL Context]: #ottl-context
 
 ### trace_statements block
@@ -138,16 +144,17 @@ debug_metrics | [debug_metrics][] | Configures the metrics that this component g
 The `trace_statements` block specifies statements which transform trace telemetry signals.
 Multiple `trace_statements` blocks can be specified.
 
-Name         | Type           | Description                                                      | Default | Required
--------------|----------------|------------------------------------------------------------------|---------|---------
-`context`    | `string`       | OTTL Context to use when interpreting the associated statements. |         | yes
-`statements` | `list(string)` | A list of OTTL statements.                                       |         | yes
+| Name         | Type           | Description                                                      | Default | Required |
+| ------------ | -------------- | ---------------------------------------------------------------- | ------- | -------- |
+| `context`    | `string`       | OTTL Context to use when interpreting the associated statements. |         | yes      |
+| `statements` | `list(string)` | A list of OTTL statements.                                       |         | yes      |
 
 The supported values for `context` are:
-* `resource`: Use when interacting only with OTLP resources (for example, resource attributes).
-* `scope`: Use when interacting only with OTLP instrumentation scope (for example, the name of the instrumentation scope).
-* `span`: Use when interacting only with OTLP spans.
-* `spanevent`: Use when interacting only with OTLP span events.
+
+- `resource`: Use when interacting only with OTLP resources (for example, resource attributes).
+- `scope`: Use when interacting only with OTLP instrumentation scope (for example, the name of the instrumentation scope).
+- `span`: Use when interacting only with OTLP spans.
+- `spanevent`: Use when interacting only with OTLP span events.
 
 Refer to [OTTL Context][] for more information about how to use contexts.
 
@@ -156,16 +163,17 @@ Refer to [OTTL Context][] for more information about how to use contexts.
 The `metric_statements` block specifies statements which transform metric telemetry signals.
 Multiple `metric_statements` blocks can be specified.
 
-Name         | Type           | Description                                                      | Default | Required
--------------|----------------|------------------------------------------------------------------|---------|---------
-`context`    | `string`       | OTTL Context to use when interpreting the associated statements. |         | yes
-`statements` | `list(string)` | A list of OTTL statements.                                       |         | yes
+| Name         | Type           | Description                                                      | Default | Required |
+| ------------ | -------------- | ---------------------------------------------------------------- | ------- | -------- |
+| `context`    | `string`       | OTTL Context to use when interpreting the associated statements. |         | yes      |
+| `statements` | `list(string)` | A list of OTTL statements.                                       |         | yes      |
 
 The supported values for `context` are:
-* `resource`: Use when interacting only with OTLP resources (for example, resource attributes).
-* `scope`: Use when interacting only with OTLP instrumentation scope (for example, the name of the instrumentation scope).
-* `metric`: Use when interacting only with individual OTLP metrics.
-* `datapoint`: Use when interacting only with individual OTLP metric data points.
+
+- `resource`: Use when interacting only with OTLP resources (for example, resource attributes).
+- `scope`: Use when interacting only with OTLP instrumentation scope (for example, the name of the instrumentation scope).
+- `metric`: Use when interacting only with individual OTLP metrics.
+- `datapoint`: Use when interacting only with individual OTLP metric data points.
 
 Refer to [OTTL Context][] for more information about how to use contexts.
 
@@ -174,15 +182,16 @@ Refer to [OTTL Context][] for more information about how to use contexts.
 The `log_statements` block specifies statements which transform log telemetry signals.
 Multiple `log_statements` blocks can be specified.
 
-Name         | Type           | Description                                                      | Default | Required
--------------|----------------|------------------------------------------------------------------|---------|---------
-`context`    | `string`       | OTTL Context to use when interpreting the associated statements. |         | yes
-`statements` | `list(string)` | A list of OTTL statements.                                       |         | yes
+| Name         | Type           | Description                                                      | Default | Required |
+| ------------ | -------------- | ---------------------------------------------------------------- | ------- | -------- |
+| `context`    | `string`       | OTTL Context to use when interpreting the associated statements. |         | yes      |
+| `statements` | `list(string)` | A list of OTTL statements.                                       |         | yes      |
 
 The supported values for `context` are:
-* `resource`: Use when interacting only with OTLP resources (for example, resource attributes).
-* `scope`: Use when interacting only with OTLP instrumentation scope (for example, the name of the instrumentation scope).
-* `log`: Use when interacting only with OTLP logs.
+
+- `resource`: Use when interacting only with OTLP resources (for example, resource attributes).
+- `scope`: Use when interacting only with OTLP instrumentation scope (for example, the name of the instrumentation scope).
+- `log`: Use when interacting only with OTLP logs.
 
 Refer to [OTTL Context][] for more information about how to use contexts.
 
@@ -193,23 +202,24 @@ For example, statements associated with a `resource` context will be able to tra
 
 Each type of `context` defines its own paths and enums specific to that context.
 Refer to the OpenTelemetry documentation for a list of paths and enums for each context:
-* [resource][OTTL resource context]
-* [scope][OTTL scope context]
-* [span][OTTL span context]
-* [spanevent][OTTL spanevent context]
-* [log][OTTL log context]
-* [metric][OTTL metric context]
-* [datapoint][OTTL datapoint context]
 
+- [resource][OTTL resource context]
+- [scope][OTTL scope context]
+- [span][OTTL span context]
+- [spanevent][OTTL spanevent context]
+- [log][OTTL log context]
+- [metric][OTTL metric context]
+- [datapoint][OTTL datapoint context]
+
+Contexts **NEVER** supply access to individual items "lower" in the protobuf definition.
 
-Contexts __NEVER__ supply access to individual items "lower" in the protobuf definition.
-- This means statements associated to a `resource` __WILL NOT__ be able to access the underlying instrumentation scopes.
-- This means statements associated to a `scope` __WILL NOT__ be able to access the underlying telemetry slices (spans, metrics, or logs).
-- Similarly, statements associated to a `metric` __WILL NOT__ be able to access individual datapoints, but can access the entire datapoints slice.
-- Similarly, statements associated to a `span` __WILL NOT__ be able to access individual SpanEvents, but can access the entire SpanEvents slice.
+- This means statements associated to a `resource` **WILL NOT** be able to access the underlying instrumentation scopes.
+- This means statements associated to a `scope` **WILL NOT** be able to access the underlying telemetry slices (spans, metrics, or logs).
+- Similarly, statements associated to a `metric` **WILL NOT** be able to access individual datapoints, but can access the entire datapoints slice.
+- Similarly, statements associated to a `span` **WILL NOT** be able to access individual SpanEvents, but can access the entire SpanEvents slice.
 
 For practical purposes, this means that a context cannot make decisions on its telemetry based on telemetry "lower" in the structure.
-For example, __the following context statement is not possible__ because it attempts to use individual datapoint attributes in the condition of a statement associated to a `metric`:
+For example, **the following context statement is not possible** because it attempts to use individual datapoint attributes in the condition of a statement associated to a `metric`:
 
 ```alloy
 metric_statements {
@@ -220,13 +230,14 @@ metric_statements {
 }
 ```
 
-Context __ALWAYS__ supply access to the items "higher" in the protobuf definition that are associated to the telemetry being transformed.
+Context **ALWAYS** supply access to the items "higher" in the protobuf definition that are associated to the telemetry being transformed.
+
 - This means that statements associated to a `datapoint` have access to a datapoint's metric, instrumentation scope, and resource.
 - This means that statements associated to a `spanevent` have access to a spanevent's span, instrumentation scope, and resource.
 - This means that statements associated to a `span`/`metric`/`log` have access to the telemetry's instrumentation scope, and resource.
 - This means that statements associated to a `scope` have access to the scope's resource.
 
-For example, __the following context statement is possible__ because `datapoint` statements can access the datapoint's metric.
+For example, **the following context statement is possible** because `datapoint` statements can access the datapoint's metric.
 
 ```alloy
 metric_statements {
@@ -238,9 +249,10 @@ metric_statements {
 ```
 
 The protobuf definitions for OTLP signals are maintained on GitHub:
-* [traces][traces protobuf]
-* [metrics][metrics protobuf]
-* [logs][logs protobuf]
+
+- [traces][traces protobuf]
+- [metrics][metrics protobuf]
+- [logs][logs protobuf]
 
 Whenever possible, associate your statements to the context which the statement intens to transform.
 The contexts are nested, and the higher-level contexts don't have to iterate through any of the
@@ -259,9 +271,9 @@ span using the `span` context, it is more efficient to use the `resource` contex
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type               | Description
---------|--------------------|-----------------------------------------------------------------
-`input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to.
+| Name    | Type               | Description                                                      |
+| ------- | ------------------ | ---------------------------------------------------------------- |
+| `input` | `otelcol.Consumer` | A value that other components can use to send telemetry data to. |
 
 `input` accepts `otelcol.Consumer` data for any telemetry signal (metrics,
 logs, or traces).
@@ -547,12 +559,10 @@ otelcol.exporter.otlp "default" {
 
 [strings]: ../../../../get-started/configuration-syntax/expressions/types_and_values/#strings
 [raw-strings]: ../../../../get-started/configuration-syntax/expressions/types_and_values/#raw-strings
-
 [traces protobuf]: https://github.com/open-telemetry/opentelemetry-proto/blob/v1.0.0/opentelemetry/proto/trace/v1/trace.proto
 [metrics protobuf]: https://github.com/open-telemetry/opentelemetry-proto/blob/v1.0.0/opentelemetry/proto/metrics/v1/metrics.proto
 [logs protobuf]: https://github.com/open-telemetry/opentelemetry-proto/blob/v1.0.0/opentelemetry/proto/logs/v1/logs.proto
 
-
 [OTTL]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/{{< param "OTEL_VERSION" >}}/pkg/ottl/README.md
 [OTTL functions]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/{{< param "OTEL_VERSION" >}}/pkg/ottl/ottlfuncs/README.md
 [convert_sum_to_gauge]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/{{< param "OTEL_VERSION" >}}/processor/transformprocessor#convert_sum_to_gauge
diff --git a/docs/sources/reference/components/otelcol/otelcol.receiver.datadog.md b/docs/sources/reference/components/otelcol/otelcol.receiver.datadog.md
index d374118d86..bab12e26fd 100644
--- a/docs/sources/reference/components/otelcol/otelcol.receiver.datadog.md
+++ b/docs/sources/reference/components/otelcol/otelcol.receiver.datadog.md
@@ -31,13 +31,13 @@ otelcol.receiver.datadog "LABEL" {
 
 `otelcol.receiver.datadog` supports the following arguments:
 
-Name                     | Type       | Description                                                      | Default            | Required
-------------------------  | ---------- | --------------------------------------------------------------- | ------------------ | --------
-`endpoint`               | `string`   | `host:port` to listen for traffic on.                            | `"localhost:8126"` | no
-`max_request_body_size`  | `string`   | Maximum request body size the server will allow.                 | `20MiB`            | no
-`include_metadata`       | `boolean`  | Propagate incoming connection metadata to downstream consumers.  | `false`            | no
-`read_timeout`           | `duration` | Read timeout for requests of the HTTP server.                    | `"60s"`            | no
-`compression_algorithms` | `list(string)` | A list of compression algorithms the server can accept.      | `["", "gzip", "zstd", "zlib", "snappy", "deflate", "lz4"]` | no
+| Name                     | Type           | Description                                                     | Default                                                    | Required |
+| ------------------------ | -------------- | --------------------------------------------------------------- | ---------------------------------------------------------- | -------- |
+| `endpoint`               | `string`       | `host:port` to listen for traffic on.                           | `"localhost:8126"`                                         | no       |
+| `max_request_body_size`  | `string`       | Maximum request body size the server will allow.                | `20MiB`                                                    | no       |
+| `include_metadata`       | `boolean`      | Propagate incoming connection metadata to downstream consumers. | `false`                                                    | no       |
+| `read_timeout`           | `duration`     | Read timeout for requests of the HTTP server.                   | `"60s"`                                                    | no       |
+| `compression_algorithms` | `list(string)` | A list of compression algorithms the server can accept.         | `["", "gzip", "zstd", "zlib", "snappy", "deflate", "lz4"]` | no       |
 
 By default, `otelcol.receiver.datadog` listens for HTTP connections on `localhost`.
 To expose the HTTP server to other machines on your network, configure `endpoint` with the IP address to listen on, or `0.0.0.0:8126` to listen on all network interfaces.
@@ -47,12 +47,12 @@ To expose the HTTP server to other machines on your network, configure `endpoint
 The following blocks are supported inside the definition of
 `otelcol.receiver.datadog`:
 
-Hierarchy     | Block             | Description                                                                | Required
-------------- | ----------------- | -------------------------------------------------------------------------- | --------
-tls           | [tls][]           | Configures TLS for the HTTP server.                                        | no
-cors          | [cors][]          | Configures CORS for the HTTP server.                                       | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
-output        | [output][]        | Configures where to send received traces.                                  | yes
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| tls           | [tls][]           | Configures TLS for the HTTP server.                                        | no       |
+| cors          | [cors][]          | Configures CORS for the HTTP server.                                       | no       |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
+| output        | [output][]        | Configures where to send received traces.                                  | yes      |
 
 [tls]: #tls-block
 [cors]: #cors-block
@@ -71,19 +71,19 @@ The `cors` block configures CORS settings for an HTTP server.
 
 The following arguments are supported:
 
-Name              | Type           | Description                                              | Default                | Required
------------------ | -------------- | -------------------------------------------------------- | ---------------------- | --------
-`allowed_origins` | `list(string)` | Allowed values for the `Origin` header.                  | `[]`                   | no
-`allowed_headers` | `list(string)` | Accepted headers from CORS requests.                     | `["X-Requested-With"]` | no
-`max_age`         | `number`       | Configures the `Access-Control-Max-Age` response header. | `0`                    | no
+| Name              | Type           | Description                                              | Default                | Required |
+| ----------------- | -------------- | -------------------------------------------------------- | ---------------------- | -------- |
+| `allowed_origins` | `list(string)` | Allowed values for the `Origin` header.                  | `[]`                   | no       |
+| `allowed_headers` | `list(string)` | Accepted headers from CORS requests.                     | `["X-Requested-With"]` | no       |
+| `max_age`         | `number`       | Configures the `Access-Control-Max-Age` response header. | `0`                    | no       |
 
 The `allowed_headers` argument specifies which headers are acceptable from a
 CORS request. The following headers are always implicitly allowed:
 
-* `Accept`
-* `Accept-Language`
-* `Content-Type`
-* `Content-Language`
+- `Accept`
+- `Accept-Language`
+- `Content-Type`
+- `Content-Language`
 
 If `allowed_headers` includes `"*"`, all headers are permitted.
 
@@ -134,6 +134,7 @@ otelcol.exporter.otlp "default" {
   }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -142,7 +143,6 @@ otelcol.exporter.otlp "default" {
 
 - Components that export [OpenTelemetry `otelcol.Consumer`](../../../compatibility/#opentelemetry-otelcolconsumer-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/otelcol/otelcol.receiver.file_stats.md b/docs/sources/reference/components/otelcol/otelcol.receiver.file_stats.md
index 41e7784988..ea63519fe4 100644
--- a/docs/sources/reference/components/otelcol/otelcol.receiver.file_stats.md
+++ b/docs/sources/reference/components/otelcol/otelcol.receiver.file_stats.md
@@ -37,12 +37,12 @@ otelcol.receiver.file_stats "LABEL" {
 
 `otelcol.receiver.file_stats` supports the following arguments:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`include` | `string` | Glob path for paths to collect stats from. | | yes
-`collection_interval` | `duration` | How often to collect statistics. | `"1m"` | no
-`initial_delay` | `duration` | Initial time to wait before collecting statistics. | `"1s"` | no
-`timeout` | `duration` | Timeout for a collection; `0s` means no timeout. | `"0s"` | no
+| Name                  | Type       | Description                                        | Default | Required |
+| --------------------- | ---------- | -------------------------------------------------- | ------- | -------- |
+| `include`             | `string`   | Glob path for paths to collect stats from.         |         | yes      |
+| `collection_interval` | `duration` | How often to collect statistics.                   | `"1m"`  | no       |
+| `initial_delay`       | `duration` | Initial time to wait before collecting statistics. | `"1s"`  | no       |
+| `timeout`             | `duration` | Timeout for a collection; `0s` means no timeout.   | `"0s"`  | no       |
 
 `include` is a glob pattern that specifies which paths (files and folders) to collect stats from.
 A `*` character matches entries in a directory, while `**` includes subdirectories.
@@ -55,23 +55,23 @@ The timeout applies to the entire collection process across all paths matched by
 
 The following blocks are supported inside the definition of `otelcol.receiver.file_stats`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-metrics | [metrics][] | Configures which metrics will be sent to downstream components. | no
-metrics > file.atime | [file.atime][] | Configures the `file.atime` metric. | no
-metrics > file.count | [file.count][] | Configures the `file.count` metric. | no
-metrics > file.ctime | [file.ctime][] | Configures the `file.ctime` metric. | no
-metrics > file.mtime | [file.mtime][] | Configures the `file.mtime` metric. | no
-metrics > file.size | [file.size][] | Configures the `file.size` metric. | no
-resource_attributes | [resource_attributes][] | Configures resource attributes for metrics sent to downstream components. | no
-resource_attributes > file.name | [file.name][] | Configures the `file.name` resource attribute. | no
-resource_attributes > file.name > metrics_include | [metrics_include][] | Metrics to include the `file.name` resource attribute in. | no
-resource_attributes > file.name > metrics_exclude | [metrics_exclude][] | Metrics to exclude the `file.name` resource attribute from. | no
-resource_attributes > file.path | [file.path][] | Configures the `file.path` resource attribute. | no
-resource_attributes > file.path > metrics_include | [metrics_include][] | Metrics to include the `file.path` resource attribute in. | no
-resource_attributes > file.path > metrics_exclude | [metrics_exclude][] | Metrics to exclude the `file.path` resource attribute from. | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
-output | [output][] | Configures where to send received telemetry data. | yes
+| Hierarchy                                         | Block                   | Description                                                                | Required |
+| ------------------------------------------------- | ----------------------- | -------------------------------------------------------------------------- | -------- |
+| metrics                                           | [metrics][]             | Configures which metrics will be sent to downstream components.            | no       |
+| metrics > file.atime                              | [file.atime][]          | Configures the `file.atime` metric.                                        | no       |
+| metrics > file.count                              | [file.count][]          | Configures the `file.count` metric.                                        | no       |
+| metrics > file.ctime                              | [file.ctime][]          | Configures the `file.ctime` metric.                                        | no       |
+| metrics > file.mtime                              | [file.mtime][]          | Configures the `file.mtime` metric.                                        | no       |
+| metrics > file.size                               | [file.size][]           | Configures the `file.size` metric.                                         | no       |
+| resource_attributes                               | [resource_attributes][] | Configures resource attributes for metrics sent to downstream components.  | no       |
+| resource_attributes > file.name                   | [file.name][]           | Configures the `file.name` resource attribute.                             | no       |
+| resource_attributes > file.name > metrics_include | [metrics_include][]     | Metrics to include the `file.name` resource attribute in.                  | no       |
+| resource_attributes > file.name > metrics_exclude | [metrics_exclude][]     | Metrics to exclude the `file.name` resource attribute from.                | no       |
+| resource_attributes > file.path                   | [file.path][]           | Configures the `file.path` resource attribute.                             | no       |
+| resource_attributes > file.path > metrics_include | [metrics_include][]     | Metrics to include the `file.path` resource attribute in.                  | no       |
+| resource_attributes > file.path > metrics_exclude | [metrics_exclude][]     | Metrics to exclude the `file.path` resource attribute from.                | no       |
+| debug_metrics                                     | [debug_metrics][]       | Configures the metrics that this component generates to monitor its state. | no       |
+| output                                            | [output][]              | Configures where to send received telemetry data.                          | yes      |
 
 [metrics]: #metrics-block
 [file.atime]: #fileatime-block
@@ -92,11 +92,11 @@ output | [output][] | Configures where to send received telemetry data. | yes
 The `metrics` block configures the set of metrics that will be sent to downstream components.
 It accepts no arguments, but contains other blocks for individual metrics:
 
-* The [file.atime][] block
-* The [file.count][] block
-* The [file.ctime][] block
-* The [file.mtime][] block
-* The [file.size][] block
+- The [file.atime][] block
+- The [file.count][] block
+- The [file.ctime][] block
+- The [file.mtime][] block
+- The [file.size][] block
 
 Refer to the documentation of individual metric blocks for whether that metric is enabled by default.
 
@@ -111,18 +111,18 @@ Refer to the documentation of individual metric blocks for whether that metric i
 The `file.atime` block configures the `file.atime` metric.
 `file.atime` tracks the elapsed time since the last access of the file or folder in Unix seconds since the epoch.
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `boolean` | Whether to collect the `file.atime` metric. | `false` | no
+| Name      | Type      | Description                                 | Default | Required |
+| --------- | --------- | ------------------------------------------- | ------- | -------- |
+| `enabled` | `boolean` | Whether to collect the `file.atime` metric. | `false` | no       |
 
 ### file.count block
 
 The `file.count` block configures the `file.count` metric.
 `file.count` tracks the number of files and folders in the specified glob pattern.
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `boolean` | Whether to collect the `file.count` metric. | `false` | no
+| Name      | Type      | Description                                 | Default | Required |
+| --------- | --------- | ------------------------------------------- | ------- | -------- |
+| `enabled` | `boolean` | Whether to collect the `file.count` metric. | `false` | no       |
 
 ### file.ctime block
 
@@ -130,35 +130,35 @@ The `file.ctime` block configures the `file.ctime` metric.
 `file.ctime` tracks the elapsed time since the last change of the file or folder in Unix seconds since the epoch.
 Changes include permissions, ownership, and timestamps.
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `boolean` | Whether to collect the `file.ctime` metric. | `false` | no
+| Name      | Type      | Description                                 | Default | Required |
+| --------- | --------- | ------------------------------------------- | ------- | -------- |
+| `enabled` | `boolean` | Whether to collect the `file.ctime` metric. | `false` | no       |
 
 ### file.mtime block
 
 The `file.mtime` block configures the `file.mtime` metric.
 `file.mtime` tracks the elapsed time since the last modification of the file or folder in Unix seconds since the epoch.
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `boolean` | Whether to collect the `file.mtime` metric. | `true` | no
+| Name      | Type      | Description                                 | Default | Required |
+| --------- | --------- | ------------------------------------------- | ------- | -------- |
+| `enabled` | `boolean` | Whether to collect the `file.mtime` metric. | `true`  | no       |
 
 ### file.size block
 
 The `file.size` block configures the `file.size` metric.
 `file.size` tracks the size of the file or folder in bytes.
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `boolean` | Whether to collect the `file.size` metric. | `true` | no
+| Name      | Type      | Description                                | Default | Required |
+| --------- | --------- | ------------------------------------------ | ------- | -------- |
+| `enabled` | `boolean` | Whether to collect the `file.size` metric. | `true`  | no       |
 
 ### resource_attributes block
 
 The `resource_attributes` block configures resource attributes for metrics sent to downstream components.
 It accepts no arguments, but contains other blocks for configuring individual resource attributes:
 
-* The [file.name][] block
-* The [file.path][] block
+- The [file.name][] block
+- The [file.path][] block
 
 Refer to the documentation of individual resource attribute blocks for whether that resource attribute is enabled by default.
 
@@ -169,9 +169,9 @@ Refer to the documentation of individual resource attribute blocks for whether t
 
 The `file.name` block configures the `file.name` resource attribute.
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `boolean` | Whether to include the `file.name` resource attribute. | `true` | no
+| Name      | Type      | Description                                            | Default | Required |
+| --------- | --------- | ------------------------------------------------------ | ------- | -------- |
+| `enabled` | `boolean` | Whether to include the `file.name` resource attribute. | `true`  | no       |
 
 When `enabled` is true, the `file.name` attribute is included in all metrics.
 
@@ -183,10 +183,10 @@ If a given metric matches all the `metrics_include` blocks and none of the `metr
 The `metrics_include` block configures a filter for matching metrics.
 The `metrics_include` block may be specified multiple times.
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`strict` | `string` | The exact name of the metric to include. | | yes*
-`regexp` | `string` | A regular expression for the metrics to include. | | yes*
+| Name     | Type     | Description                                      | Default | Required |
+| -------- | -------- | ------------------------------------------------ | ------- | -------- |
+| `strict` | `string` | The exact name of the metric to include.         |         | yes\*    |
+| `regexp` | `string` | A regular expression for the metrics to include. |         | yes\*    |
 
 Exactly one of `strict` or `regexp` must be specified.
 
@@ -195,10 +195,10 @@ Exactly one of `strict` or `regexp` must be specified.
 The `metrics_exclude` block configures a filter for excluding metrics.
 The `metrics_exclude` block may be specified multiple times.
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`strict` | `string` | The exact name of the metric to exclude. | | yes*
-`regexp` | `string` | A regular expression for the metrics to exclude. | | yes*
+| Name     | Type     | Description                                      | Default | Required |
+| -------- | -------- | ------------------------------------------------ | ------- | -------- |
+| `strict` | `string` | The exact name of the metric to exclude.         |         | yes\*    |
+| `regexp` | `string` | A regular expression for the metrics to exclude. |         | yes\*    |
 
 Exactly one of `strict` or `regexp` must be specified.
 
@@ -206,9 +206,9 @@ Exactly one of `strict` or `regexp` must be specified.
 
 The `file.path` block configures the `file.path` resource attribute.
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `boolean` | Whether to include the `file.path` resource attribute. | `false` | no
+| Name      | Type      | Description                                            | Default | Required |
+| --------- | --------- | ------------------------------------------------------ | ------- | -------- |
+| `enabled` | `boolean` | Whether to include the `file.path` resource attribute. | `false` | no       |
 
 When `enabled` is true, the `file.path` attribute is included in all metrics.
 The children blocks `metrics_include` and `metrics_exclude` can be used to further filter which metrics are given the `file.path` attribute.
@@ -230,8 +230,8 @@ If a given metric matches all the `metrics_include` blocks and none of the `metr
 
 `otelcol.receiver.file_stats` is reported as unhealthy when:
 
-* It is given an invalid configuration.
-* It runs on an unsupported operating system.
+- It is given an invalid configuration.
+- It runs on an unsupported operating system.
 
 ## Debug information
 
@@ -271,7 +271,6 @@ otelcol.exporter.otlp "default" {
 
 - Components that export [OpenTelemetry `otelcol.Consumer`](../../../compatibility/#opentelemetry-otelcolconsumer-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/otelcol/otelcol.receiver.jaeger.md b/docs/sources/reference/components/otelcol/otelcol.receiver.jaeger.md
index b6685614cc..d94503f448 100644
--- a/docs/sources/reference/components/otelcol/otelcol.receiver.jaeger.md
+++ b/docs/sources/reference/components/otelcol/otelcol.receiver.jaeger.md
@@ -45,21 +45,21 @@ otelcol.receiver.jaeger "LABEL" {
 The following blocks are supported inside the definition of
 `otelcol.receiver.jaeger`:
 
-Hierarchy                                         | Block                  | Description                                                                | Required
---------------------------------------------------|------------------------|----------------------------------------------------------------------------|---------
-protocols                                         | [protocols][]          | Configures the protocols the component can accept traffic over.            | yes
-protocols > grpc                                  | [grpc][]               | Configures a Jaeger gRPC server to receive traces.                         | no
-protocols > grpc > tls                            | [tls][]                | Configures TLS for the gRPC server.                                        | no
-protocols > grpc > keepalive                      | [keepalive][]          | Configures keepalive settings for the configured server.                   | no
-protocols > grpc > keepalive > server_parameters  | [server_parameters][]  | Server parameters used to configure keepalive settings.                    | no
-protocols > grpc > keepalive > enforcement_policy | [enforcement_policy][] | Enforcement policy for keepalive settings.                                 | no
-protocols > thrift_http                           | [thrift_http][]        | Configures a Thrift HTTP server to receive traces.                         | no
-protocols > thrift_http > tls                     | [tls][]                | Configures TLS for the Thrift HTTP server.                                 | no
-protocols > thrift_http > cors                    | [cors][]               | Configures CORS for the Thrift HTTP server.                                | no
-protocols > thrift_binary                         | [thrift_binary][]      | Configures a Thrift binary UDP server to receive traces.                   | no
-protocols > thrift_compact                        | [thrift_compact][]     | Configures a Thrift compact UDP server to receive traces.                  | no
-debug_metrics                                     | [debug_metrics][]      | Configures the metrics that this component generates to monitor its state. | no
-output                                            | [output][]             | Configures where to send received telemetry data.                          | yes
+| Hierarchy                                         | Block                  | Description                                                                | Required |
+| ------------------------------------------------- | ---------------------- | -------------------------------------------------------------------------- | -------- |
+| protocols                                         | [protocols][]          | Configures the protocols the component can accept traffic over.            | yes      |
+| protocols > grpc                                  | [grpc][]               | Configures a Jaeger gRPC server to receive traces.                         | no       |
+| protocols > grpc > tls                            | [tls][]                | Configures TLS for the gRPC server.                                        | no       |
+| protocols > grpc > keepalive                      | [keepalive][]          | Configures keepalive settings for the configured server.                   | no       |
+| protocols > grpc > keepalive > server_parameters  | [server_parameters][]  | Server parameters used to configure keepalive settings.                    | no       |
+| protocols > grpc > keepalive > enforcement_policy | [enforcement_policy][] | Enforcement policy for keepalive settings.                                 | no       |
+| protocols > thrift_http                           | [thrift_http][]        | Configures a Thrift HTTP server to receive traces.                         | no       |
+| protocols > thrift_http > tls                     | [tls][]                | Configures TLS for the Thrift HTTP server.                                 | no       |
+| protocols > thrift_http > cors                    | [cors][]               | Configures CORS for the Thrift HTTP server.                                | no       |
+| protocols > thrift_binary                         | [thrift_binary][]      | Configures a Thrift binary UDP server to receive traces.                   | no       |
+| protocols > thrift_compact                        | [thrift_compact][]     | Configures a Thrift compact UDP server to receive traces.                  | no       |
+| debug_metrics                                     | [debug_metrics][]      | Configures the metrics that this component generates to monitor its state. | no       |
+| output                                            | [output][]             | Configures where to send received telemetry data.                          | yes      |
 
 The `>` symbol indicates deeper levels of nesting.
 For example, `protocols > grpc` refers to a `grpc` block defined inside a `protocols` block.
@@ -92,15 +92,15 @@ If the `grpc` block isn't provided, a gRPC server isn't started.
 
 The following arguments are supported:
 
-Name                     | Type      | Description                                                                | Default           | Required
--------------------------|-----------|----------------------------------------------------------------------------|-------------------|---------
-`endpoint`               | `string`  | `host:port` to listen for traffic on.                                      | `"0.0.0.0:14250"` | no
-`transport`              | `string`  | Transport to use for the gRPC server.                                      | `"tcp"`           | no
-`max_recv_msg_size`      | `string`  | Maximum size of messages the server will accept.                           | `"4MiB`"          | no
-`max_concurrent_streams` | `number`  | Limit the number of concurrent streaming RPC calls.                        |                   | no
-`read_buffer_size`       | `string`  | Size of the read buffer the gRPC server will use for reading from clients. | `"512KiB"`        | no
-`write_buffer_size`      | `string`  | Size of the write buffer the gRPC server will use for writing to clients.  |                   | no
-`include_metadata`       | `boolean` | Propagate incoming connection metadata to downstream consumers.            |                   | no
+| Name                     | Type      | Description                                                                | Default           | Required |
+| ------------------------ | --------- | -------------------------------------------------------------------------- | ----------------- | -------- |
+| `endpoint`               | `string`  | `host:port` to listen for traffic on.                                      | `"0.0.0.0:14250"` | no       |
+| `transport`              | `string`  | Transport to use for the gRPC server.                                      | `"tcp"`           | no       |
+| `max_recv_msg_size`      | `string`  | Maximum size of messages the server will accept.                           | `"4MiB`"          | no       |
+| `max_concurrent_streams` | `number`  | Limit the number of concurrent streaming RPC calls.                        |                   | no       |
+| `read_buffer_size`       | `string`  | Size of the read buffer the gRPC server will use for reading from clients. | `"512KiB"`        | no       |
+| `write_buffer_size`      | `string`  | Size of the write buffer the gRPC server will use for writing to clients.  |                   | no       |
+| `include_metadata`       | `boolean` | Propagate incoming connection metadata to downstream consumers.            |                   | no       |
 
 ### tls block
 
@@ -121,13 +121,13 @@ The `server_parameters` block controls keepalive and maximum age settings for gR
 
 The following arguments are supported:
 
-Name                       | Type       | Description                                                                         | Default      | Required
----------------------------|------------|-------------------------------------------------------------------------------------|--------------|---------
-`max_connection_idle`      | `duration` | Maximum age for idle connections.                                                   | `"infinity"` | no
-`max_connection_age`       | `duration` | Maximum age for non-idle connections.                                               | `"infinity"` | no
-`max_connection_age_grace` | `duration` | Time to wait before forcibly closing connections.                                   | `"infinity"` | no
-`time`                     | `duration` | How often to ping inactive clients to check for liveness.                           | `"2h"`       | no
-`timeout`                  | `duration` | Time to wait before closing inactive clients that don't respond to liveness checks. | `"20s"`      | no
+| Name                       | Type       | Description                                                                         | Default      | Required |
+| -------------------------- | ---------- | ----------------------------------------------------------------------------------- | ------------ | -------- |
+| `max_connection_idle`      | `duration` | Maximum age for idle connections.                                                   | `"infinity"` | no       |
+| `max_connection_age`       | `duration` | Maximum age for non-idle connections.                                               | `"infinity"` | no       |
+| `max_connection_age_grace` | `duration` | Time to wait before forcibly closing connections.                                   | `"infinity"` | no       |
+| `time`                     | `duration` | How often to ping inactive clients to check for liveness.                           | `"2h"`       | no       |
+| `timeout`                  | `duration` | Time to wait before closing inactive clients that don't respond to liveness checks. | `"20s"`      | no       |
 
 ### enforcement_policy block
 
@@ -136,10 +136,10 @@ The server closes connections from clients that violate the configured policy.
 
 The following arguments are supported:
 
-Name                    | Type       | Description                                                             | Default | Required
-------------------------|------------|-------------------------------------------------------------------------|---------|---------
-`min_time`              | `duration` | Minimum time clients should wait before sending a keepalive ping.       | `"5m"`  | no
-`permit_without_stream` | `boolean`  | Allow clients to send keepalive pings when there are no active streams. | `false` | no
+| Name                    | Type       | Description                                                             | Default | Required |
+| ----------------------- | ---------- | ----------------------------------------------------------------------- | ------- | -------- |
+| `min_time`              | `duration` | Minimum time clients should wait before sending a keepalive ping.       | `"5m"`  | no       |
+| `permit_without_stream` | `boolean`  | Allow clients to send keepalive pings when there are no active streams. | `false` | no       |
 
 ### thrift_http block
 
@@ -148,12 +148,12 @@ If the `thrift_http` block isn't specified, an HTTP server isn't started.
 
 The following arguments are supported:
 
-Name                     | Type      | Description                                                     | Default           | Required
--------------------------|-----------|-----------------------------------------------------------------|-------------------|---------
-`endpoint`               | `string`  | `host:port` to listen for traffic on.                           | `"0.0.0.0:14268"` | no
-`max_request_body_size`  | `string`  | Maximum request body size the server will allow.                | `20MiB`           | no
-`include_metadata`       | `boolean` | Propagate incoming connection metadata to downstream consumers. |                   | no
-`compression_algorithms` | `list(string)` | A list of compression algorithms the server can accept.    | `["", "gzip", "zstd", "zlib", "snappy", "deflate", "lz4"]` | no
+| Name                     | Type           | Description                                                     | Default                                                    | Required |
+| ------------------------ | -------------- | --------------------------------------------------------------- | ---------------------------------------------------------- | -------- |
+| `endpoint`               | `string`       | `host:port` to listen for traffic on.                           | `"0.0.0.0:14268"`                                          | no       |
+| `max_request_body_size`  | `string`       | Maximum request body size the server will allow.                | `20MiB`                                                    | no       |
+| `include_metadata`       | `boolean`      | Propagate incoming connection metadata to downstream consumers. |                                                            | no       |
+| `compression_algorithms` | `list(string)` | A list of compression algorithms the server can accept.         | `["", "gzip", "zstd", "zlib", "snappy", "deflate", "lz4"]` | no       |
 
 ### cors block
 
@@ -161,19 +161,19 @@ The `cors` block configures CORS settings for an HTTP server.
 
 The following arguments are supported:
 
-Name              | Type           | Description                                              | Default                | Required
-------------------|----------------|----------------------------------------------------------|------------------------|---------
-`allowed_origins` | `list(string)` | Allowed values for the `Origin` header.                  |                        | no
-`allowed_headers` | `list(string)` | Accepted headers from CORS requests.                     | `["X-Requested-With"]` | no
-`max_age`         | `number`       | Configures the `Access-Control-Max-Age` response header. |                        | no
+| Name              | Type           | Description                                              | Default                | Required |
+| ----------------- | -------------- | -------------------------------------------------------- | ---------------------- | -------- |
+| `allowed_origins` | `list(string)` | Allowed values for the `Origin` header.                  |                        | no       |
+| `allowed_headers` | `list(string)` | Accepted headers from CORS requests.                     | `["X-Requested-With"]` | no       |
+| `max_age`         | `number`       | Configures the `Access-Control-Max-Age` response header. |                        | no       |
 
 The `allowed_headers` specifies which headers are acceptable from a CORS request.
 The following headers are always implicitly allowed:
 
-* `Accept`
-* `Accept-Language`
-* `Content-Type`
-* `Content-Language`
+- `Accept`
+- `Accept-Language`
+- `Content-Type`
+- `Content-Language`
 
 If `allowed_headers` includes `"*"`, all headers are permitted.
 
@@ -184,13 +184,13 @@ If the `thrift_binary` block isn't provided, a UDP server isn't started.
 
 The following arguments are supported:
 
-Name                 | Type     | Description                                                    | Default          | Required
----------------------|----------|----------------------------------------------------------------|------------------|---------
-`endpoint`           | `string` | `host:port` to listen for traffic on.                          | `"0.0.0.0:6832"` | no
-`queue_size`         | `number` | Maximum number of UDP messages that can be queued at once.     | `1000`           | no
-`max_packet_size`    | `string` | Maximum UDP message size.                                      | `"65KiB"`        | no
-`workers`            | `number` | Number of workers to concurrently read from the message queue. | `10`             | no
-`socket_buffer_size` | `string` | Buffer to allocate for the UDP socket.                         |                  | no
+| Name                 | Type     | Description                                                    | Default          | Required |
+| -------------------- | -------- | -------------------------------------------------------------- | ---------------- | -------- |
+| `endpoint`           | `string` | `host:port` to listen for traffic on.                          | `"0.0.0.0:6832"` | no       |
+| `queue_size`         | `number` | Maximum number of UDP messages that can be queued at once.     | `1000`           | no       |
+| `max_packet_size`    | `string` | Maximum UDP message size.                                      | `"65KiB"`        | no       |
+| `workers`            | `number` | Number of workers to concurrently read from the message queue. | `10`             | no       |
+| `socket_buffer_size` | `string` | Buffer to allocate for the UDP socket.                         |                  | no       |
 
 ### thrift_compact block
 
@@ -199,13 +199,13 @@ If the `thrift_compact` block isn't provided, a UDP server isn't started.
 
 The following arguments are supported:
 
-Name                 | Type     | Description                                                    | Default          | Required
----------------------|----------|----------------------------------------------------------------|------------------|---------
-`endpoint`           | `string` | `host:port` to listen for traffic on.                          | `"0.0.0.0:6831"` | no
-`queue_size`         | `number` | Maximum number of UDP messages that can be queued at once.     | `1000`           | no
-`max_packet_size`    | `string` | Maximum UDP message size.                                      | `"65KiB"`        | no
-`workers`            | `number` | Number of workers to concurrently read from the message queue. | `10`             | no
-`socket_buffer_size` | `string` | Buffer to allocate for the UDP socket.                         |                  | no
+| Name                 | Type     | Description                                                    | Default          | Required |
+| -------------------- | -------- | -------------------------------------------------------------- | ---------------- | -------- |
+| `endpoint`           | `string` | `host:port` to listen for traffic on.                          | `"0.0.0.0:6831"` | no       |
+| `queue_size`         | `number` | Maximum number of UDP messages that can be queued at once.     | `1000`           | no       |
+| `max_packet_size`    | `string` | Maximum UDP message size.                                      | `"65KiB"`        | no       |
+| `workers`            | `number` | Number of workers to concurrently read from the message queue. | `10`             | no       |
+| `socket_buffer_size` | `string` | Buffer to allocate for the UDP socket.                         |                  | no       |
 
 ### debug_metrics block
 
@@ -270,7 +270,6 @@ otelcol.exporter.otlp "default" {
 
 - Components that export [OpenTelemetry `otelcol.Consumer`](../../../compatibility/#opentelemetry-otelcolconsumer-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/otelcol/otelcol.receiver.kafka.md b/docs/sources/reference/components/otelcol/otelcol.receiver.kafka.md
index 0de0429093..e8497df707 100644
--- a/docs/sources/reference/components/otelcol/otelcol.receiver.kafka.md
+++ b/docs/sources/reference/components/otelcol/otelcol.receiver.kafka.md
@@ -38,50 +38,50 @@ otelcol.receiver.kafka "LABEL" {
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`brokers` | `array(string)` | Kafka brokers to connect to. | | yes
-`protocol_version` | `string` | Kafka protocol version to use. | | yes
-`topic` | `string` | Kafka topic to read from. | _See below_ | no
-`encoding` | `string` | Encoding of payload read from Kafka. | `"otlp_proto"` | no
-`group_id` | `string` | Consumer group to consume messages from. | `"otel-collector"` | no
-`client_id` | `string` | Consumer client ID to use. | `"otel-collector"` | no
-`initial_offset` | `string` | Initial offset to use if no offset was previously committed. | `"latest"` | no
-`resolve_canonical_bootstrap_servers_only` | `bool` | Whether to resolve then reverse-lookup broker IPs during startup. | `"false"` | no
-`session_timeout` | `duration` | The request timeout for detecting client failures when using Kafka group management. | `"10s"` | no
-`heartbeat_interval` | `duration` | The expected time between heartbeats to the consumer coordinator when using Kafka group management. | `"3s"` | no
-`min_fetch_size` | `int` | The minimum number of message bytes to fetch in a request. | `1` | no
-`default_fetch_size` | `int` | The default number of message bytes to fetch in a request. | `1048576` | no
-`max_fetch_size` | `int` | The maximum number of message bytes to fetch in a request. | `0` | no
+| Name                                       | Type            | Description                                                                                         | Default            | Required |
+| ------------------------------------------ | --------------- | --------------------------------------------------------------------------------------------------- | ------------------ | -------- |
+| `brokers`                                  | `array(string)` | Kafka brokers to connect to.                                                                        |                    | yes      |
+| `protocol_version`                         | `string`        | Kafka protocol version to use.                                                                      |                    | yes      |
+| `topic`                                    | `string`        | Kafka topic to read from.                                                                           | _See below_        | no       |
+| `encoding`                                 | `string`        | Encoding of payload read from Kafka.                                                                | `"otlp_proto"`     | no       |
+| `group_id`                                 | `string`        | Consumer group to consume messages from.                                                            | `"otel-collector"` | no       |
+| `client_id`                                | `string`        | Consumer client ID to use.                                                                          | `"otel-collector"` | no       |
+| `initial_offset`                           | `string`        | Initial offset to use if no offset was previously committed.                                        | `"latest"`         | no       |
+| `resolve_canonical_bootstrap_servers_only` | `bool`          | Whether to resolve then reverse-lookup broker IPs during startup.                                   | `"false"`          | no       |
+| `session_timeout`                          | `duration`      | The request timeout for detecting client failures when using Kafka group management.                | `"10s"`            | no       |
+| `heartbeat_interval`                       | `duration`      | The expected time between heartbeats to the consumer coordinator when using Kafka group management. | `"3s"`             | no       |
+| `min_fetch_size`                           | `int`           | The minimum number of message bytes to fetch in a request.                                          | `1`                | no       |
+| `default_fetch_size`                       | `int`           | The default number of message bytes to fetch in a request.                                          | `1048576`          | no       |
+| `max_fetch_size`                           | `int`           | The maximum number of message bytes to fetch in a request.                                          | `0`                | no       |
 
 For `max_fetch_size`, the value `0` means no limit.
 
 If `topic` is not set, different topics will be used for different telemetry signals:
 
-* Metrics will be received from an `otlp_metrics` topic.
-* Traces will be received from an `otlp_spans` topic.
-* Logs will be received from an `otlp_logs` topic.
+- Metrics will be received from an `otlp_metrics` topic.
+- Traces will be received from an `otlp_spans` topic.
+- Logs will be received from an `otlp_logs` topic.
 
 If `topic` is set to a specific value, then only the signal type that corresponds to the data stored in the topic must be set in the output block.
-For example, if `topic` is set to `"my_telemetry"`, then the `"my_telemetry"` topic can only contain either metrics, logs, or traces. 
+For example, if `topic` is set to `"my_telemetry"`, then the `"my_telemetry"` topic can only contain either metrics, logs, or traces.
 If it contains only metrics, then `otelcol.receiver.kafka` should be configured to output only metrics.
 
 The `encoding` argument determines how to decode messages read from Kafka.
 `encoding` supports encoding extensions. It tries to load an encoding extension and falls back to internal encodings if no extension was loaded.
 Available internal encodings:
 
-* `"otlp_proto"`: Decode messages as OTLP protobuf.
-* `"otlp_json"` : Decode messages as OTLP JSON.
-* `"jaeger_proto"`: Decode messages as a single Jaeger protobuf span.
-* `"jaeger_json"`: Decode messages as a single Jaeger JSON span.
-* `"zipkin_proto"`: Decode messages as a list of Zipkin protobuf spans.
-* `"zipkin_json"`: Decode messages as a list of Zipkin JSON spans.
-* `"zipkin_thrift"`: Decode messages as a list of Zipkin Thrift spans.
-* `"raw"`: Copy the log message bytes into the body of a log record.
-* `"text"`: Decode the log message as text and insert it into the body of a log record.
+- `"otlp_proto"`: Decode messages as OTLP protobuf.
+- `"otlp_json"` : Decode messages as OTLP JSON.
+- `"jaeger_proto"`: Decode messages as a single Jaeger protobuf span.
+- `"jaeger_json"`: Decode messages as a single Jaeger JSON span.
+- `"zipkin_proto"`: Decode messages as a list of Zipkin protobuf spans.
+- `"zipkin_json"`: Decode messages as a list of Zipkin JSON spans.
+- `"zipkin_thrift"`: Decode messages as a list of Zipkin Thrift spans.
+- `"raw"`: Copy the log message bytes into the body of a log record.
+- `"text"`: Decode the log message as text and insert it into the body of a log record.
   By default, UTF-8 is used to decode. A different encoding can be chosen by using `text_<ENCODING>`. For example, `text_utf-8` or `text_shift_jis`.
-* `"json"`: Decode the JSON payload and insert it into the body of a log record.
-* `"azure_resource_logs"`: The payload is converted from Azure Resource Logs format to an OTLP log.
+- `"json"`: Decode the JSON payload and insert it into the body of a log record.
+- `"azure_resource_logs"`: The payload is converted from Azure Resource Logs format to an OTLP log.
 
 `"otlp_proto"` must be used to read all telemetry types from Kafka; other
 encodings are signal-specific.
@@ -93,21 +93,21 @@ encodings are signal-specific.
 The following blocks are supported inside the definition of
 `otelcol.receiver.kafka`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-authentication | [authentication][] | Configures authentication for connecting to Kafka brokers. | no
-authentication > plaintext | [plaintext][] | Authenticates against Kafka brokers with plaintext. | no
-authentication > sasl | [sasl][] | Authenticates against Kafka brokers with SASL. | no
-authentication > sasl > aws_msk | [aws_msk][] | Additional SASL parameters when using AWS_MSK_IAM. | no
-authentication > tls | [tls][] | Configures TLS for connecting to the Kafka brokers. | no
-authentication > kerberos | [kerberos][] | Authenticates against Kafka brokers with Kerberos. | no
-metadata | [metadata][] | Configures how to retrieve metadata from Kafka brokers. | no
-metadata > retry | [retry][] | Configures how to retry metadata retrieval. | no
-autocommit | [autocommit][] | Configures how to automatically commit updated topic offsets to back to the Kafka brokers. | no
-message_marking | [message_marking][] | Configures when Kafka messages are marked as read. | no
-header_extraction | [header_extraction][] | Extract headers from Kafka records. | no
-debug_metrics | [debug_metrics][] | Configures the metrics which this component generates to monitor its state. | no
-output | [output][] | Configures where to send received telemetry data. | yes
+| Hierarchy                       | Block                 | Description                                                                                | Required |
+| ------------------------------- | --------------------- | ------------------------------------------------------------------------------------------ | -------- |
+| authentication                  | [authentication][]    | Configures authentication for connecting to Kafka brokers.                                 | no       |
+| authentication > plaintext      | [plaintext][]         | Authenticates against Kafka brokers with plaintext.                                        | no       |
+| authentication > sasl           | [sasl][]              | Authenticates against Kafka brokers with SASL.                                             | no       |
+| authentication > sasl > aws_msk | [aws_msk][]           | Additional SASL parameters when using AWS_MSK_IAM.                                         | no       |
+| authentication > tls            | [tls][]               | Configures TLS for connecting to the Kafka brokers.                                        | no       |
+| authentication > kerberos       | [kerberos][]          | Authenticates against Kafka brokers with Kerberos.                                         | no       |
+| metadata                        | [metadata][]          | Configures how to retrieve metadata from Kafka brokers.                                    | no       |
+| metadata > retry                | [retry][]             | Configures how to retry metadata retrieval.                                                | no       |
+| autocommit                      | [autocommit][]        | Configures how to automatically commit updated topic offsets to back to the Kafka brokers. | no       |
+| message_marking                 | [message_marking][]   | Configures when Kafka messages are marked as read.                                         | no       |
+| header_extraction               | [header_extraction][] | Extract headers from Kafka records.                                                        | no       |
+| debug_metrics                   | [debug_metrics][]     | Configures the metrics which this component generates to monitor its state.                | no       |
+| output                          | [output][]            | Configures where to send received telemetry data.                                          | yes      |
 
 The `>` symbol indicates deeper levels of nesting. For example,
 `authentication > tls` refers to a `tls` block defined inside an
@@ -170,10 +170,10 @@ offsets back to the Kafka brokers.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enable` | `bool` | Enable autocommitting updated topic offsets. | `true` | no
-`interval` | `duration` | How frequently to autocommit. | `"1s"` | no
+| Name       | Type       | Description                                  | Default | Required |
+| ---------- | ---------- | -------------------------------------------- | ------- | -------- |
+| `enable`   | `bool`     | Enable autocommitting updated topic offsets. | `true`  | no       |
+| `interval` | `duration` | How frequently to autocommit.                | `"1s"`  | no       |
 
 ### message_marking block
 
@@ -181,10 +181,10 @@ The `message_marking` block configures when Kafka messages are marked as read.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`after_execution` | `bool` | Mark messages after forwarding telemetry data to other components. | `false` | no
-`include_unsuccessful` | `bool` | Whether failed forwards should be marked as read. | `false` | no
+| Name                   | Type   | Description                                                        | Default | Required |
+| ---------------------- | ------ | ------------------------------------------------------------------ | ------- | -------- |
+| `after_execution`      | `bool` | Mark messages after forwarding telemetry data to other components. | `false` | no       |
+| `include_unsuccessful` | `bool` | Whether failed forwards should be marked as read.                  | `false` | no       |
 
 By default, a Kafka message is marked as read immediately after it is retrieved
 from the Kafka broker. If the `after_execution` argument is true, messages are
@@ -207,10 +207,10 @@ The `header_extraction` block configures how to extract headers from Kafka recor
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`extract_headers` | `bool` | Enables attaching header fields to resource attributes. | `false` | no
-`headers` | `list(string)` | A list of headers to extract from the Kafka record. | `[]` | no
+| Name              | Type           | Description                                             | Default | Required |
+| ----------------- | -------------- | ------------------------------------------------------- | ------- | -------- |
+| `extract_headers` | `bool`         | Enables attaching header fields to resource attributes. | `false` | no       |
+| `headers`         | `list(string)` | A list of headers to extract from the Kafka record.     | `[]`    | no       |
 
 Regular expressions are not allowed in the `headers` argument. Only exact matching will be performed.
 
@@ -267,6 +267,7 @@ otelcol.exporter.otlp "default" {
   }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -275,10 +276,9 @@ otelcol.exporter.otlp "default" {
 
 - Components that export [OpenTelemetry `otelcol.Consumer`](../../../compatibility/#opentelemetry-otelcolconsumer-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
 {{< /admonition >}}
 
-<!-- END GENERATED COMPATIBLE COMPONENTS -->
\ No newline at end of file
+<!-- END GENERATED COMPATIBLE COMPONENTS -->
diff --git a/docs/sources/reference/components/otelcol/otelcol.receiver.loki.md b/docs/sources/reference/components/otelcol/otelcol.receiver.loki.md
index 2bbd9b14d4..9c208d58f6 100644
--- a/docs/sources/reference/components/otelcol/otelcol.receiver.loki.md
+++ b/docs/sources/reference/components/otelcol/otelcol.receiver.loki.md
@@ -34,9 +34,9 @@ through inner blocks.
 The following blocks are supported inside the definition of
 `otelcol.receiver.loki`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-output | [output][] | Configures where to send converted telemetry data. | yes
+| Hierarchy | Block      | Description                                        | Required |
+| --------- | ---------- | -------------------------------------------------- | -------- |
+| output    | [output][] | Configures where to send converted telemetry data. | yes      |
 
 [output]: #output-block
 
@@ -48,9 +48,9 @@ output | [output][] | Configures where to send converted telemetry data. | yes
 
 The following fields are exported and can be referenced by other components:
 
-Name | Type | Description
----- | ---- | -----------
-`receiver` | `LogsReceiver` | A value that other components can use to send Loki logs to.
+| Name       | Type           | Description                                                 |
+| ---------- | -------------- | ----------------------------------------------------------- |
+| `receiver` | `LogsReceiver` | A value that other components can use to send Loki logs to. |
 
 ## Component health
 
diff --git a/docs/sources/reference/components/otelcol/otelcol.receiver.opencensus.md b/docs/sources/reference/components/otelcol/otelcol.receiver.opencensus.md
index b628adc8cc..6156ad8beb 100644
--- a/docs/sources/reference/components/otelcol/otelcol.receiver.opencensus.md
+++ b/docs/sources/reference/components/otelcol/otelcol.receiver.opencensus.md
@@ -36,20 +36,19 @@ otelcol.receiver.opencensus "LABEL" {
 
 `otelcol.receiver.opencensus` supports the following arguments:
 
-
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`cors_allowed_origins` | `list(string)` | A list of allowed Cross-Origin Resource Sharing (CORS) origins. |  | no
-`endpoint` | `string` | `host:port` to listen for traffic on. | `"0.0.0.0:55678"` | no
-`transport` | `string` | Transport to use for the gRPC server. | `"tcp"` | no
-`max_recv_msg_size` | `string` | Maximum size of messages the server will accept. | `"4MiB`" | no
-`max_concurrent_streams` | `number` | Limit the number of concurrent streaming RPC calls. | | no
-`read_buffer_size` | `string` | Size of the read buffer the gRPC server will use for reading from clients. | `"512KiB"` | no
-`write_buffer_size` | `string` | Size of the write buffer the gRPC server will use for writing to clients. | | no
-`include_metadata` | `boolean` | Propagate incoming connection metadata to downstream consumers. | | no
+| Name                     | Type           | Description                                                                | Default           | Required |
+| ------------------------ | -------------- | -------------------------------------------------------------------------- | ----------------- | -------- |
+| `cors_allowed_origins`   | `list(string)` | A list of allowed Cross-Origin Resource Sharing (CORS) origins.            |                   | no       |
+| `endpoint`               | `string`       | `host:port` to listen for traffic on.                                      | `"0.0.0.0:55678"` | no       |
+| `transport`              | `string`       | Transport to use for the gRPC server.                                      | `"tcp"`           | no       |
+| `max_recv_msg_size`      | `string`       | Maximum size of messages the server will accept.                           | `"4MiB`"          | no       |
+| `max_concurrent_streams` | `number`       | Limit the number of concurrent streaming RPC calls.                        |                   | no       |
+| `read_buffer_size`       | `string`       | Size of the read buffer the gRPC server will use for reading from clients. | `"512KiB"`        | no       |
+| `write_buffer_size`      | `string`       | Size of the write buffer the gRPC server will use for writing to clients.  |                   | no       |
+| `include_metadata`       | `boolean`      | Propagate incoming connection metadata to downstream consumers.            |                   | no       |
 
 `cors_allowed_origins` are the allowed [CORS](https://github.com/rs/cors) origins for HTTP/JSON requests.
-An empty list means that CORS is not enabled at all. A wildcard (*) can be
+An empty list means that CORS is not enabled at all. A wildcard (\*) can be
 used to match any origin or one or more characters of an origin.
 
 The "endpoint" parameter is the same for both gRPC and HTTP/JSON, as the protocol is recognized and processed accordingly.
@@ -64,14 +63,14 @@ in the string, such as "512KiB" or "1024KB".
 The following blocks are supported inside the definition of
 `otelcol.receiver.opencensus`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-tls | [tls][] | Configures TLS for the gRPC server. | no
-keepalive | [keepalive][] | Configures keepalive settings for the configured server. | no
-keepalive > server_parameters | [server_parameters][] | Server parameters used to configure keepalive settings. | no
-keepalive > enforcement_policy | [enforcement_policy][] | Enforcement policy for keepalive settings. | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
-output | [output][] | Configures where to send received telemetry data. | yes
+| Hierarchy                      | Block                  | Description                                                                | Required |
+| ------------------------------ | ---------------------- | -------------------------------------------------------------------------- | -------- |
+| tls                            | [tls][]                | Configures TLS for the gRPC server.                                        | no       |
+| keepalive                      | [keepalive][]          | Configures keepalive settings for the configured server.                   | no       |
+| keepalive > server_parameters  | [server_parameters][]  | Server parameters used to configure keepalive settings.                    | no       |
+| keepalive > enforcement_policy | [enforcement_policy][] | Enforcement policy for keepalive settings.                                 | no       |
+| debug_metrics                  | [debug_metrics][]      | Configures the metrics that this component generates to monitor its state. | no       |
+| output                         | [output][]             | Configures where to send received telemetry data.                          | yes      |
 
 The `>` symbol indicates deeper levels of nesting. For example, `grpc > tls`
 refers to a `tls` block defined inside a `grpc` block.
@@ -105,13 +104,13 @@ servers.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`max_connection_idle` | `duration` | Maximum age for idle connections. | `"infinity"` | no
-`max_connection_age` | `duration` | Maximum age for non-idle connections. | `"infinity"` | no
-`max_connection_age_grace` | `duration` | Time to wait before forcibly closing connections. | `"infinity"` | no
-`time` | `duration` | How often to ping inactive clients to check for liveness. | `"2h"` | no
-`timeout` | `duration` | Time to wait before closing inactive clients that do not respond to liveness checks. | `"20s"` | no
+| Name                       | Type       | Description                                                                          | Default      | Required |
+| -------------------------- | ---------- | ------------------------------------------------------------------------------------ | ------------ | -------- |
+| `max_connection_idle`      | `duration` | Maximum age for idle connections.                                                    | `"infinity"` | no       |
+| `max_connection_age`       | `duration` | Maximum age for non-idle connections.                                                | `"infinity"` | no       |
+| `max_connection_age_grace` | `duration` | Time to wait before forcibly closing connections.                                    | `"infinity"` | no       |
+| `time`                     | `duration` | How often to ping inactive clients to check for liveness.                            | `"2h"`       | no       |
+| `timeout`                  | `duration` | Time to wait before closing inactive clients that do not respond to liveness checks. | `"20s"`      | no       |
 
 ### enforcement_policy block
 
@@ -121,10 +120,10 @@ configured policy.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`min_time` | `duration` | Minimum time clients should wait before sending a keepalive ping. | `"5m"` | no
-`permit_without_stream` | `boolean` | Allow clients to send keepalive pings when there are no active streams. | `false` | no
+| Name                    | Type       | Description                                                             | Default | Required |
+| ----------------------- | ---------- | ----------------------------------------------------------------------- | ------- | -------- |
+| `min_time`              | `duration` | Minimum time clients should wait before sending a keepalive ping.       | `"5m"`  | no       |
+| `permit_without_stream` | `boolean`  | Allow clients to send keepalive pings when there are no active streams. | `false` | no       |
 
 ### debug_metrics block
 
@@ -207,6 +206,7 @@ otelcol.exporter.otlp "default" {
     }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -215,7 +215,6 @@ otelcol.exporter.otlp "default" {
 
 - Components that export [OpenTelemetry `otelcol.Consumer`](../../../compatibility/#opentelemetry-otelcolconsumer-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/otelcol/otelcol.receiver.otlp.md b/docs/sources/reference/components/otelcol/otelcol.receiver.otlp.md
index e1ecbf79ba..d887beed50 100644
--- a/docs/sources/reference/components/otelcol/otelcol.receiver.otlp.md
+++ b/docs/sources/reference/components/otelcol/otelcol.receiver.otlp.md
@@ -43,18 +43,18 @@ through inner blocks.
 The following blocks are supported inside the definition of
 `otelcol.receiver.otlp`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-grpc | [grpc][] | Configures the gRPC server to receive telemetry data. | no
-grpc > tls | [tls][] | Configures TLS for the gRPC server. | no
-grpc > keepalive | [keepalive][] | Configures keepalive settings for the configured server. | no
-grpc > keepalive > server_parameters | [server_parameters][] | Server parameters used to configure keepalive settings. | no
-grpc > keepalive > enforcement_policy | [enforcement_policy][] | Enforcement policy for keepalive settings. | no
-http | [http][] | Configures the HTTP server to receive telemetry data. | no
-http > tls | [tls][] | Configures TLS for the HTTP server. | no
-http > cors | [cors][] | Configures CORS for the HTTP server. | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
-output | [output][] | Configures where to send received telemetry data. | yes
+| Hierarchy                             | Block                  | Description                                                                | Required |
+| ------------------------------------- | ---------------------- | -------------------------------------------------------------------------- | -------- |
+| grpc                                  | [grpc][]               | Configures the gRPC server to receive telemetry data.                      | no       |
+| grpc > tls                            | [tls][]                | Configures TLS for the gRPC server.                                        | no       |
+| grpc > keepalive                      | [keepalive][]          | Configures keepalive settings for the configured server.                   | no       |
+| grpc > keepalive > server_parameters  | [server_parameters][]  | Server parameters used to configure keepalive settings.                    | no       |
+| grpc > keepalive > enforcement_policy | [enforcement_policy][] | Enforcement policy for keepalive settings.                                 | no       |
+| http                                  | [http][]               | Configures the HTTP server to receive telemetry data.                      | no       |
+| http > tls                            | [tls][]                | Configures TLS for the HTTP server.                                        | no       |
+| http > cors                           | [cors][]               | Configures CORS for the HTTP server.                                       | no       |
+| debug_metrics                         | [debug_metrics][]      | Configures the metrics that this component generates to monitor its state. | no       |
+| output                                | [output][]             | Configures where to send received telemetry data.                          | yes      |
 
 The `>` symbol indicates deeper levels of nesting. For example, `grpc > tls`
 refers to a `tls` block defined inside a `grpc` block.
@@ -76,15 +76,15 @@ The `grpc` block configures the gRPC server used by the component. If the
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`endpoint` | `string` | `host:port` to listen for traffic on. | `"0.0.0.0:4317"` | no
-`transport` | `string` | Transport to use for the gRPC server. | `"tcp"` | no
-`max_recv_msg_size` | `string` | Maximum size of messages the server will accept. | `"4MiB`" | no
-`max_concurrent_streams` | `number` | Limit the number of concurrent streaming RPC calls. | | no
-`read_buffer_size` | `string` | Size of the read buffer the gRPC server will use for reading from clients. | `"512KiB"` | no
-`write_buffer_size` | `string` | Size of the write buffer the gRPC server will use for writing to clients. | | no
-`include_metadata` | `boolean` | Propagate incoming connection metadata to downstream consumers. | | no
+| Name                     | Type      | Description                                                                | Default          | Required |
+| ------------------------ | --------- | -------------------------------------------------------------------------- | ---------------- | -------- |
+| `endpoint`               | `string`  | `host:port` to listen for traffic on.                                      | `"0.0.0.0:4317"` | no       |
+| `transport`              | `string`  | Transport to use for the gRPC server.                                      | `"tcp"`          | no       |
+| `max_recv_msg_size`      | `string`  | Maximum size of messages the server will accept.                           | `"4MiB`"         | no       |
+| `max_concurrent_streams` | `number`  | Limit the number of concurrent streaming RPC calls.                        |                  | no       |
+| `read_buffer_size`       | `string`  | Size of the read buffer the gRPC server will use for reading from clients. | `"512KiB"`       | no       |
+| `write_buffer_size`      | `string`  | Size of the write buffer the gRPC server will use for writing to clients.  |                  | no       |
+| `include_metadata`       | `boolean` | Propagate incoming connection metadata to downstream consumers.            |                  | no       |
 
 ### tls block
 
@@ -108,13 +108,13 @@ servers.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`max_connection_idle` | `duration` | Maximum age for idle connections. | `"infinity"` | no
-`max_connection_age` | `duration` | Maximum age for non-idle connections. | `"infinity"` | no
-`max_connection_age_grace` | `duration` | Time to wait before forcibly closing connections. | `"infinity"` | no
-`time` | `duration` | How often to ping inactive clients to check for liveness. | `"2h"` | no
-`timeout` | `duration` | Time to wait before closing inactive clients that do not respond to liveness checks. | `"20s"` | no
+| Name                       | Type       | Description                                                                          | Default      | Required |
+| -------------------------- | ---------- | ------------------------------------------------------------------------------------ | ------------ | -------- |
+| `max_connection_idle`      | `duration` | Maximum age for idle connections.                                                    | `"infinity"` | no       |
+| `max_connection_age`       | `duration` | Maximum age for non-idle connections.                                                | `"infinity"` | no       |
+| `max_connection_age_grace` | `duration` | Time to wait before forcibly closing connections.                                    | `"infinity"` | no       |
+| `time`                     | `duration` | How often to ping inactive clients to check for liveness.                            | `"2h"`       | no       |
+| `timeout`                  | `duration` | Time to wait before closing inactive clients that do not respond to liveness checks. | `"20s"`      | no       |
 
 ### enforcement_policy block
 
@@ -124,10 +124,10 @@ configured policy.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`min_time` | `duration` | Minimum time clients should wait before sending a keepalive ping. | `"5m"` | no
-`permit_without_stream` | `boolean` | Allow clients to send keepalive pings when there are no active streams. | `false` | no
+| Name                    | Type       | Description                                                             | Default | Required |
+| ----------------------- | ---------- | ----------------------------------------------------------------------- | ------- | -------- |
+| `min_time`              | `duration` | Minimum time clients should wait before sending a keepalive ping.       | `"5m"`  | no       |
+| `permit_without_stream` | `boolean`  | Allow clients to send keepalive pings when there are no active streams. | `false` | no       |
 
 ### http block
 
@@ -136,20 +136,21 @@ The `http` block configures the HTTP server used by the component. If the
 
 The following arguments are supported:
 
-Name | Type | Description | Default         | Required
----- | ---- | ----------- |-----------------| --------
-`endpoint` | `string` | `host:port` to listen for traffic on. | `"0.0.0.0:4318"` | no
-`max_request_body_size` | `string`   | Maximum request body size the server will allow.                   | `20MiB`          | no
-`include_metadata` | `boolean` | Propagate incoming connection metadata to downstream consumers. |                 | no
-`traces_url_path` | `string` | The URL path to receive traces on. | `"/v1/traces"`  | no
-`metrics_url_path` | `string` | The URL path to receive metrics on. | `"/v1/metrics"` | no
-`logs_url_path` | `string` | The URL path to receive logs on. | `"/v1/logs"`    | no
-`compression_algorithms` | `list(string)` | A list of compression algorithms the server can accept.    | `["", "gzip", "zstd", "zlib", "snappy", "deflate", "lz4"]` | no
+| Name                     | Type           | Description                                                     | Default                                                    | Required |
+| ------------------------ | -------------- | --------------------------------------------------------------- | ---------------------------------------------------------- | -------- |
+| `endpoint`               | `string`       | `host:port` to listen for traffic on.                           | `"0.0.0.0:4318"`                                           | no       |
+| `max_request_body_size`  | `string`       | Maximum request body size the server will allow.                | `20MiB`                                                    | no       |
+| `include_metadata`       | `boolean`      | Propagate incoming connection metadata to downstream consumers. |                                                            | no       |
+| `traces_url_path`        | `string`       | The URL path to receive traces on.                              | `"/v1/traces"`                                             | no       |
+| `metrics_url_path`       | `string`       | The URL path to receive metrics on.                             | `"/v1/metrics"`                                            | no       |
+| `logs_url_path`          | `string`       | The URL path to receive logs on.                                | `"/v1/logs"`                                               | no       |
+| `compression_algorithms` | `list(string)` | A list of compression algorithms the server can accept.         | `["", "gzip", "zstd", "zlib", "snappy", "deflate", "lz4"]` | no       |
 
 To send telemetry signals to `otelcol.receiver.otlp` with HTTP/JSON, POST to:
-* `[endpoint][traces_url_path]` for traces.
-* `[endpoint][metrics_url_path]` for metrics.
-* `[endpoint][logs_url_path]` for logs.
+
+- `[endpoint][traces_url_path]` for traces.
+- `[endpoint][metrics_url_path]` for metrics.
+- `[endpoint][logs_url_path]` for logs.
 
 ### cors block
 
@@ -157,19 +158,19 @@ The `cors` block configures CORS settings for an HTTP server.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`allowed_origins` | `list(string)` | Allowed values for the `Origin` header. | | no
-`allowed_headers` | `list(string)` | Accepted headers from CORS requests. | `["X-Requested-With"]` | no
-`max_age` | `number` | Configures the `Access-Control-Max-Age` response header. | | no
+| Name              | Type           | Description                                              | Default                | Required |
+| ----------------- | -------------- | -------------------------------------------------------- | ---------------------- | -------- |
+| `allowed_origins` | `list(string)` | Allowed values for the `Origin` header.                  |                        | no       |
+| `allowed_headers` | `list(string)` | Accepted headers from CORS requests.                     | `["X-Requested-With"]` | no       |
+| `max_age`         | `number`       | Configures the `Access-Control-Max-Age` response header. |                        | no       |
 
 The `allowed_headers` argument specifies which headers are acceptable from a
 CORS request. The following headers are always implicitly allowed:
 
-* `Accept`
-* `Accept-Language`
-* `Content-Type`
-* `Content-Language`
+- `Accept`
+- `Accept-Language`
+- `Content-Type`
+- `Content-Language`
 
 If `allowed_headers` includes `"*"`, all headers are permitted.
 
@@ -197,13 +198,13 @@ information.
 
 ## Debug metrics
 
-* `otelcol_receiver_accepted_spans_total` (counter): Number of spans successfully pushed into the pipeline.
-* `otelcol_receiver_refused_spans_total` (counter): Number of spans that could not be pushed into the pipeline.
-* `rpc_server_duration_milliseconds` (histogram): Duration of RPC requests from a gRPC server.
-* `rpc_server_request_size_bytes` (histogram): Measures size of RPC request messages (uncompressed).
-* `rpc_server_requests_per_rpc` (histogram): Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs.
-* `rpc_server_response_size_bytes` (histogram): Measures size of RPC response messages (uncompressed).
-* `rpc_server_responses_per_rpc` (histogram): Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs.
+- `otelcol_receiver_accepted_spans_total` (counter): Number of spans successfully pushed into the pipeline.
+- `otelcol_receiver_refused_spans_total` (counter): Number of spans that could not be pushed into the pipeline.
+- `rpc_server_duration_milliseconds` (histogram): Duration of RPC requests from a gRPC server.
+- `rpc_server_request_size_bytes` (histogram): Measures size of RPC request messages (uncompressed).
+- `rpc_server_requests_per_rpc` (histogram): Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs.
+- `rpc_server_response_size_bytes` (histogram): Measures size of RPC response messages (uncompressed).
+- `rpc_server_responses_per_rpc` (histogram): Measures the number of messages received per RPC. Should be 1 for all non-streaming RPCs.
 
 ## Example
 
@@ -240,6 +241,7 @@ otelcol.exporter.otlp "default" {
 ## Technical details
 
 `otelcol.receiver.otlp` supports [gzip](https://en.wikipedia.org/wiki/Gzip) for compression.
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -248,7 +250,6 @@ otelcol.exporter.otlp "default" {
 
 - Components that export [OpenTelemetry `otelcol.Consumer`](../../../compatibility/#opentelemetry-otelcolconsumer-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/otelcol/otelcol.receiver.prometheus.md b/docs/sources/reference/components/otelcol/otelcol.receiver.prometheus.md
index 6359127ed8..763e667c77 100644
--- a/docs/sources/reference/components/otelcol/otelcol.receiver.prometheus.md
+++ b/docs/sources/reference/components/otelcol/otelcol.receiver.prometheus.md
@@ -37,9 +37,9 @@ through inner blocks.
 The following blocks are supported inside the definition of
 `otelcol.receiver.prometheus`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-output | [output][] | Configures where to send received telemetry data. | yes
+| Hierarchy | Block      | Description                                       | Required |
+| --------- | ---------- | ------------------------------------------------- | -------- |
+| output    | [output][] | Configures where to send received telemetry data. | yes      |
 
 [output]: #output-block
 
@@ -51,9 +51,9 @@ output | [output][] | Configures where to send received telemetry data. | yes
 
 The following fields are exported and can be referenced by other components:
 
-Name | Type | Description
----- | ---- | -----------
-`receiver` | `MetricsReceiver` | A value that other components can use to send Prometheus metrics to.
+| Name       | Type              | Description                                                          |
+| ---------- | ----------------- | -------------------------------------------------------------------- |
+| `receiver` | `MetricsReceiver` | A value that other components can use to send Prometheus metrics to. |
 
 ## Component health
 
@@ -94,6 +94,7 @@ otelcol.exporter.otlp "default" {
   }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/otelcol/otelcol.receiver.vcenter.md b/docs/sources/reference/components/otelcol/otelcol.receiver.vcenter.md
index fd16203af9..7489883549 100644
--- a/docs/sources/reference/components/otelcol/otelcol.receiver.vcenter.md
+++ b/docs/sources/reference/components/otelcol/otelcol.receiver.vcenter.md
@@ -55,15 +55,14 @@ otelcol.receiver.vcenter "LABEL" {
 
 `otelcol.receiver.vcenter` supports the following arguments:
 
-
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`endpoint` | `string` | Endpoint to a vCenter Server or ESXi host which has the SDK path enabled. | | yes
-`username` | `string` | Username to use for authentication. | | yes
-`password` | `string` | Password to use for authentication. | | yes
-`collection_interval` | `duration` | Defines how often to collect metrics. | `"1m"` | no
-`initial_delay` | `duration` | Defines how long this receiver waits before starting. | `"1s"` | no
-`timeout` | `duration` | Defines the timeout for the underlying HTTP client. | `"0s"` | no
+| Name                  | Type       | Description                                                               | Default | Required |
+| --------------------- | ---------- | ------------------------------------------------------------------------- | ------- | -------- |
+| `endpoint`            | `string`   | Endpoint to a vCenter Server or ESXi host which has the SDK path enabled. |         | yes      |
+| `username`            | `string`   | Username to use for authentication.                                       |         | yes      |
+| `password`            | `string`   | Password to use for authentication.                                       |         | yes      |
+| `collection_interval` | `duration` | Defines how often to collect metrics.                                     | `"1m"`  | no       |
+| `initial_delay`       | `duration` | Defines how long this receiver waits before starting.                     | `"1s"`  | no       |
+| `timeout`             | `duration` | Defines the timeout for the underlying HTTP client.                       | `"0s"`  | no       |
 
 `endpoint` has the format `<protocol>://<hostname>`. For example, `https://vcsa.hostname.localnet`.
 
@@ -72,13 +71,13 @@ Name | Type | Description | Default | Required
 The following blocks are supported inside the definition of
 `otelcol.receiver.vcenter`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-tls | [tls][] | Configures TLS for the HTTP client. | no
-metrics | [metrics][] | Configures which metrics will be sent to downstream components. | no
-resource_attributes | [resource_attributes][] | Configures resource attributes for metrics sent to downstream components. | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
-output | [output][] | Configures where to send received telemetry data. | yes
+| Hierarchy           | Block                   | Description                                                                | Required |
+| ------------------- | ----------------------- | -------------------------------------------------------------------------- | -------- |
+| tls                 | [tls][]                 | Configures TLS for the HTTP client.                                        | no       |
+| metrics             | [metrics][]             | Configures which metrics will be sent to downstream components.            | no       |
+| resource_attributes | [resource_attributes][] | Configures resource attributes for metrics sent to downstream components.  | no       |
+| debug_metrics       | [debug_metrics][]       | Configures the metrics that this component generates to monitor its state. | no       |
+| output              | [output][]              | Configures where to send received telemetry data.                          | yes      |
 
 [tls]: #tls-block
 [debug_metrics]: #debug_metrics-block
@@ -95,109 +94,107 @@ isn't provided, TLS won't be used for connections to the server.
 
 ### metrics block
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`vcenter.cluster.cpu.effective` | [metric][] | Enables the `vcenter.cluster.cpu.effective` metric. | `true` | no
-`vcenter.cluster.cpu.usage` | [metric][] | Enables the `vcenter.cluster.cpu.usage` metric. | `true` | no
-`vcenter.cluster.host.count` | [metric][] | Enables the `vcenter.cluster.host.count` metric. | `true` | no
-`vcenter.cluster.memory.effective` | [metric][] | Enables the `vcenter.cluster.memory.effective` metric. | `true` | no
-`vcenter.cluster.memory.limit` | [metric][] | Enables the `vcenter.cluster.memory.limit` metric. | `true` | no
-`vcenter.cluster.vm.count` | [metric][] | Enables the `vcenter.cluster.vm.count` metric. | `true` | no
-`vcenter.cluster.vm_template.count` | [metric][] | Enables the `vcenter.cluster.vm_template.count` metric. | `true` | no
-`vcenter.cluster.vsan.congestions` | [metric][] | Enables the `vcenter.cluster.vsan.congestions` metric. | `true` | no
-`vcenter.cluster.vsan.latency.avg` | [metric][] | Enables the `vcenter.cluster.vsan.latency.avg` metric. | `true` | no
-`vcenter.cluster.vsan.operations` | [metric][] | Enables the `vcenter.cluster.vsan.operations` metric. | `true` | no
-`vcenter.cluster.vsan.throughput` | [metric][] | Enables the `vcenter.cluster.vsan.throughput` metric. | `true` | no
-`vcenter.datacenter.cluster.count` | [metric][] | Enables the `vcenter.datacenter.cluster.count` metric. | `true` | no
-`vcenter.datacenter.cpu.limit` | [metric][] | Enables the `vcenter.datacenter.cpu.limit` metric. | `true` | no
-`vcenter.datacenter.datastore.count` | [metric][] | Enables the `vcenter.datacenter.datastore.count` metric. | `true` | no
-`vcenter.datacenter.disk.space` | [metric][] | Enables the `vcenter.datacenter.disk.space` metric. | `true` | no
-`vcenter.datacenter.host.count` | [metric][] | Enables the `vcenter.datacenter.host.count` metric. | `true` | no
-`vcenter.datacenter.memory.limit` | [metric][] | Enables the `vcenter.datacenter.memory.limit` metric. | `true` | no
-`vcenter.datacenter.vm.count` | [metric][] | Enables the `vcenter.datacenter.vm.count` metric. | `true` | no
-`vcenter.datastore.disk.usage` | [metric][] | Enables the `vcenter.datastore.disk.usage` metric. | `true` | no
-`vcenter.datastore.disk.utilization` | [metric][] | Enables the `vcenter.datastore.disk.utilization` metric. | `true` | no
-`vcenter.host.cpu.capacity` | [metric][] | Enables the `vcenter.host.cpu.capacity` metric. | `true` | no
-`vcenter.host.cpu.reserved` | [metric][] | Enables the `vcenter.host.cpu.reserved` metric. | `true` | no
-`vcenter.host.cpu.usage` | [metric][] | Enables the `vcenter.host.cpu.usage` metric. | `true` | no
-`vcenter.host.cpu.utilization` | [metric][] | Enables the `vcenter.host.cpu.utilization` metric. | `true` | no
-`vcenter.host.disk.latency.avg` | [metric][] | Enables the `vcenter.host.disk.latency.avg` metric. | `true` | no
-`vcenter.host.disk.latency.max` | [metric][] | Enables the `vcenter.host.disk.latency.max` metric. | `true` | no
-`vcenter.host.disk.throughput` | [metric][] | Enables the `vcenter.host.disk.throughput` metric. | `true` | no
-`vcenter.host.memory.usage` | [metric][] | Enables the `vcenter.host.memory.usage` metric. | `true` | no
-`vcenter.host.memory.utilization` | [metric][] | Enables the `vcenter.host.memory.utilization` metric. | `true` | no
-`vcenter.host.network.packet.rate` | [metric][] | Enables the `vcenter.host.network.packet.rate` metric. | `true` | no
-`vcenter.host.network.packet.error.rate` | [metric][] | Enables the `vcenter.host.network.packet.error.rate` metric. | `true` | no
-`vcenter.host.network.packet.drop.rate` | [metric][] | Enables the `vcenter.host.network.packet.drop.rate` metric. | `true` | no
-`vcenter.host.network.throughput` | [metric][] | Enables the `vcenter.host.network.throughput` metric. | `true` | no
-`vcenter.host.network.usage` | [metric][] | Enables the `vcenter.host.network.usage` metric. | `true` | no
-`vcenter.host.vsan.cache.hit_rate` | [metric][] | Enables the `vcenter.host.vsan.cache.hit_rate` metric. | `true` | no
-`vcenter.host.vsan.congestions` | [metric][] | Enables the `vcenter.host.vsan.congestions` metric. | `true` | no
-`vcenter.host.vsan.latency.avg` | [metric][] | Enables the `vcenter.host.vsan.latency.avg` metric. | `true` | no
-`vcenter.host.vsan.operations` | [metric][] | Enables the `vcenter.host.vsan.operations` metric. | `true` | no
-`vcenter.host.vsan.throughput` | [metric][] | Enables the `vcenter.host.vsan.throughput` metric. | `true` | no
-`vcenter.resource_pool.cpu.shares` | [metric][] | Enables the `vcenter.resource_pool.cpu.shares` metric. | `true` | no
-`vcenter.resource_pool.cpu.usage` | [metric][] | Enables the `vcenter.resource_pool.cpu.usage` metric. | `true` | no
-`vcenter.resource_pool.memory.ballooned` | [metric][] | Enables the `vcenter.resource_pool.memory.ballooned` metric. | `true` | no
-`vcenter.resource_pool.memory.granted` | [metric][] | Enables the `vcenter.resource_pool.memory.granted` metric. | `true` | no
-`vcenter.resource_pool.memory.shares` | [metric][] | Enables the `vcenter.resource_pool.memory.shares` metric. | `true` | no
-`vcenter.resource_pool.memory.swapped` | [metric][] | Enables the `vcenter.resource_pool.memory.swapped` metric. | `true` | no
-`vcenter.resource_pool.memory.usage` | [metric][] | Enables the `vcenter.resource_pool.memory.usage` metric. | `true` | no
-`vcenter.vm.cpu.readiness` | [metric][] | Enables the `vcenter.vm.cpu.readiness` metric. | `true` | no
-`vcenter.vm.cpu.usage` | [metric][] | Enables the `vcenter.vm.cpu.usage` metric. | `true` | no
-`vcenter.vm.cpu.utilization` | [metric][] | Enables the `vcenter.vm.cpu.utilization` metric. | `true` | no
-`vcenter.vm.disk.latency.avg` | [metric][] | Enables the `vcenter.vm.disk.latency.avg` metric. | `true` | no
-`vcenter.vm.disk.latency.max` | [metric][] | Enables the `vcenter.vm.disk.latency.max` metric. | `true` | no
-`vcenter.vm.disk.throughput` | [metric][] | Enables the `vcenter.vm.disk.throughput` metric. | `true` | no
-`vcenter.vm.disk.usage` | [metric][] | Enables the `vcenter.vm.disk.usage` metric. | `true` | no
-`vcenter.vm.disk.utilization` | [metric][] | Enables the `vcenter.vm.disk.utilization` metric. | `true` | no
-`vcenter.vm.memory.ballooned` | [metric][] | Enables the `vcenter.vm.memory.ballooned` metric. | `true` | no
-`vcenter.vm.memory.swapped` | [metric][] | Enables the `vcenter.vm.memory.swapped` metric. | `true` | no
-`vcenter.vm.memory.swapped_ssd` | [metric][] | Enables the `vcenter.vm.memory.swapped_ssd` metric. | `true` | no
-`vcenter.vm.memory.usage` | [metric][] | Enables the `vcenter.vm.memory.usage` metric. | `true` | no
-`vcenter.vm.memory.utilization` | [metric][] | Enables the `vcenter.vm.memory.utilization` metric. | `true` | no
-`vcenter.vm.network.packet.rate` | [metric][] | Enables the `vcenter.vm.network.packet.rate` metric. | `true` | no
-`vcenter.vm.network.packet.drop.rate` | [metric][] | Enables the `vcenter.vm.network.packet.drop.rate` metric. | `true` | no
-`vcenter.vm.network.throughput` | [metric][] | Enables the `vcenter.vm.network.throughput` metric. | `true` | no
-`vcenter.vm.network.usage` | [metric][] | Enables the `vcenter.vm.network.usage` metric. | `true` | no
-`vcenter.vm.vsan.latency.avg` | [metric][] | Enables the `vcenter.vm.vsan.latency.avg` metric. | `true` | no
-`vcenter.vm.vsan.operations` | [metric][] | Enables the `vcenter.vm.vsan.operations` metric. | `true` | no
-`vcenter.vm.vsan.throughput` | [metric][] | Enables the `vcenter.vm.vsan.throughput` metric. | `true` | no
+| Name                                     | Type       | Description                                                  | Default | Required |
+| ---------------------------------------- | ---------- | ------------------------------------------------------------ | ------- | -------- |
+| `vcenter.cluster.cpu.effective`          | [metric][] | Enables the `vcenter.cluster.cpu.effective` metric.          | `true`  | no       |
+| `vcenter.cluster.cpu.usage`              | [metric][] | Enables the `vcenter.cluster.cpu.usage` metric.              | `true`  | no       |
+| `vcenter.cluster.host.count`             | [metric][] | Enables the `vcenter.cluster.host.count` metric.             | `true`  | no       |
+| `vcenter.cluster.memory.effective`       | [metric][] | Enables the `vcenter.cluster.memory.effective` metric.       | `true`  | no       |
+| `vcenter.cluster.memory.limit`           | [metric][] | Enables the `vcenter.cluster.memory.limit` metric.           | `true`  | no       |
+| `vcenter.cluster.vm.count`               | [metric][] | Enables the `vcenter.cluster.vm.count` metric.               | `true`  | no       |
+| `vcenter.cluster.vm_template.count`      | [metric][] | Enables the `vcenter.cluster.vm_template.count` metric.      | `true`  | no       |
+| `vcenter.cluster.vsan.congestions`       | [metric][] | Enables the `vcenter.cluster.vsan.congestions` metric.       | `true`  | no       |
+| `vcenter.cluster.vsan.latency.avg`       | [metric][] | Enables the `vcenter.cluster.vsan.latency.avg` metric.       | `true`  | no       |
+| `vcenter.cluster.vsan.operations`        | [metric][] | Enables the `vcenter.cluster.vsan.operations` metric.        | `true`  | no       |
+| `vcenter.cluster.vsan.throughput`        | [metric][] | Enables the `vcenter.cluster.vsan.throughput` metric.        | `true`  | no       |
+| `vcenter.datacenter.cluster.count`       | [metric][] | Enables the `vcenter.datacenter.cluster.count` metric.       | `true`  | no       |
+| `vcenter.datacenter.cpu.limit`           | [metric][] | Enables the `vcenter.datacenter.cpu.limit` metric.           | `true`  | no       |
+| `vcenter.datacenter.datastore.count`     | [metric][] | Enables the `vcenter.datacenter.datastore.count` metric.     | `true`  | no       |
+| `vcenter.datacenter.disk.space`          | [metric][] | Enables the `vcenter.datacenter.disk.space` metric.          | `true`  | no       |
+| `vcenter.datacenter.host.count`          | [metric][] | Enables the `vcenter.datacenter.host.count` metric.          | `true`  | no       |
+| `vcenter.datacenter.memory.limit`        | [metric][] | Enables the `vcenter.datacenter.memory.limit` metric.        | `true`  | no       |
+| `vcenter.datacenter.vm.count`            | [metric][] | Enables the `vcenter.datacenter.vm.count` metric.            | `true`  | no       |
+| `vcenter.datastore.disk.usage`           | [metric][] | Enables the `vcenter.datastore.disk.usage` metric.           | `true`  | no       |
+| `vcenter.datastore.disk.utilization`     | [metric][] | Enables the `vcenter.datastore.disk.utilization` metric.     | `true`  | no       |
+| `vcenter.host.cpu.capacity`              | [metric][] | Enables the `vcenter.host.cpu.capacity` metric.              | `true`  | no       |
+| `vcenter.host.cpu.reserved`              | [metric][] | Enables the `vcenter.host.cpu.reserved` metric.              | `true`  | no       |
+| `vcenter.host.cpu.usage`                 | [metric][] | Enables the `vcenter.host.cpu.usage` metric.                 | `true`  | no       |
+| `vcenter.host.cpu.utilization`           | [metric][] | Enables the `vcenter.host.cpu.utilization` metric.           | `true`  | no       |
+| `vcenter.host.disk.latency.avg`          | [metric][] | Enables the `vcenter.host.disk.latency.avg` metric.          | `true`  | no       |
+| `vcenter.host.disk.latency.max`          | [metric][] | Enables the `vcenter.host.disk.latency.max` metric.          | `true`  | no       |
+| `vcenter.host.disk.throughput`           | [metric][] | Enables the `vcenter.host.disk.throughput` metric.           | `true`  | no       |
+| `vcenter.host.memory.usage`              | [metric][] | Enables the `vcenter.host.memory.usage` metric.              | `true`  | no       |
+| `vcenter.host.memory.utilization`        | [metric][] | Enables the `vcenter.host.memory.utilization` metric.        | `true`  | no       |
+| `vcenter.host.network.packet.rate`       | [metric][] | Enables the `vcenter.host.network.packet.rate` metric.       | `true`  | no       |
+| `vcenter.host.network.packet.error.rate` | [metric][] | Enables the `vcenter.host.network.packet.error.rate` metric. | `true`  | no       |
+| `vcenter.host.network.packet.drop.rate`  | [metric][] | Enables the `vcenter.host.network.packet.drop.rate` metric.  | `true`  | no       |
+| `vcenter.host.network.throughput`        | [metric][] | Enables the `vcenter.host.network.throughput` metric.        | `true`  | no       |
+| `vcenter.host.network.usage`             | [metric][] | Enables the `vcenter.host.network.usage` metric.             | `true`  | no       |
+| `vcenter.host.vsan.cache.hit_rate`       | [metric][] | Enables the `vcenter.host.vsan.cache.hit_rate` metric.       | `true`  | no       |
+| `vcenter.host.vsan.congestions`          | [metric][] | Enables the `vcenter.host.vsan.congestions` metric.          | `true`  | no       |
+| `vcenter.host.vsan.latency.avg`          | [metric][] | Enables the `vcenter.host.vsan.latency.avg` metric.          | `true`  | no       |
+| `vcenter.host.vsan.operations`           | [metric][] | Enables the `vcenter.host.vsan.operations` metric.           | `true`  | no       |
+| `vcenter.host.vsan.throughput`           | [metric][] | Enables the `vcenter.host.vsan.throughput` metric.           | `true`  | no       |
+| `vcenter.resource_pool.cpu.shares`       | [metric][] | Enables the `vcenter.resource_pool.cpu.shares` metric.       | `true`  | no       |
+| `vcenter.resource_pool.cpu.usage`        | [metric][] | Enables the `vcenter.resource_pool.cpu.usage` metric.        | `true`  | no       |
+| `vcenter.resource_pool.memory.ballooned` | [metric][] | Enables the `vcenter.resource_pool.memory.ballooned` metric. | `true`  | no       |
+| `vcenter.resource_pool.memory.granted`   | [metric][] | Enables the `vcenter.resource_pool.memory.granted` metric.   | `true`  | no       |
+| `vcenter.resource_pool.memory.shares`    | [metric][] | Enables the `vcenter.resource_pool.memory.shares` metric.    | `true`  | no       |
+| `vcenter.resource_pool.memory.swapped`   | [metric][] | Enables the `vcenter.resource_pool.memory.swapped` metric.   | `true`  | no       |
+| `vcenter.resource_pool.memory.usage`     | [metric][] | Enables the `vcenter.resource_pool.memory.usage` metric.     | `true`  | no       |
+| `vcenter.vm.cpu.readiness`               | [metric][] | Enables the `vcenter.vm.cpu.readiness` metric.               | `true`  | no       |
+| `vcenter.vm.cpu.usage`                   | [metric][] | Enables the `vcenter.vm.cpu.usage` metric.                   | `true`  | no       |
+| `vcenter.vm.cpu.utilization`             | [metric][] | Enables the `vcenter.vm.cpu.utilization` metric.             | `true`  | no       |
+| `vcenter.vm.disk.latency.avg`            | [metric][] | Enables the `vcenter.vm.disk.latency.avg` metric.            | `true`  | no       |
+| `vcenter.vm.disk.latency.max`            | [metric][] | Enables the `vcenter.vm.disk.latency.max` metric.            | `true`  | no       |
+| `vcenter.vm.disk.throughput`             | [metric][] | Enables the `vcenter.vm.disk.throughput` metric.             | `true`  | no       |
+| `vcenter.vm.disk.usage`                  | [metric][] | Enables the `vcenter.vm.disk.usage` metric.                  | `true`  | no       |
+| `vcenter.vm.disk.utilization`            | [metric][] | Enables the `vcenter.vm.disk.utilization` metric.            | `true`  | no       |
+| `vcenter.vm.memory.ballooned`            | [metric][] | Enables the `vcenter.vm.memory.ballooned` metric.            | `true`  | no       |
+| `vcenter.vm.memory.swapped`              | [metric][] | Enables the `vcenter.vm.memory.swapped` metric.              | `true`  | no       |
+| `vcenter.vm.memory.swapped_ssd`          | [metric][] | Enables the `vcenter.vm.memory.swapped_ssd` metric.          | `true`  | no       |
+| `vcenter.vm.memory.usage`                | [metric][] | Enables the `vcenter.vm.memory.usage` metric.                | `true`  | no       |
+| `vcenter.vm.memory.utilization`          | [metric][] | Enables the `vcenter.vm.memory.utilization` metric.          | `true`  | no       |
+| `vcenter.vm.network.packet.rate`         | [metric][] | Enables the `vcenter.vm.network.packet.rate` metric.         | `true`  | no       |
+| `vcenter.vm.network.packet.drop.rate`    | [metric][] | Enables the `vcenter.vm.network.packet.drop.rate` metric.    | `true`  | no       |
+| `vcenter.vm.network.throughput`          | [metric][] | Enables the `vcenter.vm.network.throughput` metric.          | `true`  | no       |
+| `vcenter.vm.network.usage`               | [metric][] | Enables the `vcenter.vm.network.usage` metric.               | `true`  | no       |
+| `vcenter.vm.vsan.latency.avg`            | [metric][] | Enables the `vcenter.vm.vsan.latency.avg` metric.            | `true`  | no       |
+| `vcenter.vm.vsan.operations`             | [metric][] | Enables the `vcenter.vm.vsan.operations` metric.             | `true`  | no       |
+| `vcenter.vm.vsan.throughput`             | [metric][] | Enables the `vcenter.vm.vsan.throughput` metric.             | `true`  | no       |
 
 [metric]: #metric-block
 
 #### metric block
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `boolean` | Whether to enable the metric. | `true` | no
-
+| Name      | Type      | Description                   | Default | Required |
+| --------- | --------- | ----------------------------- | ------- | -------- |
+| `enabled` | `boolean` | Whether to enable the metric. | `true`  | no       |
 
 ### resource_attributes block
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`vcenter.datacenter.name` | [resource_attribute][] | Enables the `vcenter.datacenter.name` resource attribute. | `true` | no
-`vcenter.cluster.name` | [resource_attribute][] | Enables the `vcenter.cluster.name` resource attribute. | `true` | no
-`vcenter.datastore.name` | [resource_attribute][] | Enables the `vcenter.cluster.resource_pool` resource attribute. | `true` | no
-`vcenter.host.name` | [resource_attribute][] | Enables the `vcenter.host.name` resource attribute. | `true` | no
-`vcenter.resource_pool.inventory_path` | [resource_attribute][] | Enables the `vcenter.resource_pool.inventory_path` resource attribute. | `true` | no
-`vcenter.resource_pool.name` | [resource_attribute][] | Enables the `vcenter.resource_pool.name` resource attribute. | `true` | no
-`vcenter.virtual_app.inventory_path` | [resource_attribute][] | Enables the `vcenter.virtual_app.inventory_path` resource attribute. | `true` | no
-`vcenter.virtual_app.name` | [resource_attribute][] | Enables the `vcenter.virtual_app.name` resource attribute. | `true` | no
-`vcenter.vm.id` | [resource_attribute][] | Enables the `vcenter.vm.id` resource attribute. | `true` | no
-`vcenter.vm.name` | [resource_attribute][] | Enables the `vcenter.vm.name` resource attribute. | `true` | no
-`vcenter.vm_template.id` | [resource_attribute][] | Enables the `vcenter.vm_template.id` resource attribute. | `true` | no
-`vcenter.vm_template.name` | [resource_attribute][] | Enables the `vcenter.vm_template.name` resource attribute. | `true` | no
+| Name                                   | Type                   | Description                                                            | Default | Required |
+| -------------------------------------- | ---------------------- | ---------------------------------------------------------------------- | ------- | -------- |
+| `vcenter.datacenter.name`              | [resource_attribute][] | Enables the `vcenter.datacenter.name` resource attribute.              | `true`  | no       |
+| `vcenter.cluster.name`                 | [resource_attribute][] | Enables the `vcenter.cluster.name` resource attribute.                 | `true`  | no       |
+| `vcenter.datastore.name`               | [resource_attribute][] | Enables the `vcenter.cluster.resource_pool` resource attribute.        | `true`  | no       |
+| `vcenter.host.name`                    | [resource_attribute][] | Enables the `vcenter.host.name` resource attribute.                    | `true`  | no       |
+| `vcenter.resource_pool.inventory_path` | [resource_attribute][] | Enables the `vcenter.resource_pool.inventory_path` resource attribute. | `true`  | no       |
+| `vcenter.resource_pool.name`           | [resource_attribute][] | Enables the `vcenter.resource_pool.name` resource attribute.           | `true`  | no       |
+| `vcenter.virtual_app.inventory_path`   | [resource_attribute][] | Enables the `vcenter.virtual_app.inventory_path` resource attribute.   | `true`  | no       |
+| `vcenter.virtual_app.name`             | [resource_attribute][] | Enables the `vcenter.virtual_app.name` resource attribute.             | `true`  | no       |
+| `vcenter.vm.id`                        | [resource_attribute][] | Enables the `vcenter.vm.id` resource attribute.                        | `true`  | no       |
+| `vcenter.vm.name`                      | [resource_attribute][] | Enables the `vcenter.vm.name` resource attribute.                      | `true`  | no       |
+| `vcenter.vm_template.id`               | [resource_attribute][] | Enables the `vcenter.vm_template.id` resource attribute.               | `true`  | no       |
+| `vcenter.vm_template.name`             | [resource_attribute][] | Enables the `vcenter.vm_template.name` resource attribute.             | `true`  | no       |
 
 [resource_attribute]: #resource_attribute-block
 
 #### resource_attribute block
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `boolean` | Whether to enable the resource attribute. | `true` | no
-
+| Name      | Type      | Description                               | Default | Required |
+| --------- | --------- | ----------------------------------------- | ------- | -------- |
+| `enabled` | `boolean` | Whether to enable the resource attribute. | `true`  | no       |
 
 ### debug_metrics block
 
@@ -258,7 +255,6 @@ otelcol.exporter.otlp "default" {
 
 - Components that export [OpenTelemetry `otelcol.Consumer`](../../../compatibility/#opentelemetry-otelcolconsumer-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/otelcol/otelcol.receiver.zipkin.md b/docs/sources/reference/components/otelcol/otelcol.receiver.zipkin.md
index f5f66d4bca..4290a4e01f 100644
--- a/docs/sources/reference/components/otelcol/otelcol.receiver.zipkin.md
+++ b/docs/sources/reference/components/otelcol/otelcol.receiver.zipkin.md
@@ -32,13 +32,13 @@ otelcol.receiver.zipkin "LABEL" {
 
 `otelcol.receiver.zipkin` supports the following arguments:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`parse_string_tags` | `bool` | Parse string tags and binary annotations into non-string types. | `false` | no
-`endpoint` | `string` | `host:port` to listen for traffic on. | `"0.0.0.0:9411"` | no
-`max_request_body_size` | `string`   | Maximum request body size the server will allow.                   | `20MiB`          | no
-`include_metadata` | `boolean` | Propagate incoming connection metadata to downstream consumers. | | no
-`compression_algorithms` | `list(string)` | A list of compression algorithms the server can accept.    | `["", "gzip", "zstd", "zlib", "snappy", "deflate", "lz4"]` | no
+| Name                     | Type           | Description                                                     | Default                                                    | Required |
+| ------------------------ | -------------- | --------------------------------------------------------------- | ---------------------------------------------------------- | -------- |
+| `parse_string_tags`      | `bool`         | Parse string tags and binary annotations into non-string types. | `false`                                                    | no       |
+| `endpoint`               | `string`       | `host:port` to listen for traffic on.                           | `"0.0.0.0:9411"`                                           | no       |
+| `max_request_body_size`  | `string`       | Maximum request body size the server will allow.                | `20MiB`                                                    | no       |
+| `include_metadata`       | `boolean`      | Propagate incoming connection metadata to downstream consumers. |                                                            | no       |
+| `compression_algorithms` | `list(string)` | A list of compression algorithms the server can accept.         | `["", "gzip", "zstd", "zlib", "snappy", "deflate", "lz4"]` | no       |
 
 If `parse_string_tags` is `true`, string tags and binary annotations are
 converted to `int`, `bool`, and `float` if possible. String tags and binary
@@ -49,12 +49,12 @@ annotations that cannot be converted remain unchanged.
 The following blocks are supported inside the definition of
 `otelcol.receiver.zipkin`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-tls | [tls][] | Configures TLS for the HTTP server. | no
-cors | [cors][] | Configures CORS for the HTTP server. | no
-debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no
-output | [output][] | Configures where to send received traces. | yes
+| Hierarchy     | Block             | Description                                                                | Required |
+| ------------- | ----------------- | -------------------------------------------------------------------------- | -------- |
+| tls           | [tls][]           | Configures TLS for the HTTP server.                                        | no       |
+| cors          | [cors][]          | Configures CORS for the HTTP server.                                       | no       |
+| debug_metrics | [debug_metrics][] | Configures the metrics that this component generates to monitor its state. | no       |
+| output        | [output][]        | Configures where to send received traces.                                  | yes      |
 
 The `>` symbol indicates deeper levels of nesting. For example, `grpc > tls`
 refers to a `tls` block defined inside a `grpc` block.
@@ -77,19 +77,19 @@ The `cors` block configures CORS settings for an HTTP server.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`allowed_origins` | `list(string)` | Allowed values for the `Origin` header. | | no
-`allowed_headers` | `list(string)` | Accepted headers from CORS requests. | `["X-Requested-With"]` | no
-`max_age` | `number` | Configures the `Access-Control-Max-Age` response header. | | no
+| Name              | Type           | Description                                              | Default                | Required |
+| ----------------- | -------------- | -------------------------------------------------------- | ---------------------- | -------- |
+| `allowed_origins` | `list(string)` | Allowed values for the `Origin` header.                  |                        | no       |
+| `allowed_headers` | `list(string)` | Accepted headers from CORS requests.                     | `["X-Requested-With"]` | no       |
+| `max_age`         | `number`       | Configures the `Access-Control-Max-Age` response header. |                        | no       |
 
 The `allowed_headers` argument specifies which headers are acceptable from a
 CORS request. The following headers are always implicitly allowed:
 
-* `Accept`
-* `Accept-Language`
-* `Content-Type`
-* `Content-Language`
+- `Accept`
+- `Accept-Language`
+- `Content-Type`
+- `Content-Language`
 
 If `allowed_headers` includes `"*"`, all headers are permitted.
 
@@ -141,6 +141,7 @@ otelcol.exporter.otlp "default" {
   }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -149,10 +150,9 @@ otelcol.exporter.otlp "default" {
 
 - Components that export [OpenTelemetry `otelcol.Consumer`](../../../compatibility/#opentelemetry-otelcolconsumer-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
 {{< /admonition >}}
 
-<!-- END GENERATED COMPATIBLE COMPONENTS -->
\ No newline at end of file
+<!-- END GENERATED COMPATIBLE COMPONENTS -->
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.azure.md b/docs/sources/reference/components/prometheus/prometheus.exporter.azure.md
index 8dd99becd7..0db2c84db9 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.azure.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.azure.md
@@ -61,22 +61,22 @@ prometheus.exporter.azure LABEL {
 You can use the following arguments to configure the exporter's behavior.
 Omitted fields take their default values.
 
-| Name                          | Type           | Description                                                                                          | Default                                                                       | Required |
-|-------------------------------|----------------|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|----------|
-| `subscriptions`               | `list(string)` | List of subscriptions to scrape metrics from.                                                        |                                                                               | yes      |
-| `resource_type`               | `string`       | The Azure Resource Type to scrape metrics for.                                                       |                                                                               | yes      |
-| `metrics`                     | `list(string)` | The metrics to scrape from resources.                                                                |                                                                               | yes      |
-| `resource_graph_query_filter` | `string`       | The [Kusto query][] filter to apply when searching for resources. Can't be used if `regions` is set. |                                                                               | no       |
-| `regions`                     | `list(string)` | The list of regions for gathering metrics and enables gathering metrics for all resources in the subscription. Can't be used if `resource_graph_query_filter` is set. |              | no       |
-| `metric_aggregations`         | `list(string)` | Aggregations to apply for the metrics produced.                                                      |                                                                               | no       |
-| `timespan`                    | `string`       | [ISO8601 Duration][] over which the metrics are being queried.                                       | `"PT1M"` (1 minute)                                                           | no       |
-| `included_dimensions`         | `list(string)` | List of dimensions to include on the final metrics.                                                  |                                                                               | no       |
-| `included_resource_tags`      | `list(string)` | List of resource tags to include on the final metrics.                                               | `["owner"]`                                                                   | no       |
-| `metric_namespace`            | `string`       | Namespace for `resource_type` which have multiple levels of metrics.                                 |                                                                               | no       |
-| `azure_cloud_environment`     | `string`       | Name of the cloud environment to connect to.                                                         | `"azurecloud"`                                                                | no       |
-| `metric_name_template`        | `string`       | Metric template used to expose the metrics.                                                          | `"azure_{type}_{metric}_{aggregation}_{unit}"`                                | no       |
-| `metric_help_template`        | `string`       | Description of the metric.                                                                           | `"Azure metric {metric} for {type} with aggregation {aggregation} as {unit}"` | no       |
-| `validate_dimensions`         | `bool`         | Enable dimension validation in the azure sdk                                                         | `false`                                                                       | no       |
+| Name                          | Type           | Description                                                                                                                                                           | Default                                                                       | Required |
+| ----------------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | -------- |
+| `subscriptions`               | `list(string)` | List of subscriptions to scrape metrics from.                                                                                                                         |                                                                               | yes      |
+| `resource_type`               | `string`       | The Azure Resource Type to scrape metrics for.                                                                                                                        |                                                                               | yes      |
+| `metrics`                     | `list(string)` | The metrics to scrape from resources.                                                                                                                                 |                                                                               | yes      |
+| `resource_graph_query_filter` | `string`       | The [Kusto query][] filter to apply when searching for resources. Can't be used if `regions` is set.                                                                  |                                                                               | no       |
+| `regions`                     | `list(string)` | The list of regions for gathering metrics and enables gathering metrics for all resources in the subscription. Can't be used if `resource_graph_query_filter` is set. |                                                                               | no       |
+| `metric_aggregations`         | `list(string)` | Aggregations to apply for the metrics produced.                                                                                                                       |                                                                               | no       |
+| `timespan`                    | `string`       | [ISO8601 Duration][] over which the metrics are being queried.                                                                                                        | `"PT1M"` (1 minute)                                                           | no       |
+| `included_dimensions`         | `list(string)` | List of dimensions to include on the final metrics.                                                                                                                   |                                                                               | no       |
+| `included_resource_tags`      | `list(string)` | List of resource tags to include on the final metrics.                                                                                                                | `["owner"]`                                                                   | no       |
+| `metric_namespace`            | `string`       | Namespace for `resource_type` which have multiple levels of metrics.                                                                                                  |                                                                               | no       |
+| `azure_cloud_environment`     | `string`       | Name of the cloud environment to connect to.                                                                                                                          | `"azurecloud"`                                                                | no       |
+| `metric_name_template`        | `string`       | Metric template used to expose the metrics.                                                                                                                           | `"azure_{type}_{metric}_{aggregation}_{unit}"`                                | no       |
+| `metric_help_template`        | `string`       | Description of the metric.                                                                                                                                            | `"Azure metric {metric} for {type} with aggregation {aggregation} as {unit}"` | no       |
+| `validate_dimensions`         | `bool`         | Enable dimension validation in the azure sdk                                                                                                                          | `false`                                                                       | no       |
 
 The list of available `resource_type` values and their corresponding `metrics` can be found in [Azure Monitor essentials][].
 
@@ -86,13 +86,21 @@ The `resource_graph_query_filter` can be embedded into a template query of the f
 
 Valid values for `metric_aggregations` are `minimum`, `maximum`, `average`, `total`, and `count`.
 If no aggregation is specified, the value is retrieved from the metric.
+
 <!-- vale Grafana.GoogleSpacing = NO -->
+
 For example, the aggregation value of the metric `Availability` in [Microsoft.ClassicStorage/storageAccounts](https://learn.microsoft.com/en-us/azure/azure-monitor/reference/supported-metrics/microsoft-classicstorage-storageaccounts-metrics) is `average`.
+
 <!-- vale Grafana.GoogleSpacing = YES -->
+
 Every metric has its own set of dimensions.
+
 <!-- vale Grafana.GoogleSpacing = NO -->
+
 For example, the dimensions for the metric `Availability` in [Microsoft.ClassicStorage/storageAccounts](https://learn.microsoft.com/en-us/azure/azure-monitor/reference/supported-metrics/microsoft-classicstorage-storageaccounts-metrics) are `GeoType`, `ApiName`, and `Authentication`.
+
 <!-- vale Grafana.GoogleSpacing = YES -->
+
 If a single dimension is requested, it will have the name `dimension`.
 If multiple dimensions are requested, they will have the name `dimension<dimension_name>`.
 
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.blackbox.md b/docs/sources/reference/components/prometheus/prometheus.exporter.blackbox.md
index a2c65fedcb..aab8d9238a 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.blackbox.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.blackbox.md
@@ -22,7 +22,7 @@ prometheus.exporter.blackbox "LABEL" {
 }
 ```
 
-or 
+or
 
 ```alloy
 prometheus.exporter.blackbox "LABEL" {
@@ -37,8 +37,8 @@ Omitted fields take their default values.
 
 | Name                   | Type                 | Description                                                      | Default  | Required |
 | ---------------------- | -------------------- | ---------------------------------------------------------------- | -------- | -------- |
-| `config_file`          | `string`             | `blackbox_exporter` configuration file path.                       |          | no       |
-| `config`               | `string` or `secret` | `blackbox_exporter` configuration as inline string.                |          | no       |
+| `config_file`          | `string`             | `blackbox_exporter` configuration file path.                     |          | no       |
+| `config`               | `string` or `secret` | `blackbox_exporter` configuration as inline string.              |          | no       |
 | `probe_timeout_offset` | `duration`           | Offset in seconds to subtract from timeout when probing targets. | `"0.5s"` | no       |
 | `targets`              | `list(map(string))`  | Blackbox targets.                                                |          | no       |
 
@@ -55,9 +55,10 @@ You can't use both the `targets` argument and the [target][] block in the same c
 The `targets` argument must be used when blackbox targets cannot be passed as a target block because another component supplies them.
 
 You can set the following labels to a target:
-* `name`: The name of the target to probe (required).
-* `address`: The address of the target to probe (required).
-* `module`: The blackbox module to use to probe.
+
+- `name`: The name of the target to probe (required).
+- `address`: The address of the target to probe (required).
+- `module`: The blackbox module to use to probe.
 
 The component passes any additional labels to the exported target.
 
@@ -112,7 +113,7 @@ debug metrics.
 
 ### Collect metrics using a blackbox exporter configuration file
 
-This example uses a [`prometheus.scrape` component][scrape] to collect metrics from `prometheus.exporter.blackbox`. 
+This example uses a [`prometheus.scrape` component][scrape] to collect metrics from `prometheus.exporter.blackbox`.
 It adds an extra label, `env="dev"`, to the metrics emitted by the `grafana` target. The `example` target doesn't have any added labels.
 
 The `config_file` argument is used to define which `blackbox_exporter` modules to use. You can use the [blackbox example config file](https://github.com/prometheus/blackbox_exporter/blob/master/example.yml).
@@ -235,15 +236,16 @@ prometheus.remote_write "example" {
 ```
 
 The YAML file in this example looks like this:
+
 ```yaml
 - targets:
-  - localhost:9009
+    - localhost:9009
   labels:
     name: t1
     module: http_2xx
     other_label: example
 - targets:
-  - localhost:9009
+    - localhost:9009
   labels:
     name: t2
     module: http_2xx
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.cadvisor.md b/docs/sources/reference/components/prometheus/prometheus.exporter.cadvisor.md
index 5306643074..d01533100b 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.cadvisor.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.cadvisor.md
@@ -7,6 +7,7 @@ title: prometheus.exporter.cadvisor
 ---
 
 # prometheus.exporter.cadvisor
+
 The `prometheus.exporter.cadvisor` component exposes container metrics using
 [cAdvisor](https://github.com/google/cadvisor).
 
@@ -18,29 +19,30 @@ prometheus.exporter.cadvisor "LABEL" {
 ```
 
 ## Arguments
+
 The following arguments can be used to configure the exporter's behavior.
 All arguments are optional. Omitted fields take their default values.
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`store_container_labels` | `bool` | Whether to convert container labels and environment variables into labels on Prometheus metrics for each container. | `true` | no
-`allowlisted_container_labels` | `list(string)` | Allowlist of container labels to convert to Prometheus labels. | `[]`  | no
-`env_metadata_allowlist` | `list(string)` | Allowlist of environment variable keys matched with a specified prefix that needs to be collected for containers. | `[]` | no
-`raw_cgroup_prefix_allowlist` | `list(string)` | List of cgroup path prefixes that need to be collected, even when docker_only is specified. | `[]` | no
-`perf_events_config` | `string` | Path to a JSON file containing the configuration of perf events to measure. | `""` | no
-`resctrl_interval` | `duration` | Interval to update resctrl mon groups. | `0` | no
-`disabled_metrics` | `list(string)` | List of metrics to be disabled which, if set, overrides the default disabled metrics. | (see below) | no
-`enabled_metrics` | `list(string)` | List of metrics to be enabled which, if set, overrides disabled_metrics. | `[]` | no
-`storage_duration` | `duration` | Length of time to keep data stored in memory. | `2m` | no
-`containerd_host` | `string` | Containerd endpoint. | `/run/containerd/containerd.sock` | no
-`containerd_namespace` | `string` | Containerd namespace. | `k8s.io` | no
-`docker_host` | `string` | Docker endpoint. | `unix:///var/run/docker.sock` | no
-`use_docker_tls` | `bool` | Use TLS to connect to docker. | `false` | no
-`docker_tls_cert` | `string` | Path to client certificate for TLS connection to docker. | `cert.pem` | no
-`docker_tls_key` | `string` | Path to private key for TLS connection to docker. | `key.pem` | no
-`docker_tls_ca` | `string` | Path to a trusted CA for TLS connection to docker. | `ca.pem` | no
-`docker_only` | `bool` | Only report docker containers in addition to root stats. | `false` | no
-`disable_root_cgroup_stats` | `bool` | Disable collecting root Cgroup stats. | `false` | no
+| Name                           | Type           | Description                                                                                                         | Default                           | Required |
+| ------------------------------ | -------------- | ------------------------------------------------------------------------------------------------------------------- | --------------------------------- | -------- |
+| `store_container_labels`       | `bool`         | Whether to convert container labels and environment variables into labels on Prometheus metrics for each container. | `true`                            | no       |
+| `allowlisted_container_labels` | `list(string)` | Allowlist of container labels to convert to Prometheus labels.                                                      | `[]`                              | no       |
+| `env_metadata_allowlist`       | `list(string)` | Allowlist of environment variable keys matched with a specified prefix that needs to be collected for containers.   | `[]`                              | no       |
+| `raw_cgroup_prefix_allowlist`  | `list(string)` | List of cgroup path prefixes that need to be collected, even when docker_only is specified.                         | `[]`                              | no       |
+| `perf_events_config`           | `string`       | Path to a JSON file containing the configuration of perf events to measure.                                         | `""`                              | no       |
+| `resctrl_interval`             | `duration`     | Interval to update resctrl mon groups.                                                                              | `0`                               | no       |
+| `disabled_metrics`             | `list(string)` | List of metrics to be disabled which, if set, overrides the default disabled metrics.                               | (see below)                       | no       |
+| `enabled_metrics`              | `list(string)` | List of metrics to be enabled which, if set, overrides disabled_metrics.                                            | `[]`                              | no       |
+| `storage_duration`             | `duration`     | Length of time to keep data stored in memory.                                                                       | `2m`                              | no       |
+| `containerd_host`              | `string`       | Containerd endpoint.                                                                                                | `/run/containerd/containerd.sock` | no       |
+| `containerd_namespace`         | `string`       | Containerd namespace.                                                                                               | `k8s.io`                          | no       |
+| `docker_host`                  | `string`       | Docker endpoint.                                                                                                    | `unix:///var/run/docker.sock`     | no       |
+| `use_docker_tls`               | `bool`         | Use TLS to connect to docker.                                                                                       | `false`                           | no       |
+| `docker_tls_cert`              | `string`       | Path to client certificate for TLS connection to docker.                                                            | `cert.pem`                        | no       |
+| `docker_tls_key`               | `string`       | Path to private key for TLS connection to docker.                                                                   | `key.pem`                         | no       |
+| `docker_tls_ca`                | `string`       | Path to a trusted CA for TLS connection to docker.                                                                  | `ca.pem`                          | no       |
+| `docker_only`                  | `bool`         | Only report docker containers in addition to root stats.                                                            | `false`                           | no       |
+| `disable_root_cgroup_stats`    | `bool`         | Disable collecting root Cgroup stats.                                                                               | `false`                           | no       |
 
 For `allowlisted_container_labels` to take effect, `store_container_labels` must be set to `false`.
 
@@ -52,7 +54,8 @@ A `resctrl_interval` of `0` disables updating mon groups.
 
 The values for `enabled_metrics` and `disabled_metrics` do not correspond to
 Prometheus metrics, but to kinds of metrics that should (or shouldn't) be
-exposed. The full list of values that can be used is 
+exposed. The full list of values that can be used is
+
 ```
 "cpu", "sched", "percpu", "memory", "memory_numa", "cpuLoad", "diskIO", "disk",
 "network", "tcp", "advtcp", "udp", "app", "process", "hugetlb", "perf_event",
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.cloudwatch.md b/docs/sources/reference/components/prometheus/prometheus.exporter.cloudwatch.md
index dc45e8b0a6..62125e802f 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.cloudwatch.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.cloudwatch.md
@@ -121,13 +121,13 @@ prometheus.exporter.cloudwatch "queues" {
 You can use the following arguments to configure the exporter's behavior.
 Omitted fields take their default values.
 
-| Name                      | Type                | Description                                                                    | Default | Required |
-|---------------------------|---------------------|--------------------------------------------------------------------------------|---------|----------|
-| `sts_region`              | `string`            | AWS region to use when calling [STS][] for retrieving account information.     |         | yes      |
+| Name                      | Type                | Description                                                                                                                                                                                                                             | Default | Required |
+| ------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | -------- |
+| `sts_region`              | `string`            | AWS region to use when calling [STS][] for retrieving account information.                                                                                                                                                              |         | yes      |
 | `aws_sdk_version_v2`      | `bool`              | Use AWS SDK version 2.                                                                                                                                                                                                                  | `false` | no       |
-| `fips_disabled`           | `bool`              | Disable use of FIPS endpoints. Set 'true' when running outside of USA regions. | `true`  | no       |
-| `debug`                   | `bool`              | Enable debug logging on CloudWatch exporter internals.                         | `false` | no       |
-| `discovery_exported_tags` | `map(list(string))` | List of tags (value) per service (key) to export in all metrics. For example, defining the `["name", "type"]` under `"AWS/EC2"` will export the name and type tags and its values as labels in all metrics. Affects all discovery jobs. | `{}` | no |
+| `fips_disabled`           | `bool`              | Disable use of FIPS endpoints. Set 'true' when running outside of USA regions.                                                                                                                                                          | `true`  | no       |
+| `debug`                   | `bool`              | Enable debug logging on CloudWatch exporter internals.                                                                                                                                                                                  | `false` | no       |
+| `discovery_exported_tags` | `map(list(string))` | List of tags (value) per service (key) to export in all metrics. For example, defining the `["name", "type"]` under `"AWS/EC2"` will export the name and type tags and its values as labels in all metrics. Affects all discovery jobs. | `{}`    | no       |
 
 [STS]: https://docs.aws.amazon.com/STS/latest/APIReference/welcome.html
 
@@ -136,20 +136,20 @@ Omitted fields take their default values.
 You can use the following blocks in`prometheus.exporter.cloudwatch` to configure collector-specific options:
 
 | Hierarchy                 | Name                   | Description                                                                                                                                                | Required |
-|--------------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|
+| ------------------------- | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
 | discovery                 | [discovery][]          | Configures a discovery job. Multiple jobs can be configured.                                                                                               | no\*     |
 | discovery > role          | [role][]               | Configures the IAM roles the job should assume to scrape metrics. Defaults to the role configured in the environment {{< param "PRODUCT_NAME" >}} runs on. | no       |
 | discovery > metric        | [metric][]             | Configures the list of metrics the job should scrape. Multiple metrics can be defined inside one job.                                                      | yes      |
 | static                    | [static][]             | Configures a static job. Multiple jobs can be configured.                                                                                                  | no\*     |
 | static > role             | [role][]               | Configures the IAM roles the job should assume to scrape metrics. Defaults to the role configured in the environment {{< param "PRODUCT_NAME" >}} runs on. | no       |
 | static > metric           | [metric][]             | Configures the list of metrics the job should scrape. Multiple metrics can be defined inside one job.                                                      | yes      |
-| custom_namespace          | [custom_namespace][]   | Configures a custom namespace job. Multiple jobs can be configured.                                                                                               | no\*     |
+| custom_namespace          | [custom_namespace][]   | Configures a custom namespace job. Multiple jobs can be configured.                                                                                        | no\*     |
 | custom_namespace > role   | [role][]               | Configures the IAM roles the job should assume to scrape metrics. Defaults to the role configured in the environment {{< param "PRODUCT_NAME" >}} runs on. | no       |
 | custom_namespace > metric | [metric][]             | Configures the list of metrics the job should scrape. Multiple metrics can be defined inside one job.                                                      | yes      |
 | decoupled_scraping        | [decoupled_scraping][] | Configures the decoupled scraping feature to retrieve metrics on a schedule and return the cached metrics.                                                 | no       |
 
 {{< admonition type="note" >}}
-The `static`, `discovery`, and `custom_namespace` blocks are marked as not required, 
+The `static`, `discovery`, and `custom_namespace` blocks are marked as not required,
 but you must configure at least one static, discovery, or custom namespace job.
 {{< /admonition >}}
 
@@ -198,7 +198,7 @@ different `search_tags`.
 | `regions`                     | `list(string)` | List of AWS regions.                                                                                                                                                                                                                                       |         | yes      |
 | `type`                        | `string`       | CloudWatch service alias (`"alb"`, `"ec2"`, etc) or namespace name (`"AWS/EC2"`, `"AWS/S3"`, etc). Refer to [supported-services][] for a complete list.                                                                                                    |         | yes      |
 | `custom_tags`                 | `map(string)`  | Custom tags to be added as a list of key / value pairs. When exported to Prometheus format, the label name follows the following format: `custom_tag_{key}`.                                                                                               | `{}`    | no       |
-| `recently_active_only`        | `bool`         | Only return metrics that have been active in the last 3 hours.                                                                                                                                 | `false` | no       |
+| `recently_active_only`        | `bool`         | Only return metrics that have been active in the last 3 hours.                                                                                                                                                                                             | `false` | no       |
 | `search_tags`                 | `map(string)`  | List of key / value pairs to use for tag filtering (all must match). Value can be a regex.                                                                                                                                                                 | `{}`    | no       |
 | `dimension_name_requirements` | `list(string)` | List of metric dimensions to query. Before querying metric values, the total list of metrics will be filtered to only those that contain exactly this list of dimensions. An empty or undefined list results in all dimension combinations being included. | `{}`    | no       |
 | `nil_to_zero`                 | `bool`         | When `true`, `NaN` metric values are converted to 0. Individual metrics can override this value in the [metric][] block.                                                                                                                                   | `true`  | no       |
@@ -296,13 +296,12 @@ You can configure the `custom_namespace` block multiple times if you need to scr
 | Name                          | Type           | Description                                                                                                                                                                                                                                                | Default | Required |
 | ----------------------------- | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | -------- |
 | `regions`                     | `list(string)` | List of AWS regions.                                                                                                                                                                                                                                       |         | yes      |
-| `namespace`                   | `string`       | CloudWatch metric namespace.                                                                                                                                 |         | yes      |
-| `recently_active_only`        | `bool`         | Only return metrics that have been active in the last 3 hours.                                                                                                                                 | `false` | no       |
+| `namespace`                   | `string`       | CloudWatch metric namespace.                                                                                                                                                                                                                               |         | yes      |
+| `recently_active_only`        | `bool`         | Only return metrics that have been active in the last 3 hours.                                                                                                                                                                                             | `false` | no       |
 | `custom_tags`                 | `map(string)`  | Custom tags to be added as a list of key / value pairs. When exported to Prometheus format, the label name follows the following format: `custom_tag_{key}`.                                                                                               | `{}`    | no       |
 | `dimension_name_requirements` | `list(string)` | List of metric dimensions to query. Before querying metric values, the total list of metrics will be filtered to only those that contain exactly this list of dimensions. An empty or undefined list results in all dimension combinations being included. | `{}`    | no       |
 | `nil_to_zero`                 | `bool`         | When `true`, `NaN` metric values are converted to 0. Individual metrics can override this value in the [metric][] block.                                                                                                                                   | `true`  | no       |
 
-
 ### metric block
 
 Represents an AWS Metrics to scrape. To see available metrics, AWS does not keep a documentation page with all available
@@ -362,9 +361,9 @@ permission to assume the target role.
 Refer to [Granting a user permissions to switch roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_permissions-to-switch.html)
 in the AWS IAM documentation for more information about how to configure this.
 
-| Name          | Type     | Description                                                             | Default | Required |
-| ------------- | -------- | ----------------------------------------------------------------------- | ------- | -------- |
-| `role_arn`    | `string` | AWS IAM Role ARN the exporter should assume to perform AWS API calls.   |         | yes      |
+| Name          | Type     | Description                                                                                                    | Default | Required |
+| ------------- | -------- | -------------------------------------------------------------------------------------------------------------- | ------- | -------- |
+| `role_arn`    | `string` | AWS IAM Role ARN the exporter should assume to perform AWS API calls.                                          |         | yes      |
 | `external_id` | `string` | External ID used when calling STS AssumeRole API. Refer to the [IAM User Guide][details] for more information. | `""`    | no       |
 
 [details]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.consul.md b/docs/sources/reference/components/prometheus/prometheus.exporter.consul.md
index 69f4cb5c4a..a5245b837c 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.consul.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.consul.md
@@ -23,21 +23,21 @@ prometheus.exporter.consul "LABEL" {
 The following arguments can be used to configure the exporter's behavior.
 All arguments are optional. Omitted fields take their default values.
 
-| Name                       | Type       | Description                                                                                                                                                         | Default                 | Required |
-| -------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | -------- |
+| Name                       | Type       | Description                                                                                                                                                                                | Default                 | Required |
+| -------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------- | -------- |
 | `server`                   | `string`   | Address (host and port) of the Consul instance we should connect to. This could be a local {{< param "PRODUCT_NAME" >}} (localhost:8500, for instance), or the address of a Consul server. | `http://localhost:8500` | no       |
-| `ca_file`                  | `string`   | File path to a PEM-encoded certificate authority used to validate the authenticity of a server certificate.                                                         |                         | no       |
-| `cert_file`                | `string`   | File path to a PEM-encoded certificate used with the private key to verify the exporter's authenticity.                                                             |                         | no       |
-| `key_file`                 | `string`   | File path to a PEM-encoded private key used with the certificate to verify the exporter's authenticity.                                                             |                         | no       |
-| `server_name`              | `string`   | When provided, this overrides the hostname for the TLS certificate. It can be used to ensure that the certificate name matches the hostname we declare.             |                         | no       |
-| `timeout`                  | `duration` | Timeout on HTTP requests to consul.                                                                                                                                 | 500ms                   | no       |
-| `insecure_skip_verify`     | `bool`     | Disable TLS host verification.                                                                                                                                      | false                   | no       |
-| `concurrent_request_limit` | `string`   | Limit the maximum number of concurrent requests to consul, 0 means no limit.                                                                                        |                         | no       |
-| `allow_stale`              | `bool`     | Allows any Consul server (non-leader) to service a read.                                                                                                            | `true`                  | no       |
-| `require_consistent`       | `bool`     | Forces the read to be fully consistent.                                                                                                                             |                         | no       |
-| `kv_prefix`                | `string`   | Prefix under which to look for KV pairs.                                                                                                                            |                         | no       |
-| `kv_filter`                | `string`   | Only store keys that match this regex pattern.                                                                                                                      | `.*`                    | no       |
-| `generate_health_summary`  | `bool`     | Collects information about each registered service and exports `consul_catalog_service_node_healthy`.                                                               | `true`                  | no       |
+| `ca_file`                  | `string`   | File path to a PEM-encoded certificate authority used to validate the authenticity of a server certificate.                                                                                |                         | no       |
+| `cert_file`                | `string`   | File path to a PEM-encoded certificate used with the private key to verify the exporter's authenticity.                                                                                    |                         | no       |
+| `key_file`                 | `string`   | File path to a PEM-encoded private key used with the certificate to verify the exporter's authenticity.                                                                                    |                         | no       |
+| `server_name`              | `string`   | When provided, this overrides the hostname for the TLS certificate. It can be used to ensure that the certificate name matches the hostname we declare.                                    |                         | no       |
+| `timeout`                  | `duration` | Timeout on HTTP requests to consul.                                                                                                                                                        | 500ms                   | no       |
+| `insecure_skip_verify`     | `bool`     | Disable TLS host verification.                                                                                                                                                             | false                   | no       |
+| `concurrent_request_limit` | `string`   | Limit the maximum number of concurrent requests to consul, 0 means no limit.                                                                                                               |                         | no       |
+| `allow_stale`              | `bool`     | Allows any Consul server (non-leader) to service a read.                                                                                                                                   | `true`                  | no       |
+| `require_consistent`       | `bool`     | Forces the read to be fully consistent.                                                                                                                                                    |                         | no       |
+| `kv_prefix`                | `string`   | Prefix under which to look for KV pairs.                                                                                                                                                   |                         | no       |
+| `kv_filter`                | `string`   | Only store keys that match this regex pattern.                                                                                                                                             | `.*`                    | no       |
+| `generate_health_summary`  | `bool`     | Collects information about each registered service and exports `consul_catalog_service_node_healthy`.                                                                                      | `true`                  | no       |
 
 ## Exported fields
 
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.elasticsearch.md b/docs/sources/reference/components/prometheus/prometheus.exporter.elasticsearch.md
index ece2a01af8..5eb290fee9 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.elasticsearch.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.elasticsearch.md
@@ -50,7 +50,7 @@ Omitted fields take their default values.
 | `client_cert`          | `string`   | Path to PEM file that contains the corresponding cert for the private key to connect to Elasticsearch. |                           | no       |
 | `ssl_skip_verify`      | `bool`     | Skip SSL verification when connecting to Elasticsearch.                                                |                           | no       |
 | `aliases`              | `bool`     | Include informational aliases metrics.                                                                 |                           | no       |
-| `data_stream`         | `bool`     | Export stats for Data Streams.                                                                         |                           | no       |
+| `data_stream`          | `bool`     | Export stats for Data Streams.                                                                         |                           | no       |
 | `slm`                  | `bool`     | Export stats for SLM (Snapshot Lifecycle Management).                                                  |                           | no       |
 
 ## Blocks
@@ -58,9 +58,9 @@ Omitted fields take their default values.
 The following blocks are supported inside the definition of
 `prometheus.exporter.elasticsearch`:
 
-| Hierarchy           | Block             | Description                                              | Required |
-| ------------------- | ----------------- | -------------------------------------------------------- | -------- |
-| basic_auth          | [basic_auth][]    | Configure basic_auth for authenticating to the endpoint. | no       |
+| Hierarchy  | Block          | Description                                              | Required |
+| ---------- | -------------- | -------------------------------------------------------- | -------- |
+| basic_auth | [basic_auth][] | Configure basic_auth for authenticating to the endpoint. | no       |
 
 [basic_auth]: #basic_auth-block
 
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.gcp.md b/docs/sources/reference/components/prometheus/prometheus.exporter.gcp.md
index bf57f4d1e5..563cf23508 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.gcp.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.gcp.md
@@ -61,7 +61,7 @@ For example, `loadbalancing.googleapis.com:resource.labels.backend_target_name="
 {{< /admonition >}}
 
 | Name                      | Type           | Description                                                                                                                                                                                                                                              | Default | Required |
-|---------------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----------|
+| ------------------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | -------- |
 | `project_ids`             | `list(string)` | Configure the GCP Projects to scrape for metrics.                                                                                                                                                                                                        |         | yes      |
 | `metrics_prefixes`        | `list(string)` | One or more values from the supported [GCP Metrics](https://cloud.google.com/monitoring/api/metrics_gcp). These can be as targeted or loose as needed.                                                                                                   |         | yes      |
 | `extra_filters`           | `list(string)` | Used to further refine the resources you would like to collect metrics from. Any string value within a particular filter string must be enclosed in escaped double-quotes. The structure for these filters is `<targeted_metric_prefix>:<filter_query>`. | `[]`    | no       |
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.mysql.md b/docs/sources/reference/components/prometheus/prometheus.exporter.mysql.md
index ca76c50c0d..38408cfda5 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.mysql.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.mysql.md
@@ -95,9 +95,9 @@ View more detailed documentation on the tables used in `perf_schema_file_instanc
 
 ### perf_schema.memory_events block
 
-| Name            | Type     | Description                                                                         | Default            | Required |
-| --------------- | -------- | ----------------------------------------------------------------------------------- | ------------------ | -------- |
-| `remove_prefix` | `string` | Prefix to trim away from `performance_schema.memory_summary_global_by_event_name`.  | `"memory/"`        | no       |
+| Name            | Type     | Description                                                                        | Default     | Required |
+| --------------- | -------- | ---------------------------------------------------------------------------------- | ----------- | -------- |
+| `remove_prefix` | `string` | Prefix to trim away from `performance_schema.memory_summary_global_by_event_name`. | `"memory/"` | no       |
 
 ### heartbeat block
 
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.postgres.md b/docs/sources/reference/components/prometheus/prometheus.exporter.postgres.md
index 64a34d4065..183b08e2d8 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.postgres.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.postgres.md
@@ -25,7 +25,7 @@ prometheus.exporter.postgres "LABEL" {
 The following arguments are supported:
 
 | Name                         | Type           | Description                                                                   | Default | Required |
-|------------------------------|----------------|-------------------------------------------------------------------------------|---------|----------|
+| ---------------------------- | -------------- | ----------------------------------------------------------------------------- | ------- | -------- |
 | `data_source_names`          | `list(secret)` | Specifies the PostgreSQL servers to connect to.                               |         | yes      |
 | `disable_settings_metrics`   | `bool`         | Disables collection of metrics from `pg_settings`.                            | `false` | no       |
 | `disable_default_metrics`    | `bool`         | When `true`, only exposes metrics supplied from `custom_queries_config_path`. | `false` | no       |
@@ -48,36 +48,36 @@ If `disable_default_metrics` is set to `true`, only the metrics defined in the `
 A subset of metrics collectors can be controlled by setting the `enabled_collectors` argument.
 The following collectors are available for selection:
 
-* `database`
-* `database_wraparound`
-* `locks`
-* `long_running_transactions`
-* `postmaster`
-* `process_idle`
-* `replication`
-* `replication_slot`
-* `stat_activity_autovacuum`
-* `stat_bgwriter`
-* `stat_database`
-* `stat_statements`
-* `stat_user_tables`
-* `stat_wal_receiver`
-* `statio_user_indexes`
-* `statio_user_tables`
-* `wal`
-* `xlog_location`
+- `database`
+- `database_wraparound`
+- `locks`
+- `long_running_transactions`
+- `postmaster`
+- `process_idle`
+- `replication`
+- `replication_slot`
+- `stat_activity_autovacuum`
+- `stat_bgwriter`
+- `stat_database`
+- `stat_statements`
+- `stat_user_tables`
+- `stat_wal_receiver`
+- `statio_user_indexes`
+- `statio_user_tables`
+- `wal`
+- `xlog_location`
 
 By default, the following collectors are enabled:
 
-* `database`
-* `locks`
-* `replication`
-* `replication_slot`
-* `stat_bgwriter`
-* `stat_database`
-* `stat_user_tables`
-* `statio_user_tables`
-* `wal`
+- `database`
+- `locks`
+- `replication`
+- `replication_slot`
+- `stat_bgwriter`
+- `stat_database`
+- `stat_user_tables`
+- `statio_user_tables`
+- `wal`
 
 {{< admonition type="note" >}}
 Due to a limitation of the upstream exporter, when multiple `data_source_names` are used, the collectors that are controlled via the `enabled_collectors` argument will only be applied to the first data source in the list.
@@ -100,7 +100,7 @@ The `autodiscovery` block configures discovery of databases, outside of any spec
 The following arguments are supported:
 
 | Name                 | Type           | Description                                                                    | Default | Required |
-|----------------------|----------------|--------------------------------------------------------------------------------|---------|----------|
+| -------------------- | -------------- | ------------------------------------------------------------------------------ | ------- | -------- |
 | `enabled`            | `bool`         | Whether to automatically discover other databases.                             | `false` | no       |
 | `database_allowlist` | `list(string)` | List of databases to filter for, meaning only these databases will be scraped. |         | no       |
 | `database_denylist`  | `list(string)` | List of databases to filter out, meaning all other databases will be scraped.  |         | no       |
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.self.md b/docs/sources/reference/components/prometheus/prometheus.exporter.self.md
index 34078ac665..679a140a52 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.self.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.self.md
@@ -65,10 +65,12 @@ prometheus.remote_write "demo" {
   }
 }
 ```
+
 Replace the following:
-  - `PROMETHEUS_REMOTE_WRITE_URL`: The URL of the Prometheus remote_write-compatible server to send metrics to.
-  - `USERNAME`: The username to use for authentication to the remote_write API.
-  - `PASSWORD`: The password to use for authentication to the remote_write API.
+
+- `PROMETHEUS_REMOTE_WRITE_URL`: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- `USERNAME`: The username to use for authentication to the remote_write API.
+- `PASSWORD`: The password to use for authentication to the remote_write API.
 
 [scrape]: ../prometheus.scrape/
 
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.snmp.md b/docs/sources/reference/components/prometheus/prometheus.exporter.snmp.md
index 664263dcad..fdcc9cbcb4 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.snmp.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.snmp.md
@@ -59,11 +59,12 @@ The `config` argument must be a YAML document as string defining which SNMP modu
 
 The `targets` argument is an alternative to the [target][] block. This is useful when SNMP targets are supplied by another component.
 The following labels can be set to a target:
-* `name`: The name of the target (required).
-* `address` or `__address__`: The address of SNMP device (required).
-* `module`: The SNMP module to use for polling.
-* `auth`: The SNMP authentication profile to use.
-* `walk_params`: The config to use for this target.
+
+- `name`: The name of the target (required).
+- `address` or `__address__`: The address of SNMP device (required).
+- `module`: The SNMP module to use for polling.
+- `auth`: The SNMP authentication profile to use.
+- `walk_params`: The config to use for this target.
 
 Any other labels defined are added to the scraped metrics.
 
@@ -74,7 +75,7 @@ The following blocks are supported inside the definition of
 
 | Hierarchy  | Name           | Description                                                 | Required |
 | ---------- | -------------- | ----------------------------------------------------------- | -------- |
-| target     | [target][]     | Configures an SNMP target.                                  | no      |
+| target     | [target][]     | Configures an SNMP target.                                  | no       |
 | walk_param | [walk_param][] | SNMP connection profiles to override default SNMP settings. | no       |
 
 [target]: #target-block
@@ -86,7 +87,7 @@ The `target` block defines an individual SNMP target.
 The `target` block may be specified multiple times to define multiple targets. The label of the block is required and will be used in the target's `job` label.
 
 | Name           | Type          | Description                                                           | Default | Required |
-|----------------|---------------|-----------------------------------------------------------------------| ------- | -------- |
+| -------------- | ------------- | --------------------------------------------------------------------- | ------- | -------- |
 | `address`      | `string`      | The address of SNMP device.                                           |         | yes      |
 | `module`       | `string`      | SNMP module to use for polling.                                       | `""`    | no       |
 | `auth`         | `string`      | SNMP authentication profile to use.                                   | `""`    | no       |
@@ -94,7 +95,6 @@ The `target` block may be specified multiple times to define multiple targets. T
 | `snmp_context` | `string`      | Override the `context_name` parameter in the SNMP configuration file. | `""`    | no       |
 | `labels`       | `map(string)` | Map of labels to apply to all metrics captured from the target.       | `""`    | no       |
 
-
 ### walk_param block
 
 The `walk_param` block defines an individual SNMP connection profile that can be used to override default SNMP settings.
@@ -218,6 +218,7 @@ prometheus.remote_write "demo" {
 ```
 
 Replace the following:
+
 - _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to.
 - _`<USERNAME>`_: The username to use for authentication to the remote_write API.
 - _`<PASSWORD>`_: The password to use for authentication to the remote_write API.
@@ -289,6 +290,7 @@ prometheus.scrape "demo" {
 ```
 
 The YAML file in this example looks like this:
+
 ```yaml
 - name: t1
   address: localhost:161
@@ -301,6 +303,7 @@ The YAML file in this example looks like this:
 ```
 
 This example uses the [`discovery.file` component][disc] to send targets to the `prometheus.exporter.snmp` component:
+
 ```alloy
 discovery.file "example" {
   files = ["targets.yml"]
@@ -319,15 +322,16 @@ prometheus.scrape "demo" {
 ```
 
 The YAML file in this example looks like this:
+
 ```yaml
 - targets:
-  - localhost:161
+    - localhost:161
   labels:
     name: t1
     module: default
     auth: public_v2
 - targets:
-  - localhost:161
+    - localhost:161
   labels:
     name: t2
     module: default
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.snowflake.md b/docs/sources/reference/components/prometheus/prometheus.exporter.snowflake.md
index 460560f3b5..ddeef75311 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.snowflake.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.snowflake.md
@@ -67,7 +67,7 @@ Users with an encrypted private key will also need to provide a `private_key_pas
 | `private_key_password`   | `secret` | The password for the user's RSA private key (required for encrypted RSA key-pair authentication). |                  | no       |
 | `role`                   | `string` | The role to use when querying metrics.                                                            | `"ACCOUNTADMIN"` | no       |
 | `warehouse`              | `string` | The warehouse to use when querying metrics.                                                       |                  | yes      |
-| `exclude_deleted_tables` |  `bool`  | Whether to exclude deleted tables when querying table storage metrics.                            | `false`          | no       |
+| `exclude_deleted_tables` | `bool`   | Whether to exclude deleted tables when querying table storage metrics.                            | `false`          | no       |
 
 ## Blocks
 
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.unix.md b/docs/sources/reference/components/prometheus/prometheus.exporter.unix.md
index c7dc3e5c42..73246afd76 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.unix.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.unix.md
@@ -13,7 +13,6 @@ The `prometheus.exporter.unix` component uses [node_exporter](https://github.com
 The `node_exporter` itself is comprised of various _collectors_, which can be enabled and disabled at will.
 For more information on collectors, refer to the [`collectors-list`](#collectors-list) section.
 
-
 You can specify multiple `prometheus.exporter.unix` components by giving them different labels.
 
 ## Usage
@@ -105,12 +104,12 @@ The following blocks are supported inside the definition of `prometheus.exporter
 
 ### cpu block
 
-| Name            | Type      | Description                                        | Default | Required |
-| --------------- | --------- | -------------------------------------------------- |---------| -------- |
-| `guest`         | `boolean` | Enable the `node_cpu_guest_seconds_total` metric.  | false   | no       |
-| `info`          | `boolean` | Enable the `cpu_info` metric for the cpu collector.| false   | no       |
-| `bugs_include`  | `string`  | Regexp of `bugs` field in cpu info to filter.      |         | no       |
-| `flags_include` | `string`  | Regexp of `flags` field in cpu info to filter.     |         | no       |
+| Name            | Type      | Description                                         | Default | Required |
+| --------------- | --------- | --------------------------------------------------- | ------- | -------- |
+| `guest`         | `boolean` | Enable the `node_cpu_guest_seconds_total` metric.   | false   | no       |
+| `info`          | `boolean` | Enable the `cpu_info` metric for the cpu collector. | false   | no       |
+| `bugs_include`  | `string`  | Regexp of `bugs` field in cpu info to filter.       |         | no       |
+| `flags_include` | `string`  | Regexp of `flags` field in cpu info to filter.      |         | no       |
 
 ### disk block
 
@@ -121,7 +120,7 @@ The following blocks are supported inside the definition of `prometheus.exporter
 
 ### ethtool block
 
-| Name              | Type     | Description                                                                      | Default | Required |
+| Name              | Type     | Description                                                                     | Default | Required |
 | ----------------- | -------- | ------------------------------------------------------------------------------- | ------- | -------- |
 | `device_exclude`  | `string` | Regexp of ethtool devices to exclude. Mutually exclusive with `device_include`. |         | no       |
 | `device_include`  | `string` | Regexp of ethtool devices to include. Mutually exclusive with `device_exclude`. |         | no       |
@@ -132,7 +131,7 @@ The following blocks are supported inside the definition of `prometheus.exporter
 The default values vary by the operating system {{< param "PRODUCT_NAME" >}} runs on.
 
 | Name                   | Type       | Description                                                         | Default        | Required |
-|------------------------|------------|---------------------------------------------------------------------|----------------|----------|
+| ---------------------- | ---------- | ------------------------------------------------------------------- | -------------- | -------- |
 | `fs_types_exclude`     | `string`   | Regexp of filesystem types to ignore for filesystem collector.      | (_see below_ ) | no       |
 | `mount_points_exclude` | `string`   | Regexp of mount points to ignore for filesystem collector.          | (_see below_ ) | no       |
 | `mount_timeout`        | `duration` | How long to wait for a mount to respond before marking it as stale. | `"5s"`         | no       |
@@ -140,37 +139,45 @@ The default values vary by the operating system {{< param "PRODUCT_NAME" >}} run
 `fs_types_exclude` defaults to the following regular expression string:
 
 {{< code >}}
+
 ```linux
 ^(autofs|binfmt_misc|bpf|cgroup2?|configfs|debugfs|devpts|devtmpfs|fusectl|hugetlbfs|iso9660|mqueue|nsfs|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|selinuxfs|squashfs|sysfs|tracefs)$
 ```
+
 ```osx
 ^(autofs|devfs)$
 ```
+
 ```bsd
 ^devfs$
 ```
+
 {{< /code >}}
 
 `mount_points_exclude` defaults to the following regular expression string:
 
 {{< code >}}
+
 ```linux
 ^/(dev|proc|run/credentials/.+|sys|var/lib/docker/.+)($|/)
 ```
+
 ```osx
 ^/(dev)($|/)
 ```
+
 ```bsd
 ^/(dev)($|/)
 ```
+
 {{< /code >}}
 
 ### hwmon block
 
-| Name               | Type       | Description                                                                        | Default  | Required |
-|--------------------|------------|------------------------------------------------------------------------------------|----------|----------|
-| `chip_include`     | `string`   | Regular expression of hwmon chip to include. Mutually exclusive to `chip-exclude`. |          | no       |
-| `chip_exclude`     | `string`   | Regular expression of hwmon chip to exclude. Mutually exclusive to `chip-include`. |          | no       |
+| Name           | Type     | Description                                                                        | Default | Required |
+| -------------- | -------- | ---------------------------------------------------------------------------------- | ------- | -------- |
+| `chip_include` | `string` | Regular expression of hwmon chip to include. Mutually exclusive to `chip-exclude`. |         | no       |
+| `chip_exclude` | `string` | Regular expression of hwmon chip to exclude. Mutually exclusive to `chip-include`. |         | no       |
 
 ### ipvs block
 
@@ -180,7 +187,7 @@ The default values vary by the operating system {{< param "PRODUCT_NAME" >}} run
 
 ### ntp block
 
-| name                     | type       | description                                                   | default       | required |
+| name                     | type       | description                                                  | default       | required |
 | ------------------------ | ---------- | ------------------------------------------------------------ | ------------- | -------- |
 | `server`                 | `string`   | NTP server to use for the collector.                         | `"127.0.0.1"` | no       |
 | `server_is_local`        | `boolean`  | Certifies that the server address isn't a public NTP server. | false         | no       |
@@ -313,80 +320,80 @@ Enabling a collector that's not supported by the host operating system where {{<
 
 Users can choose to enable a subset of collectors to limit the amount of metrics exposed by the `prometheus.exporter.unix` component, or disable collectors that are expensive to run.
 
-| Name               | Description                                                                                                   | OS                                                                 | Enabled by default |
-|--------------------|---------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|--------------------|
-| `arp`              | Exposes ARP statistics from `/proc/net/arp`.                                                                  | Linux                                                              | yes                |
-| `bcache`           | Exposes bcache statistics from `/sys/fs/bcache`.                                                              | Linux                                                              | yes                |
-| `bonding`          | Exposes the number of configured and active slaves of Linux bonding interfaces.                               | Linux                                                              | yes                |
-| `boottime`         | Exposes system boot time derived from the `kern.boottime sysctl`.                                             | Darwin, Dragonfly, FreeBSD, NetBSD, OpenBSD, Oracle Solaris        | yes                |
-| `btrfs`            | Exposes statistics on btrfs.                                                                                  | Linux                                                              | yes                |
-| `buddyinfo`        | Exposes statistics of memory fragments as reported by `/proc/buddyinfo`.                                      | Linux                                                              | no                 |
-| `conntrack`        | Shows conntrack statistics. Does nothing if no `/proc/sys/net/netfilter/` is present.                         | Linux                                                              | yes                |
-| `cpu`              | Exposes CPU statistics.                                                                                       | Darwin, Dragonfly, FreeBSD, Linux, Oracle Solaris, NetBSD          | yes                |
-| `cpufreq`          | Exposes CPU frequency statistics.                                                                             | Linux, Oracle Solaris                                              | yes                |
-| `devstat`          | Exposes device statistics.                                                                                    | Dragonfly, FreeBSD                                                 | no                 |
-| `diskstats`        | Exposes disk I/O statistics.                                                                                  | Darwin, Linux, OpenBSD                                             | yes                |
-| `dmi`              | Exposes DMI information.                                                                                      | Linux                                                              | yes                |
-| `drbd`             | Exposes Distributed Replicated Block Device statistics (to version 8.4).                                      | Linux                                                              | no                 |
-| `drm`              | Exposes GPU card info from `/sys/class/drm/card?/device`.                                                     | Linux                                                              | no                 |
-| `edac`             | Exposes error detection and correction statistics.                                                            | Linux                                                              | yes                |
-| `entropy`          | Exposes available entropy.                                                                                    | Linux                                                              | yes                |
-| `ethtool`          | Exposes ethtool stats.                                                                                        | Linux                                                              | no                 |
-| `exec`             | Exposes execution statistics.                                                                                 | Dragonfly, FreeBSD                                                 | yes                |
-| `fibrechannel`     | Exposes FibreChannel statistics.                                                                              | Linux                                                              | yes                |
-| `filefd`           | Exposes file descriptor statistics from `/proc/sys/fs/file-nr`.                                               | Linux                                                              | yes                |
-| `filesystem`       | Exposes filesystem statistics, such as disk space used.                                                       | Darwin, Dragonfly, FreeBSD, Linux, OpenBSD                         | yes                |
-| `hwmon`            | Exposes hardware monitoring and sensor data from `/sys/class/hwmon`.                                          | Linux                                                              | yes                |
-| `infiniband`       | Exposes network statistics specific to InfiniBand and Intel OmniPath configurations.                          | Linux                                                              | yes                |
-| `interrupts`       | Exposes detailed interrupts statistics.                                                                       | Linux, OpenBSD                                                     | no                 |
-| `ipvs`             | Exposes IPVS status from `/proc/net/ip_vs` and stats from `/proc/net/ip_vs_stats`.                            | Linux                                                              | yes                |
-| `ksmd`             | Exposes kernel and system statistics from `/sys/kernel/mm/ksm`.                                               | Linux                                                              | no                 |
-| `lnstat`           | Exposes Linux network cache stats.                                                                            | Linux                                                              | no                 |
-| `loadavg`          | Exposes load average.                                                                                         | Darwin, Dragonfly, FreeBSD, Linux, NetBSD, OpenBSD, Oracle Solaris | yes                |
-| `logind`           | Exposes session counts from logind.                                                                           | Linux                                                              | no                 |
-| `mdadm`            | Exposes statistics about devices in `/proc/mdstat`. Does nothing if no `/proc/mdstat` is present.             | Linux                                                              | yes                |
-| `meminfo`          | Exposes memory statistics.                                                                                    | Darwin, Dragonfly, FreeBSD, Linux, OpenBSD, NetBSD                 | yes                |
-| `meminfo_numa`     | Exposes memory statistics from `/proc/meminfo_numa`.                                                          | Linux                                                              | no                 |
-| `mountstats`       | Exposes filesystem statistics from `/proc/self/mountstats`. Exposes detailed NFS client statistics.           | Linux                                                              | no                 |
-| `netclass`         | Exposes network interface info from `/sys/class/net`.                                                         | Linux                                                              | yes                |
-| `netdev`           | Exposes network interface statistics such as bytes transferred.                                               | Darwin, Dragonfly, FreeBSD, Linux, OpenBSD                         | yes                |
-| `netisr`           | Exposes netisr statistics.                                                                                    | FreeBSD                                                            | yes                |
-| `netstat`          | Exposes network statistics from `/proc/net/netstat`. This is the same information as `netstat -s`.            | Linux                                                              | yes                |
-| `network_route`    | Exposes network route statistics.                                                                             | Linux                                                              | no                 |
-| `nfs`              | Exposes NFS client statistics from `/proc/net/rpc/nfs`. This is the same information as `nfsstat -c`.         | Linux                                                              | yes                |
-| `nfsd`             | Exposes NFS kernel server statistics from `/proc/net/rpc/nfsd`. This is the same information as `nfsstat -s`. | Linux                                                              | yes                |
-| `ntp`              | Exposes local NTP daemon health to check time.                                                                | any                                                                | no                 |
-| `nvme`             | Exposes NVMe statistics.                                                                                      | Linux                                                              | yes                |
-| `os`               | Exposes os-release information.                                                                               | Linux                                                              | yes                |
-| `perf`             | Exposes perf based metric. **Warning**: Metrics are dependent on kernel configuration and settings.           | Linux                                                              | no                 |
-| `powersupplyclass` | Collects information on power supplies.                                                                       | any                                                                | yes                |
-| `pressure`         | Exposes pressure stall statistics from `/proc/pressure/`.                                                     | Linux kernel 4.20+ or CONFIG_PSI                                   | yes                |
-| `processes`        | Exposes aggregate process statistics from /proc.                                                              | Linux                                                              | no                 |
-| `qdisc`            | Exposes queuing discipline statistics.                                                                        | Linux                                                              | no                 |
-| `rapl`             | Exposes various statistics from `/sys/class/powercap`.                                                        | Linux                                                              | yes                |
-| `runit`            | Exposes service status from runit.                                                                            | any                                                                | no                 |
-| `schedstat`        | Exposes task scheduler statistics from `/proc/schedstat`.                                                     | Linux                                                              | yes                |
-| `sockstat`         | Exposes various statistics from `/proc/net/sockstat`.                                                         | Linux                                                              | yes                |
-| `softirqs`         | Exposes detailed softirq statistics from `/proc/softirqs`.                                                    | Linux                                                              | no                 |
-| `softnet`          | Exposes statistics from `/proc/net/softnet_stat`.                                                             | Linux                                                              | yes                |
-| `stat`             | Exposes various statistics from `/proc/stat`. This includes boot time, forks and interrupts.                  | Linux                                                              | yes                |
-| `supervisord`      | Exposes service status from supervisord.                                                                      | any                                                                | no                 |
-| `sysctl`           | Expose sysctl values from `/proc/sys`.                                                                        | Linux                                                              | no                 |
-| `systemd`          | Exposes service and system status from systemd.                                                               | Linux                                                              | no                 |
-| `tapestats`        | Exposes tape device stats.                                                                                    | Linux                                                              | yes                |
-| `tcpstat`          | Exposes TCP connection status information from `/proc/net/tcp` and `/proc/net/tcp6`. **Warning**: The current version has potential performance issues in high load situations. | Linux | no            |
-| `textfile`         | Collects metrics from files in a directory matching the filename pattern `*.prom`. The files must use [text-based exposition formats][formats].                                 | any   | yes           |
-| `thermal`          | Exposes thermal statistics.                                                                                   | Darwin                                                             | yes                |
-| `thermal_zone`     | Exposes thermal zone & cooling device statistics from `/sys/class/thermal`.                                   | Linux                                                              | yes                |
-| `time`             | Exposes the current system time.                                                                              | any                                                                | yes                |
-| `timex`            | Exposes selected `adjtimex(2)` system call stats.                                                             | Linux                                                              | yes                |
-| `udp_queues`       | Exposes UDP total lengths of the `rx_queue` and `tx_queue` from `/proc/net/udp` and `/proc/net/udp6`.         | Linux                                                              | yes                |
-| `uname`            | Exposes system information as provided by the uname system call.                                              | Darwin, FreeBSD, Linux, OpenBSD, NetBSD                            | yes                |
-| `vmstat`           | Exposes statistics from `/proc/vmstat`.                                                                       | Linux                                                              | yes                |
-| `wifi`             | Exposes WiFi device and station statistics.                                                                   | Linux                                                              | no                 |
-| `xfs`              | Exposes XFS runtime statistics.                                                                               | Linux kernel 4.4+                                                  | yes                |
-| `zfs`              | Exposes ZFS performance statistics.                                                                           | Linux, Oracle Solaris                                              | yes                |
-| `zoneinfo`         | Exposes zone stats.                                                                                           | Linux                                                              | no                 |
+| Name               | Description                                                                                                                                                                     | OS                                                                 | Enabled by default |
+| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | ------------------ |
+| `arp`              | Exposes ARP statistics from `/proc/net/arp`.                                                                                                                                    | Linux                                                              | yes                |
+| `bcache`           | Exposes bcache statistics from `/sys/fs/bcache`.                                                                                                                                | Linux                                                              | yes                |
+| `bonding`          | Exposes the number of configured and active slaves of Linux bonding interfaces.                                                                                                 | Linux                                                              | yes                |
+| `boottime`         | Exposes system boot time derived from the `kern.boottime sysctl`.                                                                                                               | Darwin, Dragonfly, FreeBSD, NetBSD, OpenBSD, Oracle Solaris        | yes                |
+| `btrfs`            | Exposes statistics on btrfs.                                                                                                                                                    | Linux                                                              | yes                |
+| `buddyinfo`        | Exposes statistics of memory fragments as reported by `/proc/buddyinfo`.                                                                                                        | Linux                                                              | no                 |
+| `conntrack`        | Shows conntrack statistics. Does nothing if no `/proc/sys/net/netfilter/` is present.                                                                                           | Linux                                                              | yes                |
+| `cpu`              | Exposes CPU statistics.                                                                                                                                                         | Darwin, Dragonfly, FreeBSD, Linux, Oracle Solaris, NetBSD          | yes                |
+| `cpufreq`          | Exposes CPU frequency statistics.                                                                                                                                               | Linux, Oracle Solaris                                              | yes                |
+| `devstat`          | Exposes device statistics.                                                                                                                                                      | Dragonfly, FreeBSD                                                 | no                 |
+| `diskstats`        | Exposes disk I/O statistics.                                                                                                                                                    | Darwin, Linux, OpenBSD                                             | yes                |
+| `dmi`              | Exposes DMI information.                                                                                                                                                        | Linux                                                              | yes                |
+| `drbd`             | Exposes Distributed Replicated Block Device statistics (to version 8.4).                                                                                                        | Linux                                                              | no                 |
+| `drm`              | Exposes GPU card info from `/sys/class/drm/card?/device`.                                                                                                                       | Linux                                                              | no                 |
+| `edac`             | Exposes error detection and correction statistics.                                                                                                                              | Linux                                                              | yes                |
+| `entropy`          | Exposes available entropy.                                                                                                                                                      | Linux                                                              | yes                |
+| `ethtool`          | Exposes ethtool stats.                                                                                                                                                          | Linux                                                              | no                 |
+| `exec`             | Exposes execution statistics.                                                                                                                                                   | Dragonfly, FreeBSD                                                 | yes                |
+| `fibrechannel`     | Exposes FibreChannel statistics.                                                                                                                                                | Linux                                                              | yes                |
+| `filefd`           | Exposes file descriptor statistics from `/proc/sys/fs/file-nr`.                                                                                                                 | Linux                                                              | yes                |
+| `filesystem`       | Exposes filesystem statistics, such as disk space used.                                                                                                                         | Darwin, Dragonfly, FreeBSD, Linux, OpenBSD                         | yes                |
+| `hwmon`            | Exposes hardware monitoring and sensor data from `/sys/class/hwmon`.                                                                                                            | Linux                                                              | yes                |
+| `infiniband`       | Exposes network statistics specific to InfiniBand and Intel OmniPath configurations.                                                                                            | Linux                                                              | yes                |
+| `interrupts`       | Exposes detailed interrupts statistics.                                                                                                                                         | Linux, OpenBSD                                                     | no                 |
+| `ipvs`             | Exposes IPVS status from `/proc/net/ip_vs` and stats from `/proc/net/ip_vs_stats`.                                                                                              | Linux                                                              | yes                |
+| `ksmd`             | Exposes kernel and system statistics from `/sys/kernel/mm/ksm`.                                                                                                                 | Linux                                                              | no                 |
+| `lnstat`           | Exposes Linux network cache stats.                                                                                                                                              | Linux                                                              | no                 |
+| `loadavg`          | Exposes load average.                                                                                                                                                           | Darwin, Dragonfly, FreeBSD, Linux, NetBSD, OpenBSD, Oracle Solaris | yes                |
+| `logind`           | Exposes session counts from logind.                                                                                                                                             | Linux                                                              | no                 |
+| `mdadm`            | Exposes statistics about devices in `/proc/mdstat`. Does nothing if no `/proc/mdstat` is present.                                                                               | Linux                                                              | yes                |
+| `meminfo`          | Exposes memory statistics.                                                                                                                                                      | Darwin, Dragonfly, FreeBSD, Linux, OpenBSD, NetBSD                 | yes                |
+| `meminfo_numa`     | Exposes memory statistics from `/proc/meminfo_numa`.                                                                                                                            | Linux                                                              | no                 |
+| `mountstats`       | Exposes filesystem statistics from `/proc/self/mountstats`. Exposes detailed NFS client statistics.                                                                             | Linux                                                              | no                 |
+| `netclass`         | Exposes network interface info from `/sys/class/net`.                                                                                                                           | Linux                                                              | yes                |
+| `netdev`           | Exposes network interface statistics such as bytes transferred.                                                                                                                 | Darwin, Dragonfly, FreeBSD, Linux, OpenBSD                         | yes                |
+| `netisr`           | Exposes netisr statistics.                                                                                                                                                      | FreeBSD                                                            | yes                |
+| `netstat`          | Exposes network statistics from `/proc/net/netstat`. This is the same information as `netstat -s`.                                                                              | Linux                                                              | yes                |
+| `network_route`    | Exposes network route statistics.                                                                                                                                               | Linux                                                              | no                 |
+| `nfs`              | Exposes NFS client statistics from `/proc/net/rpc/nfs`. This is the same information as `nfsstat -c`.                                                                           | Linux                                                              | yes                |
+| `nfsd`             | Exposes NFS kernel server statistics from `/proc/net/rpc/nfsd`. This is the same information as `nfsstat -s`.                                                                   | Linux                                                              | yes                |
+| `ntp`              | Exposes local NTP daemon health to check time.                                                                                                                                  | any                                                                | no                 |
+| `nvme`             | Exposes NVMe statistics.                                                                                                                                                        | Linux                                                              | yes                |
+| `os`               | Exposes os-release information.                                                                                                                                                 | Linux                                                              | yes                |
+| `perf`             | Exposes perf based metric. **Warning**: Metrics are dependent on kernel configuration and settings.                                                                             | Linux                                                              | no                 |
+| `powersupplyclass` | Collects information on power supplies.                                                                                                                                         | any                                                                | yes                |
+| `pressure`         | Exposes pressure stall statistics from `/proc/pressure/`.                                                                                                                       | Linux kernel 4.20+ or CONFIG_PSI                                   | yes                |
+| `processes`        | Exposes aggregate process statistics from /proc.                                                                                                                                | Linux                                                              | no                 |
+| `qdisc`            | Exposes queuing discipline statistics.                                                                                                                                          | Linux                                                              | no                 |
+| `rapl`             | Exposes various statistics from `/sys/class/powercap`.                                                                                                                          | Linux                                                              | yes                |
+| `runit`            | Exposes service status from runit.                                                                                                                                              | any                                                                | no                 |
+| `schedstat`        | Exposes task scheduler statistics from `/proc/schedstat`.                                                                                                                       | Linux                                                              | yes                |
+| `sockstat`         | Exposes various statistics from `/proc/net/sockstat`.                                                                                                                           | Linux                                                              | yes                |
+| `softirqs`         | Exposes detailed softirq statistics from `/proc/softirqs`.                                                                                                                      | Linux                                                              | no                 |
+| `softnet`          | Exposes statistics from `/proc/net/softnet_stat`.                                                                                                                               | Linux                                                              | yes                |
+| `stat`             | Exposes various statistics from `/proc/stat`. This includes boot time, forks and interrupts.                                                                                    | Linux                                                              | yes                |
+| `supervisord`      | Exposes service status from supervisord.                                                                                                                                        | any                                                                | no                 |
+| `sysctl`           | Expose sysctl values from `/proc/sys`.                                                                                                                                          | Linux                                                              | no                 |
+| `systemd`          | Exposes service and system status from systemd.                                                                                                                                 | Linux                                                              | no                 |
+| `tapestats`        | Exposes tape device stats.                                                                                                                                                      | Linux                                                              | yes                |
+| `tcpstat`          | Exposes TCP connection status information from `/proc/net/tcp` and `/proc/net/tcp6`. **Warning**: The current version has potential performance issues in high load situations. | Linux                                                              | no                 |
+| `textfile`         | Collects metrics from files in a directory matching the filename pattern `*.prom`. The files must use [text-based exposition formats][formats].                                 | any                                                                | yes                |
+| `thermal`          | Exposes thermal statistics.                                                                                                                                                     | Darwin                                                             | yes                |
+| `thermal_zone`     | Exposes thermal zone & cooling device statistics from `/sys/class/thermal`.                                                                                                     | Linux                                                              | yes                |
+| `time`             | Exposes the current system time.                                                                                                                                                | any                                                                | yes                |
+| `timex`            | Exposes selected `adjtimex(2)` system call stats.                                                                                                                               | Linux                                                              | yes                |
+| `udp_queues`       | Exposes UDP total lengths of the `rx_queue` and `tx_queue` from `/proc/net/udp` and `/proc/net/udp6`.                                                                           | Linux                                                              | yes                |
+| `uname`            | Exposes system information as provided by the uname system call.                                                                                                                | Darwin, FreeBSD, Linux, OpenBSD, NetBSD                            | yes                |
+| `vmstat`           | Exposes statistics from `/proc/vmstat`.                                                                                                                                         | Linux                                                              | yes                |
+| `wifi`             | Exposes WiFi device and station statistics.                                                                                                                                     | Linux                                                              | no                 |
+| `xfs`              | Exposes XFS runtime statistics.                                                                                                                                                 | Linux kernel 4.4+                                                  | yes                |
+| `zfs`              | Exposes ZFS performance statistics.                                                                                                                                             | Linux, Oracle Solaris                                              | yes                |
+| `zoneinfo`         | Exposes zone stats.                                                                                                                                                             | Linux                                                              | no                 |
 
 ## Run on Docker/Kubernetes
 
diff --git a/docs/sources/reference/components/prometheus/prometheus.exporter.windows.md b/docs/sources/reference/components/prometheus/prometheus.exporter.windows.md
index 816b15828f..76df80c5ba 100644
--- a/docs/sources/reference/components/prometheus/prometheus.exporter.windows.md
+++ b/docs/sources/reference/components/prometheus/prometheus.exporter.windows.md
@@ -7,6 +7,7 @@ title: prometheus.exporter.windows
 ---
 
 # prometheus.exporter.windows
+
 The `prometheus.exporter.windows` component embeds
 [windows_exporter][] which exposes a
 wide variety of hardware and OS metrics for Windows-based systems.
@@ -34,7 +35,7 @@ The following arguments can be used to configure the exporter's behavior.
 All arguments are optional. Omitted fields take their default values.
 
 | Name                 | Type           | Description                   | Default                                                     | Required |
-|----------------------|----------------|-------------------------------|-------------------------------------------------------------|----------|
+| -------------------- | -------------- | ----------------------------- | ----------------------------------------------------------- | -------- |
 | `enabled_collectors` | `list(string)` | List of collectors to enable. | `["cpu","cs","logical_disk","net","os","service","system"]` | no       |
 
 `enabled_collectors` defines a hand-picked list of enabled-by-default collectors.
@@ -46,24 +47,24 @@ Refer to the [Collectors list](#collectors-list) for the default set.
 The following blocks are supported inside the definition of
 `prometheus.exporter.windows` to configure collector-specific options:
 
-Hierarchy      | Name               | Description                              | Required
----------------|--------------------|------------------------------------------|---------
-dfsr           | [dfsr][]           | Configures the dfsr collector.           | no
-exchange       | [exchange][]       | Configures the exchange collector.       | no
-iis            | [iis][]            | Configures the iis collector.            | no
-logical_disk   | [logical_disk][]   | Configures the logical_disk collector.   | no
-msmq           | [msmq][]           | Configures the msmq collector.           | no
-mssql          | [mssql][]          | Configures the mssql collector.          | no
-network        | [network][]        | Configures the network collector.        | no
-physical_disk  | [physical_disk][]  | Configures the physical_disk collector.  | no
-printer        | [printer][]        | Configures the printer collector.        | no
-process        | [process][]        | Configures the process collector.        | no
-scheduled_task | [scheduled_task][] | Configures the scheduled_task collector. | no
-service        | [service][]        | Configures the service collector.        | no
-smb            | [smb][]            | Configures the smb collector.            | no
-smb_client     | [smb_client][]     | Configures the smb_client collector.     | no
-smtp           | [smtp][]           | Configures the smtp collector.           | no
-text_file      | [text_file][]      | Configures the text_file collector.      | no
+| Hierarchy      | Name               | Description                              | Required |
+| -------------- | ------------------ | ---------------------------------------- | -------- |
+| dfsr           | [dfsr][]           | Configures the dfsr collector.           | no       |
+| exchange       | [exchange][]       | Configures the exchange collector.       | no       |
+| iis            | [iis][]            | Configures the iis collector.            | no       |
+| logical_disk   | [logical_disk][]   | Configures the logical_disk collector.   | no       |
+| msmq           | [msmq][]           | Configures the msmq collector.           | no       |
+| mssql          | [mssql][]          | Configures the mssql collector.          | no       |
+| network        | [network][]        | Configures the network collector.        | no       |
+| physical_disk  | [physical_disk][]  | Configures the physical_disk collector.  | no       |
+| printer        | [printer][]        | Configures the printer collector.        | no       |
+| process        | [process][]        | Configures the process collector.        | no       |
+| scheduled_task | [scheduled_task][] | Configures the scheduled_task collector. | no       |
+| service        | [service][]        | Configures the service collector.        | no       |
+| smb            | [smb][]            | Configures the smb collector.            | no       |
+| smb_client     | [smb_client][]     | Configures the smb_client collector.     | no       |
+| smtp           | [smtp][]           | Configures the smtp collector.           | no       |
+| text_file      | [text_file][]      | Configures the text_file collector.      | no       |
 
 [dfsr]: #dfsr-block
 [exchange]: #exchange-block
@@ -84,34 +85,33 @@ text_file      | [text_file][]      | Configures the text_file collector.      |
 
 ### dfsr block
 
-Name             | Type           | Description                            | Default                            | Required
------------------|----------------|----------------------------------------|------------------------------------|---------
-`source_enabled` | `list(string)` | A list of DFSR Perflib sources to use. | `["connection","folder","volume"]` | no
-
+| Name             | Type           | Description                            | Default                            | Required |
+| ---------------- | -------------- | -------------------------------------- | ---------------------------------- | -------- |
+| `source_enabled` | `list(string)` | A list of DFSR Perflib sources to use. | `["connection","folder","volume"]` | no       |
 
 ### exchange block
 
-Name           | Type           | Description                  | Default       | Required
----------------|----------------|------------------------------|---------------|---------
-`enabled_list` | `list(string)` | A list of collectors to use. | `["ADAccessProcesses", "TransportQueues", "HttpProxy", "ActiveSync", "AvailabilityService", "OutlookWebAccess", "Autodiscover", "WorkloadManagement", "RpcClientAccess", "MapiHttpEmsmdb"]` | no
+| Name           | Type           | Description                  | Default                                                                                                                                                                                     | Required |
+| -------------- | -------------- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
+| `enabled_list` | `list(string)` | A list of collectors to use. | `["ADAccessProcesses", "TransportQueues", "HttpProxy", "ActiveSync", "AvailabilityService", "OutlookWebAccess", "Autodiscover", "WorkloadManagement", "RpcClientAccess", "MapiHttpEmsmdb"]` | no       |
 
 ### iis block
 
-Name           | Type     | Description                                      | Default   | Required
----------------|----------|--------------------------------------------------|-----------|---------
-`app_exclude`  | `string` | Regular expression of applications to ignore.    | `"^$"`    | no
-`app_include`  | `string` | Regular expression of applications to report on. | `"^.+$"`  | no
-`site_exclude` | `string` | Regular expression of sites to ignore.           | `"^$"`    | no
-`site_include` | `string` | Regular expression of sites to report on.        | `"^.+$"`  | no
+| Name           | Type     | Description                                      | Default  | Required |
+| -------------- | -------- | ------------------------------------------------ | -------- | -------- |
+| `app_exclude`  | `string` | Regular expression of applications to ignore.    | `"^$"`   | no       |
+| `app_include`  | `string` | Regular expression of applications to report on. | `"^.+$"` | no       |
+| `site_exclude` | `string` | Regular expression of sites to ignore.           | `"^$"`   | no       |
+| `site_include` | `string` | Regular expression of sites to report on.        | `"^.+$"` | no       |
 
 User-supplied `app_exclude`, `app_include`, `site_exclude` and `site_include` strings will be [wrapped][wrap-regex] in a regular expression.
 
 ### logical_disk block
 
-Name      | Type     | Description                               | Default   | Required
-----------|----------|-------------------------------------------|-----------|---------
-`exclude` | `string` | Regular expression of volumes to exclude. | `"^$"`    | no
-`include` | `string` | Regular expression of volumes to include. | `"^.+$"`  | no
+| Name      | Type     | Description                               | Default  | Required |
+| --------- | -------- | ----------------------------------------- | -------- | -------- |
+| `exclude` | `string` | Regular expression of volumes to exclude. | `"^$"`   | no       |
+| `include` | `string` | Regular expression of volumes to include. | `"^.+$"` | no       |
 
 Volume names must match the regular expression specified by `include` and must _not_ match the regular expression specified by `exclude` to be included.
 
@@ -119,25 +119,24 @@ User-supplied `exclude` and `include` strings will be [wrapped][wrap-regex] in a
 
 ### msmq block
 
-Name           | Type     | Description                                     | Default | Required
----------------|----------|-------------------------------------------------|---------|---------
-`where_clause` | `string` | WQL 'where' clause to use in WMI metrics query. | `""`    | no
+| Name           | Type     | Description                                     | Default | Required |
+| -------------- | -------- | ----------------------------------------------- | ------- | -------- |
+| `where_clause` | `string` | WQL 'where' clause to use in WMI metrics query. | `""`    | no       |
 
 Specifying `enabled_classes` is useful to limit the response to the MSMQs you specify, reducing the size of the response.
 
-
 ### mssql block
 
-Name | Type     | Description | Default | Required
----- |----------| ----------- | ------- | --------
-`enabled_classes` | `list(string)` | A list of MSSQL WMI classes to use. | `["accessmethods", "availreplica", "bufman", "databases", "dbreplica", "genstats", "locks", "memmgr", "sqlstats", "sqlerrors", "transactions", "waitstats"]` | no
+| Name              | Type           | Description                         | Default                                                                                                                                                      | Required |
+| ----------------- | -------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- |
+| `enabled_classes` | `list(string)` | A list of MSSQL WMI classes to use. | `["accessmethods", "availreplica", "bufman", "databases", "dbreplica", "genstats", "locks", "memmgr", "sqlstats", "sqlerrors", "transactions", "waitstats"]` | no       |
 
 ### network block
 
-Name      | Type     | Description                             | Default   | Required
-----------|----------|-----------------------------------------|-----------|---------
-`exclude` | `string` | Regular expression of NIC:s to exclude. | `"^$"`    | no
-`include` | `string` | Regular expression of NIC:s to include. | `"^.+$"`  | no
+| Name      | Type     | Description                             | Default  | Required |
+| --------- | -------- | --------------------------------------- | -------- | -------- |
+| `exclude` | `string` | Regular expression of NIC:s to exclude. | `"^$"`   | no       |
+| `include` | `string` | Regular expression of NIC:s to include. | `"^.+$"` | no       |
 
 NIC names must match the regular expression specified by `include` and must _not_ match the regular expression specified by `exclude` to be included.
 
@@ -145,19 +144,19 @@ User-supplied `exclude` and `include` strings will be [wrapped][wrap-regex] in a
 
 ### physical_disk block
 
-Name      | Type     | Description                                     | Default   | Required
-----------|----------|-------------------------------------------------|-----------|---------
-`exclude` | `string` | Regular expression of physical disk to exclude. | `"^$"`    | no
-`include` | `string` | Regular expression of physical disk to include. | `"^.+$"`  | no
+| Name      | Type     | Description                                     | Default  | Required |
+| --------- | -------- | ----------------------------------------------- | -------- | -------- |
+| `exclude` | `string` | Regular expression of physical disk to exclude. | `"^$"`   | no       |
+| `include` | `string` | Regular expression of physical disk to include. | `"^.+$"` | no       |
 
 User-supplied `exclude` and `include` strings will be [wrapped][wrap-regex] in a regular expression.
 
 ### printer block
 
-Name      | Type     | Description                               | Default   | Required
-----------|----------|-------------------------------------------|-----------|---------
-`exclude` | `string` | Regular expression of printer to exclude. | `"^$"`    | no
-`include` | `string` | Regular expression of printer to include. | `"^.+$"`  | no
+| Name      | Type     | Description                               | Default  | Required |
+| --------- | -------- | ----------------------------------------- | -------- | -------- |
+| `exclude` | `string` | Regular expression of printer to exclude. | `"^$"`   | no       |
+| `include` | `string` | Regular expression of printer to include. | `"^.+$"` | no       |
 
 Printer must match the regular expression specified by `include` and must _not_ match the regular expression specified by `exclude` to be included.
 
@@ -165,10 +164,10 @@ User-supplied `exclude` and `include` strings will be [wrapped][wrap-regex] in a
 
 ### process block
 
-Name      | Type     | Description                                 | Default   | Required
-----------|----------|---------------------------------------------|-----------|---------
-`exclude` | `string` | Regular expression of processes to exclude. | `"^$"`    | no
-`include` | `string` | Regular expression of processes to include. | `"^.+$"`  | no
+| Name      | Type     | Description                                 | Default  | Required |
+| --------- | -------- | ------------------------------------------- | -------- | -------- |
+| `exclude` | `string` | Regular expression of processes to exclude. | `"^$"`   | no       |
+| `include` | `string` | Regular expression of processes to include. | `"^.+$"` | no       |
 
 Processes must match the regular expression specified by `include` and must _not_ match the regular expression specified by `exclude` to be included.
 
@@ -176,10 +175,10 @@ User-supplied `exclude` and `include` strings will be [wrapped][wrap-regex] in a
 
 ### scheduled_task block
 
-Name      | Type     | Description                             | Default   | Required
-----------|----------|-----------------------------------------|-----------|---------
-`exclude` | `string` | Regular expression of tasks to exclude. | `"^$"`    | no
-`include` | `string` | Regular expression of tasks to include. | `"^.+$"`  | no
+| Name      | Type     | Description                             | Default  | Required |
+| --------- | -------- | --------------------------------------- | -------- | -------- |
+| `exclude` | `string` | Regular expression of tasks to exclude. | `"^$"`   | no       |
+| `include` | `string` | Regular expression of tasks to include. | `"^.+$"` | no       |
 
 For a server name to be included, it must match the regular expression specified by `include` and must _not_ match the regular expression specified by `exclude`.
 
@@ -187,11 +186,11 @@ User-supplied `exclude` and `include` strings will be [wrapped][wrap-regex] in a
 
 ### service block
 
-Name                  | Type     | Description                                           | Default   | Required
-----------------------|----------|-------------------------------------------------------|-----------|---------
-`enable_v2_collector` | `string` | Enable V2 service collector.                          | `"false"` | no
-`use_api`             | `string` | Use API calls to collect service data instead of WMI. | `"false"` | no
-`where_clause`        | `string` | WQL 'where' clause to use in WMI metrics query.       | `""`      | no
+| Name                  | Type     | Description                                           | Default   | Required |
+| --------------------- | -------- | ----------------------------------------------------- | --------- | -------- |
+| `enable_v2_collector` | `string` | Enable V2 service collector.                          | `"false"` | no       |
+| `use_api`             | `string` | Use API calls to collect service data instead of WMI. | `"false"` | no       |
+| `where_clause`        | `string` | WQL 'where' clause to use in WMI metrics query.       | `""`      | no       |
 
 The `where_clause` argument can be used to limit the response to the services you specify, reducing the size of the response.
 If `use_api` is enabled, 'where_clause' won't be effective.
@@ -200,9 +199,9 @@ The v2 collector can query service states much more efficiently, but can't provi
 
 ### smb block
 
-Name           | Type           | Description                                      | Default | Required
----------------|----------------|--------------------------------------------------|---------|---------
-`enabled_list` | `list(string)` | Deprecated (no-op), a list of collectors to use. | `[]`    | no
+| Name           | Type           | Description                                      | Default | Required |
+| -------------- | -------------- | ------------------------------------------------ | ------- | -------- |
+| `enabled_list` | `list(string)` | Deprecated (no-op), a list of collectors to use. | `[]`    | no       |
 
 The collectors specified by `enabled_list` can include the following:
 
@@ -212,9 +211,9 @@ For example, `enabled_list` may be set to `["ServerShares"]`.
 
 ### smb_client block
 
-Name           | Type           | Description                                      | Default | Required
----------------|----------------|--------------------------------------------------|---------|---------
-`enabled_list` | `list(string)` | Deprecated (no-op), a list of collectors to use. | `[]`    | no
+| Name           | Type           | Description                                      | Default | Required |
+| -------------- | -------------- | ------------------------------------------------ | ------- | -------- |
+| `enabled_list` | `list(string)` | Deprecated (no-op), a list of collectors to use. | `[]`    | no       |
 
 The collectors specified by `enabled_list` can include the following:
 
@@ -222,13 +221,12 @@ The collectors specified by `enabled_list` can include the following:
 
 For example, `enabled_list` may be set to `"ClientShares"`.
 
-
 ### smtp block
 
-Name      | Type     | Description                                       | Default   | Required
-----------|----------|---------------------------------------------------|-----------|---------
-`exclude` | `string` | Regular expression of virtual servers to ignore.  | `"^$"`    | no
-`include` | `string` | Regular expression of virtual servers to include. | `"^.+$"`  | no
+| Name      | Type     | Description                                       | Default  | Required |
+| --------- | -------- | ------------------------------------------------- | -------- | -------- |
+| `exclude` | `string` | Regular expression of virtual servers to ignore.  | `"^$"`   | no       |
+| `include` | `string` | Regular expression of virtual servers to include. | `"^.+$"` | no       |
 
 For a server name to be included, it must match the regular expression specified by `include` and must _not_ match the regular expression specified by `exclude`.
 
@@ -236,16 +234,16 @@ User-supplied `exclude` and `include` strings will be [wrapped][wrap-regex] in a
 
 ### text_file block
 
-Name                  | Type     | Description                                        | Default       | Required
-----------------------|----------|----------------------------------------------------|---------------|---------
-`text_file_directory` | `string` | The directory containing the files to be ingested. | __see_below__ | no
+| Name                  | Type     | Description                                        | Default       | Required |
+| --------------------- | -------- | -------------------------------------------------- | ------------- | -------- |
+| `text_file_directory` | `string` | The directory containing the files to be ingested. | **see_below** | no       |
 
 The default value for `text_file_directory` is relative to the location of the {{< param "PRODUCT_NAME" >}} executable.
 By default, `text_file_directory` is set to the `textfile_inputs` directory in the installation directory of {{< param "PRODUCT_NAME" >}}.
 For example, if {{< param "PRODUCT_NAME" >}} is installed in `C:\Program Files\GrafanaLabs\Alloy\`,
 the default will be `C:\Program Files\GrafanaLabs\Alloy\textfile_inputs`.
 
-When `text_file_directory` is set, only files with the extension `.prom` inside the specified directory are read. 
+When `text_file_directory` is set, only files with the extension `.prom` inside the specified directory are read.
 
 {{< admonition type="note" >}}
 The `.prom` files must end with an empty line feed for the component to recognize and read them.
@@ -272,6 +270,7 @@ debug information.
 debug metrics.
 
 [wrap-regex]: #wrapping-of-regex-strings
+
 ## Wrapping of regular expression strings
 
 Some collector blocks such as [scheduled_task][] accept a regular expression as a string argument.
@@ -287,6 +286,7 @@ However, `^(?:e.*)$` would only match "email".
 {{< /admonition >}}
 
 ## Collectors list
+
 The following table lists the available collectors that `windows_exporter` brings
 bundled in. Some collectors only work on specific operating systems; enabling a
 collector that is not supported by the host OS where {{< param "PRODUCT_NAME" >}} is running
@@ -296,68 +296,67 @@ Users can choose to enable a subset of collectors to limit the amount of
 metrics exposed by the `prometheus.exporter.windows` component,
 or disable collectors that are expensive to run.
 
-
-Name     | Description | Enabled by default
----------|-------------|--------------------
-[ad](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.ad.md) | Active Directory Domain Services |
-[adcs](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.adcs.md) | Active Directory Certificate Services |
-[adfs](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.adfs.md) | Active Directory Federation Services |
-[cache](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.cache.md) | Cache metrics |
-[cpu](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.cpu.md) | CPU usage | &#10003;
-[cpu_info](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.cpu_info.md) | CPU Information |
-[cs](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.cs.md) | "Computer System" metrics (system properties, num cpus/total memory) | &#10003;
-[container](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.container.md) | Container metrics |
-[dfsr](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.dfsr.md) | DFSR metrics |
-[dhcp](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.dhcp.md) | DHCP Server |
-[dns](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.dns.md) | DNS Server |
-[exchange](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.exchange.md) | Exchange metrics |
-[fsrmquota](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.fsrmquota.md) | Microsoft File Server Resource Manager (FSRM) Quotas collector |
-[hyperv](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.hyperv.md) | Hyper-V hosts |
-[iis](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.iis.md) | IIS sites and applications |
-[logical_disk](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.logical_disk.md) | Logical disks, disk I/O | &#10003;
-[logon](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.logon.md) | User logon sessions |
-[memory](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.memory.md) | Memory usage metrics |
-[mscluster_cluster](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.mscluster_cluster.md) | MSCluster cluster metrics |
-[mscluster_network](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.mscluster_network.md) | MSCluster network metrics |
-[mscluster_node](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.mscluster_node.md) | MSCluster Node metrics |
-[mscluster_resource](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.mscluster_resource.md) | MSCluster Resource metrics |
-[mscluster_resourcegroup](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.mscluster_resourcegroup.md) | MSCluster ResourceGroup metrics |
-[msmq](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.msmq.md) | MSMQ queues |
-[mssql](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.mssql.md) | [SQL Server Performance Objects](https://docs.microsoft.com/en-us/sql/relational-databases/performance-monitor/use-sql-server-objects#SQLServerPOs) metrics  |
-[netframework_clrexceptions](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrexceptions.md) | .NET Framework CLR Exceptions |
-[netframework_clrinterop](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrinterop.md) | .NET Framework Interop Metrics |
-[netframework_clrjit](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrjit.md) | .NET Framework JIT metrics |
-[netframework_clrloading](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrloading.md) | .NET Framework CLR Loading metrics |
-[netframework_clrlocksandthreads](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrlocksandthreads.md) | .NET Framework locks and metrics threads |
-[netframework_clrmemory](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrmemory.md) |  .NET Framework Memory metrics |
-[netframework_clrremoting](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrremoting.md) | .NET Framework Remoting metrics |
-[netframework_clrsecurity](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrsecurity.md) | .NET Framework Security Check metrics |
-[net](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.net.md) | Network interface I/O | &#10003;
-[os](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.os.md) | OS metrics (memory, processes, users) | &#10003;
-[physical_disk](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.physical_disk.md) | Physical disks | &#10003;
-[printer](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.printer.md) | Printer metrics |
-[process](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.process.md) | Per-process metrics |
-[remote_fx](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.remote_fx.md) | RemoteFX protocol (RDP) metrics |
-[scheduled_task](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.scheduled_task.md) | Scheduled Tasks metrics |
-[service](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.service.md) | Service state metrics | &#10003;
-[smb](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.smb.md) | IIS SMTP Server |
-[smb_client](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.smbclient.md) | IIS SMTP Server |
-[smtp](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.smtp.md) | IIS SMTP Server |
-[system](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.system.md) | System calls | &#10003;
-[tcp](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.tcp.md) | TCP connections |
-[teradici_pcoip](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.teradici_pcoip.md) | [Teradici PCoIP](https://www.teradici.com/web-help/pcoip_wmi_specs/) session metrics |
-[time](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.time.md) | Windows Time Service |
-[thermalzone](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.thermalzone.md) | Thermal information
-[terminal_services](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.terminal_services.md) | Terminal services (RDS)
-[textfile](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.textfile.md) | Read prometheus metrics from a text file |
-[vmware_blast](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.vmware_blast.md) | VMware Blast session metrics |
-[vmware](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.vmware.md) | Performance counters installed by the Vmware Guest agent |
+| Name                                                                                                                                                                                    | Description                                                                                                                                                 | Enabled by default |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ |
+| [ad](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.ad.md)                                                           | Active Directory Domain Services                                                                                                                            |
+| [adcs](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.adcs.md)                                                       | Active Directory Certificate Services                                                                                                                       |
+| [adfs](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.adfs.md)                                                       | Active Directory Federation Services                                                                                                                        |
+| [cache](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.cache.md)                                                     | Cache metrics                                                                                                                                               |
+| [cpu](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.cpu.md)                                                         | CPU usage                                                                                                                                                   | &#10003;           |
+| [cpu_info](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.cpu_info.md)                                               | CPU Information                                                                                                                                             |
+| [cs](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.cs.md)                                                           | "Computer System" metrics (system properties, num cpus/total memory)                                                                                        | &#10003;           |
+| [container](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.container.md)                                             | Container metrics                                                                                                                                           |
+| [dfsr](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.dfsr.md)                                                       | DFSR metrics                                                                                                                                                |
+| [dhcp](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.dhcp.md)                                                       | DHCP Server                                                                                                                                                 |
+| [dns](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.dns.md)                                                         | DNS Server                                                                                                                                                  |
+| [exchange](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.exchange.md)                                               | Exchange metrics                                                                                                                                            |
+| [fsrmquota](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.fsrmquota.md)                                             | Microsoft File Server Resource Manager (FSRM) Quotas collector                                                                                              |
+| [hyperv](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.hyperv.md)                                                   | Hyper-V hosts                                                                                                                                               |
+| [iis](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.iis.md)                                                         | IIS sites and applications                                                                                                                                  |
+| [logical_disk](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.logical_disk.md)                                       | Logical disks, disk I/O                                                                                                                                     | &#10003;           |
+| [logon](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.logon.md)                                                     | User logon sessions                                                                                                                                         |
+| [memory](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.memory.md)                                                   | Memory usage metrics                                                                                                                                        |
+| [mscluster_cluster](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.mscluster_cluster.md)                             | MSCluster cluster metrics                                                                                                                                   |
+| [mscluster_network](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.mscluster_network.md)                             | MSCluster network metrics                                                                                                                                   |
+| [mscluster_node](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.mscluster_node.md)                                   | MSCluster Node metrics                                                                                                                                      |
+| [mscluster_resource](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.mscluster_resource.md)                           | MSCluster Resource metrics                                                                                                                                  |
+| [mscluster_resourcegroup](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.mscluster_resourcegroup.md)                 | MSCluster ResourceGroup metrics                                                                                                                             |
+| [msmq](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.msmq.md)                                                       | MSMQ queues                                                                                                                                                 |
+| [mssql](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.mssql.md)                                                     | [SQL Server Performance Objects](https://docs.microsoft.com/en-us/sql/relational-databases/performance-monitor/use-sql-server-objects#SQLServerPOs) metrics |
+| [netframework_clrexceptions](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrexceptions.md)           | .NET Framework CLR Exceptions                                                                                                                               |
+| [netframework_clrinterop](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrinterop.md)                 | .NET Framework Interop Metrics                                                                                                                              |
+| [netframework_clrjit](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrjit.md)                         | .NET Framework JIT metrics                                                                                                                                  |
+| [netframework_clrloading](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrloading.md)                 | .NET Framework CLR Loading metrics                                                                                                                          |
+| [netframework_clrlocksandthreads](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrlocksandthreads.md) | .NET Framework locks and metrics threads                                                                                                                    |
+| [netframework_clrmemory](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrmemory.md)                   | .NET Framework Memory metrics                                                                                                                               |
+| [netframework_clrremoting](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrremoting.md)               | .NET Framework Remoting metrics                                                                                                                             |
+| [netframework_clrsecurity](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.netframework_clrsecurity.md)               | .NET Framework Security Check metrics                                                                                                                       |
+| [net](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.net.md)                                                         | Network interface I/O                                                                                                                                       | &#10003;           |
+| [os](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.os.md)                                                           | OS metrics (memory, processes, users)                                                                                                                       | &#10003;           |
+| [physical_disk](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.physical_disk.md)                                     | Physical disks                                                                                                                                              | &#10003;           |
+| [printer](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.printer.md)                                                 | Printer metrics                                                                                                                                             |
+| [process](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.process.md)                                                 | Per-process metrics                                                                                                                                         |
+| [remote_fx](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.remote_fx.md)                                             | RemoteFX protocol (RDP) metrics                                                                                                                             |
+| [scheduled_task](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.scheduled_task.md)                                   | Scheduled Tasks metrics                                                                                                                                     |
+| [service](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.service.md)                                                 | Service state metrics                                                                                                                                       | &#10003;           |
+| [smb](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.smb.md)                                                         | IIS SMTP Server                                                                                                                                             |
+| [smb_client](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.smbclient.md)                                            | IIS SMTP Server                                                                                                                                             |
+| [smtp](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.smtp.md)                                                       | IIS SMTP Server                                                                                                                                             |
+| [system](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.system.md)                                                   | System calls                                                                                                                                                | &#10003;           |
+| [tcp](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.tcp.md)                                                         | TCP connections                                                                                                                                             |
+| [teradici_pcoip](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.teradici_pcoip.md)                                   | [Teradici PCoIP](https://www.teradici.com/web-help/pcoip_wmi_specs/) session metrics                                                                        |
+| [time](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.time.md)                                                       | Windows Time Service                                                                                                                                        |
+| [thermalzone](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.thermalzone.md)                                         | Thermal information                                                                                                                                         |
+| [terminal_services](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.terminal_services.md)                             | Terminal services (RDS)                                                                                                                                     |
+| [textfile](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.textfile.md)                                               | Read prometheus metrics from a text file                                                                                                                    |
+| [vmware_blast](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.vmware_blast.md)                                       | VMware Blast session metrics                                                                                                                                |
+| [vmware](https://github.com/prometheus-community/windows_exporter/blob/{{< param "PROM_WIN_EXP_VERSION" >}}/docs/collector.vmware.md)                                                   | Performance counters installed by the Vmware Guest agent                                                                                                    |
 
 Refer to the linked documentation on each collector for more information on reported metrics, configuration settings and usage examples.
 
 {{< admonition type="caution" >}}
 Certain collectors will cause {{< param "PRODUCT_NAME" >}} to crash if those collectors are used and the required infrastructure isn't installed.
-These include but aren't limited to mscluster_*, vmware, nps, dns, msmq, teradici_pcoip, ad, hyperv, and scheduled_task.
+These include but aren't limited to mscluster\_\*, vmware, nps, dns, msmq, teradici_pcoip, ad, hyperv, and scheduled_task.
 {{< /admonition >}}
 
 ## Example
@@ -385,10 +384,12 @@ prometheus.remote_write "demo" {
   }
 }
 ```
+
 Replace the following:
-  - `PROMETHEUS_REMOTE_WRITE_URL`: The URL of the Prometheus remote_write-compatible server to send metrics to.
-  - `USERNAME`: The username to use for authentication to the remote_write API.
-  - `PASSWORD`: The password to use for authentication to the remote_write API.
+
+- `PROMETHEUS_REMOTE_WRITE_URL`: The URL of the Prometheus remote_write-compatible server to send metrics to.
+- `USERNAME`: The username to use for authentication to the remote_write API.
+- `PASSWORD`: The password to use for authentication to the remote_write API.
 
 [scrape]: ../prometheus.scrape/
 
diff --git a/docs/sources/reference/components/prometheus/prometheus.operator.podmonitors.md b/docs/sources/reference/components/prometheus/prometheus.operator.podmonitors.md
index 2ef2ca30b3..29bface82d 100644
--- a/docs/sources/reference/components/prometheus/prometheus.operator.podmonitors.md
+++ b/docs/sources/reference/components/prometheus/prometheus.operator.podmonitors.md
@@ -30,29 +30,29 @@ prometheus.operator.podmonitors "LABEL" {
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`forward_to` | `list(MetricsReceiver)` | List of receivers to send scraped metrics to. | | yes
-`namespaces` | `list(string)` | List of namespaces to search for PodMonitor resources. If not specified, all namespaces will be searched. || no
-`informer_sync_timeout` | `duration` | Timeout for initial sync of PodMonitor resources. | `1m` | no
+| Name                    | Type                    | Description                                                                                               | Default | Required |
+| ----------------------- | ----------------------- | --------------------------------------------------------------------------------------------------------- | ------- | -------- |
+| `forward_to`            | `list(MetricsReceiver)` | List of receivers to send scraped metrics to.                                                             |         | yes      |
+| `namespaces`            | `list(string)`          | List of namespaces to search for PodMonitor resources. If not specified, all namespaces will be searched. |         | no       |
+| `informer_sync_timeout` | `duration`              | Timeout for initial sync of PodMonitor resources.                                                         | `1m`    | no       |
 
 ## Blocks
 
 The following blocks are supported inside the definition of `prometheus.operator.podmonitors`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-client | [client][] | Configures Kubernetes client used to find PodMonitors. | no
-client > basic_auth | [basic_auth][] | Configure basic authentication to the Kubernetes API. | no
-client > authorization | [authorization][] | Configure generic authorization to the Kubernetes API. | no
-client > oauth2 | [oauth2][] | Configure OAuth2 for authenticating to the Kubernetes API. | no
-client > oauth2 > tls_config | [tls_config][] | Configure TLS settings for connecting to the Kubernetes API. | no
-client > tls_config | [tls_config][] | Configure TLS settings for connecting to the Kubernetes API. | no
-rule | [rule][] | Relabeling rules to apply to discovered targets. | no
-scrape | [scrape][] | Default scrape configuration to apply to discovered targets. | no
-selector | [selector][] | Label selector for which PodMonitors to discover. | no
-selector > match_expression | [match_expression][] | Label selector expression for which PodMonitors to discover. | no
-clustering | [clustering][] | Configure the component for when {{< param "PRODUCT_NAME" >}} is running in clustered mode. | no
+| Hierarchy                    | Block                | Description                                                                                 | Required |
+| ---------------------------- | -------------------- | ------------------------------------------------------------------------------------------- | -------- |
+| client                       | [client][]           | Configures Kubernetes client used to find PodMonitors.                                      | no       |
+| client > basic_auth          | [basic_auth][]       | Configure basic authentication to the Kubernetes API.                                       | no       |
+| client > authorization       | [authorization][]    | Configure generic authorization to the Kubernetes API.                                      | no       |
+| client > oauth2              | [oauth2][]           | Configure OAuth2 for authenticating to the Kubernetes API.                                  | no       |
+| client > oauth2 > tls_config | [tls_config][]       | Configure TLS settings for connecting to the Kubernetes API.                                | no       |
+| client > tls_config          | [tls_config][]       | Configure TLS settings for connecting to the Kubernetes API.                                | no       |
+| rule                         | [rule][]             | Relabeling rules to apply to discovered targets.                                            | no       |
+| scrape                       | [scrape][]           | Default scrape configuration to apply to discovered targets.                                | no       |
+| selector                     | [selector][]         | Label selector for which PodMonitors to discover.                                           | no       |
+| selector > match_expression  | [match_expression][] | Label selector expression for which PodMonitors to discover.                                | no       |
+| clustering                   | [clustering][]       | Configure the component for when {{< param "PRODUCT_NAME" >}} is running in clustered mode. | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `client >
 basic_auth` refers to a `basic_auth` block defined
@@ -77,25 +77,26 @@ used.
 
 The following arguments are supported:
 
-Name                     | Type                | Description                                                   | Default | Required
--------------------------|---------------------|---------------------------------------------------------------|---------|---------
-`api_server`             | `string`            | URL of the Kubernetes API server.                             |         | no
-`kubeconfig_file`        | `string`            | Path of the `kubeconfig` file to use for connecting to Kubernetes. |    | no
-`bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.          |         | no
-`bearer_token`           | `secret`            | Bearer token to authenticate with.                            |         | no
-`enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                      | `true`  | no
-`follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.  | `true`  | no
-`proxy_url`              | `string`            | HTTP proxy to send requests through.                          |         | no
-`no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. | | no
-`proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.         | `false` | no
-`proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests. |         | no
-
- At most, one of the following can be provided:
- - [`bearer_token` argument][client].
- - [`bearer_token_file` argument][client].
- - [`basic_auth` block][basic_auth].
- - [`authorization` block][authorization].
- - [`oauth2` block][oauth2].
+| Name                     | Type                | Description                                                                                      | Default | Required |
+| ------------------------ | ------------------- | ------------------------------------------------------------------------------------------------ | ------- | -------- |
+| `api_server`             | `string`            | URL of the Kubernetes API server.                                                                |         | no       |
+| `kubeconfig_file`        | `string`            | Path of the `kubeconfig` file to use for connecting to Kubernetes.                               |         | no       |
+| `bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.                                             |         | no       |
+| `bearer_token`           | `secret`            | Bearer token to authenticate with.                                                               |         | no       |
+| `enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                                                         | `true`  | no       |
+| `follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.                                     | `true`  | no       |
+| `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
+| `no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. |         | no       |
+| `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
+| `proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests.                                    |         | no       |
+
+At most, one of the following can be provided:
+
+- [`bearer_token` argument][client].
+- [`bearer_token_file` argument][client].
+- [`basic_auth` block][basic_auth].
+- [`authorization` block][authorization].
+- [`oauth2` block][oauth2].
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -129,9 +130,9 @@ The `selector` block describes a Kubernetes label selector for PodMonitors.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`match_labels` | `map(string)` | Label keys and values used to discover resources. | `{}` | no
+| Name           | Type          | Description                                       | Default | Required |
+| -------------- | ------------- | ------------------------------------------------- | ------- | -------- |
+| `match_labels` | `map(string)` | Label keys and values used to discover resources. | `{}`    | no       |
 
 When the `match_labels` argument is empty, all PodMonitor resources will be matched.
 
@@ -142,26 +143,26 @@ PodMonitors discovery.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`key` | `string` | The label name to match against. | | yes
-`operator` | `string` | The operator to use when matching. | | yes
-`values`| `list(string)` | The values used when matching. | | no
+| Name       | Type           | Description                        | Default | Required |
+| ---------- | -------------- | ---------------------------------- | ------- | -------- |
+| `key`      | `string`       | The label name to match against.   |         | yes      |
+| `operator` | `string`       | The operator to use when matching. |         | yes      |
+| `values`   | `list(string)` | The values used when matching.     |         | no       |
 
 The `operator` argument must be one of the following strings:
 
-* `"In"`
-* `"NotIn"`
-* `"Exists"`
-* `"DoesNotExist"`
+- `"In"`
+- `"NotIn"`
+- `"Exists"`
+- `"DoesNotExist"`
 
 If there are multiple `match_expressions` blocks inside of a `selector` block, they are combined together with AND clauses.
 
 ### clustering block
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `bool` | Enables sharing targets with other cluster nodes. | `false` | yes
+| Name      | Type   | Description                                       | Default | Required |
+| --------- | ------ | ------------------------------------------------- | ------- | -------- |
+| `enabled` | `bool` | Enables sharing targets with other cluster nodes. | `false` | yes      |
 
 When {{< param "PRODUCT_NAME" >}} is [using clustering][], and `enabled` is set to true,
 then this component instance opts-in to participating in
@@ -256,6 +257,7 @@ prometheus.operator.podmonitors "pods" {
     }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -264,7 +266,6 @@ prometheus.operator.podmonitors "pods" {
 
 - Components that export [Prometheus `MetricsReceiver`](../../../compatibility/#prometheus-metricsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/prometheus/prometheus.operator.probes.md b/docs/sources/reference/components/prometheus/prometheus.operator.probes.md
index d1d6421173..83332bec82 100644
--- a/docs/sources/reference/components/prometheus/prometheus.operator.probes.md
+++ b/docs/sources/reference/components/prometheus/prometheus.operator.probes.md
@@ -9,7 +9,7 @@ title: prometheus.operator.probes
 # prometheus.operator.probes
 
 `prometheus.operator.probes` discovers [Probe](https://prometheus-operator.dev/docs/api-reference/api/#monitoring.coreos.com/v1.Probe) resources in your Kubernetes cluster and scrapes the targets they reference.
- This component performs three main functions:
+This component performs three main functions:
 
 1. Discover Probe resources from your Kubernetes cluster.
 1. Discover targets or ingresses that match those Probes.
@@ -33,29 +33,29 @@ prometheus.operator.probes "LABEL" {
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`forward_to` | `list(MetricsReceiver)` | List of receivers to send scraped metrics to. | | yes
-`namespaces` | `list(string)` | List of namespaces to search for Probe resources. If not specified, all namespaces will be searched. || no
-`informer_sync_timeout` | `duration` | Timeout for initial sync of Probe resources. | `1m` | no
+| Name                    | Type                    | Description                                                                                          | Default | Required |
+| ----------------------- | ----------------------- | ---------------------------------------------------------------------------------------------------- | ------- | -------- |
+| `forward_to`            | `list(MetricsReceiver)` | List of receivers to send scraped metrics to.                                                        |         | yes      |
+| `namespaces`            | `list(string)`          | List of namespaces to search for Probe resources. If not specified, all namespaces will be searched. |         | no       |
+| `informer_sync_timeout` | `duration`              | Timeout for initial sync of Probe resources.                                                         | `1m`    | no       |
 
 ## Blocks
 
 The following blocks are supported inside the definition of `prometheus.operator.probes`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-client | [client][] | Configures Kubernetes client used to find Probes. | no
-client > basic_auth | [basic_auth][] | Configure basic authentication to the Kubernetes API. | no
-client > authorization | [authorization][] | Configure generic authorization to the Kubernetes API. | no
-client > oauth2 | [oauth2][] | Configure OAuth2 for authenticating to the Kubernetes API. | no
-client > oauth2 > tls_config | [tls_config][] | Configure TLS settings for connecting to the Kubernetes API. | no
-client > tls_config | [tls_config][] | Configure TLS settings for connecting to the Kubernetes API. | no
-rule | [rule][] | Relabeling rules to apply to discovered targets. | no
-scrape | [scrape][] | Default scrape configuration to apply to discovered targets. | no
-selector | [selector][] | Label selector for which Probes to discover. | no
-selector > match_expression | [match_expression][] | Label selector expression for which Probes to discover. | no
-clustering | [clustering][] | Configure the component for when {{< param "PRODUCT_NAME" >}} is running in clustered mode. | no
+| Hierarchy                    | Block                | Description                                                                                 | Required |
+| ---------------------------- | -------------------- | ------------------------------------------------------------------------------------------- | -------- |
+| client                       | [client][]           | Configures Kubernetes client used to find Probes.                                           | no       |
+| client > basic_auth          | [basic_auth][]       | Configure basic authentication to the Kubernetes API.                                       | no       |
+| client > authorization       | [authorization][]    | Configure generic authorization to the Kubernetes API.                                      | no       |
+| client > oauth2              | [oauth2][]           | Configure OAuth2 for authenticating to the Kubernetes API.                                  | no       |
+| client > oauth2 > tls_config | [tls_config][]       | Configure TLS settings for connecting to the Kubernetes API.                                | no       |
+| client > tls_config          | [tls_config][]       | Configure TLS settings for connecting to the Kubernetes API.                                | no       |
+| rule                         | [rule][]             | Relabeling rules to apply to discovered targets.                                            | no       |
+| scrape                       | [scrape][]           | Default scrape configuration to apply to discovered targets.                                | no       |
+| selector                     | [selector][]         | Label selector for which Probes to discover.                                                | no       |
+| selector > match_expression  | [match_expression][] | Label selector expression for which Probes to discover.                                     | no       |
+| clustering                   | [clustering][]       | Configure the component for when {{< param "PRODUCT_NAME" >}} is running in clustered mode. | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `client >
 basic_auth` refers to a `basic_auth` block defined
@@ -79,25 +79,26 @@ configuration with the service account of the running {{< param "PRODUCT_NAME" >
 
 The following arguments are supported:
 
-Name                     | Type                | Description                                                   | Default | Required
--------------------------|---------------------|---------------------------------------------------------------|---------|---------
-`api_server`             | `string`            | URL of the Kubernetes API server.                             |         | no
-`kubeconfig_file`        | `string`            | Path of the `kubeconfig` file to use for connecting to Kubernetes. |    | no
-`bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.          |         | no
-`bearer_token`           | `secret`            | Bearer token to authenticate with.                            |         | no
-`enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                      | `true`  | no
-`follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.  | `true`  | no
-`proxy_url`              | `string`            | HTTP proxy to send requests through.                          |         | no
-`no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. | | no
-`proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.         | `false` | no
-`proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests. |         | no
-
- At most, one of the following can be provided:
- - [`bearer_token` argument][client].
- - [`bearer_token_file` argument][client].
- - [`basic_auth` block][basic_auth].
- - [`authorization` block][authorization].
- - [`oauth2` block][oauth2].
+| Name                     | Type                | Description                                                                                      | Default | Required |
+| ------------------------ | ------------------- | ------------------------------------------------------------------------------------------------ | ------- | -------- |
+| `api_server`             | `string`            | URL of the Kubernetes API server.                                                                |         | no       |
+| `kubeconfig_file`        | `string`            | Path of the `kubeconfig` file to use for connecting to Kubernetes.                               |         | no       |
+| `bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.                                             |         | no       |
+| `bearer_token`           | `secret`            | Bearer token to authenticate with.                                                               |         | no       |
+| `enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                                                         | `true`  | no       |
+| `follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.                                     | `true`  | no       |
+| `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
+| `no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. |         | no       |
+| `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
+| `proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests.                                    |         | no       |
+
+At most, one of the following can be provided:
+
+- [`bearer_token` argument][client].
+- [`bearer_token_file` argument][client].
+- [`basic_auth` block][basic_auth].
+- [`authorization` block][authorization].
+- [`oauth2` block][oauth2].
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -131,9 +132,9 @@ The `selector` block describes a Kubernetes label selector for Probes.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`match_labels` | `map(string)` | Label keys and values used to discover resources. | `{}` | no
+| Name           | Type          | Description                                       | Default | Required |
+| -------------- | ------------- | ------------------------------------------------- | ------- | -------- |
+| `match_labels` | `map(string)` | Label keys and values used to discover resources. | `{}`    | no       |
 
 When the `match_labels` argument is empty, all Probe resources will be matched.
 
@@ -144,26 +145,26 @@ Probes discovery.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`key` | `string` | The label name to match against. | | yes
-`operator` | `string` | The operator to use when matching. | | yes
-`values`| `list(string)` | The values used when matching. | | no
+| Name       | Type           | Description                        | Default | Required |
+| ---------- | -------------- | ---------------------------------- | ------- | -------- |
+| `key`      | `string`       | The label name to match against.   |         | yes      |
+| `operator` | `string`       | The operator to use when matching. |         | yes      |
+| `values`   | `list(string)` | The values used when matching.     |         | no       |
 
 The `operator` argument must be one of the following strings:
 
-* `"In"`
-* `"NotIn"`
-* `"Exists"`
-* `"DoesNotExist"`
+- `"In"`
+- `"NotIn"`
+- `"Exists"`
+- `"DoesNotExist"`
 
 If there are multiple `match_expressions` blocks inside of a `selector` block, they are combined together with AND clauses.
 
 ### clustering block
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `bool` | Enables sharing targets with other cluster nodes. | `false` | yes
+| Name      | Type   | Description                                       | Default | Required |
+| --------- | ------ | ------------------------------------------------- | ------- | -------- |
+| `enabled` | `bool` | Enables sharing targets with other cluster nodes. | `false` | yes      |
 
 When {{< param "PRODUCT_NAME" >}} is running in [clustered mode][], and `enabled` is set to true,
 then this component instance opts-in to participating in
@@ -258,6 +259,7 @@ prometheus.operator.probes "probes" {
     }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -266,7 +268,6 @@ prometheus.operator.probes "probes" {
 
 - Components that export [Prometheus `MetricsReceiver`](../../../compatibility/#prometheus-metricsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/prometheus/prometheus.operator.servicemonitors.md b/docs/sources/reference/components/prometheus/prometheus.operator.servicemonitors.md
index 2e9c712c85..3cc9e75632 100644
--- a/docs/sources/reference/components/prometheus/prometheus.operator.servicemonitors.md
+++ b/docs/sources/reference/components/prometheus/prometheus.operator.servicemonitors.md
@@ -32,29 +32,29 @@ prometheus.operator.servicemonitors "LABEL" {
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`forward_to` | `list(MetricsReceiver)` | List of receivers to send scraped metrics to. | | yes
-`namespaces` | `list(string)` | List of namespaces to search for ServiceMonitor resources. If not specified, all namespaces will be searched. || no
-`informer_sync_timeout` | `duration` | Timeout for initial sync of ServiceMonitor resources. | `1m` | no
+| Name                    | Type                    | Description                                                                                                   | Default | Required |
+| ----------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------- | ------- | -------- |
+| `forward_to`            | `list(MetricsReceiver)` | List of receivers to send scraped metrics to.                                                                 |         | yes      |
+| `namespaces`            | `list(string)`          | List of namespaces to search for ServiceMonitor resources. If not specified, all namespaces will be searched. |         | no       |
+| `informer_sync_timeout` | `duration`              | Timeout for initial sync of ServiceMonitor resources.                                                         | `1m`    | no       |
 
 ## Blocks
 
 The following blocks are supported inside the definition of `prometheus.operator.servicemonitors`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-client | [client][] | Configures Kubernetes client used to find ServiceMonitors. | no
-client > basic_auth | [basic_auth][] | Configure basic authentication to the Kubernetes API. | no
-client > authorization | [authorization][] | Configure generic authorization to the Kubernetes API. | no
-client > oauth2 | [oauth2][] | Configure OAuth2 for authenticating to the Kubernetes API. | no
-client > oauth2 > tls_config | [tls_config][] | Configure TLS settings for connecting to the Kubernetes API. | no
-client > tls_config | [tls_config][] | Configure TLS settings for connecting to the Kubernetes API. | no
-rule | [rule][] | Relabeling rules to apply to discovered targets. | no
-scrape | [scrape][] | Default scrape configuration to apply to discovered targets. | no
-selector | [selector][] | Label selector for which ServiceMonitors to discover. | no
-selector > match_expression | [match_expression][] | Label selector expression for which ServiceMonitors to discover. | no
-clustering | [clustering][] | Configure the component for when {{< param "PRODUCT_NAME" >}} is running in clustered mode. | no
+| Hierarchy                    | Block                | Description                                                                                 | Required |
+| ---------------------------- | -------------------- | ------------------------------------------------------------------------------------------- | -------- |
+| client                       | [client][]           | Configures Kubernetes client used to find ServiceMonitors.                                  | no       |
+| client > basic_auth          | [basic_auth][]       | Configure basic authentication to the Kubernetes API.                                       | no       |
+| client > authorization       | [authorization][]    | Configure generic authorization to the Kubernetes API.                                      | no       |
+| client > oauth2              | [oauth2][]           | Configure OAuth2 for authenticating to the Kubernetes API.                                  | no       |
+| client > oauth2 > tls_config | [tls_config][]       | Configure TLS settings for connecting to the Kubernetes API.                                | no       |
+| client > tls_config          | [tls_config][]       | Configure TLS settings for connecting to the Kubernetes API.                                | no       |
+| rule                         | [rule][]             | Relabeling rules to apply to discovered targets.                                            | no       |
+| scrape                       | [scrape][]           | Default scrape configuration to apply to discovered targets.                                | no       |
+| selector                     | [selector][]         | Label selector for which ServiceMonitors to discover.                                       | no       |
+| selector > match_expression  | [match_expression][] | Label selector expression for which ServiceMonitors to discover.                            | no       |
+| clustering                   | [clustering][]       | Configure the component for when {{< param "PRODUCT_NAME" >}} is running in clustered mode. | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `client >
 basic_auth` refers to a `basic_auth` block defined
@@ -78,25 +78,26 @@ If the `client` block isn't provided, the default in-cluster configuration with
 
 The following arguments are supported:
 
-Name                     | Type                | Description                                                   | Default | Required
--------------------------|---------------------|---------------------------------------------------------------|---------|---------
-`api_server`             | `string`            | URL of the Kubernetes API server.                             |         | no
-`kubeconfig_file`        | `string`            | Path of the `kubeconfig` file to use for connecting to Kubernetes. |    | no
-`bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.          |         | no
-`bearer_token`           | `secret`            | Bearer token to authenticate with.                            |         | no
-`enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                      | `true`  | no
-`follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.  | `true`  | no
-`proxy_url`              | `string`            | HTTP proxy to send requests through.                          |         | no
-`no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. | | no
-`proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.         | `false` | no
-`proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests. |         | no
-
- At most, one of the following can be provided:
- - [`bearer_token` argument][client].
- - [`bearer_token_file` argument][client].
- - [`basic_auth` block][basic_auth].
- - [`authorization` block][authorization].
- - [`oauth2` block][oauth2].
+| Name                     | Type                | Description                                                                                      | Default | Required |
+| ------------------------ | ------------------- | ------------------------------------------------------------------------------------------------ | ------- | -------- |
+| `api_server`             | `string`            | URL of the Kubernetes API server.                                                                |         | no       |
+| `kubeconfig_file`        | `string`            | Path of the `kubeconfig` file to use for connecting to Kubernetes.                               |         | no       |
+| `bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.                                             |         | no       |
+| `bearer_token`           | `secret`            | Bearer token to authenticate with.                                                               |         | no       |
+| `enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                                                         | `true`  | no       |
+| `follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.                                     | `true`  | no       |
+| `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
+| `no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. |         | no       |
+| `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
+| `proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests.                                    |         | no       |
+
+At most, one of the following can be provided:
+
+- [`bearer_token` argument][client].
+- [`bearer_token_file` argument][client].
+- [`basic_auth` block][basic_auth].
+- [`authorization` block][authorization].
+- [`oauth2` block][oauth2].
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -130,9 +131,9 @@ The `selector` block describes a Kubernetes label selector for ServiceMonitors.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`match_labels` | `map(string)` | Label keys and values used to discover resources. | `{}` | no
+| Name           | Type          | Description                                       | Default | Required |
+| -------------- | ------------- | ------------------------------------------------- | ------- | -------- |
+| `match_labels` | `map(string)` | Label keys and values used to discover resources. | `{}`    | no       |
 
 When the `match_labels` argument is empty, all ServiceMonitor resources will be matched.
 
@@ -143,26 +144,26 @@ ServiceMonitors discovery.
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`key` | `string` | The label name to match against. | | yes
-`operator` | `string` | The operator to use when matching. | | yes
-`values`| `list(string)` | The values used when matching. | | no
+| Name       | Type           | Description                        | Default | Required |
+| ---------- | -------------- | ---------------------------------- | ------- | -------- |
+| `key`      | `string`       | The label name to match against.   |         | yes      |
+| `operator` | `string`       | The operator to use when matching. |         | yes      |
+| `values`   | `list(string)` | The values used when matching.     |         | no       |
 
 The `operator` argument must be one of the following strings:
 
-* `"In"`
-* `"NotIn"`
-* `"Exists"`
-* `"DoesNotExist"`
+- `"In"`
+- `"NotIn"`
+- `"Exists"`
+- `"DoesNotExist"`
 
 If there are multiple `match_expressions` blocks inside of a `selector` block, they are combined together with AND clauses.
 
 ### clustering block
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `bool` | Enables sharing targets with other cluster nodes. | `false` | yes
+| Name      | Type   | Description                                       | Default | Required |
+| --------- | ------ | ------------------------------------------------- | ------- | -------- |
+| `enabled` | `bool` | Enables sharing targets with other cluster nodes. | `false` | yes      |
 
 When {{< param "PRODUCT_NAME" >}} is using [using clustering][], and `enabled` is set to true,
 then this component instance opts-in to participating in
@@ -258,6 +259,7 @@ prometheus.operator.servicemonitors "services" {
     }
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -266,7 +268,6 @@ prometheus.operator.servicemonitors "services" {
 
 - Components that export [Prometheus `MetricsReceiver`](../../../compatibility/#prometheus-metricsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/prometheus/prometheus.receive_http.md b/docs/sources/reference/components/prometheus/prometheus.receive_http.md
index 7b00a2a241..2f1d7b539b 100644
--- a/docs/sources/reference/components/prometheus/prometheus.receive_http.md
+++ b/docs/sources/reference/components/prometheus/prometheus.receive_http.md
@@ -35,17 +35,17 @@ The component will start an HTTP server supporting the following endpoint:
 
 `prometheus.receive_http` supports the following arguments:
 
-Name         | Type             | Description                           | Default | Required
--------------|------------------|---------------------------------------|---------|---------
-`forward_to` | `list(MetricsReceiver)` | List of receivers to send metrics to. |         | yes
+| Name         | Type                    | Description                           | Default | Required |
+| ------------ | ----------------------- | ------------------------------------- | ------- | -------- |
+| `forward_to` | `list(MetricsReceiver)` | List of receivers to send metrics to. |         | yes      |
 
 ## Blocks
 
 The following blocks are supported inside the definition of `prometheus.receive_http`:
 
-Hierarchy | Name     | Description                                        | Required
-----------|----------|----------------------------------------------------|---------
-`http`    | [http][] | Configures the HTTP server that receives requests. | no
+| Hierarchy | Name     | Description                                        | Required |
+| --------- | -------- | -------------------------------------------------- | -------- |
+| `http`    | [http][] | Configures the HTTP server that receives requests. | no       |
 
 [http]: #http
 
@@ -65,12 +65,12 @@ Hierarchy | Name     | Description                                        | Requ
 
 The following are some of the metrics that are exposed when this component is used. Note that the metrics include labels such as `status_code` where relevant, which can be used to measure request success rates.
 
-* `prometheus_receive_http_request_duration_seconds` (histogram): Time (in seconds) spent serving HTTP requests.
-* `prometheus_receive_http_request_message_bytes` (histogram): Size (in bytes) of messages received in the request.
-* `prometheus_receive_http_response_message_bytes` (histogram): Size (in bytes) of messages sent in response.
-* `prometheus_receive_http_tcp_connections` (gauge): Current number of accepted TCP connections.
-* `prometheus_fanout_latency` (histogram): Write latency for sending metrics to other components.
-* `prometheus_forwarded_samples_total` (counter): Total number of samples sent to downstream components.
+- `prometheus_receive_http_request_duration_seconds` (histogram): Time (in seconds) spent serving HTTP requests.
+- `prometheus_receive_http_request_message_bytes` (histogram): Size (in bytes) of messages received in the request.
+- `prometheus_receive_http_response_message_bytes` (histogram): Size (in bytes) of messages sent in response.
+- `prometheus_receive_http_tcp_connections` (gauge): Current number of accepted TCP connections.
+- `prometheus_fanout_latency` (histogram): Write latency for sending metrics to other components.
+- `prometheus_forwarded_samples_total` (counter): Total number of samples sent to downstream components.
 
 ## Example
 
@@ -125,7 +125,8 @@ prometheus.remote_write "local" {
 
 ## Technical details
 
-`prometheus.receive_http` uses [snappy](https://en.wikipedia.org/wiki/Snappy_(compression)) for compression.
+`prometheus.receive_http` uses [snappy](<https://en.wikipedia.org/wiki/Snappy_(compression)>) for compression.
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
@@ -134,7 +135,6 @@ prometheus.remote_write "local" {
 
 - Components that export [Prometheus `MetricsReceiver`](../../../compatibility/#prometheus-metricsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/prometheus/prometheus.relabel.md b/docs/sources/reference/components/prometheus/prometheus.relabel.md
index 6ecdea18da..9d0494181c 100644
--- a/docs/sources/reference/components/prometheus/prometheus.relabel.md
+++ b/docs/sources/reference/components/prometheus/prometheus.relabel.md
@@ -12,6 +12,7 @@ Prometheus metrics follow the [OpenMetrics](https://openmetrics.io/) format.
 Each time series is uniquely identified by its metric name, plus optional
 key-value pairs called labels. Each sample represents a datapoint in the
 time series and contains a value and an optional timestamp.
+
 ```
 <metric name>{<label_1>=<label_val_1>, <label_2>=<label_val_2> ...} <value> [timestamp]
 ```
@@ -50,18 +51,18 @@ prometheus.relabel "LABEL" {
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`forward_to` | `list(MetricsReceiver)` | Where the metrics should be forwarded to, after relabeling takes place. | | yes
-`max_cache_size` | `int` | The maximum number of elements to hold in the relabeling cache. | 100,000 | no
+| Name             | Type                    | Description                                                             | Default | Required |
+| ---------------- | ----------------------- | ----------------------------------------------------------------------- | ------- | -------- |
+| `forward_to`     | `list(MetricsReceiver)` | Where the metrics should be forwarded to, after relabeling takes place. |         | yes      |
+| `max_cache_size` | `int`                   | The maximum number of elements to hold in the relabeling cache.         | 100,000 | no       |
 
 ## Blocks
 
 The following blocks are supported inside the definition of `prometheus.relabel`:
 
-Hierarchy | Name | Description | Required
---------- | ---- | ----------- | --------
-rule | [rule][] | Relabeling rules to apply to received metrics. | no
+| Hierarchy | Name     | Description                                    | Required |
+| --------- | -------- | ---------------------------------------------- | -------- |
+| rule      | [rule][] | Relabeling rules to apply to received metrics. | no       |
 
 [rule]: #rule-block
 
@@ -73,10 +74,10 @@ rule | [rule][] | Relabeling rules to apply to received metrics. | no
 
 The following fields are exported and can be referenced by other components:
 
-Name | Type | Description
----- | ---- | -----------
-`receiver` | `MetricsReceiver` | The input receiver where samples are sent to be relabeled.
-`rules`    | `RelabelRules` | The currently configured relabeling rules.
+| Name       | Type              | Description                                                |
+| ---------- | ----------------- | ---------------------------------------------------------- |
+| `receiver` | `MetricsReceiver` | The input receiver where samples are sent to be relabeled. |
+| `rules`    | `RelabelRules`    | The currently configured relabeling rules.                 |
 
 ## Component health
 
@@ -90,13 +91,13 @@ values.
 
 ## Debug metrics
 
-* `prometheus_relabel_metrics_processed` (counter): Total number of metrics processed.
-* `prometheus_relabel_metrics_written` (counter): Total number of metrics written.
-* `prometheus_relabel_cache_misses` (counter): Total number of cache misses.
-* `prometheus_relabel_cache_hits` (counter): Total number of cache hits.
-* `prometheus_relabel_cache_size` (gauge): Total size of relabel cache.
-* `prometheus_fanout_latency` (histogram): Write latency for sending to direct and indirect components.
-* `prometheus_forwarded_samples_total` (counter): Total number of samples sent to downstream components.
+- `prometheus_relabel_metrics_processed` (counter): Total number of metrics processed.
+- `prometheus_relabel_metrics_written` (counter): Total number of metrics written.
+- `prometheus_relabel_cache_misses` (counter): Total number of cache misses.
+- `prometheus_relabel_cache_hits` (counter): Total number of cache hits.
+- `prometheus_relabel_cache_size` (gauge): Total size of relabel cache.
+- `prometheus_fanout_latency` (histogram): Write latency for sending to direct and indirect components.
+- `prometheus_forwarded_samples_total` (counter): Total number of samples sent to downstream components.
 
 ## Example
 
@@ -158,6 +159,7 @@ The third and final relabeling rule which uses the `labeldrop` action removes
 the `instance` label from the set of labels.
 
 So in this case, the initial set of metrics passed to the exported receiver is:
+
 ```
 metric_a{host = "localhost/development", __address__ = "localhost", app = "backend"}  2
 metric_a{host = "cluster_a/production",  __address__ = "cluster_a", app = "backend"}  9
@@ -165,6 +167,7 @@ metric_a{host = "cluster_a/production",  __address__ = "cluster_a", app = "backe
 
 The two resulting metrics are then propagated to each receiver defined in the
 `forward_to` argument.
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/prometheus/prometheus.remote_write.md b/docs/sources/reference/components/prometheus/prometheus.remote_write.md
index a919d750f0..6bb5adbd1c 100644
--- a/docs/sources/reference/components/prometheus/prometheus.remote_write.md
+++ b/docs/sources/reference/components/prometheus/prometheus.remote_write.md
@@ -36,30 +36,30 @@ prometheus.remote_write "LABEL" {
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`external_labels` | `map(string)` | Labels to add to metrics sent over the network. | | no
+| Name              | Type          | Description                                     | Default | Required |
+| ----------------- | ------------- | ----------------------------------------------- | ------- | -------- |
+| `external_labels` | `map(string)` | Labels to add to metrics sent over the network. |         | no       |
 
 ## Blocks
 
 The following blocks are supported inside the definition of
 `prometheus.remote_write`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-endpoint | [endpoint][] | Location to send metrics to. | no
-endpoint > basic_auth | [basic_auth][] | Configure basic_auth for authenticating to the endpoint. | no
-endpoint > authorization | [authorization][] | Configure generic authorization to the endpoint. | no
-endpoint > oauth2 | [oauth2][] | Configure OAuth2 for authenticating to the endpoint. | no
-endpoint > oauth2 > tls_config | [tls_config][] | Configure TLS settings for connecting to the endpoint. | no
-endpoint > sigv4 | [sigv4][] | Configure AWS Signature Verification 4 for authenticating to the endpoint. | no
-endpoint > azuread | [azuread][] | Configure AzureAD for authenticating to the endpoint. | no
-endpoint > azuread > managed_identity | [managed_identity][] | Configure Azure user-assigned managed identity. | yes
-endpoint > tls_config | [tls_config][] | Configure TLS settings for connecting to the endpoint. | no
-endpoint > queue_config | [queue_config][] | Configuration for how metrics are batched before sending. | no
-endpoint > metadata_config | [metadata_config][] | Configuration for how metric metadata is sent. | no
-endpoint > write_relabel_config | [write_relabel_config][] | Configuration for write_relabel_config. | no
-wal | [wal][] | Configuration for the component's WAL. | no
+| Hierarchy                             | Block                    | Description                                                                | Required |
+| ------------------------------------- | ------------------------ | -------------------------------------------------------------------------- | -------- |
+| endpoint                              | [endpoint][]             | Location to send metrics to.                                               | no       |
+| endpoint > basic_auth                 | [basic_auth][]           | Configure basic_auth for authenticating to the endpoint.                   | no       |
+| endpoint > authorization              | [authorization][]        | Configure generic authorization to the endpoint.                           | no       |
+| endpoint > oauth2                     | [oauth2][]               | Configure OAuth2 for authenticating to the endpoint.                       | no       |
+| endpoint > oauth2 > tls_config        | [tls_config][]           | Configure TLS settings for connecting to the endpoint.                     | no       |
+| endpoint > sigv4                      | [sigv4][]                | Configure AWS Signature Verification 4 for authenticating to the endpoint. | no       |
+| endpoint > azuread                    | [azuread][]              | Configure AzureAD for authenticating to the endpoint.                      | no       |
+| endpoint > azuread > managed_identity | [managed_identity][]     | Configure Azure user-assigned managed identity.                            | yes      |
+| endpoint > tls_config                 | [tls_config][]           | Configure TLS settings for connecting to the endpoint.                     | no       |
+| endpoint > queue_config               | [queue_config][]         | Configuration for how metrics are batched before sending.                  | no       |
+| endpoint > metadata_config            | [metadata_config][]      | Configuration for how metric metadata is sent.                             | no       |
+| endpoint > write_relabel_config       | [write_relabel_config][] | Configuration for write_relabel_config.                                    | no       |
+| wal                                   | [wal][]                  | Configuration for the component's WAL.                                     | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `endpoint >
 basic_auth` refers to a `basic_auth` block defined inside an
@@ -85,31 +85,32 @@ The `endpoint` block describes a single location to send metrics to. Multiple
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`url` | `string` | Full URL to send metrics to. | | yes
-`name` | `string` | Optional name to identify the endpoint in metrics. | | no
-`remote_timeout` | `duration` | Timeout for requests made to the URL. | `"30s"` | no
-`headers` | `map(string)` | Extra headers to deliver with the request. | | no
-`send_exemplars` | `bool` | Whether exemplars should be sent. | `true` | no
-`send_native_histograms` | `bool` | Whether native histograms should be sent. | `false` | no
-`bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.          |         | no
-`bearer_token`           | `secret`            | Bearer token to authenticate with.                            |         | no
-`enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                      | `true`  | no
-`follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.  | `true`  | no
-`proxy_url`              | `string`            | HTTP proxy to send requests through.                          |         | no
-`no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. | | no
-`proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.         | `false` | no
-`proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests. |         | no
-
- At most, one of the following can be provided:
- - [`bearer_token` argument](#endpoint-block).
- - [`bearer_token_file` argument](#endpoint-block).
- - [`basic_auth` block][basic_auth].
- - [`authorization` block][authorization].
- - [`oauth2` block][oauth2].
- - [`sigv4` block][sigv4].
- - [`azuread` block][azuread].
+| Name                     | Type                | Description                                                                                      | Default | Required |
+| ------------------------ | ------------------- | ------------------------------------------------------------------------------------------------ | ------- | -------- |
+| `url`                    | `string`            | Full URL to send metrics to.                                                                     |         | yes      |
+| `name`                   | `string`            | Optional name to identify the endpoint in metrics.                                               |         | no       |
+| `remote_timeout`         | `duration`          | Timeout for requests made to the URL.                                                            | `"30s"` | no       |
+| `headers`                | `map(string)`       | Extra headers to deliver with the request.                                                       |         | no       |
+| `send_exemplars`         | `bool`              | Whether exemplars should be sent.                                                                | `true`  | no       |
+| `send_native_histograms` | `bool`              | Whether native histograms should be sent.                                                        | `false` | no       |
+| `bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.                                             |         | no       |
+| `bearer_token`           | `secret`            | Bearer token to authenticate with.                                                               |         | no       |
+| `enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                                                         | `true`  | no       |
+| `follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.                                     | `true`  | no       |
+| `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
+| `no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. |         | no       |
+| `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
+| `proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests.                                    |         | no       |
+
+At most, one of the following can be provided:
+
+- [`bearer_token` argument](#endpoint-block).
+- [`bearer_token_file` argument](#endpoint-block).
+- [`basic_auth` block][basic_auth].
+- [`authorization` block][authorization].
+- [`oauth2` block][oauth2].
+- [`sigv4` block][sigv4].
+- [`azuread` block][azuread].
 
 When multiple `endpoint` blocks are provided, metrics are concurrently sent to all
 configured locations. Each endpoint has a _queue_ which is used to read metrics
@@ -157,23 +158,23 @@ metrics fails.
 
 ### queue_config block
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`capacity` | `number` | Number of samples to buffer per shard. | `10000` | no
-`min_shards` | `number` | Minimum amount of concurrent shards sending samples to the endpoint. | `1` | no
-`max_shards` | `number` | Maximum number of concurrent shards sending samples to the endpoint. | `50` | no
-`max_samples_per_send` | `number` | Maximum number of samples per send. | `2000` | no
-`batch_send_deadline` | `duration` | Maximum time samples will wait in the buffer before sending. | `"5s"` | no
-`min_backoff` | `duration` | Initial retry delay. The backoff time gets doubled for each retry. | `"30ms"` | no
-`max_backoff` | `duration` | Maximum retry delay. | `"5s"` | no
-`retry_on_http_429` | `bool` | Retry when an HTTP 429 status code is received. | `true` | no
-`sample_age_limit` | `duration` | Maximum age of samples to send. | `"0s"` | no
+| Name                   | Type       | Description                                                          | Default  | Required |
+| ---------------------- | ---------- | -------------------------------------------------------------------- | -------- | -------- |
+| `capacity`             | `number`   | Number of samples to buffer per shard.                               | `10000`  | no       |
+| `min_shards`           | `number`   | Minimum amount of concurrent shards sending samples to the endpoint. | `1`      | no       |
+| `max_shards`           | `number`   | Maximum number of concurrent shards sending samples to the endpoint. | `50`     | no       |
+| `max_samples_per_send` | `number`   | Maximum number of samples per send.                                  | `2000`   | no       |
+| `batch_send_deadline`  | `duration` | Maximum time samples will wait in the buffer before sending.         | `"5s"`   | no       |
+| `min_backoff`          | `duration` | Initial retry delay. The backoff time gets doubled for each retry.   | `"30ms"` | no       |
+| `max_backoff`          | `duration` | Maximum retry delay.                                                 | `"5s"`   | no       |
+| `retry_on_http_429`    | `bool`     | Retry when an HTTP 429 status code is received.                      | `true`   | no       |
+| `sample_age_limit`     | `duration` | Maximum age of samples to send.                                      | `"0s"`   | no       |
 
 Each queue then manages a number of concurrent _shards_ which is responsible
 for sending a fraction of data to their respective endpoints. The number of
 shards is automatically raised if samples are not being sent to the endpoint
 quickly enough. The range of permitted shards can be configured with the
-`min_shards` and `max_shards` arguments. Refer to  [Tuning `max_shards`](#tuning-max_shards)
+`min_shards` and `max_shards` arguments. Refer to [Tuning `max_shards`](#tuning-max_shards)
 for more information about how to configure `max_shards`.
 
 Each shard has a buffer of samples it will keep in memory, controlled with the
@@ -201,11 +202,11 @@ The default value is `0s`, which means that all samples are sent (feature is dis
 
 ### metadata_config block
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`send` | `bool` | Controls whether metric metadata is sent to the endpoint. | `true` | no
-`send_interval` | `duration` | How frequently metric metadata is sent to the endpoint. | `"1m"` | no
-`max_samples_per_send` | `number` | Maximum number of metadata samples to send to the endpoint at once. | `2000` | no
+| Name                   | Type       | Description                                                         | Default | Required |
+| ---------------------- | ---------- | ------------------------------------------------------------------- | ------- | -------- |
+| `send`                 | `bool`     | Controls whether metric metadata is sent to the endpoint.           | `true`  | no       |
+| `send_interval`        | `duration` | How frequently metric metadata is sent to the endpoint.             | `"1m"`  | no       |
+| `max_samples_per_send` | `number`   | Maximum number of metadata samples to send to the endpoint at once. | `2000`  | no       |
 
 ### write_relabel_config block
 
@@ -216,16 +217,16 @@ Name | Type | Description | Default | Required
 The `wal` block customizes the Write-Ahead Log (WAL) used to temporarily store
 metrics before they are sent to the configured set of endpoints.
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`truncate_frequency` | `duration` | How frequently to clean up the WAL. | `"2h"` | no
-`min_keepalive_time` | `duration` | Minimum time to keep data in the WAL before it can be removed. | `"5m"` | no
-`max_keepalive_time` | `duration` | Maximum time to keep data in the WAL before removing it. | `"8h"` | no
+| Name                 | Type       | Description                                                    | Default | Required |
+| -------------------- | ---------- | -------------------------------------------------------------- | ------- | -------- |
+| `truncate_frequency` | `duration` | How frequently to clean up the WAL.                            | `"2h"`  | no       |
+| `min_keepalive_time` | `duration` | Minimum time to keep data in the WAL before it can be removed. | `"5m"`  | no       |
+| `max_keepalive_time` | `duration` | Maximum time to keep data in the WAL before removing it.       | `"8h"`  | no       |
 
 The WAL serves two primary purposes:
 
-* Buffer unsent metrics in case of intermittent network issues.
-* Populate in-memory cache after a process restart.
+- Buffer unsent metrics in case of intermittent network issues.
+- Populate in-memory cache after a process restart.
 
 The WAL is located inside a component-specific directory relative to the
 storage path {{< param "PRODUCT_NAME" >}} is configured to use. See the
@@ -246,9 +247,9 @@ of data in the WAL; samples aren't removed until they are at least as old as
 
 The following fields are exported and can be referenced by other components:
 
-Name | Type | Description
----- | ---- | -----------
-`receiver` | `MetricsReceiver` | A value which other components can use to send metrics to.
+| Name       | Type              | Description                                                |
+| ---------- | ----------------- | ---------------------------------------------------------- |
+| `receiver` | `MetricsReceiver` | A value which other components can use to send metrics to. |
 
 ## Component health
 
@@ -263,77 +264,77 @@ information.
 
 ## Debug metrics
 
-* `prometheus_remote_write_wal_storage_active_series` (gauge): Current number of active series
+- `prometheus_remote_write_wal_storage_active_series` (gauge): Current number of active series
   being tracked by the WAL.
-* `prometheus_remote_write_wal_storage_deleted_series` (gauge): Current number of series marked
+- `prometheus_remote_write_wal_storage_deleted_series` (gauge): Current number of series marked
   for deletion from memory.
-* `prometheus_remote_write_wal_out_of_order_samples_total` (counter): Total number of out of
+- `prometheus_remote_write_wal_out_of_order_samples_total` (counter): Total number of out of
   order samples ingestion failed attempts.
-* `prometheus_remote_write_wal_storage_created_series_total` (counter): Total number of created
+- `prometheus_remote_write_wal_storage_created_series_total` (counter): Total number of created
   series appended to the WAL.
-* `prometheus_remote_write_wal_storage_removed_series_total` (counter): Total number of series
+- `prometheus_remote_write_wal_storage_removed_series_total` (counter): Total number of series
   removed from the WAL.
-* `prometheus_remote_write_wal_samples_appended_total` (counter): Total number of samples
+- `prometheus_remote_write_wal_samples_appended_total` (counter): Total number of samples
   appended to the WAL.
-* `prometheus_remote_write_wal_exemplars_appended_total` (counter): Total number of exemplars
+- `prometheus_remote_write_wal_exemplars_appended_total` (counter): Total number of exemplars
   appended to the WAL.
-* `prometheus_remote_storage_samples_total` (counter): Total number of samples
+- `prometheus_remote_storage_samples_total` (counter): Total number of samples
   sent to remote storage.
-* `prometheus_remote_storage_exemplars_total` (counter): Total number of
+- `prometheus_remote_storage_exemplars_total` (counter): Total number of
   exemplars sent to remote storage.
-* `prometheus_remote_storage_metadata_total` (counter): Total number of
+- `prometheus_remote_storage_metadata_total` (counter): Total number of
   metadata entries sent to remote storage.
-* `prometheus_remote_storage_samples_failed_total` (counter): Total number of
+- `prometheus_remote_storage_samples_failed_total` (counter): Total number of
   samples that failed to send to remote storage due to non-recoverable errors.
-* `prometheus_remote_storage_exemplars_failed_total` (counter): Total number of
+- `prometheus_remote_storage_exemplars_failed_total` (counter): Total number of
   exemplars that failed to send to remote storage due to non-recoverable errors.
-* `prometheus_remote_storage_metadata_failed_total` (counter): Total number of
+- `prometheus_remote_storage_metadata_failed_total` (counter): Total number of
   metadata entries that failed to send to remote storage due to
   non-recoverable errors.
-* `prometheus_remote_storage_samples_retries_total` (counter): Total number of
+- `prometheus_remote_storage_samples_retries_total` (counter): Total number of
   samples that failed to send to remote storage but were retried due to
   recoverable errors.
-* `prometheus_remote_storage_exemplars_retried_total` (counter): Total number of
+- `prometheus_remote_storage_exemplars_retried_total` (counter): Total number of
   exemplars that failed to send to remote storage but were retried due to
   recoverable errors.
-* `prometheus_remote_storage_metadata_retried_total` (counter): Total number of
+- `prometheus_remote_storage_metadata_retried_total` (counter): Total number of
   metadata entries that failed to send to remote storage but were retried due
   to recoverable errors.
-* `prometheus_remote_storage_samples_dropped_total` (counter): Total number of
+- `prometheus_remote_storage_samples_dropped_total` (counter): Total number of
   samples which were dropped after being read from the WAL before being sent to
   remote_write because of an unknown reference ID.
-* `prometheus_remote_storage_exemplars_dropped_total` (counter): Total number
+- `prometheus_remote_storage_exemplars_dropped_total` (counter): Total number
   of exemplars which were dropped after being read from the WAL before being
   sent to remote_write because of an unknown reference ID.
-* `prometheus_remote_storage_enqueue_retries_total` (counter): Total number of
+- `prometheus_remote_storage_enqueue_retries_total` (counter): Total number of
   times enqueue has failed because a shard's queue was full.
-* `prometheus_remote_storage_sent_batch_duration_seconds` (histogram): Duration
+- `prometheus_remote_storage_sent_batch_duration_seconds` (histogram): Duration
   of send calls to remote storage.
-* `prometheus_remote_storage_queue_highest_sent_timestamp_seconds` (gauge):
+- `prometheus_remote_storage_queue_highest_sent_timestamp_seconds` (gauge):
   Unix timestamp of the latest WAL sample successfully sent by a queue.
-* `prometheus_remote_storage_samples_pending` (gauge): The number of samples
+- `prometheus_remote_storage_samples_pending` (gauge): The number of samples
   pending in shards to be sent to remote storage.
-* `prometheus_remote_storage_exemplars_pending` (gauge): The number of
+- `prometheus_remote_storage_exemplars_pending` (gauge): The number of
   exemplars pending in shards to be sent to remote storage.
-* `prometheus_remote_storage_shard_capacity` (gauge): The capacity of shards
+- `prometheus_remote_storage_shard_capacity` (gauge): The capacity of shards
   within a given queue.
-* `prometheus_remote_storage_shards` (gauge): The number of shards used for
+- `prometheus_remote_storage_shards` (gauge): The number of shards used for
   concurrent delivery of metrics to an endpoint.
-* `prometheus_remote_storage_shards_min` (gauge): The minimum number of shards
+- `prometheus_remote_storage_shards_min` (gauge): The minimum number of shards
   a queue is allowed to run.
-* `prometheus_remote_storage_shards_max` (gauge): The maximum number of a
+- `prometheus_remote_storage_shards_max` (gauge): The maximum number of a
   shards a queue is allowed to run.
-* `prometheus_remote_storage_shards_desired` (gauge): The number of shards a
+- `prometheus_remote_storage_shards_desired` (gauge): The number of shards a
   queue wants to run to be able to keep up with the amount of incoming metrics.
-* `prometheus_remote_storage_bytes_total` (counter): Total number of bytes of
+- `prometheus_remote_storage_bytes_total` (counter): Total number of bytes of
   data sent by queues after compression.
-* `prometheus_remote_storage_metadata_bytes_total` (counter): Total number of
+- `prometheus_remote_storage_metadata_bytes_total` (counter): Total number of
   bytes of metadata sent by queues after compression.
-* `prometheus_remote_storage_max_samples_per_send` (gauge): The maximum number
+- `prometheus_remote_storage_max_samples_per_send` (gauge): The maximum number
   of samples each shard is allowed to send in a single request.
-* `prometheus_remote_storage_samples_in_total` (counter): Samples read into
+- `prometheus_remote_storage_samples_in_total` (counter): Samples read into
   remote storage.
-* `prometheus_remote_storage_exemplars_in_total` (counter): Exemplars read into
+- `prometheus_remote_storage_exemplars_in_total` (counter): Exemplars read into
   remote storage.
 
 ## Examples
@@ -368,7 +369,6 @@ prometheus.scrape "demo" {
 }
 ```
 
-
 ### Send metrics to a Mimir instance with a tenant specified
 
 You can create a `prometheus.remote_write` component that sends your metrics to a specific tenant within the Mimir instance.
@@ -414,6 +414,7 @@ If your database is Mimir, the exact name of the [Mimir error][mimir-ooo-err] is
 
 The most common cause for this error is that there is more than one {{< param "PRODUCT_NAME" >}} instance scraping the same target.
 To troubleshoot, take the following steps in order:
+
 1. If you use clustering, check if the number of {{< param "PRODUCT_NAME" >}} instances changed at the time the error was logged.
    This is the only situation in which it is normal to experience an out of order error.
    The error would only happen for a short period, until the cluster stabilizes and all {{< param "PRODUCT_NAME" >}} instances have a new list of targets.
@@ -424,7 +425,7 @@ To troubleshoot, take the following steps in order:
 1. Inspect the configuration to see if there could be multiple {{< param "PRODUCT_NAME" >}} instances which scrape the same target.
 1. Inspect the WAL to see which {{< param "PRODUCT_NAME" >}} instance sent those metric samples.
    The WAL is located in a directory set by the [run command][run-cmd] `--storage.path` argument.
-   You can use [Promtool][promtool] to inspect it and find out which metric series were sent by this {{< param "PRODUCT_NAME" >}} instance since the last WAL truncation event. 
+   You can use [Promtool][promtool] to inspect it and find out which metric series were sent by this {{< param "PRODUCT_NAME" >}} instance since the last WAL truncation event.
    For example:
    ```
    ./promtool tsdb dump --match='{__name__="otelcol_connector_spanmetrics_duration_seconds_bucket", http_method="GET", job="ExampleJobName"}' /path/to/wal/
@@ -482,6 +483,7 @@ samples that can be kept in the WAL. Samples older than
 `max_keepalive_time` are forcibly removed.
 
 ### Extended `remote_write` outages
+
 When the remote write endpoint is unreachable over a period of time, the most
 recent successfully sent timestamp is not updated. The
 `min_keepalive_time` and `max_keepalive_time` arguments control the age range
@@ -491,6 +493,7 @@ If the remote write outage is longer than the `max_keepalive_time` parameter,
 then the WAL is truncated, and the oldest data is lost.
 
 ### Intermittent `remote_write` outages
+
 If the remote write endpoint is intermittently reachable, the most recent
 successfully sent timestamp is updated whenever the connection is successful.
 A successful connection updates the series' comparison with
@@ -499,6 +502,7 @@ interval which checkpoints two thirds of the segments (rounded down to the
 nearest integer) written since the previous truncation.
 
 ### Falling behind
+
 If the queue shards cannot flush data quickly enough to keep
 up-to-date with the most recent data buffered in the WAL, we say that the
 component is 'falling behind'.
@@ -532,10 +536,10 @@ increasing the value of `max_shards`.
 
 {{< param "PRODUCT_NAME" >}} exposes a few metrics that you can use to monitor the remote write shards:
 
-* `prometheus_remote_storage_shards` (gauge): The number of shards used for concurrent delivery of metrics to an endpoint.
-* `prometheus_remote_storage_shards_min` (gauge): The minimum number of shards a queue is allowed to run.
-* `prometheus_remote_storage_shards_max` (gauge): The maximum number of shards a queue is allowed to run.
-* `prometheus_remote_storage_shards_desired` (gauge): The number of shards a queue wants to run to keep up with the number of incoming metrics.
+- `prometheus_remote_storage_shards` (gauge): The number of shards used for concurrent delivery of metrics to an endpoint.
+- `prometheus_remote_storage_shards_min` (gauge): The minimum number of shards a queue is allowed to run.
+- `prometheus_remote_storage_shards_max` (gauge): The maximum number of shards a queue is allowed to run.
+- `prometheus_remote_storage_shards_desired` (gauge): The number of shards a queue wants to run to keep up with the number of incoming metrics.
 
 If you're already running {{< param "PRODUCT_NAME" >}}, a rule of thumb is to set `max_shards` to
 4x shard utilization. Using the metrics explained above, you can run the following PromQL instant query
diff --git a/docs/sources/reference/components/prometheus/prometheus.scrape.md b/docs/sources/reference/components/prometheus/prometheus.scrape.md
index 622cf1a37a..24e9fdcae2 100644
--- a/docs/sources/reference/components/prometheus/prometheus.scrape.md
+++ b/docs/sources/reference/components/prometheus/prometheus.scrape.md
@@ -40,7 +40,7 @@ time), the component reports an error.
 The following arguments are supported:
 
 | Name                          | Type                    | Description                                                                                            | Default                                                                   | Required |
-|-------------------------------|-------------------------|--------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|----------|
+| ----------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------- | -------- |
 | `targets`                     | `list(map(string))`     | List of targets to scrape.                                                                             |                                                                           | yes      |
 | `forward_to`                  | `list(MetricsReceiver)` | List of receivers to send scraped metrics to.                                                          |                                                                           | yes      |
 | `job_name`                    | `string`                | The value to use for the job label if not already set.                                                 | component name                                                            | no       |
@@ -72,11 +72,12 @@ The following arguments are supported:
 | `proxy_connect_header`        | `map(list(secret))`     | Specifies headers to send to proxies during CONNECT requests.                                          |                                                                           | no       |
 
 At most, one of the following can be provided:
- - [`bearer_token` argument](#arguments).
- - [`bearer_token_file` argument](#arguments).
- - [`basic_auth` block][basic_auth].
- - [`authorization` block][authorization].
- - [`oauth2` block][oauth2].
+
+- [`bearer_token` argument](#arguments).
+- [`bearer_token_file` argument](#arguments).
+- [`basic_auth` block][basic_auth].
+- [`authorization` block][authorization].
+- [`oauth2` block][oauth2].
 
 `scrape_protocols` controls the preferred order of protocols to negotiate during
 a scrape. The following values are supported:
@@ -86,20 +87,21 @@ a scrape. The following values are supported:
 - `PrometheusProto`
 - `PrometheusText0.0.4`
 
-If you were using the now deprecated `enable_protobuf_negotiation` argument, switch 
+If you were using the now deprecated `enable_protobuf_negotiation` argument, switch
 to using `scrape_protocols = ["PrometheusProto", "OpenMetricsText1.0.0", "OpenMetricsText0.0.1", "PrometheusText0.0.4"]` instead.
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
 `track_timestamps_staleness` controls whether Prometheus tracks [staleness][prom-staleness] of metrics with an explicit timestamp present in scraped data.
-* An "explicit timestamp" is an optional timestamp in the [Prometheus metrics exposition format][prom-text-exposition-format]. For example, this sample has a timestamp of `1395066363000`:
+
+- An "explicit timestamp" is an optional timestamp in the [Prometheus metrics exposition format][prom-text-exposition-format]. For example, this sample has a timestamp of `1395066363000`:
   ```
   http_requests_total{method="post",code="200"} 1027 1395066363000
   ```
-* If `track_timestamps_staleness` is set to `true`, a staleness marker will be inserted when a metric is no longer present or the target is down.
-* A "staleness marker" is just a {{< term "sample" >}}sample{{< /term >}} with a specific NaN value which is reserved for internal use by Prometheus.
-* It is recommended to set `track_timestamps_staleness` to `true` if the database where metrics are written to has enabled [out of order ingestion][mimir-ooo].
-* If `track_timestamps_staleness` is set to `false`, samples with explicit timestamps will only be labeled as stale after a certain time period, which in Prometheus is 5 minutes by default.
+- If `track_timestamps_staleness` is set to `true`, a staleness marker will be inserted when a metric is no longer present or the target is down.
+- A "staleness marker" is just a {{< term "sample" >}}sample{{< /term >}} with a specific NaN value which is reserved for internal use by Prometheus.
+- It is recommended to set `track_timestamps_staleness` to `true` if the database where metrics are written to has enabled [out of order ingestion][mimir-ooo].
+- If `track_timestamps_staleness` is set to `false`, samples with explicit timestamps will only be labeled as stale after a certain time period, which in Prometheus is 5 minutes by default.
 
 [prom-text-exposition-format]: https://prometheus.io/docs/instrumenting/exposition_formats/#text-based-format
 [prom-staleness]: https://prometheus.io/docs/prometheus/latest/querying/basics/#staleness
@@ -109,14 +111,14 @@ to using `scrape_protocols = ["PrometheusProto", "OpenMetricsText1.0.0", "OpenMe
 
 The following blocks are supported inside the definition of `prometheus.scrape`:
 
-Hierarchy           | Block             | Description                                                              | Required
---------------------|-------------------|--------------------------------------------------------------------------|---------
-basic_auth          | [basic_auth][]    | Configure basic_auth for authenticating to targets.                      | no
-authorization       | [authorization][] | Configure generic authorization to targets.                              | no
-oauth2              | [oauth2][]        | Configure OAuth2 for authenticating to targets.                          | no
-oauth2 > tls_config | [tls_config][]    | Configure TLS settings for connecting to targets via OAuth2.             | no
-tls_config          | [tls_config][]    | Configure TLS settings for connecting to targets.                        | no
-clustering          | [clustering][]    | Configure the component for when {{< param "PRODUCT_NAME" >}} is running in clustered mode.     | no
+| Hierarchy           | Block             | Description                                                                                 | Required |
+| ------------------- | ----------------- | ------------------------------------------------------------------------------------------- | -------- |
+| basic_auth          | [basic_auth][]    | Configure basic_auth for authenticating to targets.                                         | no       |
+| authorization       | [authorization][] | Configure generic authorization to targets.                                                 | no       |
+| oauth2              | [oauth2][]        | Configure OAuth2 for authenticating to targets.                                             | no       |
+| oauth2 > tls_config | [tls_config][]    | Configure TLS settings for connecting to targets via OAuth2.                                | no       |
+| tls_config          | [tls_config][]    | Configure TLS settings for connecting to targets.                                           | no       |
+| clustering          | [clustering][]    | Configure the component for when {{< param "PRODUCT_NAME" >}} is running in clustered mode. | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example,
 `oauth2 > tls_config` refers to a `tls_config` block defined inside
@@ -147,9 +149,9 @@ an `oauth2` block.
 
 ### clustering block
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`enabled` | `bool` | Enables sharing targets with other cluster nodes. | `false` | yes
+| Name      | Type   | Description                                       | Default | Required |
+| --------- | ------ | ------------------------------------------------- | ------- | -------- |
+| `enabled` | `bool` | Enables sharing targets with other cluster nodes. | `false` | yes      |
 
 When {{< param "PRODUCT_NAME" >}} is [using clustering][], and `enabled` is set to true,
 then this `prometheus.scrape` component instance opts-in to participating in
@@ -193,9 +195,9 @@ scrape job on the component's debug endpoint.
 
 ## Debug metrics
 
-* `prometheus_fanout_latency` (histogram): Write latency for sending to direct and indirect components.
-* `prometheus_scrape_targets_gauge` (gauge): Number of targets this component is configured to scrape.
-* `prometheus_forwarded_samples_total` (counter): Total number of samples sent to downstream components.
+- `prometheus_fanout_latency` (histogram): Write latency for sending to direct and indirect components.
+- `prometheus_scrape_targets_gauge` (gauge): Number of targets this component is configured to scrape.
+- `prometheus_forwarded_samples_total` (counter): Total number of samples sent to downstream components.
 
 ## Scraping behavior
 
@@ -236,24 +238,23 @@ the labels last used for scraping.
 The following labels are automatically injected to the scraped time series and
 can help pin down a scrape target.
 
-Label                 | Description
---------------------- | ----------
-job                   | The configured job name that the target belongs to. Defaults to the fully formed component name.
-instance              | The `__address__` or `<host>:<port>` of the scrape target's URL.
-
+| Label    | Description                                                                                      |
+| -------- | ------------------------------------------------------------------------------------------------ |
+| job      | The configured job name that the target belongs to. Defaults to the fully formed component name. |
+| instance | The `__address__` or `<host>:<port>` of the scrape target's URL.                                 |
 
 Similarly, these metrics that record the behavior of the scrape targets are
 also automatically available.
-Metric Name                | Description
+Metric Name | Description
 -------------------------- | -----------
-`up`                       | 1 if the instance is healthy and reachable, or 0 if the scrape failed.
-`scrape_duration_seconds`  | Duration of the scrape in seconds.
-`scrape_samples_scraped`   | The number of samples the target exposed.
+`up` | 1 if the instance is healthy and reachable, or 0 if the scrape failed.
+`scrape_duration_seconds` | Duration of the scrape in seconds.
+`scrape_samples_scraped` | The number of samples the target exposed.
 `scrape_samples_post_metric_relabeling` | The number of samples remaining after metric relabeling was applied.
-`scrape_series_added`      | The approximate number of new series in this scrape.
-`scrape_timeout_seconds`   | The configured scrape timeout for a target. Useful for measuring how close a target was to timing out using `scrape_duration_seconds / scrape_timeout_seconds`
-`scrape_sample_limit`      | The configured sample limit for a target. Useful for measuring how close a target was to reaching the sample limit using `scrape_samples_post_metric_relabeling / (scrape_sample_limit > 0)`
-`scrape_body_size_bytes`   | The uncompressed size of the most recent scrape response, if successful. Scrapes failing because the `body_size_limit` is exceeded report -1, other scrape failures report 0.
+`scrape_series_added` | The approximate number of new series in this scrape.
+`scrape_timeout_seconds` | The configured scrape timeout for a target. Useful for measuring how close a target was to timing out using `scrape_duration_seconds / scrape_timeout_seconds`
+`scrape_sample_limit` | The configured sample limit for a target. Useful for measuring how close a target was to reaching the sample limit using `scrape_samples_post_metric_relabeling / (scrape_sample_limit > 0)`
+`scrape_body_size_bytes` | The uncompressed size of the most recent scrape response, if successful. Scrapes failing because the `body_size_limit` is exceeded report -1, other scrape failures report 0.
 
 The `up` metric is particularly useful for monitoring and alerting on the
 health of a scrape job. It is set to `0` in case anything goes wrong with the
@@ -282,7 +283,7 @@ present.
 
 ## Example
 
-### Set up scrape jobs for `blackbox exporter` targets  
+### Set up scrape jobs for `blackbox exporter` targets
 
 The following example sets up the scrape job with certain attributes (scrape
 endpoint, scrape interval, query parameters) and lets it scrape two instances
@@ -306,6 +307,7 @@ prometheus.scrape "blackbox_scraper" {
 ```
 
 Here are the endpoints that are being scraped every 10 seconds:
+
 ```
 http://blackbox-exporter:9115/probe?target=grafana.com&module=http_2xx
 http://blackbox-exporter:9116/probe?target=grafana.com&module=http_2xx
@@ -332,17 +334,19 @@ prometheus.scrape "kubelet" {
 `prometheus.scrape` supports [gzip](https://en.wikipedia.org/wiki/Gzip) compression.
 
 The following special labels can change the behavior of prometheus.scrape:
-* `__address__` is the name of the label that holds the `<host>:<port>` address of a scrape target.
-* `__metrics_path__`   is the name of the label that holds the path on which to scrape a target.
-* `__scheme__` is the name of the label that holds the scheme (http,https) on which to  scrape a target.
-* `__scrape_interval__` is the name of the label that holds the scrape interval used to scrape a target.
-* `__scrape_timeout__` is the name of the label that holds the scrape timeout used to scrape a target.
-* `__param_<name>` is a prefix for labels that provide URL parameters `<name>` used to scrape a target.
+
+- `__address__` is the name of the label that holds the `<host>:<port>` address of a scrape target.
+- `__metrics_path__` is the name of the label that holds the path on which to scrape a target.
+- `__scheme__` is the name of the label that holds the scheme (http,https) on which to scrape a target.
+- `__scrape_interval__` is the name of the label that holds the scrape interval used to scrape a target.
+- `__scrape_timeout__` is the name of the label that holds the scrape timeout used to scrape a target.
+- `__param_<name>` is a prefix for labels that provide URL parameters `<name>` used to scrape a target.
 
 Special labels added after a scrape
-* `__name__` is the label name indicating the metric name of a timeseries.
-* `job` is the label name indicating the job from which a timeseries was scraped.
-* `instance` is the label name used for the instance label.
+
+- `__name__` is the label name indicating the metric name of a timeseries.
+- `job` is the label name indicating the job from which a timeseries was scraped.
+- `instance` is the label name used for the instance label.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
@@ -353,7 +357,6 @@ Special labels added after a scrape
 - Components that export [Targets](../../../compatibility/#targets-exporters)
 - Components that export [Prometheus `MetricsReceiver`](../../../compatibility/#prometheus-metricsreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/prometheus/prometheus.write.queue.md b/docs/sources/reference/components/prometheus/prometheus.write.queue.md
index 59ae49c695..90489aaf09 100644
--- a/docs/sources/reference/components/prometheus/prometheus.write.queue.md
+++ b/docs/sources/reference/components/prometheus/prometheus.write.queue.md
@@ -4,7 +4,6 @@ description: Learn about prometheus.write.queue
 title: prometheus.write.queue
 ---
 
-
 <span class="badge docs-labels__stage docs-labels__item">Experimental</span>
 
 # prometheus.write.queue
@@ -19,8 +18,6 @@ You can specify multiple `prometheus.write.queue` components by giving them diff
 You should consider everything here extremely experimental and highly subject to change.
 [remote_write-spec]: https://prometheus.io/docs/specs/remote_write_spec/
 
-  
-
 ## Usage
 
 ```alloy
@@ -39,20 +36,20 @@ prometheus.write.queue "LABEL" {
 
 The following arguments are supported:
 
-Name | Type | Description | Default | Required
----- | ---- | ----------- | ------- | --------
-`ttl` | `time` | `duration` | How long the samples can be queued for before they are discarded. | `2h` | no
+| Name  | Type   | Description | Default                                                           | Required |
+| ----- | ------ | ----------- | ----------------------------------------------------------------- | -------- | --- |
+| `ttl` | `time` | `duration`  | How long the samples can be queued for before they are discarded. | `2h`     | no  |
 
 ## Blocks
 
 The following blocks are supported inside the definition of
 `prometheus.write.queue`:
 
-Hierarchy | Block | Description | Required
---------- | ----- | ----------- | --------
-persistence | [persistence][] | Configuration for persistence | no
-endpoint | [endpoint][] | Location to send metrics to. | no
-endpoint > basic_auth | [basic_auth][] | Configure basic_auth for authenticating to the endpoint. | no
+| Hierarchy             | Block           | Description                                              | Required |
+| --------------------- | --------------- | -------------------------------------------------------- | -------- |
+| persistence           | [persistence][] | Configuration for persistence                            | no       |
+| endpoint              | [endpoint][]    | Location to send metrics to.                             | no       |
+| endpoint > basic_auth | [basic_auth][]  | Configure basic_auth for authenticating to the endpoint. | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `endpoint >
 basic_auth` refers to a `basic_auth` block defined inside an
@@ -69,11 +66,10 @@ are shared for each `endpoint`.
 
 The following arguments are supported:
 
-Name | Type | Description                                                                   | Default | Required
----- | ---- |-------------------------------------------------------------------------------|---------| --------
-`max_signals_to_batch` | `uint` | The maximum number of signals before they are batched to disk.                | `10000` | no
-`batch_interval` | `duration` | How often to batch signals to disk if `max_signals_to_batch` is not reached. | `5s`     | no
-
+| Name                   | Type       | Description                                                                  | Default | Required |
+| ---------------------- | ---------- | ---------------------------------------------------------------------------- | ------- | -------- |
+| `max_signals_to_batch` | `uint`     | The maximum number of signals before they are batched to disk.               | `10000` | no       |
+| `batch_interval`       | `duration` | How often to batch signals to disk if `max_signals_to_batch` is not reached. | `5s`    | no       |
 
 ### endpoint block
 
@@ -83,30 +79,29 @@ The `endpoint` block describes a single location to send metrics to. Multiple
 
 The following arguments are supported:
 
-Name | Type | Description                                                        | Default | Required
----- | ---- |--------------------------------------------------------------------| ------ | --------
-`url` | `string` | Full URL to send metrics to.                                       | | yes
-`bearer_token` | `secret` | Bearer token to authenticate with.                                 |  | no
-`write_timeout` | `duration` | Timeout for requests made to the URL.                              | `"30s"` | no
-`retry_backoff` | `duration` | How often to wait between retries.                                 | `1s` | no
-`max_retry_attempts` | Maximum number of retries before dropping the batch. | `0`                                                                | no
-`batch_count` | `uint` | How many series to queue in each queue.                            | `1000` | no
-`flush_interval` | `duration` | How often to wait until sending if `batch_count` is not triggered. | `1s` | no
-`parallelism` | `uint` | How many parallel batches to write.                                | 10 | no
-`external_labels` | `map(string)` | Labels to add to metrics sent over the network.                    | | no
+| Name                 | Type                                                 | Description                                                        | Default | Required |
+| -------------------- | ---------------------------------------------------- | ------------------------------------------------------------------ | ------- | -------- |
+| `url`                | `string`                                             | Full URL to send metrics to.                                       |         | yes      |
+| `bearer_token`       | `secret`                                             | Bearer token to authenticate with.                                 |         | no       |
+| `write_timeout`      | `duration`                                           | Timeout for requests made to the URL.                              | `"30s"` | no       |
+| `retry_backoff`      | `duration`                                           | How often to wait between retries.                                 | `1s`    | no       |
+| `max_retry_attempts` | Maximum number of retries before dropping the batch. | `0`                                                                | no      |
+| `batch_count`        | `uint`                                               | How many series to queue in each queue.                            | `1000`  | no       |
+| `flush_interval`     | `duration`                                           | How often to wait until sending if `batch_count` is not triggered. | `1s`    | no       |
+| `parallelism`        | `uint`                                               | How many parallel batches to write.                                | 10      | no       |
+| `external_labels`    | `map(string)`                                        | Labels to add to metrics sent over the network.                    |         | no       |
 
 ### basic_auth block
 
 {{< docs/shared lookup="reference/components/basic-auth-block.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
-
 ## Exported fields
 
 The following fields are exported and can be referenced by other components:
 
-Name | Type | Description
----- | ---- | -----------
-`receiver` | `MetricsReceiver` | A value that other components can use to send metrics to.
+| Name       | Type              | Description                                               |
+| ---------- | ----------------- | --------------------------------------------------------- |
+| `receiver` | `MetricsReceiver` | A value that other components can use to send metrics to. |
 
 ## Component health
 
@@ -124,75 +119,75 @@ information.
 The following metrics are provided for backward compatibility.
 They generally behave the same, but there are likely edge cases where they differ.
 
-* `prometheus_remote_write_wal_storage_created_series_total` (counter): Total number of created
+- `prometheus_remote_write_wal_storage_created_series_total` (counter): Total number of created
   series appended to the WAL.
-* `prometheus_remote_write_wal_storage_removed_series_total` (counter): Total number of series
+- `prometheus_remote_write_wal_storage_removed_series_total` (counter): Total number of series
   removed from the WAL.
-* `prometheus_remote_write_wal_samples_appended_total` (counter): Total number of samples
+- `prometheus_remote_write_wal_samples_appended_total` (counter): Total number of samples
   appended to the WAL.
-* `prometheus_remote_write_wal_exemplars_appended_total` (counter): Total number of exemplars
+- `prometheus_remote_write_wal_exemplars_appended_total` (counter): Total number of exemplars
   appended to the WAL.
-* `prometheus_remote_storage_samples_total` (counter): Total number of samples
+- `prometheus_remote_storage_samples_total` (counter): Total number of samples
   sent to remote storage.
-* `prometheus_remote_storage_exemplars_total` (counter): Total number of
+- `prometheus_remote_storage_exemplars_total` (counter): Total number of
   exemplars sent to remote storage.
-* `prometheus_remote_storage_metadata_total` (counter): Total number of
+- `prometheus_remote_storage_metadata_total` (counter): Total number of
   metadata entries sent to remote storage.
-* `prometheus_remote_storage_samples_failed_total` (counter): Total number of
+- `prometheus_remote_storage_samples_failed_total` (counter): Total number of
   samples that failed to send to remote storage due to non-recoverable errors.
-* `prometheus_remote_storage_exemplars_failed_total` (counter): Total number of
+- `prometheus_remote_storage_exemplars_failed_total` (counter): Total number of
   exemplars that failed to send to remote storage due to non-recoverable errors.
-* `prometheus_remote_storage_metadata_failed_total` (counter): Total number of
+- `prometheus_remote_storage_metadata_failed_total` (counter): Total number of
   metadata entries that failed to send to remote storage due to
   non-recoverable errors.
-* `prometheus_remote_storage_samples_retries_total` (counter): Total number of
+- `prometheus_remote_storage_samples_retries_total` (counter): Total number of
   samples that failed to send to remote storage but were retried due to
   recoverable errors.
-* `prometheus_remote_storage_exemplars_retried_total` (counter): Total number of
+- `prometheus_remote_storage_exemplars_retried_total` (counter): Total number of
   exemplars that failed to send to remote storage but were retried due to
   recoverable errors.
-* `prometheus_remote_storage_metadata_retried_total` (counter): Total number of
+- `prometheus_remote_storage_metadata_retried_total` (counter): Total number of
   metadata entries that failed to send to remote storage but were retried due
   to recoverable errors.
-* `prometheus_remote_storage_samples_dropped_total` (counter): Total number of
+- `prometheus_remote_storage_samples_dropped_total` (counter): Total number of
   samples which were dropped after being read from the WAL before being sent to
   remote_write because of an unknown reference ID.
-* `prometheus_remote_storage_exemplars_dropped_total` (counter): Total number
+- `prometheus_remote_storage_exemplars_dropped_total` (counter): Total number
   of exemplars that were dropped after being read from the WAL before being
   sent to remote_write because of an unknown reference ID.
-* `prometheus_remote_storage_enqueue_retries_total` (counter): Total number of
+- `prometheus_remote_storage_enqueue_retries_total` (counter): Total number of
   times enqueue has failed because a shard's queue was full.
-* `prometheus_remote_storage_sent_batch_duration_seconds` (histogram): Duration
+- `prometheus_remote_storage_sent_batch_duration_seconds` (histogram): Duration
   of send calls to remote storage.
-* `prometheus_remote_storage_queue_highest_sent_timestamp_seconds` (gauge):
+- `prometheus_remote_storage_queue_highest_sent_timestamp_seconds` (gauge):
   Unix timestamp of the latest WAL sample successfully sent by a queue.
-* `prometheus_remote_storage_samples_in_total` (counter): Samples read into
+- `prometheus_remote_storage_samples_in_total` (counter): Samples read into
   remote storage.
-* `prometheus_remote_storage_exemplars_in_total` (counter): Exemplars read into
+- `prometheus_remote_storage_exemplars_in_total` (counter): Exemplars read into
   remote storage.
 
 Metrics that are new to `prometheus.write.queue`. These are highly subject to change.
 
-* `alloy_queue_series_serializer_incoming_signals` (counter): Total number of series written to serialization.
-* `alloy_queue_metadata_serializer_incoming_signals` (counter): Total number of metadata written to serialization.
-* `alloy_queue_series_serializer_incoming_timestamp_seconds` (gauge): Highest timestamp of incoming series.
-* `alloy_queue_series_serializer_errors` (gauge): Number of errors for series written to serializer.
-* `alloy_queue_metadata_serializer_errors` (gauge): Number of errors for metadata written to serializer.
-* `alloy_queue_series_network_timestamp_seconds` (gauge): Highest timestamp written to an endpoint.
-* `alloy_queue_series_network_sent` (counter): Number of series sent successfully.
-* `alloy_queue_metadata_network_sent` (counter): Number of metadata sent successfully.
-* `alloy_queue_network_series_failed` (counter): Number of series failed.
-* `alloy_queue_network_metadata_failed` (counter): Number of metadata failed.
-* `alloy_queue_network_series_retried` (counter): Number of series retried due to network issues.
-* `alloy_queue_network_metadata_retried` (counter): Number of metadata retried due to network issues.
-* `alloy_queue_network_series_retried_429` (counter): Number of series retried due to status code 429.
-* `alloy_queue_network_metadata_retried_429` (counter): Number of metadata retried due to status code 429.
-* `alloy_queue_network_series_retried_5xx` (counter): Number of series retried due to status code 5xx.
-* `alloy_queue_network_metadata_retried_5xx` (counter): Number of metadata retried due to status code 5xx.
-* `alloy_queue_network_series_network_duration_seconds` (histogram): Duration writing series to endpoint.
-* `alloy_queue_network_metadata_network_duration_seconds` (histogram): Duration writing metadata to endpoint.
-* `alloy_queue_network_series_network_errors` (counter): Number of errors writing series to network.
-* `alloy_queue_network_metadata_network_errors` (counter): Number of errors writing metadata to network.
+- `alloy_queue_series_serializer_incoming_signals` (counter): Total number of series written to serialization.
+- `alloy_queue_metadata_serializer_incoming_signals` (counter): Total number of metadata written to serialization.
+- `alloy_queue_series_serializer_incoming_timestamp_seconds` (gauge): Highest timestamp of incoming series.
+- `alloy_queue_series_serializer_errors` (gauge): Number of errors for series written to serializer.
+- `alloy_queue_metadata_serializer_errors` (gauge): Number of errors for metadata written to serializer.
+- `alloy_queue_series_network_timestamp_seconds` (gauge): Highest timestamp written to an endpoint.
+- `alloy_queue_series_network_sent` (counter): Number of series sent successfully.
+- `alloy_queue_metadata_network_sent` (counter): Number of metadata sent successfully.
+- `alloy_queue_network_series_failed` (counter): Number of series failed.
+- `alloy_queue_network_metadata_failed` (counter): Number of metadata failed.
+- `alloy_queue_network_series_retried` (counter): Number of series retried due to network issues.
+- `alloy_queue_network_metadata_retried` (counter): Number of metadata retried due to network issues.
+- `alloy_queue_network_series_retried_429` (counter): Number of series retried due to status code 429.
+- `alloy_queue_network_metadata_retried_429` (counter): Number of metadata retried due to status code 429.
+- `alloy_queue_network_series_retried_5xx` (counter): Number of series retried due to status code 5xx.
+- `alloy_queue_network_metadata_retried_5xx` (counter): Number of metadata retried due to status code 5xx.
+- `alloy_queue_network_series_network_duration_seconds` (histogram): Duration writing series to endpoint.
+- `alloy_queue_network_metadata_network_duration_seconds` (histogram): Duration writing metadata to endpoint.
+- `alloy_queue_network_series_network_errors` (counter): Number of errors writing series to network.
+- `alloy_queue_network_metadata_network_errors` (counter): Number of errors writing metadata to network.
 
 ## Examples
 
@@ -235,18 +230,18 @@ Any labels that start with `__` will be removed before sending to the endpoint.
 
 ### Data retention
 
-Data is written to disk in blocks utilizing [snappy][] compression. These blocks are read on startup and resent if they are still within the TTL. 
+Data is written to disk in blocks utilizing [snappy][] compression. These blocks are read on startup and resent if they are still within the TTL.
 Any data that has not been written to disk, or that is in the network queues is lost if {{< param "PRODUCT_NAME" >}} is restarted.
 
 ### Retries
 
-`prometheus.write.queue`  will retry sending data if the following errors or HTTP status codes are returned:
+`prometheus.write.queue` will retry sending data if the following errors or HTTP status codes are returned:
+
+- Network errors.
+- HTTP 429 errors.
+- HTTP 5XX errors.
 
- * Network errors. 
- * HTTP 429 errors. 
- * HTTP 5XX errors.
- 
-`prometheus.write.queue`  will  not retry sending data if any other unsuccessful status codes are returned. 
+`prometheus.write.queue` will not retry sending data if any other unsuccessful status codes are returned.
 
 ### Memory
 
@@ -255,7 +250,7 @@ You can adjust the `max_signals_to_batch`, `parallelism`, and `batch_size` to co
 A higher `max_signals_to_batch` allows for more efficient disk compression.
 A higher `parallelism` allows more parallel writes, and `batch_size` allows more data sent at one time.
 This can allow greater throughput at the cost of more memory on both {{< param "PRODUCT_NAME" >}} and the endpoint.
-The defaults are suitable for most common usages. 
+The defaults are suitable for most common usages.
 
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
diff --git a/docs/sources/reference/components/pyroscope/pyroscope.ebpf.md b/docs/sources/reference/components/pyroscope/pyroscope.ebpf.md
index 7e9c328138..0b4053f779 100644
--- a/docs/sources/reference/components/pyroscope/pyroscope.ebpf.md
+++ b/docs/sources/reference/components/pyroscope/pyroscope.ebpf.md
@@ -14,7 +14,7 @@ title: pyroscope.ebpf
 The collected performance profiles are forwarded to the list of receivers passed in `forward_to`.
 
 {{< admonition type="note" >}}
-To use the  `pyroscope.ebpf` component you must run {{< param "PRODUCT_NAME" >}} as root and inside the host PID namespace.
+To use the `pyroscope.ebpf` component you must run {{< param "PRODUCT_NAME" >}} as root and inside the host PID namespace.
 {{< /admonition >}}
 
 You can specify multiple `pyroscope.ebpf` components by giving them different labels, however it's not recommended as it can lead to additional memory and CPU usage.
@@ -76,17 +76,17 @@ The `pyroscope.ebpf` component doesn't support any blocks. You can configure thi
 
 ## Debug information
 
-* `elf_cache` per build id and per same file symbol tables and their sizes in symbols count.
-* `pid_cache` per process elf symbol tables and their sizes in symbols count.
-* `targets` currently tracked active targets.
+- `elf_cache` per build id and per same file symbol tables and their sizes in symbols count.
+- `pid_cache` per process elf symbol tables and their sizes in symbols count.
+- `targets` currently tracked active targets.
 
 ## Debug metrics
 
-* `pyroscope_ebpf_active_targets` (gauge): Number of active targets the component tracks.
-* `pyroscope_ebpf_pprofs_total` (counter): Number of pprof profiles collected by the eBPF component.
-* `pyroscope_ebpf_profiling_sessions_failing_total` (counter): Number of profiling sessions failed.
-* `pyroscope_ebpf_profiling_sessions_total` (counter): Number of profiling sessions completed.
-* `pyroscope_fanout_latency` (histogram): Write latency for sending to direct and indirect components.
+- `pyroscope_ebpf_active_targets` (gauge): Number of active targets the component tracks.
+- `pyroscope_ebpf_pprofs_total` (counter): Number of pprof profiles collected by the eBPF component.
+- `pyroscope_ebpf_profiling_sessions_failing_total` (counter): Number of profiling sessions failed.
+- `pyroscope_ebpf_profiling_sessions_total` (counter): Number of profiling sessions completed.
+- `pyroscope_fanout_latency` (histogram): Write latency for sending to direct and indirect components.
 
 ## Profile collecting behavior
 
@@ -106,10 +106,10 @@ These labels can help you pin down a profiling target.
 
 One of the following special labels _must_ be included in each target of `targets` and the label must correspond to the container or process that is profiled:
 
-* `__container_id__`: The container ID.
-* `__meta_docker_container_id`: The ID of the Docker container.
-* `__meta_kubernetes_pod_container_id`: The ID of the Kubernetes Pod container.
-* `__process_pid__` : The process ID.
+- `__container_id__`: The container ID.
+- `__meta_docker_container_id`: The ID of the Docker container.
+- `__meta_kubernetes_pod_container_id`: The ID of the Kubernetes Pod container.
+- `__process_pid__` : The process ID.
 
 Each process is then associated with a specified target from the targets list, determined by a container ID or process PID.
 
@@ -122,9 +122,9 @@ Otherwise the process isn't profiled.
 The special label `service_name` is required and must always be present.
 If it's not specified, it's attempted to be inferred from multiple sources:
 
-* `__meta_docker_container_name`
-* `__meta_kubernetes_namespace` and `__meta_kubernetes_pod_container_name`
-* `__meta_kubernetes_pod_annotation_pyroscope_io_service_name` which is a `pyroscope.io/service_name` Pod annotation.
+- `__meta_docker_container_name`
+- `__meta_kubernetes_namespace` and `__meta_kubernetes_pod_container_name`
+- `__meta_kubernetes_pod_annotation_pyroscope_io_service_name` which is a `pyroscope.io/service_name` Pod annotation.
 
 If `service_name` isn't specified and couldn't be inferred, it's set to `unspecified`.
 
@@ -132,18 +132,18 @@ If `service_name` isn't specified and couldn't be inferred, it's set to `unspeci
 
 Symbols are extracted from various sources, including:
 
-* The `.gopclntab` section in Go language ELF files.
-* The `.symtab` and `.dynsym` sections in the debug ELF file.
-* The `.symtab` and `.dynsym` sections in the ELF file.
+- The `.gopclntab` section in Go language ELF files.
+- The `.symtab` and `.dynsym` sections in the debug ELF file.
+- The `.symtab` and `.dynsym` sections in the ELF file.
 
 The search for debug files follows [gdb algorithm][].
 For example, if the profiler wants to find the debug file for `/lib/x86_64-linux-gnu/libc.so.6` with a `.gnu_debuglink` set to `libc.so.6.debug` and a build ID `0123456789abcdef`.
 The following paths are examined:
 
-* `/usr/lib/debug/.build-id/01/0123456789abcdef.debug`
-* `/lib/x86_64-linux-gnu/libc.so.6.debug`
-* `/lib/x86_64-linux-gnu/.debug/libc.so.6.debug`
-* `/usr/lib/debug/lib/x86_64-linux-gnu/libc.so.6.debug`
+- `/usr/lib/debug/.build-id/01/0123456789abcdef.debug`
+- `/lib/x86_64-linux-gnu/libc.so.6.debug`
+- `/lib/x86_64-linux-gnu/.debug/libc.so.6.debug`
+- `/usr/lib/debug/lib/x86_64-linux-gnu/libc.so.6.debug`
 
 ### Deal with unknown symbols
 
@@ -151,9 +151,9 @@ Unknown symbols in the profiles you've collected indicate that the profiler coul
 
 This can occur for several reasons:
 
-* The process has terminated, making the ELF file inaccessible.
-* The ELF file is either corrupted or not recognized as an ELF file.
-* There is no corresponding ELF file entry in `/proc/pid/maps` for the address in the stack trace.
+- The process has terminated, making the ELF file inaccessible.
+- The ELF file is either corrupted or not recognized as an ELF file.
+- There is no corresponding ELF file entry in `/proc/pid/maps` for the address in the stack trace.
 
 ### Address unresolved symbols
 
@@ -161,8 +161,8 @@ If you only see module names without corresponding function names, for example,
 
 This can occur for several reasons:
 
-* The binary has been stripped, leaving no .symtab, .dynsym, or .gopclntab sections in the ELF file.
-* The debug file is missing or couldn't be located.
+- The binary has been stripped, leaving no .symtab, .dynsym, or .gopclntab sections in the ELF file.
+- The debug file is missing or couldn't be located.
 
 To fix this for your binaries, ensure that they're either not stripped or that you have separate debug files available.
 You can achieve this by running:
@@ -298,7 +298,6 @@ pyroscope.ebpf "default" {
 - Components that export [Targets](../../../compatibility/#targets-exporters)
 - Components that export [Pyroscope `ProfilesReceiver`](../../../compatibility/#pyroscope-profilesreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/pyroscope/pyroscope.java.md b/docs/sources/reference/components/pyroscope/pyroscope.java.md
index d27fd1e268..10cc287c53 100644
--- a/docs/sources/reference/components/pyroscope/pyroscope.java.md
+++ b/docs/sources/reference/components/pyroscope/pyroscope.java.md
@@ -13,7 +13,7 @@ title: pyroscope.java
 `pyroscope.java` continuously profiles Java processes running on the local Linux OS using [async-profiler](https://github.com/async-profiler/async-profiler).
 
 {{< admonition type="note" >}}
-To use the  `pyroscope.java` component you must run {{< param "PRODUCT_NAME" >}} as root and inside host PID namespace.
+To use the `pyroscope.java` component you must run {{< param "PRODUCT_NAME" >}} as root and inside host PID namespace.
 {{< /admonition >}}
 
 ## Usage
@@ -125,7 +125,7 @@ The following arguments are supported:
 
 | Name          | Type       | Description                                                                                                     | Default    | Required |
 | ------------- | ---------- | --------------------------------------------------------------------------------------------------------------- | ---------- | -------- |
-| `alloc`       | `string`   | Allocation profiling sampling configuration  It's passed as an `--alloc` argument to async-profiler.            | `"512k"`   | no       |
+| `alloc`       | `string`   | Allocation profiling sampling configuration It's passed as an `--alloc` argument to async-profiler.             | `"512k"`   | no       |
 | `cpu`         | `bool`     | A flag to enable CPU profiling, using `itimer` async-profiler event by default.                                 | `true`     | no       |
 | `event`       | `string`   | Sets the CPU profiling event. Can be one of `itimer`, `cpu` or `wall`.                                          | `"itimer"` | no       |
 | `interval`    | `duration` | How frequently to collect profiles from the targets.                                                            | `"60s"`    | no       |
@@ -139,10 +139,10 @@ Refer to [profiler-options](https://github.com/async-profiler/async-profiler?tab
 
 The `event` argument sets the CPU profiling event:
 
-* `itimer` - Default. Uses the [`setitimer(ITIMER_PROF)`](http://man7.org/linux/man-pages/man2/setitimer.2.html) syscall, which generates a signal every time a process consumes CPU.
-* `cpu` - Uses PMU-case sampling (like Intel PEBS or AMD IBS), can be more accurate than `itimer`, but it's not available on every platform.
-* `wall` - This samples all threads equally every given period of time regardless of thread status: Running, Sleeping, or Blocked.
-   For example, this can be helpful when profiling application start-up time or IO-intensive processes.
+- `itimer` - Default. Uses the [`setitimer(ITIMER_PROF)`](http://man7.org/linux/man-pages/man2/setitimer.2.html) syscall, which generates a signal every time a process consumes CPU.
+- `cpu` - Uses PMU-case sampling (like Intel PEBS or AMD IBS), can be more accurate than `itimer`, but it's not available on every platform.
+- `wall` - This samples all threads equally every given period of time regardless of thread status: Running, Sleeping, or Blocked.
+  For example, this can be helpful when profiling application start-up time or IO-intensive processes.
 
 #### `per_thread`
 
@@ -221,7 +221,6 @@ pyroscope.java "java" {
 - Components that export [Targets](../../../compatibility/#targets-exporters)
 - Components that export [Pyroscope `ProfilesReceiver`](../../../compatibility/#pyroscope-profilesreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/pyroscope/pyroscope.receive_http.md b/docs/sources/reference/components/pyroscope/pyroscope.receive_http.md
index 14e0e27343..d357854fba 100644
--- a/docs/sources/reference/components/pyroscope/pyroscope.receive_http.md
+++ b/docs/sources/reference/components/pyroscope/pyroscope.receive_http.md
@@ -29,8 +29,8 @@ pyroscope.receive_http "<LABEL>" {
 
 The component starts an HTTP server supporting the following endpoint.
 
-* `POST /ingest` - send profiles to the component, which will be forwarded to the receivers as configured in the `forward_to argument`.
-   The request format must match the format of the Pyroscope ingest API.
+- `POST /ingest` - send profiles to the component, which will be forwarded to the receivers as configured in the `forward_to argument`.
+  The request format must match the format of the Pyroscope ingest API.
 
 ## Arguments
 
@@ -119,7 +119,6 @@ This flexibility allows you to design a setup that best fits your infrastructure
 
 - Components that export [Pyroscope `ProfilesReceiver`](../../../compatibility/#pyroscope-profilesreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/pyroscope/pyroscope.scrape.md b/docs/sources/reference/components/pyroscope/pyroscope.scrape.md
index 8ffad78a68..522892eb24 100644
--- a/docs/sources/reference/components/pyroscope/pyroscope.scrape.md
+++ b/docs/sources/reference/components/pyroscope/pyroscope.scrape.md
@@ -25,9 +25,9 @@ The `pyroscope.scrape` component regards a scrape as successful if it responded
 
 If a scrape request fails, the [debug UI][] for `pyroscope.scrape` will show:
 
-* Detailed information about the failure.
-* The time of the last successful scrape.
-* The labels last used for scraping.
+- Detailed information about the failure.
+- The time of the last successful scrape.
+- The labels last used for scraping.
 
 The scraped performance profiles can be forwarded to components such as `pyroscope.write` via the `forward_to` argument.
 
@@ -70,13 +70,13 @@ You can use the following arguments with `pyroscope.scrape`:
 | `proxy_from_environment`   | `bool`                   | Use the proxy URL indicated by environment variables.                                            | `false`        | no       |
 | `proxy_connect_header`     | `map(list(secret))`      | Specifies headers to send to proxies during CONNECT requests.                                    |                | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][arguments] argument
-* [`bearer_token`][arguments] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][arguments] argument
+- [`bearer_token`][arguments] argument
+- [`oauth2`][oauth2] block
 
 Any omitted arguments take on their default values.
 If conflicting arguments are being passed, for example, configuring both `bearer_token` and `bearer_token_file`, then `pyroscope.scrape` will fail to start and will report an error.
@@ -125,27 +125,27 @@ This parameter is important for controlling the trade-off between resource usage
 
 If `scrape_interval` is short:
 
-* Advantages:
-  * Fewer profiles may be lost if the application being scraped crashes.
-* Disadvantages:
-  * Greater consumption of CPU, memory, and network resources during scrapes and remote writes.
-  * The backend database (Pyroscope) consumes more storage space.
+- Advantages:
+  - Fewer profiles may be lost if the application being scraped crashes.
+- Disadvantages:
+  - Greater consumption of CPU, memory, and network resources during scrapes and remote writes.
+  - The backend database (Pyroscope) consumes more storage space.
 
 If `scrape_interval` is long:
 
-* Advantages:
-  * Lower resource consumption.
-* Disadvantages:
-  * More profiles may be lost if the application being scraped crashes.
-  * If the [delta argument][] is set to `true`, the batch size of each remote write to Pyroscope may be bigger.
+- Advantages:
+  - Lower resource consumption.
+- Disadvantages:
+  - More profiles may be lost if the application being scraped crashes.
+  - If the [delta argument][] is set to `true`, the batch size of each remote write to Pyroscope may be bigger.
     The Pyroscope database may need to be tuned with higher limits.
-  * If the [delta argument][] is set to `true`, there is a larger risk of reaching the HTTP server timeouts of the application being scraped.
+  - If the [delta argument][] is set to `true`, there is a larger risk of reaching the HTTP server timeouts of the application being scraped.
 
 For example, consider this situation:
 
-* `pyroscope.scrape` is configured with a `scrape_interval` of `"60s"`.
-* The application being scraped is running an HTTP server with a timeout of 30 seconds.
-* Any scrape HTTP requests where the [delta argument][] is set to `true` will fail, because they will attempt to run for 59 seconds.
+- `pyroscope.scrape` is configured with a `scrape_interval` of `"60s"`.
+- The application being scraped is running an HTTP server with a timeout of 30 seconds.
+- Any scrape HTTP requests where the [delta argument][] is set to `true` will fail, because they will attempt to run for 59 seconds.
 
 ## Blocks
 
@@ -194,10 +194,8 @@ For example, if `profile.mutex` isn't specified in the configuration, the defaul
 [profile.process_cpu]: #profileprocess_cpu
 [profiling_config]: #profiling_config
 [tls_config]: #tls_config
-
 [fgprof]: https://github.com/felixge/fgprof
 [godeltaprof]: https://github.com/grafana/pyroscope-go/tree/main/godeltaprof
-
 [delta argument]: #delta-argument
 
 ### `authorization`
@@ -395,9 +393,9 @@ When the `delta` argument is `false`, the [pprof][] HTTP query will be instantan
 
 When the `delta` argument is `true`:
 
-* The [pprof][] HTTP query runs for a certain amount of time.
-* A `seconds` parameter is automatically added to the HTTP request.
-* The default value for the `seconds` query parameter is `scrape_interval - 1`.
+- The [pprof][] HTTP query runs for a certain amount of time.
+- A `seconds` parameter is automatically added to the HTTP request.
+- The default value for the `seconds` query parameter is `scrape_interval - 1`.
   If you set `delta_profiling_duration`, then `seconds` is assigned the same value as `delta_profiling_duration`.
   However, the `delta_profiling_duration` can't be larger than `scrape_interval`.
   For example, if you set `scrape_interval` to `"15s"`, then `seconds` defaults to `14s`
@@ -418,7 +416,7 @@ When the `delta` argument is `true`:
 
 ## Debug metrics
 
-* `pyroscope_fanout_latency` (histogram): Write latency for sending to direct and indirect components.
+- `pyroscope_fanout_latency` (histogram): Write latency for sending to direct and indirect components.
 
 ## Examples
 
@@ -464,8 +462,8 @@ http://localhost:12345/debug/pprof/profile?seconds=14
 
 `seconds=14` is added to the `/debug/pprof/profile` endpoint, because:
 
-* The `delta` argument of the `profile.process_cpu` block is `true` by default.
-* `scrape_interval` is `"15s"` by default.
+- The `delta` argument of the `profile.process_cpu` block is `true` by default.
+- `scrape_interval` is `"15s"` by default.
 
 The `/debug/fgprof` endpoint won't be scraped, because the `enabled` argument of the `profile.fgprof` block is `false` by default.
 
@@ -567,7 +565,6 @@ http://localhost:12345/debug/pprof/mutex
 - Components that export [Targets](../../../compatibility/#targets-exporters)
 - Components that export [Pyroscope `ProfilesReceiver`](../../../compatibility/#pyroscope-profilesreceiver-exporters)
 
-
 {{< admonition type="note" >}}
 Connecting some components may not be sensible or components may require further configuration to make the connection work correctly.
 Refer to the linked documentation for more details.
diff --git a/docs/sources/reference/components/pyroscope/pyroscope.write.md b/docs/sources/reference/components/pyroscope/pyroscope.write.md
index f004218d80..4a78537579 100644
--- a/docs/sources/reference/components/pyroscope/pyroscope.write.md
+++ b/docs/sources/reference/components/pyroscope/pyroscope.write.md
@@ -83,13 +83,13 @@ The following arguments are supported:
 | `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |           | no       |
 | `remote_timeout`         | `duration`          | Timeout for requests made to the URL.                                                            | `"10s"`   | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][endpoint] argument
-* [`bearer_token`][endpoint] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][endpoint] argument
+- [`bearer_token`][endpoint] argument
+- [`oauth2`][oauth2] block
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -152,6 +152,7 @@ pyroscope.scrape "default" {
   forward_to = [pyroscope.write.staging.receiver]
 }
 ```
+
 <!-- START GENERATED COMPATIBLE COMPONENTS -->
 
 ## Compatible components
diff --git a/docs/sources/reference/components/remote/remote.http.md b/docs/sources/reference/components/remote/remote.http.md
index 48526fde59..68eeb2c22a 100644
--- a/docs/sources/reference/components/remote/remote.http.md
+++ b/docs/sources/reference/components/remote/remote.http.md
@@ -42,9 +42,9 @@ You can use the following arguments with `remote.http`:
 When `remote.http` performs a poll operation, an HTTP `GET` request is made against the URL specified by the `url` argument.
 A poll is triggered by the following:
 
-* When the component first loads.
-* Every time the component's arguments get re-evaluated.
-* At the frequency specified by the `poll_frequency` argument.
+- When the component first loads.
+- Every time the component's arguments get re-evaluated.
+- At the frequency specified by the `poll_frequency` argument.
 
 The poll is successful if the URL returns a `200 OK` response code.
 All other response codes are treated as errors and mark the component as unhealthy.
diff --git a/docs/sources/reference/components/remote/remote.kubernetes.configmap.md b/docs/sources/reference/components/remote/remote.kubernetes.configmap.md
index 4392da6f33..53b3735f43 100644
--- a/docs/sources/reference/components/remote/remote.kubernetes.configmap.md
+++ b/docs/sources/reference/components/remote/remote.kubernetes.configmap.md
@@ -37,9 +37,9 @@ You can use the following arguments with `remote.kubernetes.configmap`:
 When this component performs a poll operation, it requests the ConfigMap data from the Kubernetes API.
 A poll is triggered by the following:
 
-* When the component first loads.
-* Every time the component's arguments get re-evaluated.
-* At the frequency specified by the `poll_frequency` argument.
+- When the component first loads.
+- Every time the component's arguments get re-evaluated.
+- At the frequency specified by the `poll_frequency` argument.
 
 Any error while polling will mark the component as unhealthy.
 After a successful poll, all data is exported with the same field names as the source ConfigMap.
@@ -86,13 +86,13 @@ The following arguments are supported:
 | `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
 | `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][client] argument
-* [`bearer_token`][client] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][client] argument
+- [`bearer_token`][client] argument
+- [`oauth2`][oauth2] block
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
diff --git a/docs/sources/reference/components/remote/remote.kubernetes.secret.md b/docs/sources/reference/components/remote/remote.kubernetes.secret.md
index e805a30ce4..01646f6515 100644
--- a/docs/sources/reference/components/remote/remote.kubernetes.secret.md
+++ b/docs/sources/reference/components/remote/remote.kubernetes.secret.md
@@ -37,9 +37,9 @@ You can use the following arguments with `remote.kubernetes.secret`:
 When this component performs a poll operation, it requests the Secret data from the Kubernetes API.
 A poll is triggered by the following:
 
-* When the component first loads.
-* Every time the component's arguments get re-evaluated.
-* At the frequency specified by the `poll_frequency` argument.
+- When the component first loads.
+- Every time the component's arguments get re-evaluated.
+- At the frequency specified by the `poll_frequency` argument.
 
 Any error while polling will mark the component as unhealthy.
 After a successful poll, all data is exported with the same field names as the source Secret.
@@ -86,13 +86,13 @@ The following arguments are supported:
 | `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
 | `proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests.                                    |         | no       |
 
- At most, one of the following can be provided:
+At most, one of the following can be provided:
 
-* [`authorization`][authorization] block
-* [`basic_auth`][basic_auth] block
-* [`bearer_token_file`][client] argument
-* [`bearer_token`][client] argument
-* [`oauth2`][oauth2] block
+- [`authorization`][authorization] block
+- [`basic_auth`][basic_auth] block
+- [`bearer_token_file`][client] argument
+- [`bearer_token`][client] argument
+- [`oauth2`][oauth2] block
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
diff --git a/docs/sources/reference/components/remote/remote.s3.md b/docs/sources/reference/components/remote/remote.s3.md
index 844dcd0adc..4f332842d0 100644
--- a/docs/sources/reference/components/remote/remote.s3.md
+++ b/docs/sources/reference/components/remote/remote.s3.md
@@ -20,8 +20,8 @@ By default, [AWS environment variables](https://docs.aws.amazon.com/cli/latest/u
 The `key` and `secret` arguments inside `client` blocks can be used to provide custom authentication.
 
 {{< admonition type="note" >}}
-Other S3-compatible systems can be read  with `remote.s3` but may require specific authentication environment variables.
-There is no  guarantee that `remote.s3` will work with non-AWS S3 systems.
+Other S3-compatible systems can be read with `remote.s3` but may require specific authentication environment variables.
+There is no guarantee that `remote.s3` will work with non-AWS S3 systems.
 {{< /admonition >}}
 
 ## Usage
@@ -51,9 +51,9 @@ This doesn't support reading of directories.
 
 ## Blocks
 
- | Name               | Description                                       | Required |
- | ------------------ | ------------------------------------------------- | -------- |
- | [`client`][client] | Additional options for configuring the S3 client. | no       |
+| Name               | Description                                       | Required |
+| ------------------ | ------------------------------------------------- | -------- |
+| [`client`][client] | Additional options for configuring the S3 client. | no       |
 
 [client]: #client
 
diff --git a/docs/sources/reference/components/remote/remote.vault.md b/docs/sources/reference/components/remote/remote.vault.md
index cef7ecd979..7764834bad 100644
--- a/docs/sources/reference/components/remote/remote.vault.md
+++ b/docs/sources/reference/components/remote/remote.vault.md
@@ -267,20 +267,20 @@ Using `convert.nonsensitive` allows for using the exports of `remote.vault` for
 
 `remote.vault` exposes debug information for the authentication token and secret around:
 
-* The latest request ID used for retrieving or renewing the token.
-* The most recent time when the token was retrieved or renewed.
-* The expiration time for the token (if applicable).
-* Whether the token is renewable.
-* Warnings from Vault from when the token was retrieved.
+- The latest request ID used for retrieving or renewing the token.
+- The most recent time when the token was retrieved or renewed.
+- The expiration time for the token (if applicable).
+- Whether the token is renewable.
+- Warnings from Vault from when the token was retrieved.
 
 ## Debug metrics
 
 `remote.vault` exposes the following metrics:
 
-* `remote_vault_auth_total` (counter): Total number of times the component authenticated to Vault.
-* `remote_vault_secret_reads_total` (counter): Total number of times the secret was read from Vault.
-* `remote_vault_auth_lease_renewal_total` (counter): Total number of times the component renewed its authentication token lease.
-* `remote_vault_secret_lease_renewal_total` (counter): Total number of times the component renewed its secret token lease.
+- `remote_vault_auth_total` (counter): Total number of times the component authenticated to Vault.
+- `remote_vault_secret_reads_total` (counter): Total number of times the secret was read from Vault.
+- `remote_vault_auth_lease_renewal_total` (counter): Total number of times the component renewed its authentication token lease.
+- `remote_vault_secret_lease_renewal_total` (counter): Total number of times the component renewed its secret token lease.
 
 ## Example
 
diff --git a/docs/sources/reference/config-blocks/argument.md b/docs/sources/reference/config-blocks/argument.md
index 1c528c6c5a..ef67bc4a7a 100644
--- a/docs/sources/reference/config-blocks/argument.md
+++ b/docs/sources/reference/config-blocks/argument.md
@@ -27,11 +27,11 @@ For clarity, "argument" in this section refers to arguments which can be given t
 
 The following arguments are supported:
 
-Name       | Type     | Description                          | Default | Required
------------|----------|--------------------------------------|---------|---------
-`comment`  | `string` | Description for the argument.        | `false` | no
-`default`  | `any`    | Default value for the argument.      | `null`  | no
-`optional` | `bool`   | Whether the argument may be omitted. | `false` | no
+| Name       | Type     | Description                          | Default | Required |
+| ---------- | -------- | ------------------------------------ | ------- | -------- |
+| `comment`  | `string` | Description for the argument.        | `false` | no       |
+| `default`  | `any`    | Default value for the argument.      | `null`  | no       |
+| `optional` | `bool`   | Whether the argument may be omitted. | `false` | no       |
 
 By default, all module arguments are required.
 The `optional` argument can be used to mark the module argument as optional.
@@ -41,9 +41,9 @@ When `optional` is `true`, the initial value for the module argument is specifie
 
 The following fields are exported and can be referenced by other components:
 
-Name    | Type  | Description
---------|-------|-----------------------------------
-`value` | `any` | The current value of the argument.
+| Name    | Type  | Description                        |
+| ------- | ----- | ---------------------------------- |
+| `value` | `any` | The current value of the argument. |
 
 If you use a custom component, you are responsible for determining the values for arguments.
 Other expressions within a custom component may use `argument.ARGUMENT_NAME.value` to retrieve the value you provide.
diff --git a/docs/sources/reference/config-blocks/declare.md b/docs/sources/reference/config-blocks/declare.md
index 82c993d82e..2ebe6f8810 100644
--- a/docs/sources/reference/config-blocks/declare.md
+++ b/docs/sources/reference/config-blocks/declare.md
@@ -24,11 +24,11 @@ The `declare` block has no predefined schema for its arguments.
 The body of the `declare` block is used as the component definition.
 The body can contain the following:
 
-* [argument][] blocks
-* [export][] blocks
-* [declare][] blocks
-* [import][] blocks
-* Component definitions (either built-in or custom components)
+- [argument][] blocks
+- [export][] blocks
+- [declare][] blocks
+- [import][] blocks
+- Component definitions (either built-in or custom components)
 
 The `declare` block may not contain any configuration blocks that aren't listed above.
 
diff --git a/docs/sources/reference/config-blocks/export.md b/docs/sources/reference/config-blocks/export.md
index 423a992970..19dd121220 100644
--- a/docs/sources/reference/config-blocks/export.md
+++ b/docs/sources/reference/config-blocks/export.md
@@ -24,9 +24,9 @@ export "ARGUMENT_NAME" {
 
 The following arguments are supported:
 
-Name    | Type  | Description      | Default | Required
---------|-------|------------------|---------|---------
-`value` | `any` | Value to export. |         | yes
+| Name    | Type  | Description      | Default | Required |
+| ------- | ----- | ---------------- | ------- | -------- |
+| `value` | `any` | Value to export. |         | yes      |
 
 The `value` argument determines what the value of the export is.
 To expose an exported field of another component, set `value` to an expression that references that exported value.
diff --git a/docs/sources/reference/config-blocks/http.md b/docs/sources/reference/config-blocks/http.md
index f8ffb9acf8..8d1c3376d6 100644
--- a/docs/sources/reference/config-blocks/http.md
+++ b/docs/sources/reference/config-blocks/http.md
@@ -29,12 +29,12 @@ The `http` block supports no arguments and is configured completely through inne
 
 The following blocks are supported inside the definition of `http`:
 
-Hierarchy                                 | Block                          | Description                                                   | Required
-------------------------------------------|--------------------------------|---------------------------------------------------------------|---------
-tls                                       | [tls][]                        | Define TLS settings for the HTTP server.                      | no
-tls > windows_certificate_filter          | [windows_certificate_filter][] | Configure Windows certificate store for all certificates.     | no
-tls > windows_certificate_filter > client | [client][]                     | Configure client certificates for Windows certificate filter. | no
-tls > windows_certificate_filter > server | [server][]                     | Configure server certificates for Windows certificate filter. | no
+| Hierarchy                                 | Block                          | Description                                                   | Required |
+| ----------------------------------------- | ------------------------------ | ------------------------------------------------------------- | -------- |
+| tls                                       | [tls][]                        | Define TLS settings for the HTTP server.                      | no       |
+| tls > windows_certificate_filter          | [windows_certificate_filter][] | Configure Windows certificate store for all certificates.     | no       |
+| tls > windows_certificate_filter > client | [client][]                     | Configure client certificates for Windows certificate filter. | no       |
+| tls > windows_certificate_filter > server | [server][]                     | Configure server certificates for Windows certificate filter. | no       |
 
 ### tls block
 
@@ -47,27 +47,27 @@ Similarly, if you remove the `tls` block and reload the configuration when {{< p
 To ensure all connections use TLS, configure the `tls` block before you start {{< param "PRODUCT_NAME" >}}.
 {{< /admonition >}}
 
-Name                | Type           | Description                                                      | Default          | Required
---------------------|----------------|------------------------------------------------------------------|------------------|--------------
-`cert_pem`          | `string`       | PEM data of the server TLS certificate.                          | `""`             | conditionally
-`cert_file`         | `string`       | Path to the server TLS certificate on disk.                      | `""`             | conditionally
-`key_pem`           | `string`       | PEM data of the server TLS key.                                  | `""`             | conditionally
-`key_file`          | `string`       | Path to the server TLS key on disk.                              | `""`             | conditionally
-`client_ca_pem`     | `string`       | PEM data of the client CA to validate requests against.          | `""`             | no
-`client_ca_file`    | `string`       | Path to the client CA file on disk to validate requests against. | `""`             | no
-`client_auth_type`  | `string`       | Client authentication to use.                                    | `"NoClientCert"` | no
-`cipher_suites`     | `list(string)` | Set of cipher suites to use.                                     | `[]`             | no
-`curve_preferences` | `list(string)` | Set of elliptic curves to use in a handshake.                    | `[]`             | no
-`min_version`       | `string`       | Oldest TLS version to accept from clients.                       | `""`             | no
-`max_version`       | `string`       | Newest TLS version to accept from clients.                       | `""`             | no
+| Name                | Type           | Description                                                      | Default          | Required      |
+| ------------------- | -------------- | ---------------------------------------------------------------- | ---------------- | ------------- |
+| `cert_pem`          | `string`       | PEM data of the server TLS certificate.                          | `""`             | conditionally |
+| `cert_file`         | `string`       | Path to the server TLS certificate on disk.                      | `""`             | conditionally |
+| `key_pem`           | `string`       | PEM data of the server TLS key.                                  | `""`             | conditionally |
+| `key_file`          | `string`       | Path to the server TLS key on disk.                              | `""`             | conditionally |
+| `client_ca_pem`     | `string`       | PEM data of the client CA to validate requests against.          | `""`             | no            |
+| `client_ca_file`    | `string`       | Path to the client CA file on disk to validate requests against. | `""`             | no            |
+| `client_auth_type`  | `string`       | Client authentication to use.                                    | `"NoClientCert"` | no            |
+| `cipher_suites`     | `list(string)` | Set of cipher suites to use.                                     | `[]`             | no            |
+| `curve_preferences` | `list(string)` | Set of elliptic curves to use in a handshake.                    | `[]`             | no            |
+| `min_version`       | `string`       | Oldest TLS version to accept from clients.                       | `""`             | no            |
+| `max_version`       | `string`       | Newest TLS version to accept from clients.                       | `""`             | no            |
 
 When the `tls` block is specified, arguments for the TLS certificate (using `cert_pem` or `cert_file`) and for the TLS key (using `key_pem` or `key_file`) are required.
 
 The following pairs of arguments are mutually exclusive, and only one may be configured at a time:
 
-* `cert_pem` and `cert_file`
-* `key_pem` and `key_file`
-* `client_ca_pem` and `client_ca_file`
+- `cert_pem` and `cert_file`
+- `key_pem` and `key_file`
+- `client_ca_pem` and `client_ca_file`
 
 The `client_auth_type` argument determines whether to validate client certificates.
 The default value, `NoClientCert`, indicates that the client certificate isn't validated.
@@ -75,11 +75,11 @@ The `client_ca_pem` and `client_ca_file` arguments may only be configured when `
 
 The following values are accepted for `client_auth_type`:
 
-* `NoClientCert`: client certificates are neither requested nor validated.
-* `RequestClientCert`: requests clients to send an optional certificate. Certificates provided by clients aren't validated.
-* `RequireAnyClientCert`: requires at least one certificate from clients. Certificates provided by clients aren't validated.
-* `VerifyClientCertIfGiven`: requests clients to send an optional certificate. If a certificate is sent, it must be valid.
-* `RequireAndVerifyClientCert`: requires clients to send a valid certificate.
+- `NoClientCert`: client certificates are neither requested nor validated.
+- `RequestClientCert`: requests clients to send an optional certificate. Certificates provided by clients aren't validated.
+- `RequireAnyClientCert`: requires at least one certificate from clients. Certificates provided by clients aren't validated.
+- `VerifyClientCertIfGiven`: requests clients to send an optional certificate. If a certificate is sent, it must be valid.
+- `RequireAndVerifyClientCert`: requires clients to send a valid certificate.
 
 The `client_ca_pem` or `client_ca_file` arguments may be used to perform client certificate validation.
 These arguments may only be provided when `client_auth_type` isn't set to `NoClientCert`.
@@ -88,58 +88,58 @@ The `cipher_suites` argument determines what cipher suites to use.
 If you don't provide cipher suite, a default list is used.
 The set of cipher suites specified may be from the following:
 
-Cipher                                          | Allowed in BoringCrypto builds
-------------------------------------------------|-------------------------------
-`TLS_RSA_WITH_AES_128_CBC_SHA`                  | no
-`TLS_RSA_WITH_AES_256_CBC_SHA`                  | no
-`TLS_RSA_WITH_AES_128_GCM_SHA256`               | yes
-`TLS_RSA_WITH_AES_256_GCM_SHA384`               | yes
-`TLS_AES_128_GCM_SHA256`                        | no
-`TLS_AES_256_GCM_SHA384`                        | no
-`TLS_CHACHA20_POLY1305_SHA256`                  | no
-`TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA`          | no
-`TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`          | no
-`TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`            | no
-`TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`            | no
-`TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`       | yes
-`TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`       | yes
-`TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`         | yes
-`TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`         | yes
-`TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`   | no
-`TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256` | no
+| Cipher                                          | Allowed in BoringCrypto builds |
+| ----------------------------------------------- | ------------------------------ |
+| `TLS_RSA_WITH_AES_128_CBC_SHA`                  | no                             |
+| `TLS_RSA_WITH_AES_256_CBC_SHA`                  | no                             |
+| `TLS_RSA_WITH_AES_128_GCM_SHA256`               | yes                            |
+| `TLS_RSA_WITH_AES_256_GCM_SHA384`               | yes                            |
+| `TLS_AES_128_GCM_SHA256`                        | no                             |
+| `TLS_AES_256_GCM_SHA384`                        | no                             |
+| `TLS_CHACHA20_POLY1305_SHA256`                  | no                             |
+| `TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA`          | no                             |
+| `TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`          | no                             |
+| `TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`            | no                             |
+| `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`            | no                             |
+| `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`       | yes                            |
+| `TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`       | yes                            |
+| `TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`         | yes                            |
+| `TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`         | yes                            |
+| `TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`   | no                             |
+| `TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256` | no                             |
 
 The `curve_preferences` argument determines the set of elliptic curves to prefer during a handshake in preference order.
 If not provided, a default list is used.
 The set of elliptic curves specified may be from the following:
 
-Curve       | Allowed in BoringCrypto builds
-------------|-------------------------------
-`CurveP256` | yes
-`CurveP384` | yes
-`CurveP521` | yes
-`X25519`    | no
+| Curve       | Allowed in BoringCrypto builds |
+| ----------- | ------------------------------ |
+| `CurveP256` | yes                            |
+| `CurveP384` | yes                            |
+| `CurveP521` | yes                            |
+| `X25519`    | no                             |
 
 The `min_version` and `max_version` arguments determine the oldest and newest TLS version that's acceptable from clients.
 If you don't provide the min and max TLS version, a default value is used.
 
 The following versions are recognized:
 
-* `TLS13` for TLS 1.3
-* `TLS12` for TLS 1.2
-* `TLS11` for TLS 1.1
-* `TLS10` for TLS 1.0
+- `TLS13` for TLS 1.3
+- `TLS12` for TLS 1.2
+- `TLS11` for TLS 1.1
+- `TLS10` for TLS 1.0
 
 ### windows certificate filter block
 
 The `windows_certificate_filter` block is used to configure retrieving certificates from the built-in Windows certificate store.
 When you use the `windows_certificate_filter` block the following TLS settings are overridden and cause an error if defined.
 
-* `cert_pem`
-* `cert_file`
-* `key_pem`
-* `key_file`
-* `client_ca`
-* `client_ca_file`
+- `cert_pem`
+- `cert_file`
+- `key_pem`
+- `key_file`
+- `client_ca`
+- `client_ca_file`
 
 {{< admonition type="warning" >}}
 This feature is only available on Windows.
@@ -153,23 +153,23 @@ The `windows_certificate_filter` serves the certificate even if it isn't compati
 The `server` block is used to find the certificate to check the signer.
 If multiple certificates are found, the `windows_certificate_filter` chooses the certificate with the expiration farthest in the future.
 
-Name                  | Type           | Description                                                                                          | Default | Required
-----------------------|----------------|------------------------------------------------------------------------------------------------------|---------|---------
-`store`               | `string`       | Name of the system store to look for the server Certificate, for example, LocalMachine, CurrentUser. | `""`    | yes
-`system_store`        | `string`       | Name of the store to look for the server Certificate, for example, My, CA.                           | `""`    | yes
-`issuer_common_names` | `list(string)` | Issuer common names to check against.                                                                |         | no
-`template_id`         | `string`       | Server Template ID to match in ASN1 format, for example, "1.2.3".                                    | `""`    | no
-`refresh_interval`    | `string`       | How often to check for a new server certificate.                                                     | `"5m"`  | no
+| Name                  | Type           | Description                                                                                          | Default | Required |
+| --------------------- | -------------- | ---------------------------------------------------------------------------------------------------- | ------- | -------- |
+| `store`               | `string`       | Name of the system store to look for the server Certificate, for example, LocalMachine, CurrentUser. | `""`    | yes      |
+| `system_store`        | `string`       | Name of the store to look for the server Certificate, for example, My, CA.                           | `""`    | yes      |
+| `issuer_common_names` | `list(string)` | Issuer common names to check against.                                                                |         | no       |
+| `template_id`         | `string`       | Server Template ID to match in ASN1 format, for example, "1.2.3".                                    | `""`    | no       |
+| `refresh_interval`    | `string`       | How often to check for a new server certificate.                                                     | `"5m"`  | no       |
 
 ### client block
 
 The `client` block is used to check the certificate presented to the server.
 
-Name                  | Type           | Description                                                       | Default | Required
-----------------------|----------------|-------------------------------------------------------------------|---------|---------
-`issuer_common_names` | `list(string)` | Issuer common names to check against.                             |         | no
-`subject_regex`       | `string`       | Regular expression to match Subject name.                         | `""`    | no
-`template_id`         | `string`       | Client Template ID to match in ASN1 format, for example, "1.2.3". | `""`    | no
+| Name                  | Type           | Description                                                       | Default | Required |
+| --------------------- | -------------- | ----------------------------------------------------------------- | ------- | -------- |
+| `issuer_common_names` | `list(string)` | Issuer common names to check against.                             |         | no       |
+| `subject_regex`       | `string`       | Regular expression to match Subject name.                         | `""`    | no       |
+| `template_id`         | `string`       | Client Template ID to match in ASN1 format, for example, "1.2.3". | `""`    | no       |
 
 [tls]: #tls-block
 [windows_certificate_filter]: #windows-certificate-filter-block
diff --git a/docs/sources/reference/config-blocks/import.git.md b/docs/sources/reference/config-blocks/import.git.md
index 0145c1adbf..ae74a7593b 100644
--- a/docs/sources/reference/config-blocks/import.git.md
+++ b/docs/sources/reference/config-blocks/import.git.md
@@ -25,12 +25,12 @@ import.git "NAMESPACE" {
 
 The following arguments are supported:
 
-Name             | Type       | Description                                             | Default  | Required
------------------|------------|---------------------------------------------------------|----------|---------
-`repository`     | `string`   | The Git repository address to retrieve the module from. |          | yes
-`revision`       | `string`   | The Git revision to retrieve the module from.           | `"HEAD"` | no
-`path`           | `string`   | The path in the repository where the module is stored.  |          | yes
-`pull_frequency` | `duration` | The frequency to pull the repository for updates.       | `"60s"`  | no
+| Name             | Type       | Description                                             | Default  | Required |
+| ---------------- | ---------- | ------------------------------------------------------- | -------- | -------- |
+| `repository`     | `string`   | The Git repository address to retrieve the module from. |          | yes      |
+| `revision`       | `string`   | The Git revision to retrieve the module from.           | `"HEAD"` | no       |
+| `path`           | `string`   | The path in the repository where the module is stored.  |          | yes      |
+| `pull_frequency` | `duration` | The frequency to pull the repository for updates.       | `"60s"`  | no       |
 
 The `repository` attribute must be set to a repository address that would be recognized by Git with a `git clone REPOSITORY_ADDRESS` command, such as `https://github.com/grafana/alloy.git`.
 
@@ -53,10 +53,10 @@ Pulling hosted Git repositories too often can result in throttling.
 
 The following blocks are supported inside the definition of `import.git`:
 
-Hierarchy  | Block          | Description                                                | Required
------------|----------------|------------------------------------------------------------|---------
-basic_auth | [basic_auth][] | Configure basic_auth for authenticating to the repository. | no
-ssh_key    | [ssh_key][]    | Configure an SSH Key for authenticating to the repository. | no
+| Hierarchy  | Block          | Description                                                | Required |
+| ---------- | -------------- | ---------------------------------------------------------- | -------- |
+| basic_auth | [basic_auth][] | Configure basic_auth for authenticating to the repository. | no       |
+| ssh_key    | [ssh_key][]    | Configure an SSH Key for authenticating to the repository. | no       |
 
 ### basic_auth block
 
@@ -64,12 +64,12 @@ ssh_key    | [ssh_key][]    | Configure an SSH Key for authenticating to the rep
 
 ### ssh_key block
 
-Name         | Type     | Description                       | Default | Required
--------------|----------|-----------------------------------|---------|---------
-`username`   | `string` | SSH username.                     |         | yes
-`key`        | `secret` | SSH private key.                  |         | no
-`key_file`   | `string` | SSH private key path.             |         | no
-`passphrase` | `secret` | Passphrase for SSH key if needed. |         | no
+| Name         | Type     | Description                       | Default | Required |
+| ------------ | -------- | --------------------------------- | ------- | -------- |
+| `username`   | `string` | SSH username.                     |         | yes      |
+| `key`        | `secret` | SSH private key.                  |         | no       |
+| `key_file`   | `string` | SSH private key path.             |         | no       |
+| `passphrase` | `secret` | Passphrase for SSH key if needed. |         | no       |
 
 ## Examples
 
diff --git a/docs/sources/reference/config-blocks/import.http.md b/docs/sources/reference/config-blocks/import.http.md
index c03d2986f5..8f72b2cc25 100644
--- a/docs/sources/reference/config-blocks/import.http.md
+++ b/docs/sources/reference/config-blocks/import.http.md
@@ -20,26 +20,26 @@ import.http "LABEL" {
 
 The following arguments are supported:
 
-Name             | Type          | Description                             | Default | Required
------------------|---------------|-----------------------------------------|---------|---------
-`url`            | `string`      | URL to poll.                            |         | yes
-`method`         | `string`      | Define the HTTP method for the request. | `"GET"` | no
-`headers`        | `map(string)` | Custom headers for the request.         | `{}`    | no
-`poll_frequency` | `duration`    | Frequency to poll the URL.              | `"1m"`  | no
-`poll_timeout`   | `duration`    | Timeout when polling the URL.           | `"10s"` | no
+| Name             | Type          | Description                             | Default | Required |
+| ---------------- | ------------- | --------------------------------------- | ------- | -------- |
+| `url`            | `string`      | URL to poll.                            |         | yes      |
+| `method`         | `string`      | Define the HTTP method for the request. | `"GET"` | no       |
+| `headers`        | `map(string)` | Custom headers for the request.         | `{}`    | no       |
+| `poll_frequency` | `duration`    | Frequency to poll the URL.              | `"1m"`  | no       |
+| `poll_timeout`   | `duration`    | Timeout when polling the URL.           | `"10s"` | no       |
 
 ## Blocks
 
 The following blocks are supported inside the definition of `import.http`:
 
-Hierarchy                    | Block             | Description                                              | Required
------------------------------|-------------------|----------------------------------------------------------|---------
-client                       | [client][]        | HTTP client settings when connecting to the endpoint.    | no
-client > basic_auth          | [basic_auth][]    | Configure basic_auth for authenticating to the endpoint. | no
-client > authorization       | [authorization][] | Configure generic authorization to the endpoint.         | no
-client > oauth2              | [oauth2][]        | Configure OAuth2 for authenticating to the endpoint.     | no
-client > oauth2 > tls_config | [tls_config][]    | Configure TLS settings for connecting to the endpoint.   | no
-client > tls_config          | [tls_config][]    | Configure TLS settings for connecting to the endpoint.   | no
+| Hierarchy                    | Block             | Description                                              | Required |
+| ---------------------------- | ----------------- | -------------------------------------------------------- | -------- |
+| client                       | [client][]        | HTTP client settings when connecting to the endpoint.    | no       |
+| client > basic_auth          | [basic_auth][]    | Configure basic_auth for authenticating to the endpoint. | no       |
+| client > authorization       | [authorization][] | Configure generic authorization to the endpoint.         | no       |
+| client > oauth2              | [oauth2][]        | Configure OAuth2 for authenticating to the endpoint.     | no       |
+| client > oauth2 > tls_config | [tls_config][]    | Configure TLS settings for connecting to the endpoint.   | no       |
+| client > tls_config          | [tls_config][]    | Configure TLS settings for connecting to the endpoint.   | no       |
 
 The `>` symbol indicates deeper levels of nesting.
 For example, `client > basic_auth` refers to an `basic_auth` block defined inside a `client` block.
diff --git a/docs/sources/reference/config-blocks/import.string.md b/docs/sources/reference/config-blocks/import.string.md
index a7a79da798..e1ec09598d 100644
--- a/docs/sources/reference/config-blocks/import.string.md
+++ b/docs/sources/reference/config-blocks/import.string.md
@@ -21,9 +21,9 @@ import.string "NAMESPACE" {
 
 The following arguments are supported:
 
-Name      | Type                 | Description                                                 | Default | Required
-----------|----------------------|-------------------------------------------------------------|---------|---------
-`content` | `secret` or `string` | The contents of the module to import as a secret or string. |         | yes
+| Name      | Type                 | Description                                                 | Default | Required |
+| --------- | -------------------- | ----------------------------------------------------------- | ------- | -------- |
+| `content` | `secret` or `string` | The contents of the module to import as a secret or string. |         | yes      |
 
 `content` is a string that contains the configuration of the module to import.
 `content` is typically loaded by using the exports of another component. For example,
diff --git a/docs/sources/reference/config-blocks/livedebugging.md b/docs/sources/reference/config-blocks/livedebugging.md
index b1dee2763c..0ff986523a 100644
--- a/docs/sources/reference/config-blocks/livedebugging.md
+++ b/docs/sources/reference/config-blocks/livedebugging.md
@@ -20,6 +20,7 @@ The live debugging feature uses the {{< param "PRODUCT_NAME" >}} UI to provide d
 To ensure that your data remains secure while live debugging is enabled, configure TLS in the [http block][].
 
 [http block]: ../http/
+
 {{< /admonition >}}
 
 ## Example
diff --git a/docs/sources/reference/config-blocks/logging.md b/docs/sources/reference/config-blocks/logging.md
index 86dd35f06d..21f966febb 100644
--- a/docs/sources/reference/config-blocks/logging.md
+++ b/docs/sources/reference/config-blocks/logging.md
@@ -23,27 +23,27 @@ logging {
 
 The following arguments are supported:
 
-Name       | Type                 | Description                                | Default    | Required
------------|----------------------|--------------------------------------------|------------|---------
-`level`    | `string`             | Level at which log lines should be written | `"info"`   | no
-`format`   | `string`             | Format to use for writing log lines        | `"logfmt"` | no
-`write_to` | `list(LogsReceiver)` | List of receivers to send log entries to   |            | no
+| Name       | Type                 | Description                                | Default    | Required |
+| ---------- | -------------------- | ------------------------------------------ | ---------- | -------- |
+| `level`    | `string`             | Level at which log lines should be written | `"info"`   | no       |
+| `format`   | `string`             | Format to use for writing log lines        | `"logfmt"` | no       |
+| `write_to` | `list(LogsReceiver)` | List of receivers to send log entries to   |            | no       |
 
 ### Log level
 
 The following strings are recognized as valid log levels:
 
-* `"error"`: Only write logs at the _error_ level.
-* `"warn"`: Only write logs at the _warn_ level or above.
-* `"info"`: Only write logs at _info_ level or above.
-* `"debug"`: Write all logs, including _debug_ level logs.
+- `"error"`: Only write logs at the _error_ level.
+- `"warn"`: Only write logs at the _warn_ level or above.
+- `"info"`: Only write logs at _info_ level or above.
+- `"debug"`: Write all logs, including _debug_ level logs.
 
 ### Log format
 
 The following strings are recognized as valid log line formats:
 
-* `"logfmt"`: Write logs as [logfmt][] lines.
-* `"json"`: Write logs as JSON objects.
+- `"logfmt"`: Write logs as [logfmt][] lines.
+- `"json"`: Write logs as JSON objects.
 
 ### Log receivers
 
diff --git a/docs/sources/reference/config-blocks/remotecfg.md b/docs/sources/reference/config-blocks/remotecfg.md
index fba4534700..4bea75d1dc 100644
--- a/docs/sources/reference/config-blocks/remotecfg.md
+++ b/docs/sources/reference/config-blocks/remotecfg.md
@@ -36,21 +36,21 @@ remotecfg {
 
 The following arguments are supported:
 
-Name                     | Type                | Description                                                                                      | Default     | Required
--------------------------|---------------------|--------------------------------------------------------------------------------------------------|-------------|---------
-`url`                    | `string`            | The address of the API to poll for configuration.                                                | `""`        | no
-`id`                     | `string`            | A self-reported ID.                                                                              | `see below` | no
-`attributes`             | `map(string)`       | A set of self-reported attributes.                                                               | `{}`        | no
-`poll_frequency`         | `duration`          | How often to poll the API for new configuration.                                                 | `"1m"`      | no
-`name`                   | `string`            | A human-readable name for the collector.                                                         | `""`        | no
-`bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.                                             |             | no
-`bearer_token`           | `secret`            | Bearer token to authenticate with.                                                               |             | no
-`enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                                                         | `true`      | no
-`follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.                                     | `true`      | no
-`proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |             | no
-`no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. |             | no
-`proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false`     | no
-`proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests.                                    |             | no
+| Name                     | Type                | Description                                                                                      | Default     | Required |
+| ------------------------ | ------------------- | ------------------------------------------------------------------------------------------------ | ----------- | -------- |
+| `url`                    | `string`            | The address of the API to poll for configuration.                                                | `""`        | no       |
+| `id`                     | `string`            | A self-reported ID.                                                                              | `see below` | no       |
+| `attributes`             | `map(string)`       | A set of self-reported attributes.                                                               | `{}`        | no       |
+| `poll_frequency`         | `duration`          | How often to poll the API for new configuration.                                                 | `"1m"`      | no       |
+| `name`                   | `string`            | A human-readable name for the collector.                                                         | `""`        | no       |
+| `bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.                                             |             | no       |
+| `bearer_token`           | `secret`            | Bearer token to authenticate with.                                                               |             | no       |
+| `enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                                                         | `true`      | no       |
+| `follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.                                     | `true`      | no       |
+| `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |             | no       |
+| `no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. |             | no       |
+| `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false`     | no       |
+| `proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests.                                    |             | no       |
 
 If the `url` isn't set, then the service block is a no-op.
 
@@ -64,18 +64,18 @@ The `attribute` map keys can include any custom value except the reserved prefix
 The reserved label prefix is for automatic system attributes.
 You can't override this prefix.
 
-* `collector.os`: The operating system where {{< param "PRODUCT_NAME" >}} is running.
-* `collector.version`: The version of {{< param "PRODUCT_NAME" >}}.
+- `collector.os`: The operating system where {{< param "PRODUCT_NAME" >}} is running.
+- `collector.version`: The version of {{< param "PRODUCT_NAME" >}}.
 
 The `poll_frequency` must be set to at least `"10s"`.
 
 At most, one of the following can be provided:
 
-* [`bearer_token` argument][arguments].
-* [`bearer_token_file` argument][arguments].
-* [`basic_auth` block][basic_auth].
-* [`authorization` block][authorization].
-* [`oauth2` block][oauth2].
+- [`bearer_token` argument][arguments].
+- [`bearer_token_file` argument][arguments].
+- [`basic_auth` block][basic_auth].
+- [`authorization` block][authorization].
+- [`oauth2` block][oauth2].
 
 {{< docs/shared lookup="reference/components/http-client-proxy-config-description.md" source="alloy" version="<ALLOY_VERSION>" >}}
 
@@ -83,13 +83,13 @@ At most, one of the following can be provided:
 
 The following blocks are supported inside the definition of `remotecfg`:
 
-Hierarchy           | Block             | Description                                              | Required
---------------------|-------------------|----------------------------------------------------------|---------
-basic_auth          | [basic_auth][]    | Configure basic_auth for authenticating to the endpoint. | no
-authorization       | [authorization][] | Configure generic authorization to the endpoint.         | no
-oauth2              | [oauth2][]        | Configure OAuth2 for authenticating to the endpoint.     | no
-oauth2 > tls_config | [tls_config][]    | Configure TLS settings for connecting to the endpoint.   | no
-tls_config          | [tls_config][]    | Configure TLS settings for connecting to the endpoint.   | no
+| Hierarchy           | Block             | Description                                              | Required |
+| ------------------- | ----------------- | -------------------------------------------------------- | -------- |
+| basic_auth          | [basic_auth][]    | Configure basic_auth for authenticating to the endpoint. | no       |
+| authorization       | [authorization][] | Configure generic authorization to the endpoint.         | no       |
+| oauth2              | [oauth2][]        | Configure OAuth2 for authenticating to the endpoint.     | no       |
+| oauth2 > tls_config | [tls_config][]    | Configure TLS settings for connecting to the endpoint.   | no       |
+| tls_config          | [tls_config][]    | Configure TLS settings for connecting to the endpoint.   | no       |
 
 The `>` symbol indicates deeper levels of nesting.
 For example, `oauth2 > tls_config` refers to a `tls_config` block defined inside an `oauth2` block.
diff --git a/docs/sources/reference/config-blocks/tracing.md b/docs/sources/reference/config-blocks/tracing.md
index b81fe1afdd..65e2c245eb 100644
--- a/docs/sources/reference/config-blocks/tracing.md
+++ b/docs/sources/reference/config-blocks/tracing.md
@@ -35,10 +35,10 @@ otelcol.exporter.otlp "tempo" {
 
 The following arguments are supported:
 
-Name                | Type                     | Description                                         | Default | Required
---------------------|--------------------------|-----------------------------------------------------|---------|---------
-`sampling_fraction` | `number`                 | Fraction of traces to keep.                         | `0.1`   | no
-`write_to`          | `list(otelcol.Consumer)` | Inputs from `otelcol` components to send traces to. | `[]`    | no
+| Name                | Type                     | Description                                         | Default | Required |
+| ------------------- | ------------------------ | --------------------------------------------------- | ------- | -------- |
+| `sampling_fraction` | `number`                 | Fraction of traces to keep.                         | `0.1`   | no       |
+| `write_to`          | `list(otelcol.Consumer)` | Inputs from `otelcol` components to send traces to. | `[]`    | no       |
 
 The `write_to` argument controls which components to send traces to for processing.
 The elements in the array can be any `otelcol` component that accept traces, including processors and exporters.
@@ -55,10 +55,10 @@ When set to `1` or greater, 100% of traces are kept. When set to `0` or lower, 0
 
 The following blocks are supported inside the definition of `tracing`:
 
-Hierarchy               | Block             | Description                                                  | Required
-------------------------|-------------------|--------------------------------------------------------------|---------
-sampler                 | [sampler][]       | Define custom sampling on top of the base sampling fraction. | no
-sampler > jaeger_remote | [jaeger_remote][] | Retrieve sampling information via a Jaeger remote sampler.   | no
+| Hierarchy               | Block             | Description                                                  | Required |
+| ----------------------- | ----------------- | ------------------------------------------------------------ | -------- |
+| sampler                 | [sampler][]       | Define custom sampling on top of the base sampling fraction. | no       |
+| sampler > jaeger_remote | [jaeger_remote][] | Retrieve sampling information via a Jaeger remote sampler.   | no       |
 
 The `>` symbol indicates deeper levels of nesting. For example, `sampler > jaeger_remote` refers to a `jaeger_remote` block defined inside an `sampler` block.
 
@@ -73,11 +73,11 @@ It's invalid to define more than one sampler to use in the `sampler` block.
 
 The `jaeger_remote` block configures the retrieval of sampling information through a remote server that exposes Jaeger sampling strategies.
 
-Name               | Type       | Description                                                | Default                            | Required
--------------------|------------|------------------------------------------------------------|------------------------------------|---------
-`url`              | `string`   | URL to retrieve sampling strategies from.                  | `"http://127.0.0.1:5778/sampling"` | no
-`max_operations`   | `number`   | Limit number of operations which can have custom sampling. | `256`                              | no
-`refresh_interval` | `duration` | Frequency to poll the URL for new sampling strategies.     | `"1m"`                             | no
+| Name               | Type       | Description                                                | Default                            | Required |
+| ------------------ | ---------- | ---------------------------------------------------------- | ---------------------------------- | -------- |
+| `url`              | `string`   | URL to retrieve sampling strategies from.                  | `"http://127.0.0.1:5778/sampling"` | no       |
+| `max_operations`   | `number`   | Limit number of operations which can have custom sampling. | `256`                              | no       |
+| `refresh_interval` | `duration` | Frequency to poll the URL for new sampling strategies.     | `"1m"`                             | no       |
 
 The remote sampling strategies are retrieved from the URL specified by the `url` argument, and polled for updates on a timer. The frequency for how often polling occurs is controlled by the `refresh_interval` argument.
 
diff --git a/docs/sources/reference/stdlib/array.md b/docs/sources/reference/stdlib/array.md
index 69cb90bd61..477d2c6091 100644
--- a/docs/sources/reference/stdlib/array.md
+++ b/docs/sources/reference/stdlib/array.md
@@ -42,9 +42,9 @@ Elements within the list can be any type.
 The `array.combine_maps` function allows you to join two arrays of maps if certain keys have matching values in both maps. It's particularly useful when combining labels of targets coming from different `prometheus.discovery.*` or `prometheus.exporter.*` components.
 It takes three arguments:
 
-* The first two arguments are a of type `list(map(string))`. The keys of the map are strings.
+- The first two arguments are a of type `list(map(string))`. The keys of the map are strings.
   The value for each key could be of any Alloy type such as a `string`, `integer`, `map`, or a `capsule`.
-* The third input is an `array` containing strings. The strings are the keys whose value has to match for maps to be combined.
+- The third input is an `array` containing strings. The strings are the keys whose value has to match for maps to be combined.
 
 The maps that don't contain all the keys provided in the third argument will be discarded. When maps are combined and both contain the same keys, the last value from the second argument will be used.
 
diff --git a/docs/sources/reference/stdlib/constants.md b/docs/sources/reference/stdlib/constants.md
index 36cf5e2dfa..297689bccf 100644
--- a/docs/sources/reference/stdlib/constants.md
+++ b/docs/sources/reference/stdlib/constants.md
@@ -8,9 +8,9 @@ title: constants
 
 The `constants` object exposes a list of constant values about the system {{< param "PRODUCT_NAME" >}} is running on:
 
-* `constants.hostname`: The hostname of the machine {{< param "PRODUCT_NAME" >}} is running   on.
-* `constants.os`: The operating system {{< param "PRODUCT_NAME" >}} is running on.
-* `constants.arch`: The architecture of the system {{< param "PRODUCT_NAME" >}} is running on.
+- `constants.hostname`: The hostname of the machine {{< param "PRODUCT_NAME" >}} is running on.
+- `constants.os`: The operating system {{< param "PRODUCT_NAME" >}} is running on.
+- `constants.arch`: The architecture of the system {{< param "PRODUCT_NAME" >}} is running on.
 
 ## Examples
 
diff --git a/docs/sources/reference/stdlib/encoding.md b/docs/sources/reference/stdlib/encoding.md
index 9bc8fcaed5..f7906f4f89 100644
--- a/docs/sources/reference/stdlib/encoding.md
+++ b/docs/sources/reference/stdlib/encoding.md
@@ -68,7 +68,7 @@ The `encoding.from_yaml` function decodes a string representing YAML into an {{<
 A common use case of `encoding.from_yaml` is to decode the output of a [`local.file`][] component to an {{< param "PRODUCT_NAME" >}} value.
 
 {{< admonition type="note" >}}
- Remember to escape double quotes when passing YAML string literals to `encoding.from_yaml`.
+Remember to escape double quotes when passing YAML string literals to `encoding.from_yaml`.
 
 For example, the YAML value `key: "value"` is properly represented by the string `"key: \"value\""`.
 {{< /admonition >}}
diff --git a/docs/sources/reference/stdlib/string.md b/docs/sources/reference/stdlib/string.md
index 0d1671299c..f9da6a3254 100644
--- a/docs/sources/reference/stdlib/string.md
+++ b/docs/sources/reference/stdlib/string.md
@@ -58,7 +58,7 @@ An error is also produced for an unsupported format verb.
 The specification may contain the following verbs.
 
 | Verb | Result                                                                                    |
-|------|-------------------------------------------------------------------------------------------|
+| ---- | ----------------------------------------------------------------------------------------- |
 | `%%` | Literal percent sign, consuming no value.                                                 |
 | `%t` | Convert to boolean and produce `true` or `false`.                                         |
 | `%b` | Convert to integer number and produce binary representation.                              |
@@ -183,6 +183,7 @@ If the string doesn't start with the prefix, the string is returned unchanged.
 > string.trim_prefix("helloworld", "hello")
 "world"
 ```
+
 ## string.trim_suffix
 
 `string.trim_suffix` removes the suffix from the end of a string.
@@ -203,4 +204,4 @@ If the string doesn't start with the prefix, the string is returned unchanged.
 ```alloy
 > string.trim_space("  hello\n\n")
 "hello"
-```
\ No newline at end of file
+```
diff --git a/docs/sources/release-notes.md b/docs/sources/release-notes.md
index acb732a9da..0878177354 100644
--- a/docs/sources/release-notes.md
+++ b/docs/sources/release-notes.md
@@ -59,6 +59,7 @@ This feature is in [Public preview][] and is not covered by {{< param "FULL_PROD
 
 [Public preview]: https://grafana.com/docs/release-life-cycle/
 [backward compatibility]: ../introduction/backward-compatibility/
+
 {{< /admonition >}}
 
 The `remotecfg` block has an updated argument name from `metadata` to `attributes`.
@@ -72,8 +73,9 @@ This feature is in [Public preview][] and is not covered by {{< param "FULL_PROD
 
 [Public preview]: https://grafana.com/docs/release-life-cycle/
 [backward compatibility]: ../introduction/backward-compatibility/
+
 {{< /admonition >}}
 
 The `remotecfg` block has been updated to use [alloy-remote-config](https://github.com/grafana/alloy-remote-config)
 over [agent-remote-config](https://github.com/grafana/agent-remote-config). This change
-aligns `remotecfg` API terminology with Alloy and includes updated endpoints.
\ No newline at end of file
+aligns `remotecfg` API terminology with Alloy and includes updated endpoints.
diff --git a/docs/sources/set-up/deploy.md b/docs/sources/set-up/deploy.md
index 49987f10c4..18485efb02 100644
--- a/docs/sources/set-up/deploy.md
+++ b/docs/sources/set-up/deploy.md
@@ -35,21 +35,21 @@ You can also use a Kubernetes Deployment in cases where persistent storage isn't
 
 ### Pros
 
-* Straightforward scaling using [clustering][]
-* Minimizes the "noisy neighbor" effect
-* Easy to meta-monitor
+- Straightforward scaling using [clustering][]
+- Minimizes the "noisy neighbor" effect
+- Easy to meta-monitor
 
 ### Cons
 
-* Requires running on separate infrastructure
+- Requires running on separate infrastructure
 
 ### Use for
 
-* Scalable telemetry collection
+- Scalable telemetry collection
 
 ### Don't use for
 
-* Host-level metrics and logs
+- Host-level metrics and logs
 
 ## As a host daemon
 
@@ -68,24 +68,24 @@ The simplest use case of the host daemon topology is a Kubernetes DaemonSet, and
 
 ### Pros
 
-* Doesn't require running on separate infrastructure
-* Typically leads to smaller-sized collectors
-* Lower network latency to instrumented applications
+- Doesn't require running on separate infrastructure
+- Typically leads to smaller-sized collectors
+- Lower network latency to instrumented applications
 
 ### Cons
 
-* Requires planning a process for provisioning {{< param "PRODUCT_NAME" >}} on new machines, as well as keeping configuration up to date to avoid configuration drift
-* Not possible to scale independently when using Kubernetes DaemonSets
-* Scaling the topology can strain external APIs (like service discovery) and network infrastructure (like firewalls, proxy servers, and egress points)
+- Requires planning a process for provisioning {{< param "PRODUCT_NAME" >}} on new machines, as well as keeping configuration up to date to avoid configuration drift
+- Not possible to scale independently when using Kubernetes DaemonSets
+- Scaling the topology can strain external APIs (like service discovery) and network infrastructure (like firewalls, proxy servers, and egress points)
 
 ### Use for
 
-* Collecting machine-level Prometheus metrics and logs (for example, node_exporter hardware metrics, Kubernetes Pod logs)
+- Collecting machine-level Prometheus metrics and logs (for example, node_exporter hardware metrics, Kubernetes Pod logs)
 
 ### Don't use for
 
-* Scenarios where {{< param "PRODUCT_NAME" >}} grows so large it can become a noisy neighbor
-* Collecting an unpredictable amount of telemetry
+- Scenarios where {{< param "PRODUCT_NAME" >}} grows so large it can become a noisy neighbor
+- Collecting an unpredictable amount of telemetry
 
 ## As a container sidecar
 
@@ -100,25 +100,25 @@ The Pod's controller, network configuration, enabled capabilities, and available
 
 ### Pros
 
-* Doesn't require running on separate infrastructure
-* Straightforward networking with partner applications
+- Doesn't require running on separate infrastructure
+- Straightforward networking with partner applications
 
 ### Cons
 
-* Doesn't scale separately
-* Makes resource consumption harder to monitor and predict
-* Each {{< param "PRODUCT_NAME" >}} instance doesn't have a life cycle of its own, making it harder to do things like recovering from network outages
+- Doesn't scale separately
+- Makes resource consumption harder to monitor and predict
+- Each {{< param "PRODUCT_NAME" >}} instance doesn't have a life cycle of its own, making it harder to do things like recovering from network outages
 
 ### Use for
 
-* Serverless services
-* Job/batch applications that work with a push model
-* Air-gapped applications that can't be otherwise reached over the network
+- Serverless services
+- Job/batch applications that work with a push model
+- Air-gapped applications that can't be otherwise reached over the network
 
 ### Don't use for
 
-* Long-lived applications
-* Scenarios where the {{< param "PRODUCT_NAME" >}} deployment size grows so large it can become a noisy neighbor
+- Long-lived applications
+- Scenarios where the {{< param "PRODUCT_NAME" >}} deployment size grows so large it can become a noisy neighbor
 
 [clustering]: ../../configure/clustering/
 
@@ -133,8 +133,8 @@ This provides better stability due to the isolation between processes.
 For example, an overloaded {{< param "PRODUCT_NAME" >}} instance processing traces won't impact an {{< param "PRODUCT_NAME" >}} instance processing metrics.
 Different types of signal collection require different methods for scaling:
 
-* "Pull" components such as `prometheus.scrape` and `pyroscope.scrape` are scaled using hashmod sharing or clustering.
-* "Push" components such as `otelcol.receiver.otlp` are scaled by placing a load balancer in front of the components.
+- "Pull" components such as `prometheus.scrape` and `pyroscope.scrape` are scaled using hashmod sharing or clustering.
+- "Push" components such as `otelcol.receiver.otlp` are scaled by placing a load balancer in front of the components.
 
 ### Traces
 
@@ -146,9 +146,10 @@ This similarity is because most {{< param "PRODUCT_NAME" >}} components used for
 #### When to scale
 
 To decide whether scaling is necessary, check metrics such as:
-* `otelcol_receiver_refused_spans_total` from receivers such as `otelcol.receiver.otlp`.
-* `otelcol_receiver_refused_spans_total` from processors such as `otelcol.processor.batch`.
-* `otelcol_exporter_send_failed_spans_total` from exporters such as `otelcol.exporter.otlp` and `otelcol.exporter.loadbalancing`.
+
+- `otelcol_receiver_refused_spans_total` from receivers such as `otelcol.receiver.otlp`.
+- `otelcol_receiver_refused_spans_total` from processors such as `otelcol.processor.batch`.
+- `otelcol_exporter_send_failed_spans_total` from exporters such as `otelcol.exporter.otlp` and `otelcol.exporter.loadbalancing`.
 
 #### Stateful and stateless components
 
@@ -160,9 +161,9 @@ You can forward spans with `otelcol.exporter.loadbalancing`.
 
 Examples of stateful components:
 
-* `otelcol.processor.tail_sampling`
-* `otelcol.connector.spanmetrics`
-* `otelcol.connector.servicegraph`
+- `otelcol.processor.tail_sampling`
+- `otelcol.connector.spanmetrics`
+- `otelcol.connector.servicegraph`
 
 <!-- TODO: link to the otelcol.exporter.loadbalancing docs for more info -->
 
@@ -173,7 +174,8 @@ A stateless {{< param "PRODUCT_NAME" >}} instance can be scaled without using `o
 For example, you could use an off-the-shelf load balancer to do a round-robin load balancing.
 
 Examples of stateless components:
-* `otelcol.processor.probabilistic_sampler`
-* `otelcol.processor.transform`
-* `otelcol.processor.attributes`
-* `otelcol.processor.span`
+
+- `otelcol.processor.probabilistic_sampler`
+- `otelcol.processor.transform`
+- `otelcol.processor.attributes`
+- `otelcol.processor.span`
diff --git a/docs/sources/set-up/install/ansible.md b/docs/sources/set-up/install/ansible.md
index cea08df291..fea6076966 100644
--- a/docs/sources/set-up/install/ansible.md
+++ b/docs/sources/set-up/install/ansible.md
@@ -23,32 +23,33 @@ To add {{% param "PRODUCT_NAME" %}} to a host:
 
 1. Create a file named `alloy.yml` and add the following:
 
-    ```yaml
-    - name: Install Alloy
-      hosts: all
-      become: true
-
-      tasks:
-        - name: Install Alloy
-          ansible.builtin.include_role:
-            name: grafana.grafana.alloy
-          vars:
-            alloy_config: |
-              prometheus.scrape "default" {
-                targets = [{"__address__" = "localhost:12345"}]
-                forward_to = [prometheus.remote_write.prom.receiver]
-              }
-              prometheus.remote_write "prom" {
-                endpoint {
-                    url = "<YOUR_PROMETHEUS_PUSH_ENDPOINT>"
-                }
-              }
-    ```
-
-    This snippet has a sample configuration to collect and send {{% param "PRODUCT_NAME" %}} metrics to Prometheus
-
-    Replace the following:
-    - _`<YOUR_PROMETHEUS_PUSH_ENDPOINT>`_:  The Remote write endpoint of your Prometheus Instance.
+   ```yaml
+   - name: Install Alloy
+     hosts: all
+     become: true
+
+     tasks:
+       - name: Install Alloy
+         ansible.builtin.include_role:
+           name: grafana.grafana.alloy
+         vars:
+           alloy_config: |
+             prometheus.scrape "default" {
+               targets = [{"__address__" = "localhost:12345"}]
+               forward_to = [prometheus.remote_write.prom.receiver]
+             }
+             prometheus.remote_write "prom" {
+               endpoint {
+                   url = "<YOUR_PROMETHEUS_PUSH_ENDPOINT>"
+               }
+             }
+   ```
+
+   This snippet has a sample configuration to collect and send {{% param "PRODUCT_NAME" %}} metrics to Prometheus
+
+   Replace the following:
+
+   - _`<YOUR_PROMETHEUS_PUSH_ENDPOINT>`_: The Remote write endpoint of your Prometheus Instance.
 
 1. Run the Ansible playbook. Open a terminal window and run the following command from the Ansible playbook directory.
 
diff --git a/docs/sources/set-up/install/binary.md b/docs/sources/set-up/install/binary.md
index e6e479a53b..48936215a3 100644
--- a/docs/sources/set-up/install/binary.md
+++ b/docs/sources/set-up/install/binary.md
@@ -12,10 +12,10 @@ weight: 600
 
 {{< param "PRODUCT_NAME" >}} is distributed as a standalone binary for the following operating systems and architectures:
 
-* Linux: AMD64, ARM64
-* Windows: AMD64
-* macOS: AMD64 on Intel, ARM64 on Apple Silicon
-* FreeBSD: AMD64
+- Linux: AMD64, ARM64
+- Windows: AMD64
+- macOS: AMD64 on Intel, ARM64 on Apple Silicon
+- FreeBSD: AMD64
 
 ## Download {{% param "PRODUCT_NAME" %}}
 
@@ -37,7 +37,7 @@ To download {{< param "PRODUCT_NAME" >}} as a standalone binary, perform the fol
 
    Replace the following:
 
-   * _`<BINARY_PATH>`_: The path to the extracted binary.
+   - _`<BINARY_PATH>`_: The path to the extracted binary.
 
 ### BoringCrypto binaries
 
@@ -50,7 +50,7 @@ To retrieve them, follow the steps above but search for the `alloy-boringcrypto`
 
 ## Next steps
 
-* [Run {{< param "PRODUCT_NAME" >}}][Run]
+- [Run {{< param "PRODUCT_NAME" >}}][Run]
 
 [release]: https://github.com/grafana/alloy/releases
 [Run]: ../../run/binary/
diff --git a/docs/sources/set-up/install/chef.md b/docs/sources/set-up/install/chef.md
index 43b361a3d5..74026a3953 100644
--- a/docs/sources/set-up/install/chef.md
+++ b/docs/sources/set-up/install/chef.md
@@ -28,59 +28,59 @@ To add {{< param "PRODUCT_NAME" >}} to a host:
 
 1. Add the following resources to your [Chef][] recipe to add the Grafana package repositories to your system:
 
-    ```ruby
-    if platform_family?('debian', 'rhel', 'amazon', 'fedora')
-      if platform_family?('debian')
-        remote_file '/etc/apt/keyrings/grafana.gpg' do
-          source 'https://apt.grafana.com/gpg.key'
-          mode '0644'
-          action :create
-          end
-
-        file '/etc/apt/sources.list.d/grafana.list' do
-          content "deb [signed-by=/etc/apt/keyrings/grafana.gpg] https://apt.grafana.com/ stable main"
-          mode '0644'
-          notifies :update, 'apt_update[update apt cache]', :immediately
-        end
-
-        apt_update 'update apt cache' do
-          action :nothing
-        end
-      elsif platform_family?('rhel', 'amazon', 'fedora')
-        yum_repository 'grafana' do
-          description 'grafana'
-          baseurl 'https://rpm.grafana.com/oss/rpm'
-          gpgcheck true
-          gpgkey 'https://rpm.grafana.com/gpg.key'
-          enabled true
-          action :create
-          notifies :run, 'execute[add-rhel-key]', :immediately
-        end
-
-        execute 'add-rhel-key' do
-          command "rpm --import https://rpm.grafana.com/gpg.key"
-          action :nothing
-        end
-      end
-    else
-        fail "The #{node['platform_family']} platform is not supported."
-    end
-    ```
+   ```ruby
+   if platform_family?('debian', 'rhel', 'amazon', 'fedora')
+     if platform_family?('debian')
+       remote_file '/etc/apt/keyrings/grafana.gpg' do
+         source 'https://apt.grafana.com/gpg.key'
+         mode '0644'
+         action :create
+         end
+
+       file '/etc/apt/sources.list.d/grafana.list' do
+         content "deb [signed-by=/etc/apt/keyrings/grafana.gpg] https://apt.grafana.com/ stable main"
+         mode '0644'
+         notifies :update, 'apt_update[update apt cache]', :immediately
+       end
+
+       apt_update 'update apt cache' do
+         action :nothing
+       end
+     elsif platform_family?('rhel', 'amazon', 'fedora')
+       yum_repository 'grafana' do
+         description 'grafana'
+         baseurl 'https://rpm.grafana.com/oss/rpm'
+         gpgcheck true
+         gpgkey 'https://rpm.grafana.com/gpg.key'
+         enabled true
+         action :create
+         notifies :run, 'execute[add-rhel-key]', :immediately
+       end
+
+       execute 'add-rhel-key' do
+         command "rpm --import https://rpm.grafana.com/gpg.key"
+         action :nothing
+       end
+     end
+   else
+       fail "The #{node['platform_family']} platform is not supported."
+   end
+   ```
 
 1. Add the following resources to install and enable the `alloy` service:
 
-    ```ruby
-    package 'alloy' do
-      action :install
-      flush_cache [ :before ] if platform_family?('amazon', 'rhel', 'fedora')
-      notifies :restart, 'service[alloy]', :delayed
-    end
-
-    service 'alloy' do
-      service_name 'alloy'
-      action [:enable, :start]
-    end
-    ```
+   ```ruby
+   package 'alloy' do
+     action :install
+     flush_cache [ :before ] if platform_family?('amazon', 'rhel', 'fedora')
+     notifies :restart, 'service[alloy]', :delayed
+   end
+
+   service 'alloy' do
+     service_name 'alloy'
+     action [:enable, :start]
+   end
+   ```
 
 ## Configuration
 
diff --git a/docs/sources/set-up/install/docker.md b/docs/sources/set-up/install/docker.md
index d29f5f582d..3ea6398518 100644
--- a/docs/sources/set-up/install/docker.md
+++ b/docs/sources/set-up/install/docker.md
@@ -12,13 +12,13 @@ weight: 100
 
 {{< param "PRODUCT_NAME" >}} is available as a Docker container image on the following platforms:
 
-* [Linux containers][] for AMD64 and ARM64.
-* [Windows containers][] for AMD64.
+- [Linux containers][] for AMD64 and ARM64.
+- [Windows containers][] for AMD64.
 
 ## Before you begin
 
-* Install [Docker][] on your computer.
-* Create and save an {{< param "PRODUCT_NAME" >}} configuration file on your computer, for example:
+- Install [Docker][] on your computer.
+- Create and save an {{< param "PRODUCT_NAME" >}} configuration file on your computer, for example:
 
   ```alloy
   logging {
@@ -42,7 +42,7 @@ docker run \
 
 Replace the following:
 
-* _`<CONFIG_FILE_PATH>`_: The path of the configuration file on your host system.
+- _`<CONFIG_FILE_PATH>`_: The path of the configuration file on your host system.
 
 You can modify the last line to change the arguments passed to the {{< param "PRODUCT_NAME" >}} binary.
 Refer to the documentation for [run][] for more information about the options available to the `run` command.
@@ -52,6 +52,7 @@ Make sure you pass `--server.http.listen-addr=0.0.0.0:12345` as an argument as s
 If you don't pass this argument, the [debugging UI][UI] won't be available outside of the Docker container.
 
 [UI]: ../../../troubleshoot/debug/#alloy-ui
+
 {{< /admonition >}}
 
 ### BoringCrypto images
@@ -62,8 +63,8 @@ BoringCrypto support is in _Public preview_ and is only available on AMD64 and A
 
 BoringCrypto images are published with every release starting with version 1.1:
 
-* The current BoringCrypto image is published as `grafana/alloy:boringcrypto`.
-* A specific version of the BoringCrypto image is published as
+- The current BoringCrypto image is published as `grafana/alloy:boringcrypto`.
+- A specific version of the BoringCrypto image is published as
   `grafana/alloy:<VERSION>-boringcrypto`, such as
   `grafana/alloy:v1.1.0-boringcrypto`.
 
@@ -82,7 +83,7 @@ docker run \
 
 Replace the following:
 
-* _`<CONFIG_FILE_PATH>`_: The path of the configuration file on your host system.
+- _`<CONFIG_FILE_PATH>`_: The path of the configuration file on your host system.
 
 You can modify the last line to change the arguments passed to the {{< param "PRODUCT_NAME" >}} binary.
 Refer to the documentation for [run][] for more information about the options available to the `run` command.
@@ -92,6 +93,7 @@ Make sure you pass `--server.http.listen-addr=0.0.0.0:12345` as an argument as s
 If you don't pass this argument, the [debugging UI][debug] won't be available outside of the Docker container.
 
 [debug]: ../../../troubleshoot/debug/#alloy-ui
+
 {{< /admonition >}}
 
 ## Verify
diff --git a/docs/sources/set-up/install/kubernetes.md b/docs/sources/set-up/install/kubernetes.md
index f0886f45fe..bf7c01de09 100644
--- a/docs/sources/set-up/install/kubernetes.md
+++ b/docs/sources/set-up/install/kubernetes.md
@@ -14,9 +14,9 @@ weight: 200
 
 ## Before you begin
 
-* Install [Helm][] on your computer.
-* Configure a Kubernetes cluster that you can use for {{< param "PRODUCT_NAME" >}}.
-* Configure your local Kubernetes context to point at the cluster.
+- Install [Helm][] on your computer.
+- Configure a Kubernetes cluster that you can use for {{< param "PRODUCT_NAME" >}}.
+- Configure your local Kubernetes context to point at the cluster.
 
 ## Deploy
 
@@ -42,7 +42,7 @@ To deploy {{< param "PRODUCT_NAME" >}} on Kubernetes using Helm, run the followi
 
    Replace the following:
 
-   * _`<NAMESPACE>`_: The namespace to use for your {{< param "PRODUCT_NAME" >}} installation, such as `alloy`.
+   - _`<NAMESPACE>`_: The namespace to use for your {{< param "PRODUCT_NAME" >}} installation, such as `alloy`.
 
 1. Install {{< param "PRODUCT_NAME" >}}:
 
@@ -52,8 +52,8 @@ To deploy {{< param "PRODUCT_NAME" >}} on Kubernetes using Helm, run the followi
 
    Replace the following:
 
-   * _`<NAMESPACE>`_: The namespace created in the previous step.
-   * _`<RELEASE_NAME>`_: The name to use for your {{< param "PRODUCT_NAME" >}} installation, such as `alloy`.
+   - _`<NAMESPACE>`_: The namespace created in the previous step.
+   - _`<RELEASE_NAME>`_: The name to use for your {{< param "PRODUCT_NAME" >}} installation, such as `alloy`.
 
 1. Verify that the {{< param "PRODUCT_NAME" >}} pods are running:
 
@@ -63,13 +63,13 @@ To deploy {{< param "PRODUCT_NAME" >}} on Kubernetes using Helm, run the followi
 
    Replace the following:
 
-   * _`<NAMESPACE>`_: The namespace used in the previous step.
+   - _`<NAMESPACE>`_: The namespace used in the previous step.
 
 You have successfully deployed {{< param "PRODUCT_NAME" >}} on Kubernetes, using default Helm settings.
 
 ## Next steps
 
-* [Configure {{< param "PRODUCT_NAME" >}}][Configure]
+- [Configure {{< param "PRODUCT_NAME" >}}][Configure]
 
 <!-- Refer to the [{{< param "PRODUCT_NAME" >}} Helm chart documentation on Artifact Hub](https://artifacthub.io/packages/helm/grafana/alloy) for more information about the Helm chart. -->
 
diff --git a/docs/sources/set-up/install/macos.md b/docs/sources/set-up/install/macos.md
index 437a12137e..db34e9a713 100644
--- a/docs/sources/set-up/install/macos.md
+++ b/docs/sources/set-up/install/macos.md
@@ -21,7 +21,7 @@ To verify the default prefix for Homebrew on your computer, open a terminal wind
 
 ## Before you begin
 
-* Install [Homebrew][] on your computer.
+- Install [Homebrew][] on your computer.
 
 ## Install
 
@@ -65,8 +65,8 @@ brew uninstall grafana/grafana/alloy
 
 ## Next steps
 
-* [Run {{< param "PRODUCT_NAME" >}}][Run]
-* [Configure {{< param "PRODUCT_NAME" >}}][Configure]
+- [Run {{< param "PRODUCT_NAME" >}}][Run]
+- [Configure {{< param "PRODUCT_NAME" >}}][Configure]
 
 [Homebrew]: https://brew.sh
 [Run]: ../../run/macos/
diff --git a/docs/sources/set-up/install/openshift.md b/docs/sources/set-up/install/openshift.md
index 7bb8b1f290..b67776f0a3 100644
--- a/docs/sources/set-up/install/openshift.md
+++ b/docs/sources/set-up/install/openshift.md
@@ -12,8 +12,8 @@ You can deploy {{< param "PRODUCT_NAME" >}} on the Red Hat OpenShift Container P
 
 ## Before you begin
 
-* These steps assume you have a working OCP environment.
-* You can adapt the suggested policies and configuration to meet your specific needs and security policies.
+- These steps assume you have a working OCP environment.
+- You can adapt the suggested policies and configuration to meet your specific needs and security policies.
 
 ## Configure RBAC
 
@@ -44,14 +44,14 @@ Not all of these SCCs are required for each use case.
 You can adapt the SCCs to meet your local requirements and needs.
 {{< /admonition >}}
 
-* `RunAsUser`: Specifies the user ID under which {{< param "PRODUCT_NAME" >}} runs.
+- `RunAsUser`: Specifies the user ID under which {{< param "PRODUCT_NAME" >}} runs.
   You must configure this constraint to allow a non-root user ID.
-* `SELinuxContext`: Configures the SELinux context for containers.
+- `SELinuxContext`: Configures the SELinux context for containers.
   If you run {{< param "PRODUCT_NAME" >}} as root, you must configure this constraint to make sure that SELinux policies don't block {{< param "PRODUCT_NAME" >}}.
   This SCC is generally not required to deploy {{< param "PRODUCT_NAME" >}} as a non-root user.
-* `FSGroup`: Specifies the fsGroup IDs for file system access.
+- `FSGroup`: Specifies the fsGroup IDs for file system access.
   You must configure this constraint to give {{< param "PRODUCT_NAME" >}} group access to the files it needs.
-* `Volumes`: Specifies the persistent volumes used for storage.
+- `Volumes`: Specifies the persistent volumes used for storage.
   You must configure this constraint to give {{< param "PRODUCT_NAME" >}} access to the volumes it needs.
 
 ## Example DaemonSet configuration
@@ -92,7 +92,7 @@ spec:
 
 Replace the following:
 
-* _`<ALLOY_VERSION>`_: Set to the specific {{< param "PRODUCT_NAME" >}} version you are deploying. For example, `1.5.1`.
+- _`<ALLOY_VERSION>`_: Set to the specific {{< param "PRODUCT_NAME" >}} version you are deploying. For example, `1.5.1`.
 
 {{< admonition type="note" >}}
 This example uses the simplest volume type, `emptyDir`. In this example configuration, if your node restarts, your data will be lost. Make sure you set the volume type to a persistent storage location for production environments. Refer to [Using volumes to persist container data](https://docs.openshift.com/container-platform/latest/nodes/containers/nodes-containers-volumes.html) in the OpenShift documentation for more information.
@@ -113,7 +113,7 @@ runAsUser:
 fsGroup:
   type: MustRunAs
   uid: 1000
-volumes: 
+volumes:
 - '*'
 users:
 - my-admin-user
@@ -129,10 +129,10 @@ seLinuxContext:
 
 Replace the following:
 
-* _`<SYSTEM_USER>`_: The user for your SELinux context.
-* _`<SYSTEM_ROLE>`_: The role for your SELinux context.
-* _`<CONTAINER_TYPE>`_: The container type for your SELinux context.
-* _`<LEVEL>`_: The level  for your SELinux context.
+- _`<SYSTEM_USER>`_: The user for your SELinux context.
+- _`<SYSTEM_ROLE>`_: The role for your SELinux context.
+- _`<CONTAINER_TYPE>`_: The container type for your SELinux context.
+- _`<LEVEL>`_: The level for your SELinux context.
 
 Refer to [SELinux Contexts][selinux] in the RedHat documentation for more information on the SELinux context configuration.
 
@@ -145,7 +145,7 @@ volumes:
   - downwardAPI
   - emptyDir
   - persistentVolumeClaim
-  - secret 
+  - secret
 ```
 
 {{< /admonition >}}
@@ -154,7 +154,7 @@ Refer to [Deploy {{< param "FULL_PRODUCT_NAME" >}}][deploy] for more information
 
 ## Next steps
 
-* [Configure {{< param "PRODUCT_NAME" >}}][Configure]
+- [Configure {{< param "PRODUCT_NAME" >}}][Configure]
 
 [rbac.yaml]: https://github.com/grafana/alloy/blob/main/operations/helm/charts/alloy/templates/rbac.yaml
 [rbac]: https://docs.openshift.com/container-platform/latest/authentication/using-rbac.html
diff --git a/docs/sources/set-up/install/puppet.md b/docs/sources/set-up/install/puppet.md
index afb09cb899..3670ef3fc0 100644
--- a/docs/sources/set-up/install/puppet.md
+++ b/docs/sources/set-up/install/puppet.md
@@ -26,70 +26,70 @@ To add {{< param "PRODUCT_NAME" >}} to a host:
 
 1. Make sure that the following module dependencies are declared and installed:
 
-    ```json
-    {
-    "name": "puppetlabs/apt",
-    "version_requirement": ">= 4.1.0 <= 7.0.0"
-    },
-    {
-    "name": "puppetlabs/yumrepo_core",
-    "version_requirement": "<= 2.0.0"
-    }
-    ```
+   ```json
+   {
+   "name": "puppetlabs/apt",
+   "version_requirement": ">= 4.1.0 <= 7.0.0"
+   },
+   {
+   "name": "puppetlabs/yumrepo_core",
+   "version_requirement": "<= 2.0.0"
+   }
+   ```
 
 1. Create a [Puppet][] manifest with the following class to add the Grafana package repositories, install the `alloy` package, and run the service:
 
-    ```ruby
-    class grafana_alloy::grafana_alloy () {
-      case $::os['family'] {
-        'debian': {
-          apt::source { 'grafana':
-            location => 'https://apt.grafana.com/',
-            release  => '',
-            repos    => 'stable main',
-            key      => {
-              id     => 'B53AE77BADB630A683046005963FA27710458545',
-              source => 'https://apt.grafana.com/gpg.key',
-            },
-          } -> package { 'alloy':
-            require => Exec['apt_update'],
-          } -> service { 'alloy':
-            ensure    => running,
-            name      => 'alloy',
-            enable    => true,
-            subscribe => Package['alloy'],
-          }
-        }
-        'redhat': {
-          yumrepo { 'grafana':
-            ensure   => 'present',
-            name     => 'grafana',
-            descr    => 'grafana',
-            baseurl  => 'https://packages.grafana.com/oss/rpm',
-            gpgkey   => 'https://packages.grafana.com/gpg.key',
-            enabled  => '1',
-            gpgcheck => '1',
-            target   => '/etc/yum.repo.d/grafana.repo',
-          } -> package { 'alloy':
-          } -> service { 'alloy':
-            ensure    => running,
-            name      => 'alloy',
-            enable    => true,
-            subscribe => Package['alloy'],
-          }
-        }
-        default: {
-          fail("Unsupported OS family: (${$::os['family']})")
-        }
-      }
-    }
-    ```
+   ```ruby
+   class grafana_alloy::grafana_alloy () {
+     case $::os['family'] {
+       'debian': {
+         apt::source { 'grafana':
+           location => 'https://apt.grafana.com/',
+           release  => '',
+           repos    => 'stable main',
+           key      => {
+             id     => 'B53AE77BADB630A683046005963FA27710458545',
+             source => 'https://apt.grafana.com/gpg.key',
+           },
+         } -> package { 'alloy':
+           require => Exec['apt_update'],
+         } -> service { 'alloy':
+           ensure    => running,
+           name      => 'alloy',
+           enable    => true,
+           subscribe => Package['alloy'],
+         }
+       }
+       'redhat': {
+         yumrepo { 'grafana':
+           ensure   => 'present',
+           name     => 'grafana',
+           descr    => 'grafana',
+           baseurl  => 'https://packages.grafana.com/oss/rpm',
+           gpgkey   => 'https://packages.grafana.com/gpg.key',
+           enabled  => '1',
+           gpgcheck => '1',
+           target   => '/etc/yum.repo.d/grafana.repo',
+         } -> package { 'alloy':
+         } -> service { 'alloy':
+           ensure    => running,
+           name      => 'alloy',
+           enable    => true,
+           subscribe => Package['alloy'],
+         }
+       }
+       default: {
+         fail("Unsupported OS family: (${$::os['family']})")
+       }
+     }
+   }
+   ```
 
 1. To use this class in a module, add the following line to the module's `init.pp` file:
 
-    ```ruby
-    include grafana_alloy::grafana_alloy
-    ```
+   ```ruby
+   include grafana_alloy::grafana_alloy
+   ```
 
 ## Configuration
 
@@ -100,7 +100,7 @@ You can replace this file with your own configuration, or create a configuration
 
 ## Next steps
 
-* [Configure {{< param "PRODUCT_NAME" >}}][Configure]
+- [Configure {{< param "PRODUCT_NAME" >}}][Configure]
 
 [Puppet]: https://www.puppet.com/
 [Configure]: ../../../configure/linux/
diff --git a/docs/sources/set-up/install/windows.md b/docs/sources/set-up/install/windows.md
index 154922816c..e1367f5973 100644
--- a/docs/sources/set-up/install/windows.md
+++ b/docs/sources/set-up/install/windows.md
@@ -52,17 +52,17 @@ To do a silent install of {{< param "PRODUCT_NAME" >}} on Windows, perform the f
 
 ### Silent install options
 
-* `/CONFIG=<path>` Path to the configuration file. Default: `$INSTDIR\config.alloy`
-* `/DISABLEREPORTING=<yes|no>` Disable [data collection][]. Default: `no`
-* `/DISABLEPROFILING=<yes|no>` Disable profiling endpoint. Default: `no`
-* `/ENVIRONMENT="KEY=VALUE\0KEY2=VALUE2"` Define environment variables for Windows Service. Default: ``
+- `/CONFIG=<path>` Path to the configuration file. Default: `$INSTDIR\config.alloy`
+- `/DISABLEREPORTING=<yes|no>` Disable [data collection][]. Default: `no`
+- `/DISABLEPROFILING=<yes|no>` Disable profiling endpoint. Default: `no`
+- `/ENVIRONMENT="KEY=VALUE\0KEY2=VALUE2"` Define environment variables for Windows Service. Default: ``
 
 ## Service Configuration
 
 {{< param "PRODUCT_NAME" >}} uses the Windows Registry `HKLM\Software\GrafanaLabs\Alloy` for service configuration.
 
-* `Arguments` (Type `REG_MULTI_SZ`) Each value represents a binary argument for alloy binary.
-* `Environment` (Type `REG_MULTI_SZ`) Each value represents a environment value `KEY=VALUE` for alloy binary.
+- `Arguments` (Type `REG_MULTI_SZ`) Each value represents a binary argument for alloy binary.
+- `Environment` (Type `REG_MULTI_SZ`) Each value represents a environment value `KEY=VALUE` for alloy binary.
 
 ## Uninstall
 
@@ -74,8 +74,8 @@ This includes any configuration files in the installation directory.
 
 ## Next steps
 
-* [Run {{< param "PRODUCT_NAME" >}}][Run]
-* [Configure {{< param "PRODUCT_NAME" >}}][Configure]
+- [Run {{< param "PRODUCT_NAME" >}}][Run]
+- [Configure {{< param "PRODUCT_NAME" >}}][Configure]
 
 [latest]: https://github.com/grafana/alloy/releases/latest
 [data collection]: ../../../data-collection/
diff --git a/docs/sources/set-up/migrate/from-flow.md b/docs/sources/set-up/migrate/from-flow.md
index bfd6bbcd3b..18b19fdb8a 100644
--- a/docs/sources/set-up/migrate/from-flow.md
+++ b/docs/sources/set-up/migrate/from-flow.md
@@ -19,13 +19,14 @@ If you want a fresh start with {{< param "PRODUCT_NAME" >}}, you can [uninstall
 
 [uninstall]: https://grafana.com/docs/agent/latest/flow/get-started/install/
 [install]: ../../../set-up/install/
+
 {{< /admonition >}}
 
 ## Before you begin
 
-* You must have a Grafana Agent Flow configuration to migrate.
-* You must be running Grafana Agent Flow version v0.40 or later.
-* If you use auto-scaling make sure you disable auto-scaling for your Grafana Agent Flow deployment to prevent it from scaling during the migration.
+- You must have a Grafana Agent Flow configuration to migrate.
+- You must be running Grafana Agent Flow version v0.40 or later.
+- If you use auto-scaling make sure you disable auto-scaling for your Grafana Agent Flow deployment to prevent it from scaling during the migration.
 
 ## Differences between Grafana Agent Flow and {{% param "PRODUCT_NAME" %}}
 
@@ -33,11 +34,11 @@ By default, you can only use functionality marked _Generally available_.
 
 You can enable functionality in _Experimental_ and _Public preview_ by setting the `--stability.level` flag in [run][].
 
-* The default value of `--storage.path` has changed from `data-agent/` to `data-alloy/`.
-* The default value of `--server.http.memory-addr` has changed from `agent.internal:12345` to `alloy.internal:12345`.
-* Debug metrics reported by {{% param "PRODUCT_NAME" %}} are prefixed with `alloy_` instead of `agent_`.
-* The "classic modules", `module.file`, `module.git`, `module.http`, and `module.string` have been removed in favor of import configuration blocks.
-* The `prometheus.exporter.vsphere` component has been replaced by the `otelcol.receiver.vcenter` component.
+- The default value of `--storage.path` has changed from `data-agent/` to `data-alloy/`.
+- The default value of `--server.http.memory-addr` has changed from `agent.internal:12345` to `alloy.internal:12345`.
+- Debug metrics reported by {{% param "PRODUCT_NAME" %}} are prefixed with `alloy_` instead of `agent_`.
+- The "classic modules", `module.file`, `module.git`, `module.http`, and `module.string` have been removed in favor of import configuration blocks.
+- The `prometheus.exporter.vsphere` component has been replaced by the `otelcol.receiver.vcenter` component.
 
 ## Steps
 
@@ -47,12 +48,12 @@ You can enable functionality in _Experimental_ and _Public preview_ by setting t
 
 Before migrating, modify your Grafana Agent Flow configuration to remove or replace any unsupported components:
 
-* The "classic modules" in Grafana Agent Flow have been removed in favor of the modules introduced in v0.40:
-  * `module.file` is replaced by the [`import.file`][import.file] configuration block.
-  * `module.git` is replaced by the [`import.git`][import.git] configuration block.
-  * `module.http` is replaced by the [`import.http`][import.http] configuration block.
-  * `module.string` is replaced by the [`import.string`][import.string] configuration block.
-* `prometheus.exporter.vsphere` is replaced by the [`otelcol.receiver.vcenter`][otelcol.receiver.vcenter] component.
+- The "classic modules" in Grafana Agent Flow have been removed in favor of the modules introduced in v0.40:
+  - `module.file` is replaced by the [`import.file`][import.file] configuration block.
+  - `module.git` is replaced by the [`import.git`][import.git] configuration block.
+  - `module.http` is replaced by the [`import.http`][import.http] configuration block.
+  - `module.string` is replaced by the [`import.string`][import.string] configuration block.
+- `prometheus.exporter.vsphere` is replaced by the [`otelcol.receiver.vcenter`][otelcol.receiver.vcenter] component.
 
 [import.file]: ../../../reference/config-blocks/import.file/
 [import.git]: ../../../reference/config-blocks/import.git/
@@ -66,28 +67,28 @@ Follow the [installation instructions][install] for {{< param "PRODUCT_NAME" >}}
 
 When deploying {{< param "PRODUCT_NAME" >}}, be aware of the following settings:
 
-* {{< param "PRODUCT_NAME" >}} should be deployed with topology that's the same as Grafana Agent Flow.
+- {{< param "PRODUCT_NAME" >}} should be deployed with topology that's the same as Grafana Agent Flow.
   The CPU, and storage limits should match.
-* Custom command-line flags configured in Grafana Agent Flow should be reflected in your {{< param "PRODUCT_NAME" >}} installation.
-* {{< param "PRODUCT_NAME" >}} may need to be deployed with the `--stability.level` flag in [run] to enable non-stable components:
-  * Set `--stability.level` to `experimental` if you are using the following component:
-    * [otelcol.receiver.vcenter]
-  * Otherwise, `--stability.level` may be omitted or set to the default value, `generally-available`.
-* When installing on Kubernetes, update your `values.yaml` file to rename the `agent` key to `alloy`.
-* If you are deploying {{< param "PRODUCT_NAME" >}} as a cluster:
-  * Set the number of instances to match the number of instances in your Grafana Agent Flow cluster.
-  * Don't enable auto-scaling until the migration is complete.
+- Custom command-line flags configured in Grafana Agent Flow should be reflected in your {{< param "PRODUCT_NAME" >}} installation.
+- {{< param "PRODUCT_NAME" >}} may need to be deployed with the `--stability.level` flag in [run] to enable non-stable components:
+  - Set `--stability.level` to `experimental` if you are using the following component:
+    - [otelcol.receiver.vcenter]
+  - Otherwise, `--stability.level` may be omitted or set to the default value, `generally-available`.
+- When installing on Kubernetes, update your `values.yaml` file to rename the `agent` key to `alloy`.
+- If you are deploying {{< param "PRODUCT_NAME" >}} as a cluster:
+  - Set the number of instances to match the number of instances in your Grafana Agent Flow cluster.
+  - Don't enable auto-scaling until the migration is complete.
 
 ### Migrate Grafana Agent Flow data to {{% param "PRODUCT_NAME" %}}
 
 Migrate your Grafana Agent Flow data to {{< param "PRODUCT_NAME" >}} by copying the contents of the Grafana Agent Flow data directory to the {{< param "PRODUCT_NAME" >}} data directory.
 
-* Linux installations: copy the _contents_ of `/var/lib/grafana-agent-flow` to `/var/lib/alloy/data`.
-* macOS installations: copy the _contents_ of `$(brew --prefix)/etc/grafana-agent-flow/data` to `$(brew --prefix)/etc/alloy/data`.
-* Windows installations: copy the _contents_ of `%ProgramData%\Grafana Agent Flow\data` to `%ProgramData%\GrafanaLabs\Alloy\data`.
-* Docker: copy the contents of mounted volumes to a new directory, and then mount the directory when running {{% param "PRODUCT_NAME" %}}.
-* Kubernetes: use `kubectl cp` to copy the _contents_ of the data directory on Flow pods to the data directory on {{% param "PRODUCT_NAME" %}} pods.
-  * The data directory is determined by the `agent.storagePath` (default `/tmp/agent`) and `alloy.storagePath` (default `/tmp/alloy`) fields in `values.yaml`.
+- Linux installations: copy the _contents_ of `/var/lib/grafana-agent-flow` to `/var/lib/alloy/data`.
+- macOS installations: copy the _contents_ of `$(brew --prefix)/etc/grafana-agent-flow/data` to `$(brew --prefix)/etc/alloy/data`.
+- Windows installations: copy the _contents_ of `%ProgramData%\Grafana Agent Flow\data` to `%ProgramData%\GrafanaLabs\Alloy\data`.
+- Docker: copy the contents of mounted volumes to a new directory, and then mount the directory when running {{% param "PRODUCT_NAME" %}}.
+- Kubernetes: use `kubectl cp` to copy the _contents_ of the data directory on Flow pods to the data directory on {{% param "PRODUCT_NAME" %}} pods.
+  - The data directory is determined by the `agent.storagePath` (default `/tmp/agent`) and `alloy.storagePath` (default `/tmp/alloy`) fields in `values.yaml`.
 
 ### Migrate pipelines that receive data over the network
 
diff --git a/docs/sources/set-up/migrate/from-operator.md b/docs/sources/set-up/migrate/from-operator.md
index ddb6476e45..01d1cfd4f0 100644
--- a/docs/sources/set-up/migrate/from-operator.md
+++ b/docs/sources/set-up/migrate/from-operator.md
@@ -20,42 +20,42 @@ You can migrate from Grafana Agent Operator to {{< param "PRODUCT_NAME" >}}.
 1. Create a `values.yaml` file, which contains options for deploying {{< param "PRODUCT_NAME" >}}.
    You can start with the [default values][] and customize as you see fit, or start with this snippet, which should be a good starting point for what Grafana Agent Operator does.
 
-    ```yaml
-    alloy:
-      configMap:
-        create: true
-      clustering:
-        enabled: true
-    controller:
-      type: 'statefulset'
-      replicas: 2
-    crds:
-      create: false
-    ```
-
-    This configuration deploys {{< param "PRODUCT_NAME" >}} as a `StatefulSet` using the built-in [clustering][] functionality to allow distributing scrapes across all {{< param "PRODUCT_NAME" >}} pods.
-
-    This is one of many deployment possible modes. For example, you may want to use a `DaemonSet` to collect host-level logs or metrics.
-    See the {{< param "PRODUCT_NAME" >}} [deployment guide][] for more details about different topologies.
+   ```yaml
+   alloy:
+     configMap:
+       create: true
+     clustering:
+       enabled: true
+   controller:
+     type: "statefulset"
+     replicas: 2
+   crds:
+     create: false
+   ```
+
+   This configuration deploys {{< param "PRODUCT_NAME" >}} as a `StatefulSet` using the built-in [clustering][] functionality to allow distributing scrapes across all {{< param "PRODUCT_NAME" >}} pods.
+
+   This is one of many deployment possible modes. For example, you may want to use a `DaemonSet` to collect host-level logs or metrics.
+   See the {{< param "PRODUCT_NAME" >}} [deployment guide][] for more details about different topologies.
 
 1. Create an {{< param "PRODUCT_NAME" >}} configuration file, `config.alloy`.
 
-    In the next step, you add to this configuration as you convert `MetricsInstances`. You can add any additional configuration to this file as you need.
+   In the next step, you add to this configuration as you convert `MetricsInstances`. You can add any additional configuration to this file as you need.
 
 1. Install the Grafana Helm repository:
 
-    ```shell
-    helm repo add grafana https://grafana.github.io/helm-charts
-    helm repo update
-    ```
+   ```shell
+   helm repo add grafana https://grafana.github.io/helm-charts
+   helm repo update
+   ```
 
 1. Create a Helm release. You can name the release anything you like. The following command installs a release called `alloy-metrics` in the `monitoring` namespace.
 
-    ```shell
-    helm upgrade alloy-metrics grafana/alloy -i -n monitoring -f values.yaml --set-file alloy.configMap.content=config.alloy
-    ```
+   ```shell
+   helm upgrade alloy-metrics grafana/alloy -i -n monitoring -f values.yaml --set-file alloy.configMap.content=config.alloy
+   ```
 
-    This command uses the `--set-file` flag to pass the configuration file as a Helm value so that you can continue to edit it as a regular {{< param "PRODUCT_NAME" >}} configuration file.
+   This command uses the `--set-file` flag to pass the configuration file as a Helm value so that you can continue to edit it as a regular {{< param "PRODUCT_NAME" >}} configuration file.
 
 ## Convert `MetricsInstance` to {{% param "PRODUCT_NAME" %}} components
 
@@ -137,7 +137,7 @@ alloy:
   clustering:
     enabled: false
   controller:
-    type: 'daemonset'
+    type: "daemonset"
   mounts:
     # -- Mount /var/log from the host into the container for log collection.
     varlog: true
@@ -273,6 +273,7 @@ However, all Grafana Agent Static mode integrations have an equivalent component
 The [reference documentation][component documentation] should help convert those integrations to their {{< param "PRODUCT_NAME" >}} equivalent.
 
 <!-- ToDo: Validate path -->
+
 [default values]: https://github.com/grafana/alloy/blob/main/operations/helm/charts/alloy/values.yaml
 [clustering]: ../../../get-started/clustering/
 [deployment guide]: ../../../set-up/deploy/
diff --git a/docs/sources/set-up/migrate/from-otelcol.md b/docs/sources/set-up/migrate/from-otelcol.md
index 1d55789c6d..36cf68906f 100644
--- a/docs/sources/set-up/migrate/from-otelcol.md
+++ b/docs/sources/set-up/migrate/from-otelcol.md
@@ -14,20 +14,20 @@ The built-in {{< param "FULL_PRODUCT_NAME" >}} convert command can migrate your
 
 This topic describes how to:
 
-* Convert an OpenTelemetry Collector configuration to a {{< param "PRODUCT_NAME" >}} configuration.
-* Run an OpenTelemetry Collector configuration natively using {{< param "PRODUCT_NAME" >}}.
+- Convert an OpenTelemetry Collector configuration to a {{< param "PRODUCT_NAME" >}} configuration.
+- Run an OpenTelemetry Collector configuration natively using {{< param "PRODUCT_NAME" >}}.
 
 ## Components used in this topic
 
-* [`otelcol.receiver.otlp`][otelcol.receiver.otlp]
-* [`otelcol.processor.memory_limiter`][otelcol.processor.memory_limiter]
-* [`otelcol.exporter.otlp`][otelcol.exporter.otlp]
+- [`otelcol.receiver.otlp`][otelcol.receiver.otlp]
+- [`otelcol.processor.memory_limiter`][otelcol.processor.memory_limiter]
+- [`otelcol.exporter.otlp`][otelcol.exporter.otlp]
 
 ## Before you begin
 
-* You must have an OpenTelemetry Collector configuration.
-* You must have a set of OpenTelemetry Collector applications ready to push telemetry data to {{< param "PRODUCT_NAME" >}}.
-* You must be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
+- You must have an OpenTelemetry Collector configuration.
+- You must have a set of OpenTelemetry Collector applications ready to push telemetry data to {{< param "PRODUCT_NAME" >}}.
+- You must be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
 
 ## Convert an OpenTelemetry Collector configuration
 
@@ -44,8 +44,8 @@ In this task, you use the [convert][] CLI command to output a {{< param "PRODUCT
 
    Replace the following:
 
-   * _`<INPUT_CONFIG_PATH>`_: The full path to the OpenTelemetry Collector configuration.
-   * _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+   - _`<INPUT_CONFIG_PATH>`_: The full path to the OpenTelemetry Collector configuration.
+   - _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
 
 1. [Run][run_cli] {{< param "PRODUCT_NAME" >}} using the new {{< param "PRODUCT_NAME" >}} configuration from _`<OUTPUT_CONFIG_PATH>`_:
 
@@ -54,10 +54,10 @@ In this task, you use the [convert][] CLI command to output a {{< param "PRODUCT
 1. If the `convert` command can't convert an OpenTelemetry Collector configuration, diagnostic information is sent to `stderr`.\
    You can bypass any non-critical issues and output the {{< param "PRODUCT_NAME" >}} configuration using a best-effort conversion by including the `--bypass-errors` flag.
 
-    {{< admonition type="caution" >}}
-    If you bypass the errors, the behavior of the converted configuration may not match the original OpenTelemetry Collector configuration.
-    Make sure you fully test the converted configuration before using it in a production environment.
-    {{< /admonition >}}
+   {{< admonition type="caution" >}}
+   If you bypass the errors, the behavior of the converted configuration may not match the original OpenTelemetry Collector configuration.
+   Make sure you fully test the converted configuration before using it in a production environment.
+   {{< /admonition >}}
 
    ```shell
    alloy convert --source-format=otelcol --bypass-errors --output=<OUTPUT_CONFIG_PATH> <INPUT_CONFIG_PATH>
@@ -65,8 +65,8 @@ In this task, you use the [convert][] CLI command to output a {{< param "PRODUCT
 
    Replace the following:
 
-   * _`<INPUT_CONFIG_PATH>`_: The full path to the OpenTelemetry Collector configuration.
-   * _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+   - _`<INPUT_CONFIG_PATH>`_: The full path to the OpenTelemetry Collector configuration.
+   - _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
 
 1. You can also output a diagnostic report by including the `--report` flag.
 
@@ -76,19 +76,19 @@ In this task, you use the [convert][] CLI command to output a {{< param "PRODUCT
 
    Replace the following:
 
-   * _`<INPUT_CONFIG_PATH>`_: The full path to the OpenTelemetry Collector configuration.
-   * _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
-   * _`<OUTPUT_REPORT_PATH>`_: The output path for the report.
+   - _`<INPUT_CONFIG_PATH>`_: The full path to the OpenTelemetry Collector configuration.
+   - _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+   - _`<OUTPUT_REPORT_PATH>`_: The output path for the report.
 
-    Using the [example][] OpenTelemetry Collector configuration below, the diagnostic report provides the following information:
+   Using the [example][] OpenTelemetry Collector configuration below, the diagnostic report provides the following information:
 
-    ```plaintext
-    (Info) Converted receiver/otlp into otelcol.receiver.otlp.default
-    (Info) Converted processor/memory_limiter into otelcol.processor.memory_limiter.default
-    (Info) Converted exporter/otlp into otelcol.exporter.otlp.default
+   ```plaintext
+   (Info) Converted receiver/otlp into otelcol.receiver.otlp.default
+   (Info) Converted processor/memory_limiter into otelcol.processor.memory_limiter.default
+   (Info) Converted exporter/otlp into otelcol.exporter.otlp.default
 
-    A configuration file was generated successfully.
-    ```
+   A configuration file was generated successfully.
+   ```
 
 ## Run an OpenTelemetry Collector configuration
 
@@ -137,7 +137,6 @@ processors:
     limit_percentage: 90
     check_interval: 1s
 
-
 service:
   pipelines:
     metrics:
@@ -162,8 +161,8 @@ alloy convert --source-format=otelcol --output=<OUTPUT_CONFIG_PATH> <INPUT_CONFI
 
 Replace the following:
 
-* _`<INPUT_CONFIG_PATH>`_: The full path to the OpenTelemetry Collector configuration.
-* _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+- _`<INPUT_CONFIG_PATH>`_: The full path to the OpenTelemetry Collector configuration.
+- _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
 
 The new {{< param "PRODUCT_NAME" >}} configuration file looks like this:
 
@@ -206,14 +205,14 @@ After the configuration is converted, review the {{< param "PRODUCT_NAME" >}} co
 
 The following list is specific to the convert command and not {{< param "PRODUCT_NAME" >}}:
 
-* Components are supported which directly embed upstream OpenTelemetry Collector features. You can get a general idea of which exist in
+- Components are supported which directly embed upstream OpenTelemetry Collector features. You can get a general idea of which exist in
   {{< param "PRODUCT_NAME" >}} for conversion by reviewing the `otelcol.*` components in the [Component Reference][].
   Any additional unsupported features are returned as errors during conversion.
-* Check if you are using any extra command line arguments with OpenTelemetry Collector that aren't present in your configuration file.
-* Meta-monitoring metrics exposed by {{< param "PRODUCT_NAME" >}} usually match OpenTelemetry Collector meta-monitoring metrics but uses a different name.
+- Check if you are using any extra command line arguments with OpenTelemetry Collector that aren't present in your configuration file.
+- Meta-monitoring metrics exposed by {{< param "PRODUCT_NAME" >}} usually match OpenTelemetry Collector meta-monitoring metrics but uses a different name.
   Make sure that you use the new metric names, for example, in your alerts and dashboards queries.
-* The logs produced by {{< param "PRODUCT_NAME" >}} differ from those produced by OpenTelemetry Collector.
-* {{< param "FULL_PRODUCT_NAME" >}} exposes the {{< param "PRODUCT_NAME" >}} [UI][].
+- The logs produced by {{< param "PRODUCT_NAME" >}} differ from those produced by OpenTelemetry Collector.
+- {{< param "FULL_PRODUCT_NAME" >}} exposes the {{< param "PRODUCT_NAME" >}} [UI][].
 
 [OpenTelemetry Collector]: https://opentelemetry.io/docs/collector/configuration/
 [debugging]: #debugging
diff --git a/docs/sources/set-up/migrate/from-prometheus.md b/docs/sources/set-up/migrate/from-prometheus.md
index f06f5a1d29..eafee1cadd 100644
--- a/docs/sources/set-up/migrate/from-prometheus.md
+++ b/docs/sources/set-up/migrate/from-prometheus.md
@@ -14,19 +14,19 @@ The built-in {{< param "PRODUCT_NAME" >}} convert command can migrate your [Prom
 
 This topic describes how to:
 
-* Convert a Prometheus configuration to an {{< param "PRODUCT_NAME" >}} configuration.
-* Run a Prometheus configuration natively using {{< param "PRODUCT_NAME" >}}.
+- Convert a Prometheus configuration to an {{< param "PRODUCT_NAME" >}} configuration.
+- Run a Prometheus configuration natively using {{< param "PRODUCT_NAME" >}}.
 
 ## Components used in this topic
 
-* [`prometheus.scrape`][prometheus.scrape]
-* [`prometheus.remote_write`][prometheus.remote_write]
+- [`prometheus.scrape`][prometheus.scrape]
+- [`prometheus.remote_write`][prometheus.remote_write]
 
 ## Before you begin
 
-* You must have a Prometheus configuration.
-* You must have a set of Prometheus applications ready to push telemetry data to {{< param "PRODUCT_NAME" >}}.
-* You must be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
+- You must have a Prometheus configuration.
+- You must have a set of Prometheus applications ready to push telemetry data to {{< param "PRODUCT_NAME" >}}.
+- You must be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
 
 ## Convert a Prometheus configuration
 
@@ -43,8 +43,8 @@ In this task, you use the [convert][] CLI command to output an {{< param "PRODUC
 
    Replace the following:
 
-   * _`<INPUT_CONFIG_PATH>`_: The full path to the Prometheus configuration.
-   * _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+   - _`<INPUT_CONFIG_PATH>`_: The full path to the Prometheus configuration.
+   - _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
 
 1. [Run][] {{< param "PRODUCT_NAME" >}} using the new {{< param "PRODUCT_NAME" >}} configuration from _`<OUTPUT_CONFIG_PATH>`_:
 
@@ -64,8 +64,8 @@ In this task, you use the [convert][] CLI command to output an {{< param "PRODUC
 
    Replace the following:
 
-   * _`<INPUT_CONFIG_PATH>`_: The full path to the Prometheus configuration.
-   * _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+   - _`<INPUT_CONFIG_PATH>`_: The full path to the Prometheus configuration.
+   - _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
 
 1. You can also output a diagnostic report by including the `--report` flag.
 
@@ -75,18 +75,18 @@ In this task, you use the [convert][] CLI command to output an {{< param "PRODUC
 
    Replace the following:
 
-   * _`<INPUT_CONFIG_PATH>`_: The full path to the Prometheus configuration.
-   * _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
-   * _`<OUTPUT_REPORT_PATH>`_: The output path for the report.
+   - _`<INPUT_CONFIG_PATH>`_: The full path to the Prometheus configuration.
+   - _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+   - _`<OUTPUT_REPORT_PATH>`_: The output path for the report.
 
-    Using the [example][] Prometheus configuration below, the diagnostic report provides the following information:
+   Using the [example][] Prometheus configuration below, the diagnostic report provides the following information:
 
-    ```plaintext
-    (Info) Converted scrape_configs job_name "prometheus" into...
-      A prometheus.scrape.prometheus component
-    (Info) Converted 1 remote_write[s] "grafana-cloud" into...
-      A prometheus.remote_write.default component
-    ```
+   ```plaintext
+   (Info) Converted scrape_configs job_name "prometheus" into...
+     A prometheus.scrape.prometheus component
+   (Info) Converted 1 remote_write[s] "grafana-cloud" into...
+     A prometheus.remote_write.default component
+   ```
 
 ## Run a Prometheus configuration
 
@@ -121,7 +121,7 @@ The following Prometheus configuration file provides the input for the conversio
 
 ```yaml
 global:
-  scrape_timeout:    45s
+  scrape_timeout: 45s
 
 scrape_configs:
   - job_name: "prometheus"
@@ -144,8 +144,8 @@ alloy convert --source-format=prometheus --output=<OUTPUT_CONFIG_PATH> <INPUT_CO
 
 Replace the following:
 
-* _`<INPUT_CONFIG_PATH>`_: The full path to the Prometheus configuration.
-* _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+- _`<INPUT_CONFIG_PATH>`_: The full path to the Prometheus configuration.
+- _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
 
 The new {{< param "PRODUCT_NAME" >}} configuration file looks like this:
 
@@ -190,13 +190,13 @@ After the configuration is converted, review the {{< param "PRODUCT_NAME" >}} co
 
 The following list is specific to the convert command and not {{< param "PRODUCT_NAME" >}}:
 
-* The following configurations aren't available for conversion to {{< param "PRODUCT_NAME" >}}: `rule_files`, `alerting`, `remote_read`, `storage`, and `tracing`.
+- The following configurations aren't available for conversion to {{< param "PRODUCT_NAME" >}}: `rule_files`, `alerting`, `remote_read`, `storage`, and `tracing`.
   Any additional unsupported features are returned as errors during conversion.
-* Check if you are using any extra command line arguments with Prometheus that aren't present in your configuration file. For example, `--web.listen-address`.
-* Meta-monitoring metrics exposed by {{< param "PRODUCT_NAME" >}} usually match Prometheus meta-monitoring metrics but uses a different name.
+- Check if you are using any extra command line arguments with Prometheus that aren't present in your configuration file. For example, `--web.listen-address`.
+- Meta-monitoring metrics exposed by {{< param "PRODUCT_NAME" >}} usually match Prometheus meta-monitoring metrics but uses a different name.
   Make sure that you use the new metric names, for example, in your alerts and dashboards queries.
-* The logs produced by {{< param "PRODUCT_NAME" >}} differ from those produced by Prometheus.
-* {{< param "PRODUCT_NAME" >}} exposes the {{< param "PRODUCT_NAME" >}} [UI][].
+- The logs produced by {{< param "PRODUCT_NAME" >}} differ from those produced by Prometheus.
+- {{< param "PRODUCT_NAME" >}} exposes the {{< param "PRODUCT_NAME" >}} [UI][].
 
 [Prometheus]: https://prometheus.io/docs/prometheus/latest/configuration/configuration/
 [debugging]: #debugging
diff --git a/docs/sources/set-up/migrate/from-promtail.md b/docs/sources/set-up/migrate/from-promtail.md
index 67769f9cac..4d283e6315 100644
--- a/docs/sources/set-up/migrate/from-promtail.md
+++ b/docs/sources/set-up/migrate/from-promtail.md
@@ -14,19 +14,19 @@ The built-in {{< param "PRODUCT_NAME" >}} convert command can migrate your [Prom
 
 This topic describes how to:
 
-* Convert a Promtail configuration to an {{< param "PRODUCT_NAME" >}} configuration.
-* Run a Promtail configuration natively using {{< param "PRODUCT_NAME" >}}.
+- Convert a Promtail configuration to an {{< param "PRODUCT_NAME" >}} configuration.
+- Run a Promtail configuration natively using {{< param "PRODUCT_NAME" >}}.
 
 ## Components used in this topic
 
-* [`local.file_match`][local.file_match]
-* [`loki.source.file`][loki.source.file]
-* [`loki.write`][loki.write]
+- [`local.file_match`][local.file_match]
+- [`loki.source.file`][loki.source.file]
+- [`loki.write`][loki.write]
 
 ## Before you begin
 
-* You must have a Promtail configuration.
-* You must be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
+- You must have a Promtail configuration.
+- You must be familiar with the concept of [Components][] in {{< param "PRODUCT_NAME" >}}.
 
 ## Convert a Promtail configuration
 
@@ -43,8 +43,9 @@ This conversion allows you to take full advantage of the many additional feature
    ```
 
    Replace the following:
-    * _`<INPUT_CONFIG_PATH>`_: The full path to the Promtail configuration.
-    * _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+
+   - _`<INPUT_CONFIG_PATH>`_: The full path to the Promtail configuration.
+   - _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
 
 1. [Run][run] {{< param "PRODUCT_NAME" >}} using the new configuration from _`<OUTPUT_CONFIG_PATH>`_:
 
@@ -63,8 +64,9 @@ This conversion allows you to take full advantage of the many additional feature
    ```
 
    Replace the following:
-   * _`<INPUT_CONFIG_PATH>`_: The full path to the Promtail configuration.
-   * _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+
+   - _`<INPUT_CONFIG_PATH>`_: The full path to the Promtail configuration.
+   - _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
 
 1. You can also output a diagnostic report by including the `--report` flag.
 
@@ -74,16 +76,16 @@ This conversion allows you to take full advantage of the many additional feature
 
    Replace the following:
 
-   * _`<INPUT_CONFIG_PATH>`_: The full path to the Promtail configuration.
-   * _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
-   * _`<OUTPUT_REPORT_PATH>`_: The output path for the report.
+   - _`<INPUT_CONFIG_PATH>`_: The full path to the Promtail configuration.
+   - _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+   - _`<OUTPUT_REPORT_PATH>`_: The output path for the report.
 
    If you use the [example](#example) Promtail configuration below, the diagnostic report provides the following information:
 
-    ```plaintext
-    (Warning) If you have a tracing set up for Promtail, it cannot be migrated to {{< param "PRODUCT_NAME" >}} automatically. Refer to the documentation on how to configure tracing in {{< param "PRODUCT_NAME" >}}.
-    (Warning) The metrics from {{< param "PRODUCT_NAME" >}} are different from the metrics emitted by Promtail. If you rely on Promtail's metrics, you must change your configuration, for example, your alerts and dashboards.
-    ```
+   ```plaintext
+   (Warning) If you have a tracing set up for Promtail, it cannot be migrated to {{< param "PRODUCT_NAME" >}} automatically. Refer to the documentation on how to configure tracing in {{< param "PRODUCT_NAME" >}}.
+   (Warning) The metrics from {{< param "PRODUCT_NAME" >}} are different from the metrics emitted by Promtail. If you rely on Promtail's metrics, you must change your configuration, for example, your alerts and dashboards.
+   ```
 
 ## Run a Promtail configuration
 
@@ -100,7 +102,7 @@ Your configuration file must be a valid Promtail configuration file rather than
 
 1. You can follow the convert CLI command [debugging][] instructions to generate a diagnostic report.
 
-1. Refer to the {{< param "PRODUCT_NAME" >}}  [Debugging][DebuggingUI] for more information about running {{< param "PRODUCT_NAME" >}}.
+1. Refer to the {{< param "PRODUCT_NAME" >}} [Debugging][DebuggingUI] for more information about running {{< param "PRODUCT_NAME" >}}.
 
 1. If your Promtail configuration can't be converted and loaded directly into {{< param "PRODUCT_NAME" >}}, diagnostic information is sent to `stderr`.
    You can bypass any non-critical issues and start {{< param "PRODUCT_NAME" >}} by including the `--config.bypass-conversion-errors` flag in addition to `--config.format=promtail`.
@@ -136,8 +138,8 @@ alloy convert --source-format=promtail --output=<OUTPUT_CONFIG_PATH> <INPUT_CONF
 
 Replace the following:
 
-* _`<INPUT_CONFIG_PATH>`_: The full path to the Promtail configuration.
-* _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+- _`<INPUT_CONFIG_PATH>`_: The full path to the Promtail configuration.
+- _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
 
 The new {{< param "PRODUCT_NAME" >}} configuration file looks like this:
 
@@ -170,15 +172,15 @@ After the configuration is converted, review the {{< param "PRODUCT_NAME" >}} co
 
 The following list is specific to the convert command and not {{< param "PRODUCT_NAME" >}}:
 
-* Check if you are using any extra command line arguments with Promtail that aren't present in your configuration file. For example, `-max-line-size`.
-* Check if you are setting any environment variables, whether [expanded in the configuration file][] itself or consumed directly by Promtail, such as `JAEGER_AGENT_HOST`.
-* In {{< param "PRODUCT_NAME" >}}, the positions file is saved at a different location.
+- Check if you are using any extra command line arguments with Promtail that aren't present in your configuration file. For example, `-max-line-size`.
+- Check if you are setting any environment variables, whether [expanded in the configuration file][] itself or consumed directly by Promtail, such as `JAEGER_AGENT_HOST`.
+- In {{< param "PRODUCT_NAME" >}}, the positions file is saved at a different location.
   Refer to the [`loki.source.file`][loki.source.file] documentation for more details.
   Check if you have any setup, for example, a Kubernetes Persistent Volume, that you must update to use the new positions path.
-* Meta-monitoring metrics exposed by {{< param "PRODUCT_NAME" >}} usually match Promtail meta-monitoring metrics but uses a different name.
+- Meta-monitoring metrics exposed by {{< param "PRODUCT_NAME" >}} usually match Promtail meta-monitoring metrics but uses a different name.
   Make sure that you use the new metric names, for example, in your alerts and dashboards queries.
-* The logs produced by {{< param "PRODUCT_NAME" >}} differ from those produced by Promtail.
-* {{< param "PRODUCT_NAME" >}} exposes the {{< param "PRODUCT_NAME" >}} [UI][], which differs from the Promtail Web UI.
+- The logs produced by {{< param "PRODUCT_NAME" >}} differ from those produced by Promtail.
+- {{< param "PRODUCT_NAME" >}} exposes the {{< param "PRODUCT_NAME" >}} [UI][], which differs from the Promtail Web UI.
 
 [Promtail]: https://www.grafana.com/docs/loki/<LOKI_VERSION>/clients/promtail/
 [debugging]: #debugging
diff --git a/docs/sources/set-up/migrate/from-static.md b/docs/sources/set-up/migrate/from-static.md
index 231c14e0d0..18cc70822f 100644
--- a/docs/sources/set-up/migrate/from-static.md
+++ b/docs/sources/set-up/migrate/from-static.md
@@ -14,25 +14,25 @@ The built-in {{< param "PRODUCT_NAME" >}} convert command can migrate your [Graf
 
 This topic describes how to:
 
-* Convert a Grafana Agent Static configuration to an {{< param "PRODUCT_NAME" >}} configuration.
-* Run a Grafana Agent Static configuration natively using {{< param "PRODUCT_NAME" >}}.
+- Convert a Grafana Agent Static configuration to an {{< param "PRODUCT_NAME" >}} configuration.
+- Run a Grafana Agent Static configuration natively using {{< param "PRODUCT_NAME" >}}.
 
 ## Components used in this topic
 
-* [`prometheus.scrape`][prometheus.scrape]
-* [`prometheus.remote_write`][prometheus.remote_write]
-* [`local.file_match`][local.file_match]
-* [`loki.process`][loki.process]
-* [`loki.source.file`][loki.source.file]
-* [`loki.write`][loki.write]
-* [`otelcol.receiver.otlp`][otelcol.receiver.otlp]
-* [`otelcol.processor.batch`][otelcol.processor.batch]
-* [`otelcol.exporter.otlp`][otelcol.exporter.otlp]
+- [`prometheus.scrape`][prometheus.scrape]
+- [`prometheus.remote_write`][prometheus.remote_write]
+- [`local.file_match`][local.file_match]
+- [`loki.process`][loki.process]
+- [`loki.source.file`][loki.source.file]
+- [`loki.write`][loki.write]
+- [`otelcol.receiver.otlp`][otelcol.receiver.otlp]
+- [`otelcol.processor.batch`][otelcol.processor.batch]
+- [`otelcol.exporter.otlp`][otelcol.exporter.otlp]
 
 ## Before you begin
 
-* You must have a Grafana Agent Static configuration.
-* You must be familiar with the [Components][] concept in {{< param "PRODUCT_NAME" >}}.
+- You must have a Grafana Agent Static configuration.
+- You must be familiar with the [Components][] concept in {{< param "PRODUCT_NAME" >}}.
 
 ## Convert a Grafana Agent Static configuration
 
@@ -49,9 +49,9 @@ This conversion allows you to take full advantage of the many additional feature
 
    Replace the following:
 
-    * _`<INPUT_CONFIG_PATH>`_: The full path to the configuration file for Grafana Agent Static.
-    * _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
-  
+   - _`<INPUT_CONFIG_PATH>`_: The full path to the configuration file for Grafana Agent Static.
+   - _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+
 1. [Stop][] Grafana Agent static.
 
 1. [Run][run alloy] {{< param "PRODUCT_NAME" >}} using the new {{< param "PRODUCT_NAME" >}} configuration from _`<OUTPUT_CONFIG_PATH>`_:
@@ -72,26 +72,26 @@ This conversion allows you to take full advantage of the many additional feature
 
    Replace the following:
 
-   * _`<INPUT_CONFIG_PATH>`_: The full path to the configuration file for Grafana Agent Static.
-   * _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+   - _`<INPUT_CONFIG_PATH>`_: The full path to the configuration file for Grafana Agent Static.
+   - _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
 
 1. You can use the `--report` flag to output a diagnostic report.
 
    ```shell
    alloy convert --source-format=static --report=<OUTPUT_REPORT_PATH> --output=<OUTPUT_CONFIG_PATH> <INPUT_CONFIG_PATH>
-    ```
+   ```
 
    Replace the following:
 
-   * _`<INPUT_CONFIG_PATH>`_: The full path to the configuration file for Grafana Agent Static.
-   * _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
-   * _`<OUTPUT_REPORT_PATH>`_: The output path for the report.
+   - _`<INPUT_CONFIG_PATH>`_: The full path to the configuration file for Grafana Agent Static.
+   - _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+   - _`<OUTPUT_REPORT_PATH>`_: The output path for the report.
 
    Using the [example][] Grafana Agent Static configuration below, the diagnostic report provides the following information.
 
-    ```plaintext
-    (Warning) Please review your agent command line flags and ensure they are set in your {{< param "PRODUCT_NAME" >}} configuration file where necessary.
-    ```
+   ```plaintext
+   (Warning) Please review your agent command line flags and ensure they are set in your {{< param "PRODUCT_NAME" >}} configuration file where necessary.
+   ```
 
 ## Run a Grafana Agent Static mode configuration
 
@@ -142,9 +142,9 @@ metrics:
       scrape_configs:
         - job_name: local-agent
           static_configs:
-            - targets: ['127.0.0.1:12345']
+            - targets: ["127.0.0.1:12345"]
               labels:
-                cluster: 'localhost'
+                cluster: "localhost"
 
 logs:
   global:
@@ -158,7 +158,7 @@ logs:
         - job_name: varlogs
           static_configs:
             - targets:
-              - localhost
+                - localhost
               labels:
                 job: varlogs
                 host: mylocalhost
@@ -167,13 +167,13 @@ logs:
             - match:
                 selector: '{filename="/var/log/*.log"}'
                 stages:
-                - drop:
-                    expression: '^[^0-9]{4}'
-                - regex:
-                    expression: '^(?P<timestamp>\d{4}/\d{2}/\d{2} \d{2}:\d{2}:\d{2}) \[(?P<level>[[:alpha:]]+)\] (?:\d+)\#(?:\d+): \*(?:\d+) (?P<message>.+)$'
-                - pack:
-                    labels:
-                      - level
+                  - drop:
+                      expression: "^[^0-9]{4}"
+                  - regex:
+                      expression: '^(?P<timestamp>\d{4}/\d{2}/\d{2} \d{2}:\d{2}:\d{2}) \[(?P<level>[[:alpha:]]+)\] (?:\d+)\#(?:\d+): \*(?:\d+) (?P<message>.+)$'
+                  - pack:
+                      labels:
+                        - level
       clients:
         - url: https://USER_ID:API_KEY@logs-prod3.grafana.net/loki/api/v1/push
 
@@ -203,8 +203,8 @@ alloy convert --source-format=static --output=<OUTPUT_CONFIG_PATH> <INPUT_CONFIG
 
 Replace the following:
 
-* _`<INPUT_CONFIG_PATH>`_: The full path to the configuration file for Grafana Agent Static.
-* _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+- _`<INPUT_CONFIG_PATH>`_: The full path to the configuration file for Grafana Agent Static.
+- _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
 
 The {{< param "PRODUCT_NAME" >}} configuration file looks like this:
 
@@ -334,8 +334,8 @@ alloy convert --source-format=static --extra-args="-enable-features=integrations
 
 Replace the following:
 
-* _`<INPUT_CONFIG_PATH>`_: The full path to the configuration file for Grafana Agent Static.
-* _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
+- _`<INPUT_CONFIG_PATH>`_: The full path to the configuration file for Grafana Agent Static.
+- _`<OUTPUT_CONFIG_PATH>`_: The full path to output the {{< param "PRODUCT_NAME" >}} configuration.
 
 ## Environment variables
 
@@ -353,16 +353,16 @@ After the configuration is converted, review the {{< param "PRODUCT_NAME" >}} co
 
 The following list is specific to the convert command and not {{< param "PRODUCT_NAME" >}}:
 
-* The [Agent Management][] configuration options can't be automatically converted to {{< param "PRODUCT_NAME" >}}.
+- The [Agent Management][] configuration options can't be automatically converted to {{< param "PRODUCT_NAME" >}}.
   Any additional unsupported features are returned as errors during conversion.
-* There is no gRPC server to configure for {{< param "PRODUCT_NAME" >}}. Any non-default configuration shows as unsupported during the conversion.
-* Check if you are using any extra command line arguments with Grafana Agent Static that aren't present in your configuration file. For example, `-server.http.address`.
-* Check if you are using any environment variables in your Grafana Agent Static configuration.
+- There is no gRPC server to configure for {{< param "PRODUCT_NAME" >}}. Any non-default configuration shows as unsupported during the conversion.
+- Check if you are using any extra command line arguments with Grafana Agent Static that aren't present in your configuration file. For example, `-server.http.address`.
+- Check if you are using any environment variables in your Grafana Agent Static configuration.
   These are evaluated during conversion, and you may want to replace them with the {{< param "PRODUCT_NAME" >}} Standard library [sys.env][] function after conversion.
-* Review additional [Prometheus Limitations][] for limitations specific to your [Metrics][] configuration.
-* Review additional [Promtail Limitations][] for limitations specific to your [Logs][] configuration.
-* The logs produced by {{< param "PRODUCT_NAME" >}} differ from those produced by Grafana Agent Static.
-* {{< param "PRODUCT_NAME" >}} exposes the {{< param "PRODUCT_NAME" >}} [UI][].
+- Review additional [Prometheus Limitations][] for limitations specific to your [Metrics][] configuration.
+- Review additional [Promtail Limitations][] for limitations specific to your [Logs][] configuration.
+- The logs produced by {{< param "PRODUCT_NAME" >}} differ from those produced by Grafana Agent Static.
+- {{< param "PRODUCT_NAME" >}} exposes the {{< param "PRODUCT_NAME" >}} [UI][].
 
 [debugging]: #debugging
 [example]: #example
@@ -389,5 +389,5 @@ The following list is specific to the convert command and not {{< param "PRODUCT
 [UI]: ../../../troubleshoot/debug/#alloy-ui
 [otelcol.receiver.otlp]: ../../../reference/components/otelcol/otelcol.receiver.otlp/
 [otelcol.processor.batch]: ../../../reference/components/otelcol/otelcol.processor.batch/
-[otelcol.exporter.otlp]:../../../reference/components/otelcol/otelcol.exporter.otlp/
+[otelcol.exporter.otlp]: ../../../reference/components/otelcol/otelcol.exporter.otlp/
 [Stop]: https://grafana.com/docs/agent/latest/static/set-up/start-agent
diff --git a/docs/sources/set-up/run/binary.md b/docs/sources/set-up/run/binary.md
index 23ddb68d5b..3792bab6f8 100644
--- a/docs/sources/set-up/run/binary.md
+++ b/docs/sources/set-up/run/binary.md
@@ -24,8 +24,8 @@ To start {{< param "PRODUCT_NAME" >}}, run the following command in a terminal o
 
 Replace the following:
 
-* _`<BINARY_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} binary file.
-* _`<CONFIG_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} configuration file.
+- _`<BINARY_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} binary file.
+- _`<CONFIG_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} configuration file.
 
 ## Set up {{% param "PRODUCT_NAME" %}} as a Linux systemd service
 
@@ -67,8 +67,8 @@ These steps assume you have a default systemd and {{< param "PRODUCT_NAME" >}} c
 
    Replace the following:
 
-    * _`<BINARY_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} binary file.
-    * _`<WORKING_DIRECTORY>`_: The path to a working directory, for example `/var/lib/alloy`.
+   - _`<BINARY_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} binary file.
+   - _`<WORKING_DIRECTORY>`_: The path to a working directory, for example `/var/lib/alloy`.
 
 1. Create an environment file in `/etc/default/` called `alloy` with the following contents:
 
@@ -93,7 +93,7 @@ These steps assume you have a default systemd and {{< param "PRODUCT_NAME" >}} c
 
    Replace the following:
 
-    * _`<CONFIG_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} configuration file.
+   - _`<CONFIG_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} configuration file.
 
 1. To reload the service files, run the following command in a terminal window:
 
@@ -127,9 +127,9 @@ To write the output and error logs to a file, you can use the redirection operat
 
 Replace the following:
 
-* _`<BINARY_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} binary file.
-* _`<CONFIG_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} configuration file.
-* _`<OUTPUT_FILE>`_: The output filename.
+- _`<BINARY_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} binary file.
+- _`<CONFIG_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} configuration file.
+- _`<OUTPUT_FILE>`_: The output filename.
 
 [InstallBinary]: ../../install/binary/
 [StartLinux]: ../linux/
diff --git a/docs/sources/set-up/run/windows.md b/docs/sources/set-up/run/windows.md
index bf91945a13..7ebeaa1cdf 100644
--- a/docs/sources/set-up/run/windows.md
+++ b/docs/sources/set-up/run/windows.md
@@ -17,9 +17,9 @@ To verify that {{< param "PRODUCT_NAME" >}} is running as a Windows Service:
 
 1. Open the Windows Services manager:
 
-    1. Right click on the Start Menu and select **Run**.
+   1. Right click on the Start Menu and select **Run**.
 
-    1. Type: `services.msc` and click **OK**.
+   1. Type: `services.msc` and click **OK**.
 
 1. Scroll down to find the **{{< param "PRODUCT_NAME" >}}** service and verify that the **Status** is **Running**.
 
@@ -31,9 +31,9 @@ To view the logs, perform the following steps:
 
 1. Open the Event Viewer:
 
-    1. Right click on the Start Menu and select **Run**.
+   1. Right click on the Start Menu and select **Run**.
 
-    1. Type `eventvwr` and click **OK**.
+   1. Type `eventvwr` and click **OK**.
 
 1. In the Event Viewer, click on **Windows Logs > Application**.
 
diff --git a/docs/sources/shared/agent-deprecation.md b/docs/sources/shared/agent-deprecation.md
index 7cae5ca61b..3196359331 100644
--- a/docs/sources/shared/agent-deprecation.md
+++ b/docs/sources/shared/agent-deprecation.md
@@ -6,11 +6,11 @@ labels:
     - oss
 ---
 
-[//]: # 'This file provides an admonition caution to change to Grafana Agent to Grafana Alloy.'
-[//]: # 'This shared file is included in many repositories.'
+[//]: # "This file provides an admonition caution to change to Grafana Agent to Grafana Alloy."
+[//]: # "This shared file is included in many repositories."
 [//]: #
-[//]: # 'If you make changes to this file, verify that the meaning and content are not changed in any place where the file is included.'
-[//]: # 'Any links should be fully qualified and not relative: /docs/grafana/ instead of ../grafana/.'
+[//]: # "If you make changes to this file, verify that the meaning and content are not changed in any place where the file is included."
+[//]: # "Any links should be fully qualified and not relative: /docs/grafana/ instead of ../grafana/."
 
 {{< admonition type="caution" >}}
 Grafana Alloy is the new name for our distribution of the OTel collector.
@@ -18,4 +18,5 @@ Grafana Agent has been deprecated and is in Long-Term Support (LTS) through Octo
 Read more about why we recommend migrating to [Grafana Alloy][alloy].
 
 [alloy]: https://grafana.com/blog/2024/04/09/grafana-alloy-opentelemetry-collector-with-prometheus-pipelines/
+
 {{< /admonition >}}
diff --git a/docs/sources/shared/index.md b/docs/sources/shared/index.md
index c061db6fd4..3d73463458 100644
--- a/docs/sources/shared/index.md
+++ b/docs/sources/shared/index.md
@@ -3,4 +3,3 @@ canonical: https://grafana.com/docs/alloy/latest/shared/
 description: Shared content
 headless: true
 ---
-
diff --git a/docs/sources/shared/reference/components/authorization-block.md b/docs/sources/shared/reference/components/authorization-block.md
index 2c1f8a4354..bfff7a73dc 100644
--- a/docs/sources/shared/reference/components/authorization-block.md
+++ b/docs/sources/shared/reference/components/authorization-block.md
@@ -4,10 +4,10 @@ description: Shared content, authorization block
 headless: true
 ---
 
-Name               | Type     | Description                                | Default | Required
--------------------|----------|--------------------------------------------|---------|---------
-`credentials_file` | `string` | File containing the secret value.          |         | no
-`credentials`      | `secret` | Secret value.                              |         | no
-`type`             | `string` | Authorization type, for example, "Bearer". |         | no
+| Name               | Type     | Description                                | Default | Required |
+| ------------------ | -------- | ------------------------------------------ | ------- | -------- |
+| `credentials_file` | `string` | File containing the secret value.          |         | no       |
+| `credentials`      | `secret` | Secret value.                              |         | no       |
+| `type`             | `string` | Authorization type, for example, "Bearer". |         | no       |
 
 `credential` and `credentials_file` are mutually exclusive, and only one can be provided inside an `authorization` block.
diff --git a/docs/sources/shared/reference/components/azuread-block.md b/docs/sources/shared/reference/components/azuread-block.md
index dcb9a70188..31a6f75c66 100644
--- a/docs/sources/shared/reference/components/azuread-block.md
+++ b/docs/sources/shared/reference/components/azuread-block.md
@@ -4,12 +4,12 @@ description: Shared content, azuread block
 headless: true
 ---
 
-Name    | Type     | Description      | Default         | Required
---------|----------|------------------|-----------------|---------
-`cloud` | `string` | The Azure Cloud. | `"AzurePublic"` | no
+| Name    | Type     | Description      | Default         | Required |
+| ------- | -------- | ---------------- | --------------- | -------- |
+| `cloud` | `string` | The Azure Cloud. | `"AzurePublic"` | no       |
 
 The supported values for `cloud` are:
 
-* `"AzurePublic"`
-* `"AzureChina"`
-* `"AzureGovernment"`
+- `"AzurePublic"`
+- `"AzureChina"`
+- `"AzureGovernment"`
diff --git a/docs/sources/shared/reference/components/basic-auth-block.md b/docs/sources/shared/reference/components/basic-auth-block.md
index 8ff77ae4e6..5c175a5a3d 100644
--- a/docs/sources/shared/reference/components/basic-auth-block.md
+++ b/docs/sources/shared/reference/components/basic-auth-block.md
@@ -4,10 +4,10 @@ description: Shared content, basic auth block
 headless: true
 ---
 
-Name            | Type     | Description                              | Default | Required
-----------------|----------|------------------------------------------|---------|---------
-`password_file` | `string` | File containing the basic auth password. |         | no
-`password`      | `secret` | Basic auth password.                     |         | no
-`username`      | `string` | Basic auth username.                     |         | no
+| Name            | Type     | Description                              | Default | Required |
+| --------------- | -------- | ---------------------------------------- | ------- | -------- |
+| `password_file` | `string` | File containing the basic auth password. |         | no       |
+| `password`      | `secret` | Basic auth password.                     |         | no       |
+| `username`      | `string` | Basic auth username.                     |         | no       |
 
 `password` and `password_file` are mutually exclusive, and only one can be provided inside a `basic_auth` block.
diff --git a/docs/sources/shared/reference/components/exporter-component-exports.md b/docs/sources/shared/reference/components/exporter-component-exports.md
index 8d349f2436..d0d49a2724 100644
--- a/docs/sources/shared/reference/components/exporter-component-exports.md
+++ b/docs/sources/shared/reference/components/exporter-component-exports.md
@@ -6,9 +6,9 @@ headless: true
 
 The following fields are exported and can be referenced by other components.
 
-Name      | Type                | Description
-----------|---------------------|----------------------------------------------------------
-`targets` | `list(map(string))` | The targets that can be used to collect exporter metrics.
+| Name      | Type                | Description                                               |
+| --------- | ------------------- | --------------------------------------------------------- |
+| `targets` | `list(map(string))` | The targets that can be used to collect exporter metrics. |
 
 For example, the `targets` can either be passed to a `discovery.relabel` component to rewrite the targets' label sets or to a `prometheus.scrape` component that collects the exposed metrics.
 
diff --git a/docs/sources/shared/reference/components/extract-field-block.md b/docs/sources/shared/reference/components/extract-field-block.md
index 9789402e3e..ac8007300e 100644
--- a/docs/sources/shared/reference/components/extract-field-block.md
+++ b/docs/sources/shared/reference/components/extract-field-block.md
@@ -6,18 +6,18 @@ headless: true
 
 The following attributes are supported:
 
-Name        | Type     | Description                                                                                   | Default | Required
-------------|----------|-----------------------------------------------------------------------------------------------|---------|---------
-`from`      | `string` | The source of the labels or annotations. Allowed values are `pod`, `namespace`, and `node`.    | `pod`   | no
-`key_regex` | `string` | A regular expression used to extract a key that matches the regular expression.               | `""`    | no
-`key`       | `string` | The annotation or label name. This key must exactly match an annotation or label name.        | `""`    | no
-`regex`     | `string` | An optional field used to extract a sub-string from a complex field value.                    | `""`    | no
-`tag_name`  | `string` | The name of the resource attribute added to logs, metrics, or spans.                          | `""`    | no
+| Name        | Type     | Description                                                                                 | Default | Required |
+| ----------- | -------- | ------------------------------------------------------------------------------------------- | ------- | -------- |
+| `from`      | `string` | The source of the labels or annotations. Allowed values are `pod`, `namespace`, and `node`. | `pod`   | no       |
+| `key_regex` | `string` | A regular expression used to extract a key that matches the regular expression.             | `""`    | no       |
+| `key`       | `string` | The annotation or label name. This key must exactly match an annotation or label name.      | `""`    | no       |
+| `regex`     | `string` | An optional field used to extract a sub-string from a complex field value.                  | `""`    | no       |
+| `tag_name`  | `string` | The name of the resource attribute added to logs, metrics, or spans.                        | `""`    | no       |
 
 When you don't specify the `tag_name`, a default tag name is used with the format:
 
-* `k8s.pod.annotations.<annotation key>`
-* `k8s.pod.labels.<label key>`
+- `k8s.pod.annotations.<annotation key>`
+- `k8s.pod.labels.<label key>`
 
 For example, if `tag_name` isn't specified and the key is `git_sha`, the attribute name will be `k8s.pod.annotations.git_sha`.
 
@@ -26,8 +26,8 @@ When `key_regex` is present, `tag_name` supports back reference to both named ca
 
 For example, assume your Pod spec contains the following labels:
 
-* `app.kubernetes.io/component: mysql`
-* `app.kubernetes.io/version: 5.7.21`
+- `app.kubernetes.io/component: mysql`
+- `app.kubernetes.io/version: 5.7.21`
 
 If you'd like to add tags for all labels with the prefix `app.kubernetes.io/` and trim the prefix, then you can specify the following extraction rules:
 
diff --git a/docs/sources/shared/reference/components/field-filter-block.md b/docs/sources/shared/reference/components/field-filter-block.md
index 76c40083c6..56cb9282f0 100644
--- a/docs/sources/shared/reference/components/field-filter-block.md
+++ b/docs/sources/shared/reference/components/field-filter-block.md
@@ -6,15 +6,15 @@ headless: true
 
 The following attributes are supported:
 
-Name    | Type     | Description                                                   | Default  | Required
---------|----------|---------------------------------------------------------------|----------|---------
-`key`   | `string` | The key or name of the field or labels that a filter can use. |          | yes
-`value` | `string` | The value associated with the key that a filter can use.      |          | yes
-`op`    | `string` | The filter operation to apply on the given key: value pair.   | `equals` | no
+| Name    | Type     | Description                                                   | Default  | Required |
+| ------- | -------- | ------------------------------------------------------------- | -------- | -------- |
+| `key`   | `string` | The key or name of the field or labels that a filter can use. |          | yes      |
+| `value` | `string` | The value associated with the key that a filter can use.      |          | yes      |
+| `op`    | `string` | The filter operation to apply on the given key: value pair.   | `equals` | no       |
 
 For `op`, the following values are allowed:
 
-* `equals`: The field value must equal the provided value.
-* `not-equals`: The field value must not be equal to the provided value.
-* `exists`: The field value must exist. Only applicable to `annotation` fields.
-* `does-not-exist`: The field value must not exist. Only applicable to `annotation` fields.
+- `equals`: The field value must equal the provided value.
+- `not-equals`: The field value must not be equal to the provided value.
+- `exists`: The field value must exist. Only applicable to `annotation` fields.
+- `does-not-exist`: The field value must not exist. Only applicable to `annotation` fields.
diff --git a/docs/sources/shared/reference/components/http-client-config-block.md b/docs/sources/shared/reference/components/http-client-config-block.md
index 8a41b288d1..a2abc6f945 100644
--- a/docs/sources/shared/reference/components/http-client-config-block.md
+++ b/docs/sources/shared/reference/components/http-client-config-block.md
@@ -4,16 +4,16 @@ description: Shared content, http client config block
 headless: true
 ---
 
-Name                     | Type                | Description                                                   | Default | Required
--------------------------|---------------------|---------------------------------------------------------------|---------|---------
-`bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.          |         | no
-`bearer_token`           | `secret`            | Bearer token to authenticate with.                            |         | no
-`enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                      | `true`  | no
-`follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.  | `true`  | no
-`proxy_url`              | `string`            | HTTP proxy to send requests through.                          |         | no
-`no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. | | no
-`proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.         | `false` | no
-`proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests. |         | no
+| Name                     | Type                | Description                                                                                      | Default | Required |
+| ------------------------ | ------------------- | ------------------------------------------------------------------------------------------------ | ------- | -------- |
+| `bearer_token_file`      | `string`            | File containing a bearer token to authenticate with.                                             |         | no       |
+| `bearer_token`           | `secret`            | Bearer token to authenticate with.                                                               |         | no       |
+| `enable_http2`           | `bool`              | Whether HTTP2 is supported for requests.                                                         | `true`  | no       |
+| `follow_redirects`       | `bool`              | Whether redirects returned by the server should be followed.                                     | `true`  | no       |
+| `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
+| `no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. |         | no       |
+| `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
+| `proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests.                                    |         | no       |
 
 `bearer_token`, `bearer_token_file`, `basic_auth`, `authorization`, and `oauth2` are mutually exclusive, and only one can be provided inside of a `http_client_config` block.
 
diff --git a/docs/sources/shared/reference/components/loki-server-grpc.md b/docs/sources/shared/reference/components/loki-server-grpc.md
index 7308d01420..87be677e2e 100644
--- a/docs/sources/shared/reference/components/loki-server-grpc.md
+++ b/docs/sources/shared/reference/components/loki-server-grpc.md
@@ -8,14 +8,14 @@ The `grpc` block configures the gRPC server.
 
 You can use the following arguments to configure the `grpc` block. Any omitted fields take their default values.
 
-Name                            | Type       | Description                                                                                                         | Default      | Required
---------------------------------|------------|---------------------------------------------------------------------------------------------------------------------|--------------|---------
-`conn_limit`                    | `int`      | Maximum number of simultaneous HTTP connections. Defaults to no limit.                                              | `0`          | no
-`listen_address`                | `string`   | Network address on which the server listens for new connections. It defaults to accepting all incoming connections. | `""`         | no
-`listen_port`                   | `int`      | Port number on which the server listens for new connections. Defaults to a random free port.                        | `0`          | no
-`max_connection_age_grace`      | `duration` | An additive period after `max_connection_age` after which the connection is forcibly closed.                        | `"infinity"` | no
-`max_connection_age`            | `duration` | The duration for the maximum time a connection may exist before it's closed.                                        | `"infinity"` | no
-`max_connection_idle`           | `duration` | The duration after which an idle connection is closed.                                                              | `"infinity"` | no
-`server_max_concurrent_streams` | `int`      | Limit on the number of concurrent streams for gRPC calls (0 = unlimited).                                           | `100`        | no
-`server_max_recv_msg_size`      | `int`      | Limit on the size of a gRPC message this server can receive (bytes).                                                | `4MB`        | no
-`server_max_send_msg_size`      | `int`      | Limit on the size of a gRPC message this server can send (bytes).                                                   | `4MB`        | no
+| Name                            | Type       | Description                                                                                                         | Default      | Required |
+| ------------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------- | ------------ | -------- |
+| `conn_limit`                    | `int`      | Maximum number of simultaneous HTTP connections. Defaults to no limit.                                              | `0`          | no       |
+| `listen_address`                | `string`   | Network address on which the server listens for new connections. It defaults to accepting all incoming connections. | `""`         | no       |
+| `listen_port`                   | `int`      | Port number on which the server listens for new connections. Defaults to a random free port.                        | `0`          | no       |
+| `max_connection_age_grace`      | `duration` | An additive period after `max_connection_age` after which the connection is forcibly closed.                        | `"infinity"` | no       |
+| `max_connection_age`            | `duration` | The duration for the maximum time a connection may exist before it's closed.                                        | `"infinity"` | no       |
+| `max_connection_idle`           | `duration` | The duration after which an idle connection is closed.                                                              | `"infinity"` | no       |
+| `server_max_concurrent_streams` | `int`      | Limit on the number of concurrent streams for gRPC calls (0 = unlimited).                                           | `100`        | no       |
+| `server_max_recv_msg_size`      | `int`      | Limit on the size of a gRPC message this server can receive (bytes).                                                | `4MB`        | no       |
+| `server_max_send_msg_size`      | `int`      | Limit on the size of a gRPC message this server can send (bytes).                                                   | `4MB`        | no       |
diff --git a/docs/sources/shared/reference/components/loki-server-http.md b/docs/sources/shared/reference/components/loki-server-http.md
index e0510dcd70..2871e53b0a 100644
--- a/docs/sources/shared/reference/components/loki-server-http.md
+++ b/docs/sources/shared/reference/components/loki-server-http.md
@@ -8,11 +8,11 @@ The `http` block configures the HTTP server.
 
 You can use the following arguments to configure the `http` block. Any omitted fields take their default values.
 
-Name                   | Type       | Description                                                                                                      | Default  | Required
------------------------|------------|------------------------------------------------------------------------------------------------------------------|----------|---------
-`conn_limit`           | `int`      | Maximum number of simultaneous HTTP connections. Defaults to no limit.                                           | `0`      | no
-`listen_address`       | `string`   | Network address on which the server listens for new connections. Defaults to accepting all incoming connections. | `""`     | no
-`listen_port`          | `int`      | Port number on which the server listens for new connections.                                                     | `8080`   | no
-`server_idle_timeout`  | `duration` | Idle timeout for HTTP server.                                                                                    | `"120s"` | no
-`server_read_timeout`  | `duration` | Read timeout for HTTP server.                                                                                    | `"30s"`  | no
-`server_write_timeout` | `duration` | Write timeout for HTTP server.                                                                                   | `"30s"`  | no
+| Name                   | Type       | Description                                                                                                      | Default  | Required |
+| ---------------------- | ---------- | ---------------------------------------------------------------------------------------------------------------- | -------- | -------- |
+| `conn_limit`           | `int`      | Maximum number of simultaneous HTTP connections. Defaults to no limit.                                           | `0`      | no       |
+| `listen_address`       | `string`   | Network address on which the server listens for new connections. Defaults to accepting all incoming connections. | `""`     | no       |
+| `listen_port`          | `int`      | Port number on which the server listens for new connections.                                                     | `8080`   | no       |
+| `server_idle_timeout`  | `duration` | Idle timeout for HTTP server.                                                                                    | `"120s"` | no       |
+| `server_read_timeout`  | `duration` | Read timeout for HTTP server.                                                                                    | `"30s"`  | no       |
+| `server_write_timeout` | `duration` | Write timeout for HTTP server.                                                                                   | `"30s"`  | no       |
diff --git a/docs/sources/shared/reference/components/managed_identity-block.md b/docs/sources/shared/reference/components/managed_identity-block.md
index ed36d87ee4..79beed285f 100644
--- a/docs/sources/shared/reference/components/managed_identity-block.md
+++ b/docs/sources/shared/reference/components/managed_identity-block.md
@@ -4,15 +4,15 @@ description: Shared content, managed_identity block
 headless: true
 ---
 
-Name        | Type     | Description                                             | Default | Required
-------------|----------|---------------------------------------------------------|---------|---------
-`client_id` | `string` | Client ID of the managed identity used to authenticate. |         | yes
+| Name        | Type     | Description                                             | Default | Required |
+| ----------- | -------- | ------------------------------------------------------- | ------- | -------- |
+| `client_id` | `string` | Client ID of the managed identity used to authenticate. |         | yes      |
 
 `client_id` should be a valid [UUID][] in one of the supported formats:
 
-* `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`
-* `urn:uuid:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`
-* Microsoft encoding: `{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}`
-* Raw hex encoding: `xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx`
+- `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`
+- `urn:uuid:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`
+- Microsoft encoding: `{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}`
+- Raw hex encoding: `xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx`
 
 [UUID]: https://en.wikipedia.org/wiki/Universally_unique_identifier
diff --git a/docs/sources/shared/reference/components/match-properties-block.md b/docs/sources/shared/reference/components/match-properties-block.md
index 0b16d7042e..197e0ae29b 100644
--- a/docs/sources/shared/reference/components/match-properties-block.md
+++ b/docs/sources/shared/reference/components/match-properties-block.md
@@ -6,15 +6,15 @@ headless: true
 
 The following arguments are supported:
 
-Name                 | Type           | Description                                                                    | Default | Required
----------------------|----------------|--------------------------------------------------------------------------------|---------|---------
-`match_type`         | `string`       | Controls how items to match against are interpreted.                           |         | yes
-`log_bodies`         | `list(string)` | A list of strings that the LogRecord's body field must match against.          | `[]`    | no
-`log_severity_texts` | `list(string)` | A list of strings that the LogRecord's severity text field must match against. | `[]`    | no
-`metric_names`       | `list(string)` | A list of strings to match the metric name against.                            | `[]`    | no
-`services`           | `list(string)` | A list of items to match the service name against.                             | `[]`    | no
-`span_kinds`         | `list(string)` | A list of items to match the span kind against.                                | `[]`    | no
-`span_names`         | `list(string)` | A list of items to match the span name against.                                | `[]`    | no
+| Name                 | Type           | Description                                                                    | Default | Required |
+| -------------------- | -------------- | ------------------------------------------------------------------------------ | ------- | -------- |
+| `match_type`         | `string`       | Controls how items to match against are interpreted.                           |         | yes      |
+| `log_bodies`         | `list(string)` | A list of strings that the LogRecord's body field must match against.          | `[]`    | no       |
+| `log_severity_texts` | `list(string)` | A list of strings that the LogRecord's severity text field must match against. | `[]`    | no       |
+| `metric_names`       | `list(string)` | A list of strings to match the metric name against.                            | `[]`    | no       |
+| `services`           | `list(string)` | A list of items to match the service name against.                             | `[]`    | no       |
+| `span_kinds`         | `list(string)` | A list of items to match the span kind against.                                | `[]`    | no       |
+| `span_names`         | `list(string)` | A list of items to match the span name against.                                | `[]`    | no       |
 
 `match_type` is required and must be set to either `"regexp"` or `"strict"`.
 
diff --git a/docs/sources/shared/reference/components/oauth2-block.md b/docs/sources/shared/reference/components/oauth2-block.md
index 75515bbecf..764c70484e 100644
--- a/docs/sources/shared/reference/components/oauth2-block.md
+++ b/docs/sources/shared/reference/components/oauth2-block.md
@@ -4,18 +4,18 @@ description: Shared content, oauth2 block
 headless: true
 ---
 
-Name                     | Type                | Description                                                   | Default | Required
--------------------------|---------------------|---------------------------------------------------------------|---------|---------
-`client_id`              | `string`            | OAuth2 client ID.                                             |         | no
-`client_secret_file`     | `string`            | File containing the OAuth2 client secret.                     |         | no
-`client_secret`          | `secret`            | OAuth2 client secret.                                         |         | no
-`endpoint_params`        | `map(string)`       | Optional parameters to append to the token URL.               |         | no
-`proxy_url`              | `string`            | HTTP proxy to send requests through.                          |         | no
-`no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. | | no
-`proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.         | `false` | no
-`proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests. |         | no
-`scopes`                 | `list(string)`      | List of scopes to authenticate with.                          |         | no
-`token_url`              | `string`            | URL to fetch the token from.                                  |         | no
+| Name                     | Type                | Description                                                                                      | Default | Required |
+| ------------------------ | ------------------- | ------------------------------------------------------------------------------------------------ | ------- | -------- |
+| `client_id`              | `string`            | OAuth2 client ID.                                                                                |         | no       |
+| `client_secret_file`     | `string`            | File containing the OAuth2 client secret.                                                        |         | no       |
+| `client_secret`          | `secret`            | OAuth2 client secret.                                                                            |         | no       |
+| `endpoint_params`        | `map(string)`       | Optional parameters to append to the token URL.                                                  |         | no       |
+| `proxy_url`              | `string`            | HTTP proxy to send requests through.                                                             |         | no       |
+| `no_proxy`               | `string`            | Comma-separated list of IP addresses, CIDR notations, and domain names to exclude from proxying. |         | no       |
+| `proxy_from_environment` | `bool`              | Use the proxy URL indicated by environment variables.                                            | `false` | no       |
+| `proxy_connect_header`   | `map(list(secret))` | Specifies headers to send to proxies during CONNECT requests.                                    |         | no       |
+| `scopes`                 | `list(string)`      | List of scopes to authenticate with.                                                             |         | no       |
+| `token_url`              | `string`            | URL to fetch the token from.                                                                     |         | no       |
 
 `client_secret` and `client_secret_file` are mutually exclusive, and only one can be provided inside an `oauth2` block.
 
diff --git a/docs/sources/shared/reference/components/otelcol-compression-field.md b/docs/sources/shared/reference/components/otelcol-compression-field.md
index f085af50aa..794141e995 100644
--- a/docs/sources/shared/reference/components/otelcol-compression-field.md
+++ b/docs/sources/shared/reference/components/otelcol-compression-field.md
@@ -7,10 +7,10 @@ headless: true
 By default, requests are compressed with Gzip.
 The `compression` argument controls which compression mechanism to use. Supported strings are:
 
-* `"gzip"`
-* `"zlib"`
-* `"deflate"`
-* `"snappy"`
-* `"zstd"`
+- `"gzip"`
+- `"zlib"`
+- `"deflate"`
+- `"snappy"`
+- `"zstd"`
 
 If you set `compression` to `"none"` or an empty string `""`, the requests aren't compressed.
diff --git a/docs/sources/shared/reference/components/otelcol-debug-metrics-block.md b/docs/sources/shared/reference/components/otelcol-debug-metrics-block.md
index 94315e4f7c..6ea69bb9bd 100644
--- a/docs/sources/shared/reference/components/otelcol-debug-metrics-block.md
+++ b/docs/sources/shared/reference/components/otelcol-debug-metrics-block.md
@@ -8,10 +8,10 @@ The `debug_metrics` block configures the metrics that this component generates t
 
 The following arguments are supported:
 
-Name                               | Type      | Description                                          | Default | Required
------------------------------------|-----------|------------------------------------------------------|---------|---------
-`disable_high_cardinality_metrics` | `boolean` | Whether to disable certain high cardinality metrics. | `true`  | no
-`level` | `string` |  Controls the level of detail for metrics emitted by the wrapped collector. | `"detailed"`  | no
+| Name                               | Type      | Description                                                                | Default      | Required |
+| ---------------------------------- | --------- | -------------------------------------------------------------------------- | ------------ | -------- |
+| `disable_high_cardinality_metrics` | `boolean` | Whether to disable certain high cardinality metrics.                       | `true`       | no       |
+| `level`                            | `string`  | Controls the level of detail for metrics emitted by the wrapped collector. | `"detailed"` | no       |
 
 `disable_high_cardinality_metrics` is the Grafana Alloy equivalent to the `telemetry.disableHighCardinalityMetrics` feature gate in the OpenTelemetry Collector.
 It removes attributes that could cause high cardinality metrics.
diff --git a/docs/sources/shared/reference/components/otelcol-filter-attribute-block.md b/docs/sources/shared/reference/components/otelcol-filter-attribute-block.md
index c939fe0188..685c384625 100644
--- a/docs/sources/shared/reference/components/otelcol-filter-attribute-block.md
+++ b/docs/sources/shared/reference/components/otelcol-filter-attribute-block.md
@@ -5,16 +5,16 @@ headless: true
 
 This block specifies an attribute to match against:
 
-* More than one `attribute` block can be defined.
-* Only `match_type = "strict"` is allowed if `attribute` is specified.
-* All `attribute` blocks must match exactly for a match to occur.
+- More than one `attribute` block can be defined.
+- Only `match_type = "strict"` is allowed if `attribute` is specified.
+- All `attribute` blocks must match exactly for a match to occur.
 
 The following arguments are supported:
 
-Name    | Type     | Description                           | Default | Required
---------|----------|---------------------------------------|---------|---------
-`key`   | `string` | The attribute key.                    |         | yes
-`value` | `any`    | The attribute value to match against. |         | no
+| Name    | Type     | Description                           | Default | Required |
+| ------- | -------- | ------------------------------------- | ------- | -------- |
+| `key`   | `string` | The attribute key.                    |         | yes      |
+| `value` | `any`    | The attribute value to match against. |         | no       |
 
 If `value` isn't set, any value will match.
 The type of `value` could be a number, a string, or a boolean.
diff --git a/docs/sources/shared/reference/components/otelcol-filter-library-block.md b/docs/sources/shared/reference/components/otelcol-filter-library-block.md
index 2467e466b1..c4141839df 100644
--- a/docs/sources/shared/reference/components/otelcol-filter-library-block.md
+++ b/docs/sources/shared/reference/components/otelcol-filter-library-block.md
@@ -5,15 +5,15 @@ headless: true
 
 This block specifies properties to match the implementation library against:
 
-* More than one `library` block can be defined.
-* A match occurs if the span's implementation library matches at least one `library` block.
+- More than one `library` block can be defined.
+- A match occurs if the span's implementation library matches at least one `library` block.
 
 The following arguments are supported:
 
-Name      | Type     | Description                   | Default | Required
-----------|----------|-------------------------------|---------|---------
-`name`    | `string` | The attribute key.            |         | yes
-`version` | `string` | The version to match against. | null    | no
+| Name      | Type     | Description                   | Default | Required |
+| --------- | -------- | ----------------------------- | ------- | -------- |
+| `name`    | `string` | The attribute key.            |         | yes      |
+| `version` | `string` | The version to match against. | null    | no       |
 
 If `version` is unset, any version matches.
 If `version` is set to an empty string, it only matches a library version, which is also an empty string.
diff --git a/docs/sources/shared/reference/components/otelcol-filter-log-severity-block.md b/docs/sources/shared/reference/components/otelcol-filter-log-severity-block.md
index c0a5b02daf..08ca8274a5 100644
--- a/docs/sources/shared/reference/components/otelcol-filter-log-severity-block.md
+++ b/docs/sources/shared/reference/components/otelcol-filter-log-severity-block.md
@@ -7,41 +7,41 @@ This block defines how to match based on a log record's SeverityNumber field.
 
 The following arguments are supported:
 
-Name              | Type     | Description                                   | Default | Required
-------------------|----------|-----------------------------------------------|---------|---------
-`match_undefined` | `bool`   | Whether logs with "undefined" severity match. |         | yes
-`min`             | `string` | The lowest severity that may be matched.      |         | yes
+| Name              | Type     | Description                                   | Default | Required |
+| ----------------- | -------- | --------------------------------------------- | ------- | -------- |
+| `match_undefined` | `bool`   | Whether logs with "undefined" severity match. |         | yes      |
+| `min`             | `string` | The lowest severity that may be matched.      |         | yes      |
 
 If `match_undefined` is true, entries with undefined severity will match.
 
 The following table lists the severities supported by OTel.
 The value for `min` should be one of the values in the "Log Severity" column.
 
-Log Severity | Severity number
------------- | ---------------
-TRACE        | 1
-TRACE2       | 2
-TRACE3       | 3
-TRACE4       | 4
-DEBUG        | 5
-DEBUG2       | 6
-DEBUG3       | 7
-DEBUG4       | 8
-INFO         | 9
-INFO2        | 10
-INFO3        | 11
-INFO4        | 12
-WARN         | 13
-WARN2        | 14
-WARN3        | 15
-WARN4        | 16
-ERROR        | 17
-ERROR2       | 18
-ERROR3       | 19
-ERROR4       | 20
-FATAL        | 21
-FATAL2       | 22
-FATAL3       | 23
-FATAL4       | 24
+| Log Severity | Severity number |
+| ------------ | --------------- |
+| TRACE        | 1               |
+| TRACE2       | 2               |
+| TRACE3       | 3               |
+| TRACE4       | 4               |
+| DEBUG        | 5               |
+| DEBUG2       | 6               |
+| DEBUG3       | 7               |
+| DEBUG4       | 8               |
+| INFO         | 9               |
+| INFO2        | 10              |
+| INFO3        | 11              |
+| INFO4        | 12              |
+| WARN         | 13              |
+| WARN2        | 14              |
+| WARN3        | 15              |
+| WARN4        | 16              |
+| ERROR        | 17              |
+| ERROR2       | 18              |
+| ERROR3       | 19              |
+| ERROR4       | 20              |
+| FATAL        | 21              |
+| FATAL2       | 22              |
+| FATAL3       | 23              |
+| FATAL4       | 24              |
 
 For example, if the `min` attribute in the `log_severity` block is "INFO", then INFO, WARN, ERROR, and FATAL logs will match.
diff --git a/docs/sources/shared/reference/components/otelcol-filter-regexp-block.md b/docs/sources/shared/reference/components/otelcol-filter-regexp-block.md
index 706de5f28d..e3fba84862 100644
--- a/docs/sources/shared/reference/components/otelcol-filter-regexp-block.md
+++ b/docs/sources/shared/reference/components/otelcol-filter-regexp-block.md
@@ -8,10 +8,10 @@ It configures a Least Recently Used (LRU) cache.
 
 The following arguments are supported:
 
-Name                    | Type   | Description                                                           | Default | Required
-------------------------|--------|-----------------------------------------------------------------------|---------|---------
-`cache_enabled`         | `bool` | Determines whether match results are LRU cached.                      | `false` | no
-`cache_max_num_entries` | `int`  | The max number of entries of the LRU cache that stores match results. | `0`     | no
+| Name                    | Type   | Description                                                           | Default | Required |
+| ----------------------- | ------ | --------------------------------------------------------------------- | ------- | -------- |
+| `cache_enabled`         | `bool` | Determines whether match results are LRU cached.                      | `false` | no       |
+| `cache_max_num_entries` | `int`  | The max number of entries of the LRU cache that stores match results. | `0`     | no       |
 
 Enabling `cache_enabled` could make subsequent matches faster.
 Cache size is unlimited unless `cache_max_num_entries` is also specified.
diff --git a/docs/sources/shared/reference/components/otelcol-filter-resource-block.md b/docs/sources/shared/reference/components/otelcol-filter-resource-block.md
index 5d036cfe99..b0256f75e3 100644
--- a/docs/sources/shared/reference/components/otelcol-filter-resource-block.md
+++ b/docs/sources/shared/reference/components/otelcol-filter-resource-block.md
@@ -5,15 +5,15 @@ headless: true
 
 This block specifies items to match the resources against:
 
-* More than one `resource` block can be defined.
-* A match occurs if the input data resources match at least one `resource` block.
+- More than one `resource` block can be defined.
+- A match occurs if the input data resources match at least one `resource` block.
 
 The following arguments are supported:
 
-Name    | Type     | Description                          | Default | Required
---------|----------|--------------------------------------|---------|---------
-`key`   | `string` | The resource key.                    |         | yes
-`value` | `any`    | The resource value to match against. |         | no
+| Name    | Type     | Description                          | Default | Required |
+| ------- | -------- | ------------------------------------ | ------- | -------- |
+| `key`   | `string` | The resource key.                    |         | yes      |
+| `value` | `any`    | The resource value to match against. |         | no       |
 
 If `value` isn't set, any value will match.
 The type of `value` could be a number, a string, or a boolean.
diff --git a/docs/sources/shared/reference/components/otelcol-grpc-balancer-name.md b/docs/sources/shared/reference/components/otelcol-grpc-balancer-name.md
index fc63d3c820..626684756b 100644
--- a/docs/sources/shared/reference/components/otelcol-grpc-balancer-name.md
+++ b/docs/sources/shared/reference/components/otelcol-grpc-balancer-name.md
@@ -5,9 +5,9 @@ headless: true
 
 The supported values for `balancer_name` are listed in the gRPC documentation on [Load balancing][]:
 
-* `pick_first`: Tries to connect to the first address, uses it for all RPCs if it connects, or tries the next address if it fails (and keeps doing that until one connection is successful).
+- `pick_first`: Tries to connect to the first address, uses it for all RPCs if it connects, or tries the next address if it fails (and keeps doing that until one connection is successful).
   Because of this, all the RPCs will be sent to the same backend.
-* `round_robin`: Connects to all the addresses it sees and sends an RPC to each backend one at a time in order.
+- `round_robin`: Connects to all the addresses it sees and sends an RPC to each backend one at a time in order.
   For example, the first RPC is sent to backend-1, the second RPC is sent to backend-2, and the third RPC is sent to backend-1.
 
 [Load balancing]: https://github.com/grpc/grpc-go/blob/master/examples/features/load_balancing/README.md
diff --git a/docs/sources/shared/reference/components/otelcol-kafka-authentication-kerberos.md b/docs/sources/shared/reference/components/otelcol-kafka-authentication-kerberos.md
index 4d4dea0b81..fbfd1bb7e8 100644
--- a/docs/sources/shared/reference/components/otelcol-kafka-authentication-kerberos.md
+++ b/docs/sources/shared/reference/components/otelcol-kafka-authentication-kerberos.md
@@ -7,16 +7,16 @@ The `kerberos` block configures Kerberos authentication against the Kafka broker
 
 The following arguments are supported:
 
-Name                       | Type     | Description                                                     | Default | Required
----------------------------|----------|-----------------------------------------------------------------|---------|---------
-`service_name`             | `string` | Kerberos service name.                                          |         | no
-`realm`                    | `string` | Kerberos realm.                                                 |         | no
-`use_keytab`               | `string` | Enables using keytab instead of password.                       |         | no
-`username`                 | `string` | Kerberos username to authenticate as.                           |         | yes
-`password`                 | `secret` | Kerberos password to authenticate with.                         |         | no
-`config_file`              | `string` | Path to Kerberos location, for example, `/etc/krb5.conf`.       |         | no
-`keytab_file`              | `string` | Path to keytab file, for example, `/etc/security/kafka.keytab`. |         | no
-`disable_fast_negotiation` | `bool`   | Disable PA-FX-FAST negotiation.                                 | `false` | no
+| Name                       | Type     | Description                                                     | Default | Required |
+| -------------------------- | -------- | --------------------------------------------------------------- | ------- | -------- |
+| `service_name`             | `string` | Kerberos service name.                                          |         | no       |
+| `realm`                    | `string` | Kerberos realm.                                                 |         | no       |
+| `use_keytab`               | `string` | Enables using keytab instead of password.                       |         | no       |
+| `username`                 | `string` | Kerberos username to authenticate as.                           |         | yes      |
+| `password`                 | `secret` | Kerberos password to authenticate with.                         |         | no       |
+| `config_file`              | `string` | Path to Kerberos location, for example, `/etc/krb5.conf`.       |         | no       |
+| `keytab_file`              | `string` | Path to keytab file, for example, `/etc/security/kafka.keytab`. |         | no       |
+| `disable_fast_negotiation` | `bool`   | Disable PA-FX-FAST negotiation.                                 | `false` | no       |
 
 When `use_keytab` is `false`, the `password` argument is required.
 When `use_keytab` is `true`, the file pointed to by the `keytab_file` argument is used for authentication instead.
diff --git a/docs/sources/shared/reference/components/otelcol-kafka-authentication-plaintext.md b/docs/sources/shared/reference/components/otelcol-kafka-authentication-plaintext.md
index cdc99b1dfc..7561cb456b 100644
--- a/docs/sources/shared/reference/components/otelcol-kafka-authentication-plaintext.md
+++ b/docs/sources/shared/reference/components/otelcol-kafka-authentication-plaintext.md
@@ -7,7 +7,7 @@ The `plaintext` block configures plain text authentication against Kafka brokers
 
 The following arguments are supported:
 
-Name       | Type     | Description                                    | Default | Required
------------|----------|------------------------------------------------|---------|---------
-`username` | `string` | Username to use for plain text authentication. |         | yes
-`password` | `secret` | Password to use for plain text authentication. |         | yes
+| Name       | Type     | Description                                    | Default | Required |
+| ---------- | -------- | ---------------------------------------------- | ------- | -------- |
+| `username` | `string` | Username to use for plain text authentication. |         | yes      |
+| `password` | `secret` | Password to use for plain text authentication. |         | yes      |
diff --git a/docs/sources/shared/reference/components/otelcol-kafka-authentication-sasl-aws_msk.md b/docs/sources/shared/reference/components/otelcol-kafka-authentication-sasl-aws_msk.md
index ca705a92ed..3e35bb1cd5 100644
--- a/docs/sources/shared/reference/components/otelcol-kafka-authentication-sasl-aws_msk.md
+++ b/docs/sources/shared/reference/components/otelcol-kafka-authentication-sasl-aws_msk.md
@@ -7,7 +7,7 @@ The `aws_msk` block configures extra parameters for SASL authentication when usi
 
 The following arguments are supported:
 
-Name          | Type     | Description                                   | Default | Required
---------------|----------|-----------------------------------------------|---------|---------
-`region`      | `string` | AWS region the MSK cluster is based in.       |         | yes
-`broker_addr` | `string` | MSK address to connect to for authentication. |         | yes
+| Name          | Type     | Description                                   | Default | Required |
+| ------------- | -------- | --------------------------------------------- | ------- | -------- |
+| `region`      | `string` | AWS region the MSK cluster is based in.       |         | yes      |
+| `broker_addr` | `string` | MSK address to connect to for authentication. |         | yes      |
diff --git a/docs/sources/shared/reference/components/otelcol-kafka-authentication-sasl.md b/docs/sources/shared/reference/components/otelcol-kafka-authentication-sasl.md
index ced8807098..dcec36bba9 100644
--- a/docs/sources/shared/reference/components/otelcol-kafka-authentication-sasl.md
+++ b/docs/sources/shared/reference/components/otelcol-kafka-authentication-sasl.md
@@ -7,19 +7,19 @@ The `sasl` block configures SASL authentication against Kafka brokers.
 
 The following arguments are supported:
 
-Name        | Type     | Description                                              | Default | Required
-------------|----------|----------------------------------------------------------|---------|---------
-`username`  | `string` | Username to use for SASL authentication.                 |         | yes
-`password`  | `secret` | Password to use for SASL authentication.                 |         | yes
-`mechanism` | `string` | SASL mechanism to use when authenticating.               |         | yes
-`version`   | `number` | Version of the SASL Protocol to use when authenticating. | `0`     | no
+| Name        | Type     | Description                                              | Default | Required |
+| ----------- | -------- | -------------------------------------------------------- | ------- | -------- |
+| `username`  | `string` | Username to use for SASL authentication.                 |         | yes      |
+| `password`  | `secret` | Password to use for SASL authentication.                 |         | yes      |
+| `mechanism` | `string` | SASL mechanism to use when authenticating.               |         | yes      |
+| `version`   | `number` | Version of the SASL Protocol to use when authenticating. | `0`     | no       |
 
 The `mechanism` argument can be set to one of the following strings:
 
-* `"PLAIN"`
-* `"AWS_MSK_IAM"`
-* `"SCRAM-SHA-256"`
-* `"SCRAM-SHA-512"`
+- `"PLAIN"`
+- `"AWS_MSK_IAM"`
+- `"SCRAM-SHA-256"`
+- `"SCRAM-SHA-512"`
 
 When `mechanism` is set to `"AWS_MSK_IAM"`, the `aws_msk` child block must also be provided.
 
diff --git a/docs/sources/shared/reference/components/otelcol-kafka-metadata-retry.md b/docs/sources/shared/reference/components/otelcol-kafka-metadata-retry.md
index 4b7eeab87b..d82e1f47ce 100644
--- a/docs/sources/shared/reference/components/otelcol-kafka-metadata-retry.md
+++ b/docs/sources/shared/reference/components/otelcol-kafka-metadata-retry.md
@@ -7,7 +7,7 @@ The `retry` block configures how to retry retrieving metadata when retrieval fai
 
 The following arguments are supported:
 
-Name          | Type       | Description                                      | Default   | Required
---------------|------------|--------------------------------------------------|-----------|---------
-`max_retries` | `number`   | How many times to reattempt retrieving metadata. | `3`       | no
-`backoff`     | `duration` | Time to wait between retries.                    | `"250ms"` | no
+| Name          | Type       | Description                                      | Default   | Required |
+| ------------- | ---------- | ------------------------------------------------ | --------- | -------- |
+| `max_retries` | `number`   | How many times to reattempt retrieving metadata. | `3`       | no       |
+| `backoff`     | `duration` | Time to wait between retries.                    | `"250ms"` | no       |
diff --git a/docs/sources/shared/reference/components/otelcol-kafka-metadata.md b/docs/sources/shared/reference/components/otelcol-kafka-metadata.md
index 80fde9c49c..3c78942676 100644
--- a/docs/sources/shared/reference/components/otelcol-kafka-metadata.md
+++ b/docs/sources/shared/reference/components/otelcol-kafka-metadata.md
@@ -7,9 +7,9 @@ The `metadata` block configures how to retrieve and store metadata from the Kafk
 
 The following arguments are supported:
 
-Name                 | Type   | Description                                   | Default | Required
----------------------|--------|-----------------------------------------------|---------|---------
-`include_all_topics` | `bool` | When true, maintains metadata for all topics. | `true`  | no
+| Name                 | Type   | Description                                   | Default | Required |
+| -------------------- | ------ | --------------------------------------------- | ------- | -------- |
+| `include_all_topics` | `bool` | When true, maintains metadata for all topics. | `true`  | no       |
 
 If the `include_all_topics` argument is `true`, a full set of metadata for all topics is maintained rather than the minimal set that has been necessary so far.
 Including the full set of metadata is more convenient for users but can consume a substantial amount of memory if you have many topics and partitions.
diff --git a/docs/sources/shared/reference/components/otelcol-queue-block.md b/docs/sources/shared/reference/components/otelcol-queue-block.md
index c08d6a3bd5..50ece973eb 100644
--- a/docs/sources/shared/reference/components/otelcol-queue-block.md
+++ b/docs/sources/shared/reference/components/otelcol-queue-block.md
@@ -6,11 +6,11 @@ headless: true
 
 The following arguments are supported:
 
-Name            | Type      | Description                                                                | Default | Required
-----------------|-----------|----------------------------------------------------------------------------|---------|---------
-`enabled`       | `boolean` | Enables an in-memory buffer before sending data to the client.             | `true`  | no
-`num_consumers` | `number`  | Number of readers to send batches written to the queue in parallel.        | `10`    | no
-`queue_size`    | `number`  | Maximum number of unwritten batches allowed in the queue at the same time. | `1000`  | no
+| Name            | Type      | Description                                                                | Default | Required |
+| --------------- | --------- | -------------------------------------------------------------------------- | ------- | -------- |
+| `enabled`       | `boolean` | Enables an in-memory buffer before sending data to the client.             | `true`  | no       |
+| `num_consumers` | `number`  | Number of readers to send batches written to the queue in parallel.        | `10`    | no       |
+| `queue_size`    | `number`  | Maximum number of unwritten batches allowed in the queue at the same time. | `1000`  | no       |
 
 When `enabled` is `true`, data is first written to an in-memory buffer before sending it to the configured server.
 Batches sent to the component's `input` exported field are added to the buffer as long as the number of unsent batches doesn't exceed the configured `queue_size`.
diff --git a/docs/sources/shared/reference/components/otelcol-retry-block.md b/docs/sources/shared/reference/components/otelcol-retry-block.md
index 5edc7e58c3..bdc36a25e8 100644
--- a/docs/sources/shared/reference/components/otelcol-retry-block.md
+++ b/docs/sources/shared/reference/components/otelcol-retry-block.md
@@ -6,14 +6,14 @@ headless: true
 
 The following arguments are supported:
 
-Name                   | Type       | Description                                            | Default | Required
------------------------|------------|--------------------------------------------------------|---------|---------
-`enabled`              | `boolean`  | Enables retrying failed requests.                      | `true`  | no
-`initial_interval`     | `duration` | Initial time to wait before retrying a failed request. | `"5s"`  | no
-`max_elapsed_time`     | `duration` | Maximum time to wait before discarding a failed batch. | `"5m"`  | no
-`max_interval`         | `duration` | Maximum time to wait between retries.                  | `"30s"` | no
-`multiplier`           | `number`   | Factor to grow wait time before retrying.              | `1.5`   | no
-`randomization_factor` | `number`   | Factor to randomize wait time before retrying.         | `0.5`   | no
+| Name                   | Type       | Description                                            | Default | Required |
+| ---------------------- | ---------- | ------------------------------------------------------ | ------- | -------- |
+| `enabled`              | `boolean`  | Enables retrying failed requests.                      | `true`  | no       |
+| `initial_interval`     | `duration` | Initial time to wait before retrying a failed request. | `"5s"`  | no       |
+| `max_elapsed_time`     | `duration` | Maximum time to wait before discarding a failed batch. | `"5m"`  | no       |
+| `max_interval`         | `duration` | Maximum time to wait between retries.                  | `"30s"` | no       |
+| `multiplier`           | `number`   | Factor to grow wait time before retrying.              | `1.5`   | no       |
+| `randomization_factor` | `number`   | Factor to randomize wait time before retrying.         | `0.5`   | no       |
 
 When `enabled` is `true`, failed batches are retried after a given interval.
 The `initial_interval` argument specifies how long to wait before the first retry attempt.
diff --git a/docs/sources/shared/reference/components/otelcol-tls-client-block.md b/docs/sources/shared/reference/components/otelcol-tls-client-block.md
index 424a95fc91..c740c4e5ed 100644
--- a/docs/sources/shared/reference/components/otelcol-tls-client-block.md
+++ b/docs/sources/shared/reference/components/otelcol-tls-client-block.md
@@ -6,22 +6,22 @@ headless: true
 
 The following arguments are supported:
 
-Name                           | Type           | Description                                                                                  | Default     | Required
--------------------------------|----------------|----------------------------------------------------------------------------------------------|-------------|---------
-`ca_file`                      | `string`       | Path to the CA file.                                                                         |             | no
-`ca_pem`                       | `string`       | CA PEM-encoded text to validate the server with.                                             |             | no
-`cert_file`                    | `string`       | Path to the TLS certificate.                                                                 |             | no
-`cert_pem`                     | `string`       | Certificate PEM-encoded text for client authentication.                                      |             | no
-`insecure_skip_verify`         | `boolean`      | Ignores insecure server TLS certificates.                                                    |             | no
-`include_system_ca_certs_pool` | `boolean`      | Whether to load the system certificate authorities pool alongside the certificate authority. | `false`     | no
-`insecure`                     | `boolean`      | Disables TLS when connecting to the configured server.                                       |             | no
-`key_file`                     | `string`       | Path to the TLS certificate key.                                                             |             | no
-`key_pem`                      | `secret`       | Key PEM-encoded text for client authentication.                                              |             | no
-`max_version`                  | `string`       | Maximum acceptable TLS version for connections.                                              | `"TLS 1.3"` | no
-`min_version`                  | `string`       | Minimum acceptable TLS version for connections.                                              | `"TLS 1.2"` | no
-`cipher_suites`                | `list(string)` | A list of TLS cipher suites that the TLS transport can use.                                  | `[]`        | no
-`reload_interval`              | `duration`     | The duration after which the certificate is reloaded.                                        | `"0s"`      | no
-`server_name`                  | `string`       | Verifies the hostname of server certificates when set.                                       |             | no
+| Name                           | Type           | Description                                                                                  | Default     | Required |
+| ------------------------------ | -------------- | -------------------------------------------------------------------------------------------- | ----------- | -------- |
+| `ca_file`                      | `string`       | Path to the CA file.                                                                         |             | no       |
+| `ca_pem`                       | `string`       | CA PEM-encoded text to validate the server with.                                             |             | no       |
+| `cert_file`                    | `string`       | Path to the TLS certificate.                                                                 |             | no       |
+| `cert_pem`                     | `string`       | Certificate PEM-encoded text for client authentication.                                      |             | no       |
+| `insecure_skip_verify`         | `boolean`      | Ignores insecure server TLS certificates.                                                    |             | no       |
+| `include_system_ca_certs_pool` | `boolean`      | Whether to load the system certificate authorities pool alongside the certificate authority. | `false`     | no       |
+| `insecure`                     | `boolean`      | Disables TLS when connecting to the configured server.                                       |             | no       |
+| `key_file`                     | `string`       | Path to the TLS certificate key.                                                             |             | no       |
+| `key_pem`                      | `secret`       | Key PEM-encoded text for client authentication.                                              |             | no       |
+| `max_version`                  | `string`       | Maximum acceptable TLS version for connections.                                              | `"TLS 1.3"` | no       |
+| `min_version`                  | `string`       | Minimum acceptable TLS version for connections.                                              | `"TLS 1.2"` | no       |
+| `cipher_suites`                | `list(string)` | A list of TLS cipher suites that the TLS transport can use.                                  | `[]`        | no       |
+| `reload_interval`              | `duration`     | The duration after which the certificate is reloaded.                                        | `"0s"`      | no       |
+| `server_name`                  | `string`       | Verifies the hostname of server certificates when set.                                       |             | no       |
 
 If the server doesn't support TLS, you must set the `insecure` argument to `true`.
 
@@ -31,9 +31,9 @@ If `reload_interval` is set to `"0s"`, the certificate never reloaded.
 
 The following pairs of arguments are mutually exclusive and can't both be set simultaneously:
 
-* `ca_pem` and `ca_file`
-* `cert_pem` and `cert_file`
-* `key_pem` and `key_file`
+- `ca_pem` and `ca_file`
+- `cert_pem` and `cert_file`
+- `key_pem` and `key_file`
 
 If `cipher_suites` is left blank, a safe default list is used.
 Refer to the [Go TLS documentation][golang-tls] for a list of supported cipher suites.
diff --git a/docs/sources/shared/reference/components/otelcol-tls-server-block.md b/docs/sources/shared/reference/components/otelcol-tls-server-block.md
index 0724d9f304..049aa476e6 100644
--- a/docs/sources/shared/reference/components/otelcol-tls-server-block.md
+++ b/docs/sources/shared/reference/components/otelcol-tls-server-block.md
@@ -6,33 +6,33 @@ headless: true
 
 The following arguments are supported:
 
-Name                           | Type           | Description                                                                                  | Default     | Required
--------------------------------|----------------|----------------------------------------------------------------------------------------------|-------------|---------
-`ca_file`                      | `string`       | Path to the CA file.                                                                         |             | no
-`ca_pem`                       | `string`       | CA PEM-encoded text to validate the server with.                                             |             | no
-`cert_file`                    | `string`       | Path to the TLS certificate.                                                                 |             | no
-`cert_pem`                     | `string`       | Certificate PEM-encoded text for client authentication.                                      |             | no
-`include_system_ca_certs_pool` | `boolean`      | Whether to load the system certificate authorities pool alongside the certificate authority. | `false`     | no
-`key_file`                     | `string`       | Path to the TLS certificate key.                                                             |             | no
-`key_pem`                      | `secret`       | Key PEM-encoded text for client authentication.                                              |             | no
-`max_version`                  | `string`       | Maximum acceptable TLS version for connections.                                              | `"TLS 1.3"` | no
-`min_version`                  | `string`       | Minimum acceptable TLS version for connections.                                              | `"TLS 1.2"` | no
-`cipher_suites`                | `list(string)` | A list of TLS cipher suites that the TLS transport can use.                                  | `[]`        | no
-`reload_interval`              | `duration`     | The duration after which the certificate is reloaded.                                        | `"0s"`      | no
-`client_ca_file`               | `string`       | Path to the TLS cert to use by the server to verify a client certificate.                    |             | no
+| Name                           | Type           | Description                                                                                  | Default     | Required |
+| ------------------------------ | -------------- | -------------------------------------------------------------------------------------------- | ----------- | -------- |
+| `ca_file`                      | `string`       | Path to the CA file.                                                                         |             | no       |
+| `ca_pem`                       | `string`       | CA PEM-encoded text to validate the server with.                                             |             | no       |
+| `cert_file`                    | `string`       | Path to the TLS certificate.                                                                 |             | no       |
+| `cert_pem`                     | `string`       | Certificate PEM-encoded text for client authentication.                                      |             | no       |
+| `include_system_ca_certs_pool` | `boolean`      | Whether to load the system certificate authorities pool alongside the certificate authority. | `false`     | no       |
+| `key_file`                     | `string`       | Path to the TLS certificate key.                                                             |             | no       |
+| `key_pem`                      | `secret`       | Key PEM-encoded text for client authentication.                                              |             | no       |
+| `max_version`                  | `string`       | Maximum acceptable TLS version for connections.                                              | `"TLS 1.3"` | no       |
+| `min_version`                  | `string`       | Minimum acceptable TLS version for connections.                                              | `"TLS 1.2"` | no       |
+| `cipher_suites`                | `list(string)` | A list of TLS cipher suites that the TLS transport can use.                                  | `[]`        | no       |
+| `reload_interval`              | `duration`     | The duration after which the certificate is reloaded.                                        | `"0s"`      | no       |
+| `client_ca_file`               | `string`       | Path to the TLS cert to use by the server to verify a client certificate.                    |             | no       |
 
 If `reload_interval` is set to `"0s"`, the certificate never reloaded.
 
 The following pairs of arguments are mutually exclusive and can't both be set simultaneously:
 
-* `ca_pem` and `ca_file`
-* `cert_pem` and `cert_file`
-* `key_pem` and `key_file`
+- `ca_pem` and `ca_file`
+- `cert_pem` and `cert_file`
+- `key_pem` and `key_file`
 
 If `cipher_suites` is left blank, a safe default list is used.
 Refer to the [Go Cipher Suites documentation][golang-cipher-suites] for a list of supported cipher suites.
 
-`client_ca_file` sets the `ClientCA` and `ClientAuth` to `RequireAndVerifyClientCert` in the `TLSConfig`. 
+`client_ca_file` sets the `ClientCA` and `ClientAuth` to `RequireAndVerifyClientCert` in the `TLSConfig`.
 Refer to the [Go TLS documentation][golang-tls] for more information.
 
 [golang-tls]: https://godoc.org/crypto/tls#Config
diff --git a/docs/sources/shared/reference/components/output-block-logs.md b/docs/sources/shared/reference/components/output-block-logs.md
index f340cc42dc..0db0977503 100644
--- a/docs/sources/shared/reference/components/output-block-logs.md
+++ b/docs/sources/shared/reference/components/output-block-logs.md
@@ -8,9 +8,9 @@ The `output` block configures a set of components to forward resulting telemetry
 
 The following arguments are supported:
 
-Name   | Type                     | Description                        | Default | Required
--------|--------------------------|------------------------------------|---------|---------
-`logs` | `list(otelcol.Consumer)` | List of consumers to send logs to. | `[]`    | no
+| Name   | Type                     | Description                        | Default | Required |
+| ------ | ------------------------ | ---------------------------------- | ------- | -------- |
+| `logs` | `list(otelcol.Consumer)` | List of consumers to send logs to. | `[]`    | no       |
 
 You must specify the `output` block, but all its arguments are optional.
 By default, telemetry data is dropped.
diff --git a/docs/sources/shared/reference/components/output-block-metrics.md b/docs/sources/shared/reference/components/output-block-metrics.md
index ef5abdefe5..bd0b3a96b3 100644
--- a/docs/sources/shared/reference/components/output-block-metrics.md
+++ b/docs/sources/shared/reference/components/output-block-metrics.md
@@ -7,9 +7,9 @@ The `output` block configures a set of components to forward resulting telemetry
 
 The following arguments are supported:
 
-Name      | Type                     | Description                           | Default | Required
-----------|--------------------------|---------------------------------------|---------|---------
-`metrics` | `list(otelcol.Consumer)` | List of consumers to send metrics to. | `[]`    | no
+| Name      | Type                     | Description                           | Default | Required |
+| --------- | ------------------------ | ------------------------------------- | ------- | -------- |
+| `metrics` | `list(otelcol.Consumer)` | List of consumers to send metrics to. | `[]`    | no       |
 
 You must specify the `output` block, but all its arguments are optional.
 By default, telemetry data is dropped.
diff --git a/docs/sources/shared/reference/components/output-block-traces.md b/docs/sources/shared/reference/components/output-block-traces.md
index bb39d85a07..f1a82a0225 100644
--- a/docs/sources/shared/reference/components/output-block-traces.md
+++ b/docs/sources/shared/reference/components/output-block-traces.md
@@ -8,9 +8,9 @@ The `output` block configures a set of components to forward resulting telemetry
 
 The following arguments are supported:
 
-Name     | Type                     | Description                          | Default | Required
----------|--------------------------|--------------------------------------|---------|---------
-`traces` | `list(otelcol.Consumer)` | List of consumers to send traces to. | `[]`    | no
+| Name     | Type                     | Description                          | Default | Required |
+| -------- | ------------------------ | ------------------------------------ | ------- | -------- |
+| `traces` | `list(otelcol.Consumer)` | List of consumers to send traces to. | `[]`    | no       |
 
 You must specify the `output` block, but all its arguments are optional.
 By default, telemetry data is dropped.
diff --git a/docs/sources/shared/reference/components/output-block.md b/docs/sources/shared/reference/components/output-block.md
index 4d0d196a09..68922924df 100644
--- a/docs/sources/shared/reference/components/output-block.md
+++ b/docs/sources/shared/reference/components/output-block.md
@@ -8,11 +8,11 @@ The `output` block configures a set of components to forward resulting telemetry
 
 The following arguments are supported:
 
-Name      | Type                     | Description                           | Default | Required
-----------|--------------------------|---------------------------------------|---------|---------
-`logs`    | `list(otelcol.Consumer)` | List of consumers to send logs to.    | `[]`    | no
-`metrics` | `list(otelcol.Consumer)` | List of consumers to send metrics to. | `[]`    | no
-`traces`  | `list(otelcol.Consumer)` | List of consumers to send traces to.  | `[]`    | no
+| Name      | Type                     | Description                           | Default | Required |
+| --------- | ------------------------ | ------------------------------------- | ------- | -------- |
+| `logs`    | `list(otelcol.Consumer)` | List of consumers to send logs to.    | `[]`    | no       |
+| `metrics` | `list(otelcol.Consumer)` | List of consumers to send metrics to. | `[]`    | no       |
+| `traces`  | `list(otelcol.Consumer)` | List of consumers to send traces to.  | `[]`    | no       |
 
 You must specify the `output` block, but all its arguments are optional.
 By default, telemetry data is dropped.
diff --git a/docs/sources/shared/reference/components/prom-operator-scrape.md b/docs/sources/shared/reference/components/prom-operator-scrape.md
index 03f939b061..612d442d73 100644
--- a/docs/sources/shared/reference/components/prom-operator-scrape.md
+++ b/docs/sources/shared/reference/components/prom-operator-scrape.md
@@ -4,7 +4,7 @@ description: Shared content, prom operator scrape
 headless: true
 ---
 
-Name                      | Type       | Description                                                                                                                  | Default | Required
---------------------------|------------|------------------------------------------------------------------------------------------------------------------------------|---------|---------
-`default_scrape_interval` | `duration` | The default interval between scraping targets. Used as the default if the target resource doesn't provide a scrape interval. | `1m`    | no
-`default_scrape_timeout`  | `duration` | The default timeout for scrape requests. Used as the default if the target resource doesn't provide a scrape timeout.        | `10s`   | no
+| Name                      | Type       | Description                                                                                                                  | Default | Required |
+| ------------------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------- | ------- | -------- |
+| `default_scrape_interval` | `duration` | The default interval between scraping targets. Used as the default if the target resource doesn't provide a scrape interval. | `1m`    | no       |
+| `default_scrape_timeout`  | `duration` | The default timeout for scrape requests. Used as the default if the target resource doesn't provide a scrape timeout.        | `10s`   | no       |
diff --git a/docs/sources/shared/reference/components/rule-block-logs.md b/docs/sources/shared/reference/components/rule-block-logs.md
index baba7c4c7d..e951e280f3 100644
--- a/docs/sources/shared/reference/components/rule-block-logs.md
+++ b/docs/sources/shared/reference/components/rule-block-logs.md
@@ -10,29 +10,29 @@ The transformations are applied in top-down order if more than one `rule` block
 You can use the following arguments to configure a `rule`.
 All arguments are optional. Omitted fields take their default values.
 
-Name            | Type           | Description                                                                                                                          | Default | Required
-----------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------|---------|---------
-`action`        | `string`       | The relabeling action to perform.                                                                                                    | replace | no
-`modulus`       | `uint`         | A positive integer used to calculate the modulus of the hashed source label values.                                                  |         | no
-`regex`         | `string`       | A valid RE2 expression with support for parenthesized capture groups. Used to match the extracted value from the combination of the `source_label` and `separator` fields or filter labels during the `labelkeep/labeldrop/labelmap` actions. | `(.*)` | no
-`replacement`   | `string`       | The value against which a regular expression replace is performed if the regular expression matches the extracted value. Supports previously captured groups. | `"$1"`      | no
-`separator`     | `string`       | The separator used to concatenate the values present in `source_labels`.                                                             | ;       | no
-`source_labels` | `list(string)` | The list of labels whose values are to be selected. Their content is concatenated using the `separator` and matched against `regex`. |         | no
-`target_label`  | `string`       | Label to which the resulting value is written to.                                                                                    |         | no
+| Name            | Type           | Description                                                                                                                                                                                                                                   | Default | Required |
+| --------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | -------- |
+| `action`        | `string`       | The relabeling action to perform.                                                                                                                                                                                                             | replace | no       |
+| `modulus`       | `uint`         | A positive integer used to calculate the modulus of the hashed source label values.                                                                                                                                                           |         | no       |
+| `regex`         | `string`       | A valid RE2 expression with support for parenthesized capture groups. Used to match the extracted value from the combination of the `source_label` and `separator` fields or filter labels during the `labelkeep/labeldrop/labelmap` actions. | `(.*)`  | no       |
+| `replacement`   | `string`       | The value against which a regular expression replace is performed if the regular expression matches the extracted value. Supports previously captured groups.                                                                                 | `"$1"`  | no       |
+| `separator`     | `string`       | The separator used to concatenate the values present in `source_labels`.                                                                                                                                                                      | ;       | no       |
+| `source_labels` | `list(string)` | The list of labels whose values are to be selected. Their content is concatenated using the `separator` and matched against `regex`.                                                                                                          |         | no       |
+| `target_label`  | `string`       | Label to which the resulting value is written to.                                                                                                                                                                                             |         | no       |
 
 You can use the following actions:
 
-* `drop`      - Drops logs where `regex` matches the string extracted using the `source_labels` and `separator`.
-* `dropequal` - Drop targets for which the concatenated `source_labels` do match `target_label`.
-* `hashmod`   - Hashes the concatenated labels, calculates its modulo `modulus`, and writes the result to the `target_label`.
-* `keep`      - Keeps logs where `regex` matches the string extracted using the `source_labels` and `separator`.
-* `keepequal` - Drop targets for which the concatenated `source_labels` don't match `target_label`.
-* `labeldrop` - Matches `regex` against all label names. Any labels that match are removed from the log's label set.
-* `labelkeep` - Matches `regex` against all label names. Any labels that don't match are removed from the log's label set.
-* `labelmap`  - Matches `regex` against all label names. Any labels that match are renamed according to the contents of the `replacement` field.
-* `lowercase` - Sets `target_label` to the lowercase form of the concatenated `source_labels`.
-* `replace`   - Matches `regex` to the concatenated labels. If there's a match, it replaces the content of the `target_label` using the contents of the `replacement` field.
-* `uppercase` - Sets `target_label` to the uppercase form of the concatenated `source_labels`.
+- `drop` - Drops logs where `regex` matches the string extracted using the `source_labels` and `separator`.
+- `dropequal` - Drop targets for which the concatenated `source_labels` do match `target_label`.
+- `hashmod` - Hashes the concatenated labels, calculates its modulo `modulus`, and writes the result to the `target_label`.
+- `keep` - Keeps logs where `regex` matches the string extracted using the `source_labels` and `separator`.
+- `keepequal` - Drop targets for which the concatenated `source_labels` don't match `target_label`.
+- `labeldrop` - Matches `regex` against all label names. Any labels that match are removed from the log's label set.
+- `labelkeep` - Matches `regex` against all label names. Any labels that don't match are removed from the log's label set.
+- `labelmap` - Matches `regex` against all label names. Any labels that match are renamed according to the contents of the `replacement` field.
+- `lowercase` - Sets `target_label` to the lowercase form of the concatenated `source_labels`.
+- `replace` - Matches `regex` to the concatenated labels. If there's a match, it replaces the content of the `target_label` using the contents of the `replacement` field.
+- `uppercase` - Sets `target_label` to the uppercase form of the concatenated `source_labels`.
 
 {{< admonition type="note" >}}
 The regular expression capture groups can be referred to using either the `$CAPTURE_GROUP_NUMBER` or `${CAPTURE_GROUP_NUMBER}` notation.
diff --git a/docs/sources/shared/reference/components/rule-block.md b/docs/sources/shared/reference/components/rule-block.md
index 35ec5994a2..7efe096464 100644
--- a/docs/sources/shared/reference/components/rule-block.md
+++ b/docs/sources/shared/reference/components/rule-block.md
@@ -10,29 +10,29 @@ If more than one `rule` block is defined, the transformations are applied in top
 The following arguments can be used to configure a `rule`.
 All arguments are optional. Omitted fields take their default values.
 
-Name            | Type           | Description                                                                                                                          | Default | Required
-----------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------|---------|---------
-`action`        | `string`       | The relabeling action to perform.                                                                                                    | replace | no
-`modulus`       | `uint`         | A positive integer used to calculate the modulus of the hashed source label values.                                                  |         | no
-`regex`         | `string`       | A valid RE2 expression with support for parenthesized capture groups. Used to match the extracted value from the combination of the `source_label` and `separator` fields or filter labels during the `labelkeep/labeldrop/labelmap` actions. | `(.*)` | no
-`replacement`   | `string`       | The value against which a regular expression replace is performed, if the regular expression matches the extracted value. Supports previously captured groups. | `"$1"`      | no
-`separator`     | `string`       | The separator used to concatenate the values present in `source_labels`.                                                             | ;       | no
-`source_labels` | `list(string)` | The list of labels whose values are to be selected. Their content is concatenated using the `separator` and matched against `regex`. |         | no
-`target_label`  | `string`       | Label to which the resulting value will be written to.                                                                               |         | no
+| Name            | Type           | Description                                                                                                                                                                                                                                   | Default | Required |
+| --------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | -------- |
+| `action`        | `string`       | The relabeling action to perform.                                                                                                                                                                                                             | replace | no       |
+| `modulus`       | `uint`         | A positive integer used to calculate the modulus of the hashed source label values.                                                                                                                                                           |         | no       |
+| `regex`         | `string`       | A valid RE2 expression with support for parenthesized capture groups. Used to match the extracted value from the combination of the `source_label` and `separator` fields or filter labels during the `labelkeep/labeldrop/labelmap` actions. | `(.*)`  | no       |
+| `replacement`   | `string`       | The value against which a regular expression replace is performed, if the regular expression matches the extracted value. Supports previously captured groups.                                                                                | `"$1"`  | no       |
+| `separator`     | `string`       | The separator used to concatenate the values present in `source_labels`.                                                                                                                                                                      | ;       | no       |
+| `source_labels` | `list(string)` | The list of labels whose values are to be selected. Their content is concatenated using the `separator` and matched against `regex`.                                                                                                          |         | no       |
+| `target_label`  | `string`       | Label to which the resulting value will be written to.                                                                                                                                                                                        |         | no       |
 
 You can use the following actions:
 
-* `drop`      - Drops metrics where `regex` matches the string extracted using the `source_labels` and `separator`.
-* `dropequal` - Drop targets for which the concatenated `source_labels` do match `target_label`.
-* `hashmod`   - Hashes the concatenated labels, calculates its modulo `modulus` and writes the result to the `target_label`.
-* `keep`      - Keeps metrics where `regex` matches the string extracted using the `source_labels` and `separator`.
-* `keepequal` - Drop targets for which the concatenated `source_labels` don't match `target_label`.
-* `labeldrop` - Matches `regex` against all label names. Any labels that match are removed from the metric's label set.
-* `labelkeep` - Matches `regex` against all label names. Any labels that don't match are removed from the metric's label set.
-* `labelmap`  - Matches `regex` against all label names. Any labels that match are renamed according to the contents of the `replacement` field.
-* `lowercase` - Sets `target_label` to the lowercase form of the concatenated `source_labels`.
-* `replace`   - Matches `regex` to the concatenated labels. If there's a match, it replaces the content of the `target_label` using the contents of the `replacement` field.
-* `uppercase` - Sets `target_label` to the uppercase form of the concatenated `source_labels`.
+- `drop` - Drops metrics where `regex` matches the string extracted using the `source_labels` and `separator`.
+- `dropequal` - Drop targets for which the concatenated `source_labels` do match `target_label`.
+- `hashmod` - Hashes the concatenated labels, calculates its modulo `modulus` and writes the result to the `target_label`.
+- `keep` - Keeps metrics where `regex` matches the string extracted using the `source_labels` and `separator`.
+- `keepequal` - Drop targets for which the concatenated `source_labels` don't match `target_label`.
+- `labeldrop` - Matches `regex` against all label names. Any labels that match are removed from the metric's label set.
+- `labelkeep` - Matches `regex` against all label names. Any labels that don't match are removed from the metric's label set.
+- `labelmap` - Matches `regex` against all label names. Any labels that match are renamed according to the contents of the `replacement` field.
+- `lowercase` - Sets `target_label` to the lowercase form of the concatenated `source_labels`.
+- `replace` - Matches `regex` to the concatenated labels. If there's a match, it replaces the content of the `target_label` using the contents of the `replacement` field.
+- `uppercase` - Sets `target_label` to the uppercase form of the concatenated `source_labels`.
 
 {{< admonition type="note" >}}
 The regular expression capture groups can be referred to using either the `$CAPTURE_GROUP_NUMBER` or `${CAPTURE_GROUP_NUMBER}` notation.
diff --git a/docs/sources/shared/reference/components/sigv4-block.md b/docs/sources/shared/reference/components/sigv4-block.md
index 7c14c3d614..9a14dbf8b1 100644
--- a/docs/sources/shared/reference/components/sigv4-block.md
+++ b/docs/sources/shared/reference/components/sigv4-block.md
@@ -4,13 +4,13 @@ description: Shared content, sigv4 block
 headless: true
 ---
 
-Name         | Type     | Description                                         | Default | Required
--------------|----------|-----------------------------------------------------|---------|---------
-`access_key` | `string` | AWS API access key.                                 |         | no
-`profile`    | `string` | Named AWS profile used to authenticate.             |         | no
-`region`     | `string` | AWS region.                                         |         | no
-`role_arn`   | `string` | AWS Role ARN, an alternative to using AWS API keys. |         | no
-`secret_key` | `secret` | AWS API secret key.                                 |         | no
+| Name         | Type     | Description                                         | Default | Required |
+| ------------ | -------- | --------------------------------------------------- | ------- | -------- |
+| `access_key` | `string` | AWS API access key.                                 |         | no       |
+| `profile`    | `string` | Named AWS profile used to authenticate.             |         | no       |
+| `region`     | `string` | AWS region.                                         |         | no       |
+| `role_arn`   | `string` | AWS Role ARN, an alternative to using AWS API keys. |         | no       |
+| `secret_key` | `secret` | AWS API secret key.                                 |         | no       |
 
 If `region` is left blank, the region from the default credentials chain is used.
 
diff --git a/docs/sources/shared/reference/components/tls-config-block.md b/docs/sources/shared/reference/components/tls-config-block.md
index 533755af6d..7819d42a8e 100644
--- a/docs/sources/shared/reference/components/tls-config-block.md
+++ b/docs/sources/shared/reference/components/tls-config-block.md
@@ -4,30 +4,30 @@ description: Shared content, tls config block
 headless: true
 ---
 
-Name                   | Type     | Description                                              | Default | Required
------------------------|----------|----------------------------------------------------------|---------|---------
-`ca_pem`               | `string` | CA PEM-encoded text to validate the server with.         |         | no
-`ca_file`              | `string` | CA certificate to validate the server with.              |         | no
-`cert_pem`             | `string` | Certificate PEM-encoded text for client authentication.  |         | no
-`cert_file`            | `string` | Certificate file for client authentication.              |         | no
-`insecure_skip_verify` | `bool`   | Disables validation of the server certificate.           |         | no
-`key_file`             | `string` | Key file for client authentication.                      |         | no
-`key_pem`              | `secret` | Key PEM-encoded text for client authentication.          |         | no
-`min_version`          | `string` | Minimum acceptable TLS version.                          |         | no
-`server_name`          | `string` | ServerName extension to indicate the name of the server. |         | no
+| Name                   | Type     | Description                                              | Default | Required |
+| ---------------------- | -------- | -------------------------------------------------------- | ------- | -------- |
+| `ca_pem`               | `string` | CA PEM-encoded text to validate the server with.         |         | no       |
+| `ca_file`              | `string` | CA certificate to validate the server with.              |         | no       |
+| `cert_pem`             | `string` | Certificate PEM-encoded text for client authentication.  |         | no       |
+| `cert_file`            | `string` | Certificate file for client authentication.              |         | no       |
+| `insecure_skip_verify` | `bool`   | Disables validation of the server certificate.           |         | no       |
+| `key_file`             | `string` | Key file for client authentication.                      |         | no       |
+| `key_pem`              | `secret` | Key PEM-encoded text for client authentication.          |         | no       |
+| `min_version`          | `string` | Minimum acceptable TLS version.                          |         | no       |
+| `server_name`          | `string` | ServerName extension to indicate the name of the server. |         | no       |
 
 The following pairs of arguments are mutually exclusive and can't both be set simultaneously:
 
-* `ca_pem` and `ca_file`
-* `cert_pem` and `cert_file`
-* `key_pem` and `key_file`
+- `ca_pem` and `ca_file`
+- `cert_pem` and `cert_file`
+- `key_pem` and `key_file`
 
 When configuring client authentication, both the client certificate (using `cert_pem` or `cert_file`) and the client key (using `key_pem` or `key_file`) must be provided.
 
 When `min_version` isn't provided, the minimum acceptable TLS version is inherited from Go's default minimum version, TLS 1.2.
 If `min_version` is provided, it must be set to one of the following strings:
 
-* `"TLS10"` (TLS 1.0)
-* `"TLS11"` (TLS 1.1)
-* `"TLS12"` (TLS 1.2)
-* `"TLS13"` (TLS 1.3)
+- `"TLS10"` (TLS 1.0)
+- `"TLS11"` (TLS 1.1)
+- `"TLS12"` (TLS 1.2)
+- `"TLS13"` (TLS 1.3)
diff --git a/docs/sources/shared/reference/components/write_relabel_config.md b/docs/sources/shared/reference/components/write_relabel_config.md
index c07c133728..f1894aae5b 100644
--- a/docs/sources/shared/reference/components/write_relabel_config.md
+++ b/docs/sources/shared/reference/components/write_relabel_config.md
@@ -13,29 +13,29 @@ If more than one `write_relabel_config` block is defined, the transformations ar
 The following arguments can be used to configure a `write_relabel_config`.
 All arguments are optional. Omitted fields take their default values.
 
-Name            | Type           | Description                                                                                                                          | Default | Required
-----------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------|---------|---------
-`action`        | `string`       | The relabeling action to perform.                                                                                                    | replace | no
-`modulus`       | `uint`         | A positive integer used to calculate the modulus of the hashed source label values.                                                  |         | no
-`regex`         | `string`       | A valid RE2 expression with support for parenthesized capture groups. Used to match the extracted value from the combination of the `source_label` and `separator` fields or filter labels during the `labelkeep/labeldrop/labelmap` actions. | `(.*)` | no
-`replacement`   | `string`       | The value against which a regular expression replace is performed, if the regular expression matches the extracted value. Supports previously captured groups. | `"$1"`      | no
-`separator`     | `string`       | The separator used to concatenate the values present in `source_labels`.                                                             | ;       | no
-`source_labels` | `list(string)` | The list of labels whose values are to be selected. Their content is concatenated using the `separator` and matched against `regex`. |         | no
-`target_label`  | `string`       | Label to which the resulting value will be written to.                                                                               |         | no
+| Name            | Type           | Description                                                                                                                                                                                                                                   | Default | Required |
+| --------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | -------- |
+| `action`        | `string`       | The relabeling action to perform.                                                                                                                                                                                                             | replace | no       |
+| `modulus`       | `uint`         | A positive integer used to calculate the modulus of the hashed source label values.                                                                                                                                                           |         | no       |
+| `regex`         | `string`       | A valid RE2 expression with support for parenthesized capture groups. Used to match the extracted value from the combination of the `source_label` and `separator` fields or filter labels during the `labelkeep/labeldrop/labelmap` actions. | `(.*)`  | no       |
+| `replacement`   | `string`       | The value against which a regular expression replace is performed, if the regular expression matches the extracted value. Supports previously captured groups.                                                                                | `"$1"`  | no       |
+| `separator`     | `string`       | The separator used to concatenate the values present in `source_labels`.                                                                                                                                                                      | ;       | no       |
+| `source_labels` | `list(string)` | The list of labels whose values are to be selected. Their content is concatenated using the `separator` and matched against `regex`.                                                                                                          |         | no       |
+| `target_label`  | `string`       | Label to which the resulting value will be written to.                                                                                                                                                                                        |         | no       |
 
 You can use the following actions:
 
-* `drop`      - Drops metrics where `regex` matches the string extracted using the `source_labels` and `separator`.
-* `dropequal` - Drop targets for which the concatenated `source_labels` do match `target_label`.
-* `hashmod`   - Hashes the concatenated labels, calculates its modulo `modulus` and writes the result to the `target_label`.
-* `keep`      - Keeps metrics where `regex` matches the string extracted using the `source_labels` and `separator`.
-* `keepequal` - Drop targets for which the concatenated `source_labels` don't match `target_label`.
-* `labeldrop` - Matches `regex` against all label names. Any labels that match are removed from the metric's label set.
-* `labelkeep` - Matches `regex` against all label names. Any labels that don't match are removed from the metric's label set.
-* `labelmap`  - Matches `regex` against all label names. Any labels that match are renamed according to the contents of the `replacement` field.
-* `lowercase` - Sets `target_label` to the lowercase form of the concatenated `source_labels`.
-* `replace`   - Matches `regex` to the concatenated labels. If there's a match, it replaces the content of the `target_label` using the contents of the `replacement` field.
-* `uppercase` - Sets `target_label` to the uppercase form of the concatenated `source_labels`.
+- `drop` - Drops metrics where `regex` matches the string extracted using the `source_labels` and `separator`.
+- `dropequal` - Drop targets for which the concatenated `source_labels` do match `target_label`.
+- `hashmod` - Hashes the concatenated labels, calculates its modulo `modulus` and writes the result to the `target_label`.
+- `keep` - Keeps metrics where `regex` matches the string extracted using the `source_labels` and `separator`.
+- `keepequal` - Drop targets for which the concatenated `source_labels` don't match `target_label`.
+- `labeldrop` - Matches `regex` against all label names. Any labels that match are removed from the metric's label set.
+- `labelkeep` - Matches `regex` against all label names. Any labels that don't match are removed from the metric's label set.
+- `labelmap` - Matches `regex` against all label names. Any labels that match are renamed according to the contents of the `replacement` field.
+- `lowercase` - Sets `target_label` to the lowercase form of the concatenated `source_labels`.
+- `replace` - Matches `regex` to the concatenated labels. If there's a match, it replaces the content of the `target_label` using the contents of the `replacement` field.
+- `uppercase` - Sets `target_label` to the uppercase form of the concatenated `source_labels`.
 
 {{< admonition type="note" >}}
 The regular expression capture groups can be referred to using either the `$CAPTURE_GROUP_NUMBER` or `${CAPTURE_GROUP_NUMBER}` notation.
diff --git a/docs/sources/troubleshoot/controller_metrics.md b/docs/sources/troubleshoot/controller_metrics.md
index cf6312c56f..b7e29b7843 100644
--- a/docs/sources/troubleshoot/controller_metrics.md
+++ b/docs/sources/troubleshoot/controller_metrics.md
@@ -18,13 +18,13 @@ Metrics for the controller are exposed at the `/metrics` HTTP endpoint of the {{
 
 The controller exposes the following metrics:
 
-* `alloy_component_controller_evaluating` (Gauge): Set to `1` whenever the  component controller is evaluating components.
+- `alloy_component_controller_evaluating` (Gauge): Set to `1` whenever the component controller is evaluating components.
   This value may be misrepresented depending on how fast evaluations complete or how often evaluations occur.
-* `alloy_component_controller_running_components` (Gauge): The current number of running components by health.
-   The health is represented in the `health_type` label.
-* `alloy_component_evaluation_seconds` (Histogram): The time it takes to evaluate components after one of their dependencies is updated.
-* `alloy_component_dependencies_wait_seconds` (Histogram): Time spent by components waiting to be evaluated after one of their dependencies is updated.
-* `alloy_component_evaluation_queue_size` (Gauge): The current number of component evaluations waiting to be performed.
+- `alloy_component_controller_running_components` (Gauge): The current number of running components by health.
+  The health is represented in the `health_type` label.
+- `alloy_component_evaluation_seconds` (Histogram): The time it takes to evaluate components after one of their dependencies is updated.
+- `alloy_component_dependencies_wait_seconds` (Histogram): Time spent by components waiting to be evaluated after one of their dependencies is updated.
+- `alloy_component_evaluation_queue_size` (Gauge): The current number of component evaluations waiting to be performed.
 
 [component controller]: ../../get-started/component_controller/
 [alloy run]: ../../reference/cli/run/
diff --git a/docs/sources/troubleshoot/debug.md b/docs/sources/troubleshoot/debug.md
index 0e674aa1a1..438ad57706 100644
--- a/docs/sources/troubleshoot/debug.md
+++ b/docs/sources/troubleshoot/debug.md
@@ -29,6 +29,7 @@ If you are running a custom installation of {{< param "PRODUCT_NAME" >}}, refer
 
 [install]: ../../set-up/install/
 [alloy run]: ../../reference/cli/run/
+
 {{< /admonition >}}
 
 ### Home page
@@ -54,10 +55,10 @@ Clicking a component in the graph navigates to the [Component detail page](#comp
 
 The component detail page shows the following information for each component:
 
-* The health of the component with a message explaining the health.
-* The current evaluated arguments for the component.
-* The current exports for the component.
-* The current debug info for the component if the component has debug info.
+- The health of the component with a message explaining the health.
+- The current evaluated arguments for the component.
+- The current exports for the component.
+- The current debug info for the component if the component has debug info.
 
 From there you can also go to the component documentation or to its corresponding [Live Debugging page](#live-debugging-page).
 
@@ -65,6 +66,7 @@ From there you can also go to the component documentation or to its correspondin
 Values marked as a [secret][] are obfuscated and display as the text `(secret)`.
 
 [secret]: ../../get-started/configuration-syntax/expressions/types_and_values/#secrets
+
 {{< /admonition >}}
 
 ### Clustering page
@@ -73,10 +75,10 @@ Values marked as a [secret][] are obfuscated and display as the text `(secret)`.
 
 The clustering page shows the following information for each cluster node:
 
-* The node's name.
-* The node's advertised address.
-* The node's current state (Viewer/Participant/Terminating).
-* The local node that serves the UI.
+- The node's name.
+- The node's advertised address.
+- The node's current state (Viewer/Participant/Terminating).
+- The local node that serves the UI.
 
 ### Live Debugging page
 
@@ -88,14 +90,15 @@ Live debugging provides a real-time stream of debugging data from a component. Y
 Live debugging is disabled by default to avoid accidentally displaying sensitive telemetry data. To enable live debugging, configure the [livedebugging block][livedebugging].
 
 [livedebugging]: ../../reference/config-blocks/livedebugging/
+
 {{< /admonition >}}
 
 Live debugging allows you to do the following:
 
-* Pause and clear the data stream.
-* Sample data and disable auto-scrolling to handle heavy loads.
-* Search through the data using keywords.
-* Copy the entire data stream to the clipboard.
+- Pause and clear the data stream.
+- Sample data and disable auto-scrolling to handle heavy loads.
+- Search through the data using keywords.
+- Copy the entire data stream to the clipboard.
 
 The format and content of the debugging data vary depending on the component type.
 
@@ -104,21 +107,21 @@ Live debugging isn't yet available in all components.
 
 Supported components:
 
-* `loki.process`
-* `loki.relabel`
-* `loki.secretfilter`
-* `otelcol.processor.*`
-* `otelcol.receiver.*`
-* `prometheus.relabel`
-{{< /admonition >}}
+- `loki.process`
+- `loki.relabel`
+- `loki.secretfilter`
+- `otelcol.processor.*`
+- `otelcol.receiver.*`
+- `prometheus.relabel`
+  {{< /admonition >}}
 
 ## Debug using the UI
 
 To debug using the UI:
 
-* Ensure that no component is reported as unhealthy.
-* Ensure that the arguments and exports for misbehaving components appear correct.
-* Ensure that the live debugging data meets your expectations.
+- Ensure that no component is reported as unhealthy.
+- Ensure that the arguments and exports for misbehaving components appear correct.
+- Ensure that the live debugging data meets your expectations.
 
 ## Examine logs
 
@@ -134,18 +137,18 @@ Refer to the [`logging` block][logging] page to see how to find logs for your sy
 
 To debug issues when using [clustering][], check for the following symptoms.
 
-* **Cluster not converging**: The cluster peers aren't converging on the same view of their peers' status.
+- **Cluster not converging**: The cluster peers aren't converging on the same view of their peers' status.
   This is most likely due to network connectivity issues between the cluster nodes.
   Use the {{< param "PRODUCT_NAME" >}} UI of each running peer to understand which nodes aren't picked up correctly.
-* **Cluster split brain**: The cluster peers aren't aware of one another, thinking they're the only node present.
+- **Cluster split brain**: The cluster peers aren't aware of one another, thinking they're the only node present.
   Again, check for network connectivity issues.
   Check that the addresses or DNS names given to the node to join are correctly formatted and reachable.
-* **Configuration drift**: Clustering assumes that all nodes are running with the same configuration file at roughly the same time.
+- **Configuration drift**: Clustering assumes that all nodes are running with the same configuration file at roughly the same time.
   Check the logs for issues with the reloaded configuration file as well as the graph page to verify changes have been applied.
-* **Node name conflicts**: Clustering assumes all nodes have unique names.
+- **Node name conflicts**: Clustering assumes all nodes have unique names.
   Nodes with conflicting names are rejected and won't join the cluster.
   Look at the clustering UI page for the list of current peers with their names, and check the logs for any reported name conflict events.
-* **Node stuck in terminating state**: The node attempted to gracefully shut down and set its state to Terminating, but it hasn't completely gone away.
+- **Node stuck in terminating state**: The node attempted to gracefully shut down and set its state to Terminating, but it hasn't completely gone away.
   Check the clustering page to view the state of the peers and verify that the terminating {{< param "PRODUCT_NAME" >}} has been shut down.
 
 {{< admonition type="note" >}}
diff --git a/docs/sources/troubleshoot/support_bundle.md b/docs/sources/troubleshoot/support_bundle.md
index 89a777a156..7c97654475 100644
--- a/docs/sources/troubleshoot/support_bundle.md
+++ b/docs/sources/troubleshoot/support_bundle.md
@@ -34,16 +34,17 @@ In addition, you can inspect the [support bundle implementation](https://github.
 to verify the code used to generate these bundles.
 
 A support bundle contains the following data:
-* `alloy-components.json` contains information about the [components][components] running on this {{< param "PRODUCT_NAME" >}} instance, generated by the 
-`/api/v0/web/components` endpoint.
-* `alloy-logs.txt` contains the logs during the bundle generation.
-* `alloy-metadata.yaml` contains the {{< param "PRODUCT_NAME" >}} build version and the installation's operating system, architecture, and uptime.
-* `alloy-metrics.txt` contains a snapshot of the internal metrics for {{< param "PRODUCT_NAME" >}}.
-* `alloy-peers.json` contains information about the identified cluster peers of this {{< param "PRODUCT_NAME" >}} instance, generated by the 
-`/api/v0/web/peers` endpoint.
-* `alloy-runtime-flags.txt` contains the values of the runtime flags available in {{< param "PRODUCT_NAME" >}}.
-* The `pprof/` directory contains Go runtime profiling data (CPU, heap, goroutine, mutex, block profiles) as exported by the pprof package.
-Refer to the [profile][profile] documentation for more details on how to use this information.
+
+- `alloy-components.json` contains information about the [components][components] running on this {{< param "PRODUCT_NAME" >}} instance, generated by the
+  `/api/v0/web/components` endpoint.
+- `alloy-logs.txt` contains the logs during the bundle generation.
+- `alloy-metadata.yaml` contains the {{< param "PRODUCT_NAME" >}} build version and the installation's operating system, architecture, and uptime.
+- `alloy-metrics.txt` contains a snapshot of the internal metrics for {{< param "PRODUCT_NAME" >}}.
+- `alloy-peers.json` contains information about the identified cluster peers of this {{< param "PRODUCT_NAME" >}} instance, generated by the
+  `/api/v0/web/peers` endpoint.
+- `alloy-runtime-flags.txt` contains the values of the runtime flags available in {{< param "PRODUCT_NAME" >}}.
+- The `pprof/` directory contains Go runtime profiling data (CPU, heap, goroutine, mutex, block profiles) as exported by the pprof package.
+  Refer to the [profile][profile] documentation for more details on how to use this information.
 
 [profile]: ../profile/
 [components]: ../../get-started/components/
diff --git a/docs/sources/tutorials/first-components-and-stdlib.md b/docs/sources/tutorials/first-components-and-stdlib.md
index 0b58db17f4..7859eb56af 100644
--- a/docs/sources/tutorials/first-components-and-stdlib.md
+++ b/docs/sources/tutorials/first-components-and-stdlib.md
@@ -15,11 +15,11 @@ It introduces a basic pipeline that collects metrics from the host and sends the
 
 To complete this tutorial:
 
-* You must set up a [local Grafana instance][previous tutorial].
+- You must set up a [local Grafana instance][previous tutorial].
 
 ### Recommended reading
 
-* [{{< param "PRODUCT_NAME" >}} configuration syntax][configuration syntax]
+- [{{< param "PRODUCT_NAME" >}} configuration syntax][configuration syntax]
 
 ## {{% param "PRODUCT_NAME" %}} configuration syntax basics
 
@@ -29,9 +29,9 @@ An {{< param "PRODUCT_NAME" >}} configuration file contains three elements:
 
    `key = value` pairs used to configure individual settings.
 
-    ```alloy
-    url = "http://localhost:9090"
-    ```
+   ```alloy
+   url = "http://localhost:9090"
+   ```
 
 1. **Expressions**
 
@@ -45,25 +45,25 @@ An {{< param "PRODUCT_NAME" >}} configuration file contains three elements:
    Blocks are used to configure components with groups of attributes or nested blocks.
    The following example block can be used to configure the logging output of {{< param "PRODUCT_NAME" >}}:
 
-    ```alloy
-    logging {
-        level  = "debug"
-        format = "json"
-    }
-    ```
+   ```alloy
+   logging {
+       level  = "debug"
+       format = "json"
+   }
+   ```
 
-    {{< admonition type="note" >}}
-    The default log level is `info` and the default log format is `logfmt`.
-    {{< /admonition >}}
+   {{< admonition type="note" >}}
+   The default log level is `info` and the default log format is `logfmt`.
+   {{< /admonition >}}
 
-    Try pasting this into `config.alloy` and running `<BINARY_FILE_PATH> run config.alloy` to see what happens. Replace _`<BINARY_FILE_PATH>`_ with the path to the {{< param "PRODUCT_NAME" >}} binary.
+   Try pasting this into `config.alloy` and running `<BINARY_FILE_PATH> run config.alloy` to see what happens. Replace _`<BINARY_FILE_PATH>`_ with the path to the {{< param "PRODUCT_NAME" >}} binary.
 
-    Congratulations, you've just written your first {{< param "PRODUCT_NAME" >}} configuration file.
-    This configuration won't do anything. In the next step, you add some functionality to this configuration.
+   Congratulations, you've just written your first {{< param "PRODUCT_NAME" >}} configuration file.
+   This configuration won't do anything. In the next step, you add some functionality to this configuration.
 
-    {{< admonition type="note" >}}
-    Comments in {{< param "PRODUCT_NAME" >}} syntax are prefixed with `//` and are single-line only. For example: `// This is a comment`.
-    {{< /admonition >}}
+   {{< admonition type="note" >}}
+   Comments in {{< param "PRODUCT_NAME" >}} syntax are prefixed with `//` and are single-line only. For example: `// This is a comment`.
+   {{< /admonition >}}
 
 ## Components
 
@@ -71,9 +71,9 @@ Components are the building blocks of an {{< param "PRODUCT_NAME" >}} configurat
 
 ### Recommended reading
 
-* [Components][]
-* [Components configuration language][]
-* [Component controller][]
+- [Components][]
+- [Components configuration language][]
+- [Component controller][]
 
 ### An example pipeline
 
@@ -101,6 +101,7 @@ A list of all available components can be found in the [Component reference][].
 Each component has a link to its documentation, which contains a description of what the component does, its arguments, its exports, and examples.
 
 [Component reference]: ../../reference/components/
+
 {{< /admonition >}}
 
 This pipeline has two components: `local.file` and `prometheus.remote_write`.
@@ -127,9 +128,9 @@ Now that you have a simple pipeline, you can send your first metrics.
 
 ### Recommended reading
 
-* Optional: [`prometheus.exporter.unix`][prometheus.exporter.unix]
-* Optional: [`prometheus.scrape`][prometheus.scrape]
-* Optional: [`prometheus.remote_write`][prometheus.remote_write]
+- Optional: [`prometheus.exporter.unix`][prometheus.exporter.unix]
+- Optional: [`prometheus.scrape`][prometheus.scrape]
+- Optional: [`prometheus.remote_write`][prometheus.remote_write]
 
 ### Modify your pipeline and scrape the metrics
 
@@ -165,7 +166,7 @@ Run {{< param "PRODUCT_NAME" >}} with the following command:
 
 Replace the following:
 
-* _`<BINARY_FILE_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} binary.
+- _`<BINARY_FILE_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} binary.
 
 Navigate to [http://localhost:3000/explore][] in your browser.
 After ~15-20 seconds, you should be able to see the metrics from the `prometheus.exporter.unix` component.
@@ -181,9 +182,9 @@ The following diagram is an example pipeline:
 
 Your pipeline configuration defines three components:
 
-* `prometheus.scrape` - A component that scrapes metrics from components that export targets.
-* `prometheus.exporter.unix` - A component that exports metrics from the host, built around [node_exporter][].
-* `prometheus.remote_write` - A component that sends metrics to a Prometheus remote-write compatible endpoint.
+- `prometheus.scrape` - A component that scrapes metrics from components that export targets.
+- `prometheus.exporter.unix` - A component that exports metrics from the host, built around [node_exporter][].
+- `prometheus.remote_write` - A component that sends metrics to a Prometheus remote-write compatible endpoint.
 
 The `prometheus.scrape` component references the `prometheus.exporter.unix` component's targets export, which is a list of scrape targets.
 The `prometheus.scrape` component forwards the scraped metrics to the `prometheus.remote_write` component.
@@ -198,7 +199,7 @@ The following exercise guides you through modifying your pipeline to scrape metr
 
 ### Recommended Reading
 
-* Optional: [`prometheus.exporter.redis`][prometheus.exporter.redis]
+- Optional: [`prometheus.exporter.redis`][prometheus.exporter.redis]
 
 Start a container running Redis and configure {{< param "PRODUCT_NAME" >}} to scrape the metrics.
 
@@ -217,6 +218,7 @@ To give a visual hint, you want to create a pipeline that looks like this:
 Refer to the [`array.concat`][array.concat] standard library function for information about combining lists of values into a single list.
 
 [array.concat]: ../../reference/stdlib/array/
+
 {{< /admonition >}}
 
 You can run {{< param "PRODUCT_NAME" >}} with the new configuration file with the following command:
@@ -227,7 +229,7 @@ You can run {{< param "PRODUCT_NAME" >}} with the new configuration file with th
 
 Replace the following:
 
-* _`<BINARY_FILE_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} binary.
+- _`<BINARY_FILE_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} binary.
 
 Navigate to [http://localhost:3000/explore][] in your browser.
 After the first scrape, you should be able to query for `redis` metrics as well as `node` metrics.
diff --git a/docs/sources/tutorials/logs-and-relabeling-basics.md b/docs/sources/tutorials/logs-and-relabeling-basics.md
index 096ef88940..00f827ce99 100644
--- a/docs/sources/tutorials/logs-and-relabeling-basics.md
+++ b/docs/sources/tutorials/logs-and-relabeling-basics.md
@@ -14,7 +14,7 @@ This tutorial covers some basic metric relabeling, and shows you how to send log
 
 To complete this tutorial:
 
-* You must complete the [First components and the standard library][first] tutorial.
+- You must complete the [First components and the standard library][first] tutorial.
 
 ## Relabel metrics
 
@@ -22,7 +22,7 @@ Now that you have built a basic pipeline and scraped some metrics, you can use t
 
 ### Recommended reading
 
-* Optional: [`prometheus.relabel`][prometheus.relabel]
+- Optional: [`prometheus.relabel`][prometheus.relabel]
 
 ### Add a `prometheus.relabel` component to your pipeline
 
@@ -87,6 +87,7 @@ These labels are considered internal and are dropped before relabeling rules fro
 If you would like to keep or act on these kinds of labels, use a [`discovery.relabel`][discovery.relabel] component.
 
 [discovery.relabel]: ../../reference/components/discovery/discovery.relabel/
+
 {{< /admonition >}}
 
 ## Send logs to Loki
@@ -95,9 +96,9 @@ Now that you've created components and chained them together, you can collect so
 
 ### Recommended reading
 
-* Optional: [`local.file_match`][local.file_match]
-* Optional: [`loki.source.file`][loki.source.file]
-* Optional: [`loki.write`][loki.write]
+- Optional: [`local.file_match`][local.file_match]
+- Optional: [`loki.source.file`][loki.source.file]
+- Optional: [`loki.write`][loki.write]
 
 ### Find and collect the logs
 
@@ -154,8 +155,8 @@ The following exercise guides you through adding a label to the logs, and filter
 
 ### Recommended reading
 
-* [`loki.relabel`][loki.relabel]
-* [`loki.process`][loki.process]
+- [`loki.relabel`][loki.relabel]
+- [`loki.process`][loki.process]
 
 ### Add a Label to Logs
 
@@ -186,6 +187,7 @@ You can use the [`loki.relabel`][loki.relabel] component to relabel and add labe
 
 [loki.relabel]: ../../reference/components/loki/loki.relabel/
 [prometheus.relabel]: ../../reference/components/prometheus/prometheus.relabel/
+
 {{< /admonition >}}
 
 Run {{< param "PRODUCT_NAME" >}} and execute the following:
diff --git a/docs/sources/tutorials/processing-logs.md b/docs/sources/tutorials/processing-logs.md
index f1cb0b4611..a2a24970f3 100644
--- a/docs/sources/tutorials/processing-logs.md
+++ b/docs/sources/tutorials/processing-logs.md
@@ -15,7 +15,7 @@ It covers using `loki.source.api` to receive logs over HTTP, processing and filt
 
 To complete this tutorial:
 
-* You must complete the [Logs and relabeling basics][logs] tutorial.
+- You must complete the [Logs and relabeling basics][logs] tutorial.
 
 ## Receive logs over HTTP and Process
 
@@ -24,7 +24,7 @@ It can be useful for receiving logs from other {{< param "PRODUCT_NAME" >}}s or
 
 ### Recommended reading
 
-* Optional: [`loki.source.api`][loki.source.api]
+- Optional: [`loki.source.api`][loki.source.api]
 
 ### Set up the `loki.source.api` component
 
@@ -54,9 +54,9 @@ You are configuring the `loki.source.api` component to listen on `127.0.0.1:9999
 
 ### Recommended reading
 
-* [`loki.process#stage.drop`][loki.process#stage.drop]
-* [`loki.process#stage.json`][loki.process#stage.json]
-* [`loki.process#stage.labels`][loki.process#stage.labels]
+- [`loki.process#stage.drop`][loki.process#stage.drop]
+- [`loki.process#stage.json`][loki.process#stage.json]
+- [`loki.process#stage.labels`][loki.process#stage.labels]
 
 ### Configure the `loki.process` and `loki.write` components
 
@@ -153,12 +153,12 @@ Here is the example log line:
 
 ```json
 {
-    "log": {
-        "is_secret": "true",
-        "level": "info",
-        "message": "This is a secret message!",
-    },
-    "timestamp": "2023-11-16T06:01:50Z",
+  "log": {
+    "is_secret": "true",
+    "level": "info",
+    "message": "This is a secret message!"
+  },
+  "timestamp": "2023-11-16T06:01:50Z"
 }
 ```
 
@@ -200,12 +200,12 @@ Extracted map _after_ performing this stage:
 
 ```json
 {
-    "log": {
-        "is_secret": "true",
-        "level": "info",
-        "message": "This is a secret message!",
-    },
-    "ts": "2023-11-16T06:01:50Z",
+  "log": {
+    "is_secret": "true",
+    "level": "info",
+    "message": "This is a secret message!"
+  },
+  "ts": "2023-11-16T06:01:50Z"
 }
 ```
 
@@ -264,12 +264,12 @@ Extracted map _before_ performing this stage:
 
 ```json
 {
-    "log": {
-        "is_secret": "true",
-        "level": "info",
-        "message": "This is a secret message!",
-    },
-    "ts": "2023-11-16T06:01:50Z",
+  "log": {
+    "is_secret": "true",
+    "level": "info",
+    "message": "This is a secret message!"
+  },
+  "ts": "2023-11-16T06:01:50Z"
 }
 ```
 
@@ -277,15 +277,15 @@ Extracted map _after_ performing this stage:
 
 ```json
 {
-    "log": {
-        "is_secret": "true",
-        "level": "info",
-        "message": "This is a secret message!",
-    },
-    "ts": "2023-11-16T06:01:50Z",
+  "log": {
     "is_secret": "true",
     "level": "info",
-    "log_line": "This is a secret message!",
+    "message": "This is a secret message!"
+  },
+  "ts": "2023-11-16T06:01:50Z",
+  "is_secret": "true",
+  "level": "info",
+  "log_line": "This is a secret message!"
 }
 ```
 
@@ -343,7 +343,7 @@ Modify `config.alloy` with the configuration from the previous example and start
 
 Replace the following:
 
-* _`<BINARY_FILE_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} binary.
+- _`<BINARY_FILE_PATH>`_: The path to the {{< param "PRODUCT_NAME" >}} binary.
 
 Try executing the following which inserts the current timestamp:
 
diff --git a/docs/sources/tutorials/send-logs-to-loki.md b/docs/sources/tutorials/send-logs-to-loki.md
index 480c44425b..e530c4ae04 100644
--- a/docs/sources/tutorials/send-logs-to-loki.md
+++ b/docs/sources/tutorials/send-logs-to-loki.md
@@ -15,12 +15,12 @@ killercoda:
         replacement: Grafana Alloy
       - regexp: '{{[%<] *param *"PRODUCT_NAME" *[%>]}}'
         replacement: Alloy
-      - regexp: 'docker compose'
+      - regexp: "docker compose"
         replacement: docker-compose
       - regexp: '\.\./\.\./'
-        replacement: 'https://grafana.com/docs/alloy/latest/'
-      - regexp: '../send-metrics-to-prometheus/'
-        replacement: 'https://grafana.com/docs/alloy/latest/tutorials/send-metrics-to-prometheus/'
+        replacement: "https://grafana.com/docs/alloy/latest/"
+      - regexp: "../send-metrics-to-prometheus/"
+        replacement: "https://grafana.com/docs/alloy/latest/tutorials/send-metrics-to-prometheus/"
 
   backend:
     imageid: ubuntu
@@ -36,16 +36,17 @@ This tutorial shows you how to configure {{< param "PRODUCT_NAME" >}} to collect
 
 To complete this tutorial:
 
-* You must have a basic understanding of {{< param "PRODUCT_NAME" >}} and telemetry collection in general.
-* You should be familiar with Prometheus, PromQL, Loki, LogQL, and basic Grafana navigation.
-<!-- INTERACTIVE ignore START -->
-{{< admonition type="tip" >}}
-Alternatively, you can try out this example in the interactive learning environment: [Sending Logs to Loki](https://killercoda.com/grafana-labs/course/alloy/send-logs-to-loki).
+- You must have a basic understanding of {{< param "PRODUCT_NAME" >}} and telemetry collection in general.
+- You should be familiar with Prometheus, PromQL, Loki, LogQL, and basic Grafana navigation.
+  <!-- INTERACTIVE ignore START -->
+  {{< admonition type="tip" >}}
+  Alternatively, you can try out this example in the interactive learning environment: [Sending Logs to Loki](https://killercoda.com/grafana-labs/course/alloy/send-logs-to-loki).
 
 It's a fully configured environment with all the dependencies already installed.
 
-![Interactive](/media/docs/alloy/Alloy-Interactive-Learning-Environment-(Doc-Banner).png)
+![Interactive](</media/docs/alloy/Alloy-Interactive-Learning-Environment-(Doc-Banner).png>)
 {{< /admonition >}}
+
 <!-- INTERACTIVE ignore END -->
 
 <!-- INTERACTIVE page intro.md END -->
@@ -55,10 +56,13 @@ It's a fully configured environment with all the dependencies already installed.
 ## Install {{% param "PRODUCT_NAME" %}} and start the service
 
 <!-- INTERACTIVE ignore START -->
+
 This tutorial requires a Linux or macOS environment with Docker installed.
+
 <!-- INTERACTIVE ignore END -->
 
 {{< docs/ignore >}}
+
 > This online sandbox environment is based on an Ubuntu image and has Docker pre-installed. To install {{% param "PRODUCT_NAME" %}} in the sandbox, perform the following steps.
 
 {{< /docs/ignore >}}
@@ -68,7 +72,7 @@ This tutorial requires a Linux or macOS environment with Docker installed.
 Install and run {{< param "PRODUCT_NAME" >}} on Linux.
 
 1. [Install {{< param "PRODUCT_NAME" >}}][Linux Install].
-{{< docs/ignore >}}
+   {{< docs/ignore >}}
 1. To view the {{% param "PRODUCT_NAME" %}} UI within the sandbox, {{% param "PRODUCT_NAME" %}} must run on all interfaces. Run the following command before you start the {{% param "PRODUCT_NAME" %}} service.
 
    ```bash
@@ -76,9 +80,11 @@ Install and run {{< param "PRODUCT_NAME" >}} on Linux.
    ```
 
 {{< /docs/ignore >}}
+
 1. [Run {{< param "PRODUCT_NAME" >}}][Run on Linux].
 
 <!-- INTERACTIVE ignore START -->
+
 ### macOS
 
 Install and run {{< param "PRODUCT_NAME" >}} on macOS.
@@ -101,8 +107,9 @@ You can use the following Docker Compose file to set up a local Grafana instance
 This Docker Compose file includes Loki and Prometheus configured as data sources.
 
 {{< docs/ignore >}}
+
 > The interactive sandbox has a VSCode-like editor that allows you to access files and folders. To access this feature, click on the `Editor` tab. The editor also has a terminal that you can use to run commands. Since some commands assume you are within a specific directory, we recommend running the commands in `tab1`.
-{{< /docs/ignore >}}
+> {{< /docs/ignore >}}
 
 1. Create a directory and save the Docker Compose file as `docker-compose.yml`.
 
@@ -114,70 +121,73 @@ This Docker Compose file includes Loki and Prometheus configured as data sources
 
 1. Copy the following Docker Compose file into `docker-compose.yml`.
    {{< docs/ignore >}}
-    > We recommend using the `Editor` tab to copy and paste the Docker Compose file. However, you can also use a terminal editor like `nano` or `vim`.
-   {{< /docs/ignore >}}
+
+   > We recommend using the `Editor` tab to copy and paste the Docker Compose file. However, you can also use a terminal editor like `nano` or `vim`.
+   > {{< /docs/ignore >}}
 
    ```yaml
-    version: '3'
-    services:
-      loki:
-        image: grafana/loki:3.0.0
-        ports:
-          - "3100:3100"
-        command: -config.file=/etc/loki/local-config.yaml
-      prometheus:
-        image: prom/prometheus:v2.47.0
-        command:
-          - --web.enable-remote-write-receiver
-          - --config.file=/etc/prometheus/prometheus.yml
-        ports:
-          - "9090:9090"
-      grafana:
-        environment:
-          - GF_PATHS_PROVISIONING=/etc/grafana/provisioning
-          - GF_AUTH_ANONYMOUS_ENABLED=true
-          - GF_AUTH_ANONYMOUS_ORG_ROLE=Admin
-        entrypoint:
-          - sh
-          - -euc
-          - |
-            mkdir -p /etc/grafana/provisioning/datasources
-            cat <<EOF > /etc/grafana/provisioning/datasources/ds.yaml
-            apiVersion: 1
-            datasources:
-            - name: Loki
-              type: loki
-              access: proxy
-              orgId: 1
-              url: http://loki:3100
-              basicAuth: false
-              isDefault: false
-              version: 1
-              editable: false
-            - name: Prometheus
-              type: prometheus
-              orgId: 1
-              url: http://prometheus:9090
-              basicAuth: false
-              isDefault: true
-              version: 1
-              editable: false
-            EOF
-            /run.sh
-        image: grafana/grafana:11.0.0
-        ports:
-          - "3000:3000"
-    ```
+   version: "3"
+   services:
+     loki:
+       image: grafana/loki:3.0.0
+       ports:
+         - "3100:3100"
+       command: -config.file=/etc/loki/local-config.yaml
+     prometheus:
+       image: prom/prometheus:v2.47.0
+       command:
+         - --web.enable-remote-write-receiver
+         - --config.file=/etc/prometheus/prometheus.yml
+       ports:
+         - "9090:9090"
+     grafana:
+       environment:
+         - GF_PATHS_PROVISIONING=/etc/grafana/provisioning
+         - GF_AUTH_ANONYMOUS_ENABLED=true
+         - GF_AUTH_ANONYMOUS_ORG_ROLE=Admin
+       entrypoint:
+         - sh
+         - -euc
+         - |
+           mkdir -p /etc/grafana/provisioning/datasources
+           cat <<EOF > /etc/grafana/provisioning/datasources/ds.yaml
+           apiVersion: 1
+           datasources:
+           - name: Loki
+             type: loki
+             access: proxy
+             orgId: 1
+             url: http://loki:3100
+             basicAuth: false
+             isDefault: false
+             version: 1
+             editable: false
+           - name: Prometheus
+             type: prometheus
+             orgId: 1
+             url: http://prometheus:9090
+             basicAuth: false
+             isDefault: true
+             version: 1
+             editable: false
+           EOF
+           /run.sh
+       image: grafana/grafana:11.0.0
+       ports:
+         - "3000:3000"
+   ```
 
 1. To start the local Grafana instance, run the following command.
 
    ```bash
     docker compose up -d
    ```
+
     <!-- INTERACTIVE ignore START -->
-    {{< admonition type="note" >}}
-      If you encounter the following error when you start your Docker container, `docker: 'compose' is not a docker command`, use the command `docker-compose up` to start your Docker container.
-    {{< /admonition >}}
+
+   {{< admonition type="note" >}}
+   If you encounter the following error when you start your Docker container, `docker: 'compose' is not a docker command`, use the command `docker-compose up` to start your Docker container.
+   {{< /admonition >}}
     <!-- INTERACTIVE ignore END -->
 
 1. Open [http://localhost:3000](http://localhost:3000) in your browser to access the Grafana UI.
@@ -206,17 +216,17 @@ touch config.alloy
 
 Copy and paste the following component configuration at the top of the file.
 
-   ```alloy
-    local.file_match "local_files" {
-        path_targets = [{"__path__" = "/var/log/*.log"}]
-        sync_period = "5s"
-    }
-   ```
+```alloy
+ local.file_match "local_files" {
+     path_targets = [{"__path__" = "/var/log/*.log"}]
+     sync_period = "5s"
+ }
+```
 
 This configuration creates a [local.file_match][] component named `local_files` which does the following:
 
-* It tells {{< param "PRODUCT_NAME" >}} which files to source.
-* It checks for new files every 5 seconds.
+- It tells {{< param "PRODUCT_NAME" >}} which files to source.
+- It checks for new files every 5 seconds.
 
 ### Second component: Scraping
 
@@ -232,9 +242,9 @@ Copy and paste the following component configuration below the previous componen
 
 This configuration creates a [`loki.source.file`][loki.source.file] component named `log_scrape` which does the following:
 
-* It connects to the `local_files` component as its source or target.
-* It forwards the logs it scrapes to the receiver of another component called `filter_logs`.
-* It provides extra attributes and options to tail the log files from the end so you don't ingest the entire log file history.
+- It connects to the `local_files` component as its source or target.
+- It forwards the logs it scrapes to the receiver of another component called `filter_logs`.
+- It provides extra attributes and options to tail the log files from the end so you don't ingest the entire log file history.
 
 ### Third component: Filter non-essential logs
 
@@ -260,11 +270,11 @@ Within this component, you can define one or more processing stages to specify h
 
 This configuration creates a [`loki.process`][loki.process] component named `filter_logs` which does the following:
 
-* It receives scraped log entries from the default `log_scrape` component.
-* It uses the `stage.drop` block to define what to drop from the scraped logs.
-* It uses the `expression` parameter to identify the specific log entries to drop.
-* It uses an optional string label `drop_counter_reason` to show the reason for dropping the log entries.
-* It forwards the processed logs to the receiver of another component called `grafana_loki`.
+- It receives scraped log entries from the default `log_scrape` component.
+- It uses the `stage.drop` block to define what to drop from the scraped logs.
+- It uses the `expression` parameter to identify the specific log entries to drop.
+- It uses an optional string label `drop_counter_reason` to show the reason for dropping the log entries.
+- It forwards the processed logs to the receiver of another component called `grafana_loki`.
 
 The [`loki.process`][loki.process] documentation provides more comprehensive information on processing logs.
 
@@ -290,20 +300,25 @@ This final component creates a [`loki.write`][loki.write] component named `grafa
 This completes the simple configuration pipeline.
 
 <!-- INTERACTIVE ignore START -->
+
 {{< admonition type="tip" >}}
 The `basic_auth` block is commented out because the local `docker compose` stack doesn't require it.
 It's included in this example to show how you can configure authorization for other environments.
 For further authorization options, refer to the [`loki.write`][loki.write] component reference.
 
 [loki.write]: ../../reference/components/loki/loki.write/
+
 {{< /admonition >}}
+
 <!-- INTERACTIVE ignore END -->
 
 {{< docs/ignore >}}
+
 > The `basic_auth` block is commented out because the local `docker compose` stack doesn't require it. It's included in this example to show how you can configure authorization for other environments. For further authorization options, refer to the [`loki.write`](../../reference/components/loki/loki.write/) component reference.
-{{< /docs/ignore >}}
+> {{< /docs/ignore >}}
 
 With this configuration, {{< param "PRODUCT_NAME" >}} connects directly to the Loki instance running in the Docker container.
+
 <!-- INTERACTIVE page step3.md END -->
 
 <!-- INTERACTIVE page step4.md START -->
@@ -321,6 +336,7 @@ With this configuration, {{< param "PRODUCT_NAME" >}} connects directly to the L
    {{< /docs/ignore >}}
 
    <!-- INTERACTIVE ignore START -->
+
    {{< code >}}
 
    ```macos
@@ -339,16 +355,19 @@ With this configuration, {{< param "PRODUCT_NAME" >}} connects directly to the L
    ```bash
     curl -X POST http://localhost:12345/-/reload
    ```
+
    <!-- INTERACTIVE ignore START -->
+
    {{< admonition type="tip" >}}
    This step uses the {{< param "PRODUCT_NAME" >}} UI on `localhost` port `12345`.
    If you chose to run {{< param "PRODUCT_NAME" >}} in a Docker container, make sure you use the `--server.http.listen-addr=0.0.0.0:12345` argument.
    If you don't use this argument, the [debugging UI][debug] won't be available outside of the Docker container.
 
    [debug]: ../../troubleshoot/debug/#alloy-ui
+
    {{< /admonition >}}
    <!-- INTERACTIVE ignore END -->
-  
+
    {{< docs/ignore >}}
 
    > This step uses the {{< param "PRODUCT_NAME" >}} UI on `localhost` port `12345`. If you chose to run {{< param "PRODUCT_NAME" >}} in a Docker container, make sure you use the `--server.http.listen-addr=` argument. If you don't use this argument, the [debugging UI](../../troubleshoot/debug/#alloy-ui) won't be available outside of the Docker container.
@@ -359,23 +378,26 @@ With this configuration, {{< param "PRODUCT_NAME" >}} connects directly to the L
 
 {{< docs/ignore >}}
 
-   ```bash
-    sudo systemctl reload alloy
-   ```
+```bash
+ sudo systemctl reload alloy
+```
 
 {{< /docs/ignore >}}
+
 <!-- INTERACTIVE ignore START -->
-   {{< code >}}
 
-   ```macos
-   brew services restart alloy
-   ```
+{{< code >}}
 
-   ```linux
-   sudo systemctl reload alloy
-   ```
+```macos
+brew services restart alloy
+```
+
+```linux
+sudo systemctl reload alloy
+```
+
+{{< /code >}}
 
-   {{< /code >}}
 <!-- INTERACTIVE ignore END -->
 
 ## Inspect your configuration in the {{% param "PRODUCT_NAME" %}} UI
diff --git a/docs/sources/tutorials/send-metrics-to-prometheus.md b/docs/sources/tutorials/send-metrics-to-prometheus.md
index 8c665356e7..6695a6f074 100644
--- a/docs/sources/tutorials/send-metrics-to-prometheus.md
+++ b/docs/sources/tutorials/send-metrics-to-prometheus.md
@@ -16,12 +16,12 @@ killercoda:
         replacement: Grafana Alloy
       - regexp: '{{[%<] *param *"PRODUCT_NAME" *[%>]}}'
         replacement: Alloy
-      - regexp: 'docker compose'
+      - regexp: "docker compose"
         replacement: docker-compose
       - regexp: '\.\./\.\./'
-        replacement: 'https://grafana.com/docs/alloy/latest/'
-      - regexp: '../send-logs-to-loki/'
-        replacement: 'https://grafana.com/docs/alloy/latest/tutorials/send-logs-to-loki/'
+        replacement: "https://grafana.com/docs/alloy/latest/"
+      - regexp: "../send-logs-to-loki/"
+        replacement: "https://grafana.com/docs/alloy/latest/tutorials/send-logs-to-loki/"
 
   backend:
     imageid: ubuntu
@@ -36,30 +36,34 @@ In the [previous tutorial][], you learned how to configure {{< param "PRODUCT_NA
 This tutorial shows you how to configure {{< param "PRODUCT_NAME" >}} to collect and process metrics from your local machine, send them to Prometheus, and use Grafana to explore the results.
 
 <!-- INTERACTIVE ignore START -->
+
 ## Before you begin
 
 To complete this tutorial:
 
-* You must have a basic understanding of Alloy and telemetry collection in general.
-* You should be familiar with Prometheus, PromQL, Loki, LogQL, and basic Grafana navigation.
-* You must complete the [previous tutorial][] to prepare the following prerequisites:
-  * Install {{< param "PRODUCT_NAME" >}} and start the service in your environment.
-  * Set up a local Grafana instance.
-  * Create a `config.alloy` file.
+- You must have a basic understanding of Alloy and telemetry collection in general.
+- You should be familiar with Prometheus, PromQL, Loki, LogQL, and basic Grafana navigation.
+- You must complete the [previous tutorial][] to prepare the following prerequisites:
+  - Install {{< param "PRODUCT_NAME" >}} and start the service in your environment.
+  - Set up a local Grafana instance.
+  - Create a `config.alloy` file.
 
 <!-- INTERACTIVE ignore START -->
+
 {{< admonition type="tip" >}}
 Alternatively, you can try out this example in the interactive learning environment: [Sending metrics to Prometheus](https://killercoda.com/grafana-labs/course/alloy/send-metrics-to-prometheus).
 
 It's a fully configured environment with all the dependencies already installed.
 
-![Interactive](/media/docs/alloy/Alloy-Interactive-Learning-Environment-(Doc-Banner).png)
+![Interactive](</media/docs/alloy/Alloy-Interactive-Learning-Environment-(Doc-Banner).png>)
 {{< /admonition >}}
+
 <!-- INTERACTIVE ignore END -->
 
 {{< docs/ignore >}}
+
 > Since this tutorial builds on the previous one, a setup script is automatically run to ensure you have the necessary prerequisites in place. This should take no longer than 1 minute to complete. You may begin the tutorial when you see this message: `Installation script has now been completed. You may now begin the tutorial.`
-{{< /docs/ignore >}}
+> {{< /docs/ignore >}}
 
 <!-- INTERACTIVE page intro.md END -->
 
@@ -74,8 +78,9 @@ You add components to your `config.alloy` file to tell {{< param "PRODUCT_NAME"
 The following steps build on the `config.alloy` file you created in the previous tutorial.
 
 {{< docs/ignore >}}
+
 > The interactive sandbox has a VSCode-like editor that allows you to access files and folders. To access this feature, click on the `Editor` tab. The editor also has a terminal that you can use to run commands. Since some commands assume you are within a specific directory, we recommend running the commands in `tab1`.
-{{< /docs/ignore >}}
+> {{< /docs/ignore >}}
 
 ### First component: Scraping
 
@@ -93,9 +98,9 @@ prometheus.scrape "scrape_metrics" {
 
 This configuration creates a [`prometheus.scrape`][prometheus.scrape] component named `scrape_metrics` which does the following:
 
-* It connects to the `local_system` component as its source or target.
-* It forwards the metrics it scrapes to the receiver of another component called `filter_metrics`.
-* It tells {{< param "PRODUCT_NAME" >}} to scrape metrics every 10 seconds.
+- It connects to the `local_system` component as its source or target.
+- It forwards the metrics it scrapes to the receiver of another component called `filter_metrics`.
+- It tells {{< param "PRODUCT_NAME" >}} to scrape metrics every 10 seconds.
 
 ### Second component: Filter metrics
 
@@ -123,9 +128,9 @@ Within this component, you can define rule blocks to specify how you would like
 
 This configuration creates a [`prometheus.relabel`][prometheus.relabel] component named `filter_metrics` which does the following:
 
-* It receives scraped metrics from the `scrape_metrics` component.
-* It tells {{< param "PRODUCT_NAME" >}} to drop metrics that have an `"env"` label equal to `"dev"`.
-* It forwards the processed metrics to the receiver of another component called `metrics_service`.
+- It receives scraped metrics from the `scrape_metrics` component.
+- It tells {{< param "PRODUCT_NAME" >}} to drop metrics that have an `"env"` label equal to `"dev"`.
+- It forwards the processed metrics to the receiver of another component called `metrics_service`.
 
 ### Third component: Write metrics to Prometheus
 
@@ -149,6 +154,7 @@ This final component creates a [`prometheus.remote_write`][prometheus.remote_wri
 This completes the simple configuration pipeline.
 
 <!-- INTERACTIVE ignore START -->
+
 {{< admonition type="tip" >}}
 The `basic_auth` is commented out because the local `docker compose` stack doesn't require it.
 It's included in this example to show how you can configure authorization for other environments.
@@ -156,12 +162,15 @@ It's included in this example to show how you can configure authorization for ot
 For further authorization options, refer to the [`prometheus.remote_write`][prometheus.remote_write] component documentation.
 
 [prometheus.remote_write]: ../../reference/components/prometheus/prometheus.remote_write/
+
 {{< /admonition >}}
+
 <!-- INTERACTIVE ignore END -->
 
 {{< docs/ignore >}}
+
 > The `basic_auth` is commented out because the local `docker compose` stack doesn't require it. It's included in this example to show how you can configure authorization for other environments. For further authorization options, refer to the [`prometheus.remote_write`](../../reference/components/prometheus/prometheus.remote_write/) component documentation.
-{{< /docs/ignore >}}
+> {{< /docs/ignore >}}
 
 This connects directly to the Prometheus instance running in the Docker container.
 
@@ -180,7 +189,9 @@ sudo cp config.alloy /etc/alloy/config.alloy
 ```
 
 {{< /docs/ignore >}}
+
 <!-- INTERACTIVE ignore START -->
+
 {{< code >}}
 
 ```macos
@@ -192,6 +203,7 @@ sudo cp config.alloy /etc/alloy/config.alloy
 ```
 
 {{< /code >}}
+
 <!-- INTERACTIVE ignore END -->
 
 Call the `/-/reload` endpoint to tell {{< param "PRODUCT_NAME" >}} to reload the configuration file without a system service restart.
@@ -201,6 +213,7 @@ curl -X POST http://localhost:12345/-/reload
 ```
 
 <!-- INTERACTIVE ignore START -->
+
 {{< admonition type="tip" >}}
 This step uses the {{< param "PRODUCT_NAME" >}} UI, on `localhost` port `12345`.
 If you choose to run Alloy in a Docker container, make sure you use the `--server.http.listen-addr=0.0.0.0:12345` argument.
@@ -208,7 +221,9 @@ If you choose to run Alloy in a Docker container, make sure you use the `--serve
 If you don't use this argument, the [debugging UI][debug] won't be available outside of the Docker container.
 
 [debug]: ../../troubleshoot/debug/#alloy-ui
+
 {{< /admonition >}}
+
 <!-- INTERACTIVE ignore END -->
 
 {{< docs/ignore >}}
@@ -228,6 +243,7 @@ Optional: You can do a system service restart {{< param "PRODUCT_NAME" >}} and l
 {{< /docs/ignore >}}
 
 <!-- INTERACTIVE ignore START -->
+
 {{< code >}}
 
 ```macos
@@ -239,6 +255,7 @@ sudo systemctl reload alloy
 ```
 
 {{< /code >}}
+
 <!-- INTERACTIVE ignore END -->
 
 <!-- INTERACTIVE page step2.md END -->