Remove beta callout

website/docs/docs/cloud/about-cloud-develop-defer.md

@@ -13,7 +13,7 @@ Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to pr
 
 ## Required setup
 
-- You must select the **[Production environment](/docs/deploy/deploy-environments#set-as-production-environment-beta)** checkbox in the **Environment Settings** page. 
+- You must select the **[Production environment](/docs/deploy/deploy-environments#set-as-production-environment)** checkbox in the **Environment Settings** page. 
   - This can be set for one deployment environment per dbt Cloud project.
 - You must have a successful job run first.
 

website/docs/docs/collaborate/explore-projects.md

@@ -17,7 +17,7 @@ Try dbt Explorer! It's available in [Public Preview](/docs/dbt-versions/product-
 ## Prerequisites
 
 - You have a [multi-tenant](/docs/cloud/about-cloud/tenancy#multi-tenant) or AWS single-tenant dbt Cloud account on the [Team or Enterprise plan](https://www.getdbt.com/pricing/).
-- You have set up a [production deployment environment](/docs/deploy/deploy-environments#set-as-production-environment-beta) for each project you want to explore.
+- You have set up a [production deployment environment](/docs/deploy/deploy-environments#set-as-production-environment) for each project you want to explore.
     - There has been at least one successful job run in the production deployment environment.
 - You are on the dbt Explorer page. To do this, select **Explore** from the top navigation bar in dbt Cloud.
 

website/docs/docs/collaborate/govern/project-dependencies.md

@@ -29,7 +29,7 @@ Starting in dbt v1.6 or higher, `packages.yml` has been renamed to `dependencies
 
 In order to add project dependencies and resolve cross-project `ref`, you must:
 - Use dbt v1.6 or higher for **both** the upstream ("producer") project and the downstream ("consumer") project.
-- Have a deployment environment in the upstream ("producer") project [that is set to be your production environment](/docs/deploy/deploy-environments#set-as-production-environment-beta)
+- Have a deployment environment in the upstream ("producer") project [that is set to be your production environment](/docs/deploy/deploy-environments#set-as-production-environment)
 - Have a successful run of the upstream ("producer") project
 - Have a multi-tenant or single-tenant [dbt Cloud Enterprise](https://www.getdbt.com/pricing) account (Azure ST is not supported but coming soon)
 

website/docs/docs/deploy/deploy-environments.md

@@ -28,16 +28,12 @@ To create a new dbt Cloud development environment, navigate to **Deploy** -> **E
 
 <Lightbox src="/img/docs/dbt-cloud/cloud-configuring-dbt-cloud/create-deploy-env.jpg" width="85%" title="Navigate to Deploy ->  Environments to create a deployment environment" />
 
-### Set as production environment (Beta)
+### Set as production environment
 
-import ExpBeta from '/snippets/_explorer-beta-banner.md';  
-
-<ExpBeta/>
+In dbt Cloud, each project can have one designated deployment environment, which serves as its production environment. This production environment is _essential_ for using features like dbt Explorer and cross-project references. It acts as the source of truth for the project's production state in dbt Cloud.
 
 <Lightbox src="/img/docs/dbt-cloud/using-dbt-cloud/prod-settings.jpg" width="70%" title="Set your production environment as the default environment in your Environment Settings"/>
 
-In dbt Cloud, each project can have one designated deployment environment, which serves as its production environment. This production environment is _essential_ for using features like dbt Explorer and cross-project references. It acts as the source of truth for the project's production state in dbt Cloud.
-
 ### Semantic Layer
 
 For Semantic Layer-eligible customers, the next section of environment settings is the Semantic Layer configurations. [The Semantic Layer setup guide](/docs/use-dbt-semantic-layer/setup-sl) has the most up-to-date setup instructions!

website/snippets/_explorer-beta-note.md

@@ -1 +1 @@
-**Note:** Make sure to set the environment to "Production" so you can take advantage of features like dbt Explorer and cross-project references. Refer to [Set product environment](/docs/deploy/deploy-environments#set-as-production-environment-beta) for details.
+**Note:** Make sure to set the environment to "Production" so you can take advantage of features like dbt Explorer and cross-project references. Refer to [Set product environment](/docs/deploy/deploy-environments#set-as-production-environment) for details.