feat: remove universal broker EA disclaimer

Author: shuaibmunshi

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,10 +1,5 @@
 # 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 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 set of client replicas is called a Broker deployment. The diagram below shows two deployments, Universal Broker A and Universal Broker B.