diff --git a/docs/customization/account-portal/overview.mdx b/docs/customization/account-portal/overview.mdx
index d7da74184a..e74b3c6337 100644
--- a/docs/customization/account-portal/overview.mdx
+++ b/docs/customization/account-portal/overview.mdx
@@ -32,7 +32,7 @@ For each application environment, Clerk provides pages for sign-up, sign-in, use
The sign-in page hosts the prebuilt [``](/docs/components/authentication/sign-in) component, which renders a UI for signing in users. The functionality of the `` component is controlled by the instance settings you specify in your [Clerk Dashboard](https://dashboard.clerk.com), such as [sign-up and sign-in options](/docs/authentication/configuration/sign-up-sign-in-options) and [social connections](/docs/authentication/social-connections/overview).
-
+
Redirect users to the sign-in page using the [``](/docs/components/control/redirect-to-signin) control component.
@@ -40,7 +40,7 @@ Redirect users to the sign-in page using the [``](/docs/comp
The sign-up page hosts the prebuilt [``](/docs/components/authentication/sign-up) component, which renders a UI for signing up users. The functionality of the `` component is controlled by the instance settings you specify in your [Clerk Dashboard](https://dashboard.clerk.com), such as [sign-up and sign-in options](/docs/authentication/configuration/sign-up-sign-in-options) and [social connections](/docs/authentication/social-connections/overview).
-
+
Redirect users to the sign-up page using the [``](/docs/components/control/redirect-to-signup) control component.
diff --git a/docs/deployments/changing-domains.mdx b/docs/deployments/changing-domains.mdx
index 291ec8022c..de13769a7a 100644
--- a/docs/deployments/changing-domains.mdx
+++ b/docs/deployments/changing-domains.mdx
@@ -11,8 +11,8 @@ Learn how to change your Clerk production instance's domain or subdomain.
## Change domain
1. Update your production domain in two ways:
- - [the Clerk Dashboard](#update-your-domain-via-clerk-dashboard)
- - [Clerk's backend API](#update-your-domain-via-backend-api)
+ - the [Clerk Dashboard](#update-your-domain-via-clerk-dashboard)
+ - the [backend API](#update-your-domain-via-backend-api)
1. Once you make the change to your domain, you will need to update the following:
- Update DNS records
- Generate new SSL certificates
diff --git a/docs/deployments/set-up-staging.mdx b/docs/deployments/set-up-staging.mdx
index 03909bef66..2eafdbb04a 100644
--- a/docs/deployments/set-up-staging.mdx
+++ b/docs/deployments/set-up-staging.mdx
@@ -3,7 +3,7 @@ title: Set up a staging environment with Clerk
description: Learn how to set up a staging environment with Clerk authentication.
---
-Staging environments enable you to internally test and demo changes to your application or website before deploying them to production. Currently, Clerk only offers **Development** and **Production** instances. Official support for **Staging** instances is still on [Clerk's roadmap](https://feedback.clerk.com/roadmap/de417dd1-fa2e-4997-868f-4c9248027e7d). However, you can set up a "staging environment" by creating a subdomain for a separate Clerk application.
+Staging environments enable you to internally test and demo changes to your application or website before deploying them to production. Currently, Clerk only offers **Development** and **Production** instances. Official support for **Staging** instances is still on the [roadmap](https://feedback.clerk.com/roadmap/de417dd1-fa2e-4997-868f-4c9248027e7d). However, you can set up a "staging environment" by creating a subdomain for a separate Clerk application.
Creating a separate Clerk application will prevent you from using live production environment data in your staging environment. If you are on a Pro, Enterprise, or Startup plan, **Clerk will fully upgrade your staging application for free.**