addresses feedback

content/en/docs/collector/deployment/agent.md

@@ -5,12 +5,12 @@ description:
 weight: 2
 ---
 
-The agent collector deployment pattern consists of
-applications — [instrumented][instrumentation] with an OpenTelemetry SDK using
-[OpenTelemetry protocol (OTLP)][otlp] — or other collectors (using the OTLP
-exporter) that send telemetry signals to a [collector][collector] instance
-running with the application or on the same host as the application (such as a
-sidecar or a daemonset).
+The agent collector deployment pattern consists of applications —
+[instrumented][instrumentation] with an OpenTelemetry SDK using [OpenTelemetry
+protocol (OTLP)][otlp] — or other collectors (using the OTLP exporter) that send
+telemetry signals to a [collector][collector] instance running with the
+application or on the same host as the application (such as a sidecar or a
+daemonset).
 
 Each client-side SDK or downstream collector is configured with a collector
 location:

content/en/docs/collector/deployment/gateway.md

@@ -34,8 +34,8 @@ Let's have a look at such a case where we are using the load-balancing exporter:
    signals to a group of collectors.
 1. The collectors are configured to send telemetry data to one or more backends.
 
-> **Note** Currently, only trace pipelines are supported by the load-balancing
-> exporter.
+{{% alert title="Note" color="info" %}} Currently, the load-balancing exporter
+only supports pipelines of the `traces` type. {{% /alert %}}
 
 ## Example