Docs suggest only gateway collectors can support proxy settings

This change is attempting to clarify that any collector can support proxy settings. However most customers would prefer to use a gateway collector so they don't need to configure proxy settings on each collector.

Feel free to wordsmith this PR to convey that message.

admin/authentication/allow-services.rst

@@ -28,7 +28,7 @@ Ensure that you give the proxy the ability to resolve the network names and make
 Use the Splunk Distribution of the OpenTelemetry Collector
 =======================================================================
 
-Use the :new-page:`Splunk Distribution of OpenTelemetry Collector <https://docs.splunk.com/Observability/gdi/opentelemetry/deployment-modes.html>` in data forwarding (gateway) mode. You can forward metrics locally to the Splunk Distribution of OpenTelemetry Collector, which serves as your local store-and-forward service for telemetry.
+The :new-page:`Splunk Distribution of OpenTelemetry Collector <https://docs.splunk.com/Observability/gdi/opentelemetry/deployment-modes.html>` supports configuring proxies. You can configure this on each collector, or a more typical method would be to configure a collector in data forwarding (gateway) mode. In the gateway paradigm you only need to configure the gateway collector(s) with the proxy settings; all other collectors can simply send data to the gateway collector.
 
 Ensure that you give the Splunk Distribution of OpenTelemetry Collector the ability to resolve the network names and make outbound HTTPS network connections to the URLs listed in :ref:`allow-urls` or the domains listed in :ref:`allow-domains`. Verify also the list of :ref:`exposed ports and endpoints <otel-exposed-endpoints>`.