Merge pull request #686 from snyk/feat/universal-broker-ga

feat: remove universal broker EA disclaimer [ACC-2903] [DOCT-1742]

Author: mikeromard

docs/developer-tools/scm-integrations/scm-integrations-and-snyk-broker.md

@@ -43,7 +43,7 @@ GitLab account with `Maintainer` permission.
 
 ## GitHub Server App for Universal Broker
 
-If your GithHub server is not publicly available, you can provide access to it through the Universal Broker, a proxy deployed in your internal network to facilitate outbound connections and communication with Snyk.
+If your GitHub server is not publicly available, you can provide access to it through the Universal Broker, a proxy deployed in your internal network to facilitate outbound connections and communication with Snyk.
 
 The setup process for Universal Broker involves:
 

docs/enterprise-setup/snyk-broker/universal-broker/README.md

@@ -1,11 +1,6 @@
 # Universal Broker
 
-{% hint style="info" %}
-**Release status**\
-Universal Broker is in Early Access and is available only with Enterprise plans.
-{% endhint %}
-
-The Universal Broker improves the management of Broker deployments and connections, supporting many connections of any type through a single running client, preferably with multiple replicas, that is, entirely distinct clients. Credentials remain entirely local to your network and are never stored on the Snyk platform, which uses credentials references.
+The Universal Broker improves the management of Broker deployments and connections by supporting many connections of any type with a single running client (container) or with multiple client replicas. Credentials remain within your network and are never stored by or transmitted to Snyk. The Snyk platform uses credentials references to instruct the Universal Broker how to authenticate with your private resources.
 
 Each client or client with replicas is called a Broker deployment. The diagram shows two deployments, Universal Broker A and Universal Broker B.