chore: authorized redirect URI > redirect URI (#1632)

docs/authentication/social-connections/atlassian.mdx

@@ -7,7 +7,7 @@ How to set up social connection with Atlassian
 
 ## Overview
 
-Adding social connection with Atlassian to your app with Clerk is done in a few steps - you will need to populate the **Client ID**, **Client Secret** and **Authorized redirect URI** in your instance settings.
+Adding social connection with Atlassian to your app with Clerk is done in a few steps - you will need to populate the **Client ID**, **Client Secret** and **Redirect URI** in your instance settings.
 
 To make the development flow as smooth as possible, Clerk uses  preconfigured shared OAuth credentials and redirect URIs for development instances - no other configuration is needed.
 
@@ -49,7 +49,7 @@ This is done by navigating to the Authorization section and clicking on Add.
 
 ![Atlassian OAuth 2.0 Authorization page](/docs/images/authentication-providers/atlassian/3d60a54bb48c03257afbf769f1f50cf45f18871c-3456x1730.png)
 
-In this section, you will need to paste the Authorized redirect URI that Clerk has provided for you.
+In this section, you will need to paste the Redirect URI that Clerk has provided for you.
 
 ![Atlassian OAuth 2.0 App callback URL settings](/docs/images/authentication-providers/atlassian/a6dc9bd0902359cad9c94de1bdcbd4c9112bff1d-3456x1730.png)
 

docs/authentication/social-connections/bitbucket.mdx

@@ -7,7 +7,7 @@ How to set up social connection with Bitbucket
 
 ## Overview
 
-Adding social connection with Bitbucket to your app with Clerk is done in a few steps - you will need to populate the **Client ID**, **Client Secret** and **Authorized redirect URI** in your instance settings.
+Adding social connection with Bitbucket to your app with Clerk is done in a few steps - you will need to populate the **Client ID**, **Client Secret** and **Redirect URI** in your instance settings.
 
 To make the development flow as smooth as possible, Clerk uses  preconfigured shared OAuth credentials and redirect URIs for development instances - no other configuration is needed.
 
@@ -37,7 +37,7 @@ From there, click on the desired existing workspace or create a new one, then na
 
 You will need to create a consumer if you don't have one already.
 
-The first important setting for the connection to work is the **Callback URL**. Paste the **Authorized redirect URI** from your Clerk Bitbucket settings in this field:
+The first important setting for the connection to work is the **Callback URL**. Paste the **Redirect URI** from your Clerk Bitbucket settings in this field:
 
 ![OAuth consumer creation](/docs/images/authentication-providers/bitbucket/3c3f5f49188f740839a9e0f348ffe4d34a5300c3-3360x1782.png)
 

docs/authentication/social-connections/box.mdx

@@ -7,7 +7,7 @@ How to set up social connection with Box
 
 ## Overview
 
-Adding social connection with Box to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Authorized redirect URI** in your instance settings.
+Adding social connection with Box to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Redirect URI** in your instance settings.
 
 To make the development flow as smooth as possible, Clerk uses preconfigured shared OAuth credentials and redirect URIs for development instances - no other configuration is needed.
 

docs/authentication/social-connections/coinbase.mdx

@@ -7,7 +7,7 @@ How to set up social connection with Coinbase
 
 ## Overview
 
-Adding social connection with Coinbase to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Authorized redirect URI** in your instance settings.
+Adding social connection with Coinbase to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Redirect URI** in your instance settings.
 
 To make the development flow as smooth as possible, Clerk uses preconfigured shared OAuth credentials and redirect URIs for development instances - no other configuration is needed.
 
@@ -29,7 +29,7 @@ You need to set all the required fields and the corresponding **Permitted Redire
 
 ![Creating application](/docs/images/authentication-providers/coinbase/creating-application.jpg)
 
-Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections). In the top navigation, select **Configure**. Then in the sidebar, select **SSO Connections**. Select the **Add connection** button, and select **For all users**. In the **Choose provider** dropdown, select **Coinbase**. Toggle on **Use custom credentials** and copy **Authorized redirect URI**. Make sure the value matches the **Redirect URIs**, as shown below.
+Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections). In the top navigation, select **Configure**. Then in the sidebar, select **SSO Connections**. Select the **Add connection** button, and select **For all users**. In the **Choose provider** dropdown, select **Coinbase**. Toggle on **Use custom credentials** and copy **Redirect URI**. Make sure the value matches the **Redirect URIs**, as shown below.
 
 ![Copying the Client ID and Client Secret from the Box dashboard](/docs/images/authentication-providers/coinbase/copying-values-from-box-dashboard.jpg)
 

docs/authentication/social-connections/discord.mdx

@@ -44,15 +44,15 @@ To make the setup process easier, it's recommended to keep two browser tabs open
   1. Select **Add connection** and select **For all users**.
   1. In the **Choose provider** dropdown, select **Discord**.
   1. Ensure that both **Enable for sign-up and sign-in** and **Use custom credentials** are toggled on.
-  1. Save the **Authorized redirect URI** somewhere secure. Keep the modal and page open.
+  1. Save the **Redirect URI** somewhere secure. Keep the modal and page open.
 
   ### Create a Discord Developer app
 
   1. On a separate page, go to the [Discord Developers Portal](https://discord.com/developers/applications) and sign in.
   1. In the top-right, select **New Application**.
   1. Complete the required fields and select **Create**. You'll be redirected to the **General Information** page.
   1. In the sidebar, select **OAuth2**.
-  1. Under **Redirects**, select **Add Redirect**. Paste the **Authorized Redirect URI** you saved from the Clerk Dashboard.
+  1. Under **Redirects**, select **Add Redirect**. Paste the **Redirect URI** you saved from the Clerk Dashboard.
   1. Select **Save Changes**. You may need to tap anywhere on the screen for the button to show. Keep this page open.
 
   ### Set the Client ID and Client Secret in your Clerk Dashboard

docs/authentication/social-connections/dropbox.mdx

@@ -7,7 +7,7 @@ How to set up social connection with Dropbox
 
 ## Overview
 
-Adding social connection with Dropbox to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Authorized redirect URI** in your instance settings.
+Adding social connection with Dropbox to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Redirect URI** in your instance settings.
 
 To make the development flow as smooth as possible, Clerk uses preconfigured shared OAuth credentials and redirect URIs for development instances - no other configuration is needed.
 
@@ -29,7 +29,7 @@ First, you need to register a new OAuth Dropbox app at the [Dropbox App Console]
 
 First you need to choose the API type, the App's type of access and to set a name for your new application. You also need to add the **OAuth Redirect URLs.**
 
-Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections). In the top navigation, select **Configure**. Then in the sidebar, select **SSO Connections**. Select the **Add connection** button, and select **For all users**. In the **Choose provider** dropdown, select **Dropbox**. Toggle on **Use custom credentials** and copy **Authorized redirect URI**. Paste the value into the **OAuth Redirect URIs** input and click create.
+Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections). In the top navigation, select **Configure**. Then in the sidebar, select **SSO Connections**. Select the **Add connection** button, and select **For all users**. In the **Choose provider** dropdown, select **Dropbox**. Toggle on **Use custom credentials** and copy **Redirect URI**. Paste the value into the **OAuth Redirect URIs** input and click create.
 
 Once all the above are complete, copy the **Client ID** and **Client Secret.** Go back to the Clerk Dashboard and paste them into the respective fields.
 

docs/authentication/social-connections/facebook.mdx

@@ -7,7 +7,7 @@ How to set up social connection with Facebook
 
 ## Overview
 
-Adding social connection with Facebook to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Authorized redirect URI** in your instance settings.
+Adding social connection with Facebook to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Redirect URI** in your instance settings.
 
 To make the development flow as smooth as possible, Clerk uses  preconfigured shared OAuth credentials and redirect URIs for development instances - no other configuration is needed.
 
@@ -39,6 +39,6 @@ Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=u
 
 ![Adding the valid OAuth Redirect URI](/docs/images/authentication-providers/facebook/c0be80ce8fed2b4d14d04fcbf56318b80295093d-1467x989.png)
 
-Before you close the modal, copy the **Authorized redirect URI**. Go back to the Facebook dashboard, open the **Facebook Login** menu (sidebar) and click **Settings**. Paste the URI you copied before into the **Valid OAuth Redirect URIs** field. Hit **Save Changes**.
+Before you close the modal, copy the **Redirect URI**. Go back to the Facebook dashboard, open the **Facebook Login** menu (sidebar) and click **Settings**. Paste the URI you copied before into the **Valid OAuth Redirect URIs** field. Hit **Save Changes**.
 
 Finally, select **Add connection** so that the settings are applied. Congratulations! Social connection with Facebook is now configured for your instance.

docs/authentication/social-connections/github.mdx

@@ -45,14 +45,14 @@ To make the setup process easier, it's recommended to keep two browser tabs open
   1. Select **Add connection** and choose **For all users**.
   1. In the **Choose provider** dropdown, select **GitHub**.
   1. Ensure that both **Enable for sign-up and sign-in** and **Use custom credentials** are toggled on.
-  1. Save the **Authorized redirect URI** somewhere secure. Keep the modal and page open.
+  1. Save the **Redirect URI** somewhere secure. Keep the modal and page open.
 
   ### Create a GitHub app
 
   1. On a separate page, go to [GitHub's Developer Settings](https://github.com/settings/apps).
   1. In the sidebar, select **OAuth Apps**, then select [**New OAuth app**](https://github.com/settings/applications/new). You'll be redirected to the **Register a new OAuth app** form.
   1. Enter your **Application name** and **Homepage URL**.
-  1. In **Authorization callback URL**, paste the **Authorized Redirect URI** you saved from the Clerk Dashboard.
+  1. In **Authorization callback URL**, paste the **Redirect URI** you saved from the Clerk Dashboard.
   1. Select **Register application**. You'll be redirected to your GitHub app's **General** page.
 
   ### Set the Client ID and Client Secret in your Clerk Dashboard

docs/authentication/social-connections/gitlab.mdx

@@ -7,7 +7,7 @@ How to set up social connection with GitLab
 
 ## Overview
 
-Adding social connection with GitLab to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Authorized redirect URI** in your instance settings.
+Adding social connection with GitLab to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Redirect URI** in your instance settings.
 
 To make the development flow as smooth as possible, Clerk uses  preconfigured shared OAuth credentials and redirect URIs for development instances - no other configuration is needed.
 
@@ -27,7 +27,7 @@ First, you need to register a new OAuth GitLab app. Follow the official GitLab i
 
 ![Creating an OAuth GitLab app](/docs/images/authentication-providers/gitlab/7e67b1cb88c1df509cac722d6a6b2d7c624686f8-1919x840.png)
 
-Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections). In the top navigation, select **Configure**. Then in the sidebar, select **SSO Connections**. Select the **Add connection** button, and select **For all users**. In the **Choose provider** dropdown, select **GitLab**. Toggle on **Use custom credentials** and copy **Authorized redirect URI**. Go back to the GitLab panel, paste the value into the **Redirect URI**, select any scopes that would you like your users to provide and save the application.
+Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections). In the top navigation, select **Configure**. Then in the sidebar, select **SSO Connections**. Select the **Add connection** button, and select **For all users**. In the **Choose provider** dropdown, select **GitLab**. Toggle on **Use custom credentials** and copy **Redirect URI**. Go back to the GitLab panel, paste the value into the **Redirect URI**, select any scopes that would you like your users to provide and save the application.
 
 Once creation is complete, you'll get redirected to application's panel. Copy the **Application ID** and **Secret.** Go back to the Clerk Dashboard and paste them into the respective fields.
 

docs/authentication/social-connections/google.mdx

@@ -47,7 +47,7 @@ To make the setup process easier, it's recommended to keep two browser tabs open
   1. Select **Add connection** and select **For all users**.
   1. In the **Choose provider** dropdown, select **Google**.
   1. Ensure that both **Enable for sign-up and sign-in** and **Use custom credentials** are toggled on.
-  1. Save the **Authorized redirect URI** somewhere secure. Keep this modal and page open.
+  1. Save the **Redirect URI** somewhere secure. Keep this modal and page open.
 
   ### Create a Google Developer project
 
@@ -57,7 +57,7 @@ To make the setup process easier, it's recommended to keep two browser tabs open
   1. In the menu on the left, select **Credentials**.
   1. Select **Create Credentials**. Then, select **OAuth client ID.** You may need to [configure your OAuth consent screen](https://support.google.com/cloud/answer/6158849?hl=en#userconsent\&zippy=%2Cuser-consent).
   1. Select the appropriate application type for your project. Most likely, you will choose **Web application**.
-  1. In the **Authorized redirect URIs** setting, paste the **Authorized redirect URI** value you saved from the Clerk Dashboard.
+  1. In the **Authorized Redirect URIs** setting, paste the **Redirect URI** value you saved from the Clerk Dashboard.
   1. Select **Create**. Keep this page open.
 
   ### Set the Client ID and Client Secret in your Clerk Dashboard

docs/authentication/social-connections/hubspot.mdx

@@ -7,7 +7,7 @@ How to set up social connection with HubSpot
 
 ## Overview
 
-Adding social connection with HubSpot to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Authorized redirect URI** in your instance settings.
+Adding social connection with HubSpot to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Redirect URI** in your instance settings.
 
 To make the development flow as smooth as possible, Clerk uses  preconfigured shared OAuth credentials and redirect URIs for development instances - no other configuration is needed.
 
@@ -31,6 +31,6 @@ Once your app is created, click on the **Auth** tab and copy the **App Id** and
 
 Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections). In the top navigation, select **Configure**. Then in the sidebar, select **SSO Connections**. Select the **Add connection** button, and select **For all users**. In the **Choose provider** dropdown, select **HubSpot**. Toggle on **Use custom credentials** and paste the values you obtained during the previous step.
 
-Before you close the modal, copy the **Authorized redirect URI**. Go back to the HubSpot panel and paste it into the **Redirect URL** field and click **Save**.
+Before you close the modal, copy the **Redirect URI**. Go back to the HubSpot panel and paste it into the **Redirect URL** field and click **Save**.
 
 Finally, select **Add connection** so that the settings are applied. Congratulations! Social connection with HubSpot is now configured for your instance.

docs/authentication/social-connections/huggingface.mdx

@@ -53,16 +53,16 @@ To configure your production instance, follow these steps:
      - **Logo URL**: Enter the URL of the logo for your application.
      - **Token Expiration**: Set the duration for which the token will be valid.
      - **Scopes**: Select the scopes that your application requires. Ensure that **openid**, **profile**, and **email** are included.
-     - **Redirect URLs**: You will need to add the **Authorized redirect URI** from Clerk. See the next step.
+     - **Redirect URLs**: You will need to add the **Redirect URI** from Clerk. See the next step.
 
   ### Get your Redirect URI from Clerk
 
   1. Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections).
   1. In the top navigation, select **Configure**. Then in the sidebar, select **SSO Connections**.
   1. Select the **Add connection** button, and select **For all users**.
   1. In the **Choose provider** dropdown, select **Hugging Face**.
-  1. Ensure that both **Enable for sign-up and sign-in** and **Use custom credentials** are toggled on. Then, copy the **Authorized redirect URI**.
-  1. Navigate back to Hugging Face and paste the **Authorized redirect URI** into the **Redirect URLs** field.
+  1. Ensure that both **Enable for sign-up and sign-in** and **Use custom credentials** are toggled on. Then, copy the **Redirect URI**.
+  1. Navigate back to Hugging Face and paste the **Redirect URI** into the **Redirect URLs** field.
   1. Select **Create application**.
 
   ### Set the Client ID and Client Secret in Clerk

docs/authentication/social-connections/line.mdx

@@ -7,7 +7,7 @@ How to set up social connection with LINE
 
 ## Overview
 
-Adding social connection with LINE to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Authorized redirect URI** in your instance settings.
+Adding social connection with LINE to your app with Clerk is done in a few steps - you only need to set the **Client ID**, **Client Secret** and **Redirect URI** in your instance settings.
 
 To make the development flow as smooth as possible, Clerk uses preconfigured shared OAuth credentials and redirect URIs for development instances - no other configuration is needed.
 
@@ -34,7 +34,7 @@ The next step is to create a new **LINE Login channel**. You will have to select
 
 In the next screen, after the app has been created, you will find the **Basic settings** of the application. If you want to also make email address available for your application, you will have to apply for **Email address permission** in the bottom of your app's **Basic settings**.
 
-Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections). In the top navigation, select **Configure**. Then in the sidebar, select **SSO Connections**. Select the **Add connection** button, and select **For all users**. In the **Choose provider** dropdown, select **LINE**. Toggle on **Use custom credentials** and copy **Authorized redirect URI**. Paste the value into the **LINE login → Callback URL** input.
+Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections). In the top navigation, select **Configure**. Then in the sidebar, select **SSO Connections**. Select the **Add connection** button, and select **For all users**. In the **Choose provider** dropdown, select **LINE**. Toggle on **Use custom credentials** and copy **Redirect URI**. Paste the value into the **LINE login → Callback URL** input.
 
 Once all the above are complete, copy the **Channel ID** and **Channel secret.** Go back to the Clerk Dashboard and paste them into the respective fields.