diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 28f2cb1698..2f0bd45d3f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,6 +1,6 @@
# Contributing to Clerk's documentation
-Thanks for being willing to contribute to [Clerk's documentation](https://clerk.com/docs)! This document outlines how to effectively contribute to the documentation content located in this repository. Check out the [style guide](./styleguides/styleguide.md) for more information on our guidelines for writing content.
+Thanks for being willing to contribute to [Clerk's documentation](https://clerk.com/docs)! This document outlines how to effectively contribute to the documentation content located in this repository. See the [style guide](./styleguides/styleguide.md) for more information on our guidelines for writing content.
## Written in MDX
diff --git a/docs/advanced-usage/clerk-idp.mdx b/docs/advanced-usage/clerk-idp.mdx
index 890cd78d43..0adb7e166a 100644
--- a/docs/advanced-usage/clerk-idp.mdx
+++ b/docs/advanced-usage/clerk-idp.mdx
@@ -10,7 +10,7 @@ Clerk can be configured as an identity provider to facilitate Single Sign-On (SS
## When should you use Clerk as an OAuth provider?
-You can use Clerk as an OAuth provider if you want your users to sign in to a third party site or a tool using their credentials from your application. **This is not the same as supporting an OAuth provider, such as Google, in your application. If you want your users to be able to sign in to your application with an OAuth provider, see [the dedicated guide](/docs/authentication/social-connections/oauth#configuration).**
+You can use Clerk as an OAuth provider if you want your users to sign in to a third party site or a tool using their credentials from your application. **This is not the same as supporting an OAuth provider, such as Google, in your application. If you want your users to be able to sign in to your application with an OAuth provider, see the [dedicated guide](/docs/authentication/social-connections/oauth#configuration).**
## How it works
diff --git a/docs/advanced-usage/satellite-domains.mdx b/docs/advanced-usage/satellite-domains.mdx
index d451505ce4..b38cdc136f 100644
--- a/docs/advanced-usage/satellite-domains.mdx
+++ b/docs/advanced-usage/satellite-domains.mdx
@@ -407,4 +407,4 @@ To access authentication state from a satellite domain, users will be transparen
You can repeat this process and create as many satellite applications as you need.
-If you have any questions about satellite domains, or you're having any trouble setting this up, please contact [support@clerk.com](mailto:support@clerk.com)
+If you have any questions about satellite domains, or you're having any trouble setting this up, contact [support@clerk.com](mailto:support@clerk.com)
diff --git a/docs/advanced-usage/using-proxies.mdx b/docs/advanced-usage/using-proxies.mdx
index 4e24707c2c..8c1bb035c5 100644
--- a/docs/advanced-usage/using-proxies.mdx
+++ b/docs/advanced-usage/using-proxies.mdx
@@ -20,7 +20,7 @@ When using a proxy, all requests to the Frontend API will be made through your d
To get started, you need to create an application from the [Clerk Dashboard](https://dashboard.clerk.com/). Once you create an instance via the Clerk Dashboard, you will be prompted to choose a domain. For the purposes of this guide, the domain will be `app.dev`.
> [!NOTE]
- > For more information on creating a Clerk application, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
+ > For more information on creating a Clerk application, see the [setup guide](/docs/quickstarts/setup-clerk).
### Configure your proxy server
@@ -146,7 +146,7 @@ When using a proxy, all requests to the Frontend API will be made through your d
> [!NOTE]
- > Every proxy configuration will be different and we're here to help. Please [reach out](/contact/support){{ target: '_blank' }} if there's a specific use-case you're looking to solve.
+ > Every proxy configuration will be different and we're here to help. [Contact support](/contact/support){{ target: '_blank' }} if there's a specific use-case you're looking to solve.
### Enable proxying
@@ -305,4 +305,4 @@ When using a proxy, all requests to the Frontend API will be made through your d
Your application should now be able to access the Frontend API from your proxy!
-If you have any questions about proxying, or you're having any trouble setting this up, please contact [support@clerk.com](mailto:support@clerk.com).
+If you have any questions about proxying, or you're having any trouble setting this up, contact [support@clerk.com](mailto:support@clerk.com).
diff --git a/docs/authentication/configuration/email-sms-templates.mdx b/docs/authentication/configuration/email-sms-templates.mdx
index 5ce93cefb0..4dc0a4077f 100644
--- a/docs/authentication/configuration/email-sms-templates.mdx
+++ b/docs/authentication/configuration/email-sms-templates.mdx
@@ -23,7 +23,7 @@ It will be useful to take a look at the following terms as they will reappear in
### Revolvapp WYSIWYG email editor plugin
-The email editor uses the [Revolvapp](https://imperavi.com/redactor/legacy/revolvapp) email template editor plugin by Imperavi. To acquaint yourself with the template markup syntax, please consult the corresponding [documentation page](https://imperavi.com/redactor/legacy/revolvapp/docs/syntax/quick-start).
+The email editor uses the [Revolvapp](https://imperavi.com/redactor/legacy/revolvapp) email template editor plugin by Imperavi. To acquaint yourself with the template markup syntax, consult [Imperavi's docs](https://imperavi.com/redactor/legacy/revolvapp/docs/syntax/quick-start).
As you will see, the template markup is an HTML-like language and each type of node supports its own set of attributes which control its behavior. A lot of the attributes are borrowed from HTML itself.
diff --git a/docs/authentication/configuration/session-options.mdx b/docs/authentication/configuration/session-options.mdx
index f488ac610e..9f45163e4a 100644
--- a/docs/authentication/configuration/session-options.mdx
+++ b/docs/authentication/configuration/session-options.mdx
@@ -80,4 +80,4 @@ There are two main ways to add the multi-session feature to your application:
Session tokens are JWTs that contain a set of [default claims](/docs/backend-requests/resources/session-tokens) required by Clerk. You can customize these tokens by providing additional claims of your own.
-To learn how to customize session tokens, check out our [Customize your session token](/docs/backend-requests/making/custom-session-token) guide.
+To learn how to customize session tokens, see the [dedicated guide](/docs/backend-requests/making/custom-session-token).
diff --git a/docs/authentication/configuration/sign-up-sign-in-options.mdx b/docs/authentication/configuration/sign-up-sign-in-options.mdx
index 733ff2a0c3..e68a634b39 100644
--- a/docs/authentication/configuration/sign-up-sign-in-options.mdx
+++ b/docs/authentication/configuration/sign-up-sign-in-options.mdx
@@ -208,4 +208,4 @@ To reset a user's MFA:
## Restrictions
-Clerk provides a set of restriction options designed to provide you with enhanced control over who can gain access to your application. Restrictions can limit sign-ups or prevent accounts with specific identifiers, such as email addresses, phone numbers, and even entire domains, from accessing your application. [Learn more about restrictions.](/docs/authentication/configuration/restrictions)
+Clerk provides a set of restriction options designed to provide you with enhanced control over who can gain access to your application. Restrictions can limit sign-ups or prevent accounts with specific identifiers, such as email addresses, phone numbers, and even entire domains, from accessing your application. [Learn more about restrictions](/docs/authentication/configuration/restrictions).
diff --git a/docs/authentication/overview.mdx b/docs/authentication/overview.mdx
index ce6700cf48..751d726583 100644
--- a/docs/authentication/overview.mdx
+++ b/docs/authentication/overview.mdx
@@ -9,4 +9,4 @@ Clerk supports multiple authentication strategies so that you can implement the
Clerk's configuration settings affect how the users of your application can [sign up and sign in](/docs/authentication/configuration/sign-up-sign-in-options) and which properties are editable via their user profile. You can also manage [user sessions](/docs/authentication/configuration/session-options), [control who gets access](/docs/authentication/configuration/restrictions) to your application, and [customize the email & SMS messages](/docs/authentication/configuration/email-sms-templates) that are sent by Clerk during authentication flows. All of these settings can be found under the **User & Authentication** section in the [Clerk Dashboard](https://dashboard.clerk.com/).
-Check out our detailed guide for information on [how to set up your application](/docs/quickstarts/setup-clerk).
+For more information on how to set up your application, see the [setup guide](/docs/quickstarts/setup-clerk).
diff --git a/docs/authentication/saml/custom-provider.mdx b/docs/authentication/saml/custom-provider.mdx
index cc64295782..15162ea682 100644
--- a/docs/authentication/saml/custom-provider.mdx
+++ b/docs/authentication/saml/custom-provider.mdx
@@ -101,7 +101,7 @@ Clerk supports Enterprise SSO via the SAML protocol, enabling you to create auth
For example, say you were using Google as your IdP. Google users have the "Phone number" attribute. Clerk does not have a direct mapping for this attribute, as you can see in the Clerk Dashboard in the **Attribute mapping** section. Instead, in the Google dashboard, you would map Google's "Phone number" claim to `public_metadata_phone_number`. Then, in Clerk, the value for the user's phone number would be saved in the user's `User.publicMetadata` under the key `phone_number`.
- [Learn more about how to access the metadata from our APIs.](/docs/users/metadata)
+ Learn more about [how to access the metadata from our APIs](/docs/users/metadata).
### Activate your SAML connection
diff --git a/docs/authentication/saml/google.mdx b/docs/authentication/saml/google.mdx
index 87357f6bbd..88c0bcaaff 100644
--- a/docs/authentication/saml/google.mdx
+++ b/docs/authentication/saml/google.mdx
@@ -120,7 +120,7 @@ description: Learn how to integrate Google Workspace with Clerk using SAML SSO.
The value for the user's phone number will be saved in the user's `User.publicMetadata` under the key `phone_number`.
- [Learn more about how to access the metadata from our APIs.](/docs/users/metadata)
+ Learn more about [how to access the metadata from our APIs](/docs/users/metadata).
### Enable the connection on Google
diff --git a/docs/authentication/saml/overview.mdx b/docs/authentication/saml/overview.mdx
index 84d9ab5ead..7f0bd583aa 100644
--- a/docs/authentication/saml/overview.mdx
+++ b/docs/authentication/saml/overview.mdx
@@ -44,10 +44,10 @@ Yes, Clerk supports both Service Provider-initiated (SP-initiated) and Identity
### How much does it cost?
-For production instances, each active connection costs $50 per month. SAML connections require the Pro plan and the Enhanced Authentication Add-on. Please see [pricing](/pricing){{ target: '_blank' }} for those costs, and the costs of other add-ons or features.
+For production instances, each active connection costs $50 per month. SAML connections require the Pro plan and the Enhanced Authentication Add-on. See [pricing](/pricing){{ target: '_blank' }} for those costs, and the costs of other add-ons or features.
For development instances, SAML connections will always be free, but capped to 5.
### Can I get a bulk discount?
-Yes, [reach out to support](/contact/support){{ target: '_blank' }} to work out a custom plan.
+Yes, [contact support](/contact/support){{ target: '_blank' }} to work out a custom plan.
diff --git a/docs/authentication/social-connections/atlassian.mdx b/docs/authentication/social-connections/atlassian.mdx
index 4817c83d1f..195f114d9e 100644
--- a/docs/authentication/social-connections/atlassian.mdx
+++ b/docs/authentication/social-connections/atlassian.mdx
@@ -18,7 +18,7 @@ For production instances, you will need to generate your own Client ID and Clien
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
- You need to have a Atlassian developer account. To create one, [click here](https://developer.atlassian.com/).
## Configuring an Atlassian OAuth 2.0 Integration
diff --git a/docs/authentication/social-connections/bitbucket.mdx b/docs/authentication/social-connections/bitbucket.mdx
index 5b364d165e..6ce431692f 100644
--- a/docs/authentication/social-connections/bitbucket.mdx
+++ b/docs/authentication/social-connections/bitbucket.mdx
@@ -18,7 +18,7 @@ For production instances, you will need to generate your own Consumer Key and Co
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
- You need to have a Bitbucket account. To create one, [click here](https://bitbucket.org/account/signup).
## Configuring Bitbucket social connection
diff --git a/docs/authentication/social-connections/box.mdx b/docs/authentication/social-connections/box.mdx
index c5d0893370..4bc3263bbc 100644
--- a/docs/authentication/social-connections/box.mdx
+++ b/docs/authentication/social-connections/box.mdx
@@ -18,7 +18,7 @@ For production instances, you will need to generate your own Client ID and Clien
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
- You need to have a Box developer account. To create one, [click here](https://developer.box.com/).
## Configuring Box social connection
diff --git a/docs/authentication/social-connections/dropbox.mdx b/docs/authentication/social-connections/dropbox.mdx
index 1de4dd325f..b4f9ee467c 100644
--- a/docs/authentication/social-connections/dropbox.mdx
+++ b/docs/authentication/social-connections/dropbox.mdx
@@ -18,7 +18,7 @@ For production instances, you will need to generate your own Client ID and Clien
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
- You need to have a Dropbox account. To create one, [click here](https://www.dropbox.com/lp/developers).
## Configuring Dropbox social connection
diff --git a/docs/authentication/social-connections/facebook.mdx b/docs/authentication/social-connections/facebook.mdx
index ee49fd4692..d1dadca059 100644
--- a/docs/authentication/social-connections/facebook.mdx
+++ b/docs/authentication/social-connections/facebook.mdx
@@ -18,7 +18,7 @@ For production instances, you will need to create your own developer account wit
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
- You need to have a Facebook Developer account. To create one, consult the [Register as a Facebook developer](https://developers.facebook.com/docs/development/register) page.
## Configuring Facebook social connection
diff --git a/docs/authentication/social-connections/hubspot.mdx b/docs/authentication/social-connections/hubspot.mdx
index dc810ef48c..3a1e77863c 100644
--- a/docs/authentication/social-connections/hubspot.mdx
+++ b/docs/authentication/social-connections/hubspot.mdx
@@ -18,7 +18,7 @@ For production instances, you will need to create your own developer account wit
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
- You need to have a HubSpot Developer account. To create one, [click here](https://app.hubspot.com/signup/developers/step/existing-user?_ga=2.145169076.1430980384.1628431607-741498900.1628431607).
## Configuring HubSpot social connection
diff --git a/docs/authentication/social-connections/line.mdx b/docs/authentication/social-connections/line.mdx
index 515e099771..f9ca2f1ca0 100644
--- a/docs/authentication/social-connections/line.mdx
+++ b/docs/authentication/social-connections/line.mdx
@@ -21,7 +21,7 @@ For production instances, you will need to generate your own Client ID and Clien
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
- You need to have a LINE developer account. To create one, [click here](https://developers.line.biz/en/).
## Configuring LINE social connection
diff --git a/docs/authentication/social-connections/linkedin.mdx b/docs/authentication/social-connections/linkedin.mdx
index c9d0a20c17..c453dc3d54 100644
--- a/docs/authentication/social-connections/linkedin.mdx
+++ b/docs/authentication/social-connections/linkedin.mdx
@@ -19,7 +19,7 @@ For production instances, you will need to generate your own Client ID and Clien
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
- You need to have a LinkedIn account. To create one, [click here](https://developer.linkedin.com/).
## Configuring LinkedIn social connection
diff --git a/docs/authentication/social-connections/notion.mdx b/docs/authentication/social-connections/notion.mdx
index 730a441ea3..ff2d821cad 100644
--- a/docs/authentication/social-connections/notion.mdx
+++ b/docs/authentication/social-connections/notion.mdx
@@ -18,7 +18,7 @@ For production instances, you will need to generate your own Client ID and Clien
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
- You need to have a Notion developer account. To create one, [click here](https://developers.notion.com/).
## Configuring Notion social connection
diff --git a/docs/authentication/social-connections/oauth.mdx b/docs/authentication/social-connections/oauth.mdx
index 91d9b7a0af..42e1d60268 100644
--- a/docs/authentication/social-connections/oauth.mdx
+++ b/docs/authentication/social-connections/oauth.mdx
@@ -8,12 +8,12 @@ Clerk makes it easy to add social connection capabilities to your application. W
> [!NOTE]
> When using social connections, the sign-up and sign-in flows are equivalent. If a user doesn't have an account and tries to sign in, an account will be made for them, and vice versa.
-The easiest way to add social connections to your Clerk app is by using [prebuilt components](/docs/components/overview). If you prefer a more custom solution, check out how to [build a social connection flow using the Clerk API](/docs/custom-flows/oauth-connections).
+The easiest way to add social connections to your Clerk app is by using [prebuilt components](/docs/components/overview). If you prefer a more custom solution, see the [build a social connection flow using the Clerk API guide](/docs/custom-flows/oauth-connections).
## Before you start
-- You need to create a Clerk application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out the [Set up your application](/docs/quickstarts/setup-clerk) guide.
-- You need to install the correct SDK for your application. You can find steps on how to do so through the [quickstart guides.](/docs/quickstarts/overview)
+- You need to create a Clerk application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out the [setup guide](/docs/quickstarts/setup-clerk).
+- You need to install the correct SDK for your application. For more information, see the [quickstart guides](/docs/quickstarts/overview).
## Enable a social connection
@@ -144,13 +144,13 @@ To configure the option for users to sign up and sign in with a social provider:
When signed in, a user can connect to further social providers. There is no need to perform another sign-up.
-When using the [Account Portal](/docs/customization/account-portal/overview) pages, users can see which providers they have already connected to and which ones they can still connect to on their [user profile page.](/docs/customization/account-portal/overview#user-profile)
+When using the [Account Portal](/docs/customization/account-portal/overview) pages, users can see which providers they have already connected to and which ones they can still connect to on their [user profile page](/docs/customization/account-portal/overview#user-profile).
When using the [prebuilt components](/docs/components/overview), you can use the [``](/docs/components/user/user-profile) component to allow users to connect to further social providers.
## OAuth for native applications
-Currently, the prebuilt components are not supported in native applications, but you can use the Clerk API to [build a custom flow for authenticating with social connections.](/docs/custom-flows/oauth-connections)
+Currently, the prebuilt components are not supported in native applications, but you can use the Clerk API to [build a custom flow for authenticating with social connections](/docs/custom-flows/oauth-connections).
Clerk ensures that security critical nonces are passed only to allowlisted URLs when the OAuth flow is completed in native browsers or webviews. For maximum security in your **production** instances, you need to allowlist your custom redirect URLs via the [Clerk Dashboard](https://dashboard.clerk.com/) or the [Clerk Backend API](/docs/references/backend/redirect-urls/create-redirect-url).
@@ -166,4 +166,4 @@ You can use [Sign in with Apple](https://developer.apple.com/sign-in-with-apple/
Instead of the typical OAuth flow that performs redirects in a browser context, you can utilize Apple's native authorization and provide the openID token and grant code to Clerk. Clerk ensures that the user will be verified in a secure and reliable way with the information that Apple has provided about the user.
-See [the dedicated guide](/docs/authentication/social-connections/apple) for additional information on how to configure Apple as a social provider for your Clerk instance.
+For additional information on how to configure Apple as a social provider for your Clerk instance, see the [dedicated guide](/docs/authentication/social-connections/apple).
diff --git a/docs/authentication/social-connections/overview.mdx b/docs/authentication/social-connections/overview.mdx
index a2502ae3a5..d97041a66e 100644
--- a/docs/authentication/social-connections/overview.mdx
+++ b/docs/authentication/social-connections/overview.mdx
@@ -157,4 +157,4 @@ Clerk provides a wide range of social providers to ease your user's sign-up and
- 
-Don't see the provider you're looking for? You can [configure a custom OIDC-compatible provider](/docs/authentication/social-connections/custom-provider) or [request a new one.](https://feedback.clerk.com/roadmap/f9045ac8-0c8e-4f30-b84f-8d551b0767b9?_gl=1*1ywoqdy*_gcl_au*OTUwODgxMjg2LjE3MTI1OTEwNzMuMTczNjk0NTcxMC4xNzE1MTk4MTEyLjE3MTUxOTgxMTI.)
+Don't see the provider you're looking for? You can [configure a custom OIDC-compatible provider](/docs/authentication/social-connections/custom-provider) or [request a new one](https://feedback.clerk.com/roadmap/f9045ac8-0c8e-4f30-b84f-8d551b0767b9?_gl=1*1ywoqdy*_gcl_au*OTUwODgxMjg2LjE3MTI1OTEwNzMuMTczNjk0NTcxMC4xNzE1MTk4MTEyLjE3MTUxOTgxMTI.).
diff --git a/docs/authentication/social-connections/twitch.mdx b/docs/authentication/social-connections/twitch.mdx
index d08bd2897a..87ef7c16a6 100644
--- a/docs/authentication/social-connections/twitch.mdx
+++ b/docs/authentication/social-connections/twitch.mdx
@@ -18,7 +18,7 @@ For production instances, you will need to generate your own Client ID and Clien
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
- You need to have a Twitch account. To create one, [click here](https://www.twitch.tv/).
## Configuring Twitch social connection
diff --git a/docs/authentication/social-connections/twitter.mdx b/docs/authentication/social-connections/twitter.mdx
index 54449ced7b..3f864006d7 100644
--- a/docs/authentication/social-connections/twitter.mdx
+++ b/docs/authentication/social-connections/twitter.mdx
@@ -19,8 +19,8 @@ Clerk does not currently support preconfigured shared OAuth credentials for Twit
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
-- You need to have a Twitter Application set up so it can be used for Social connection. If you don't have a Twitter Application, click [here](https://developer.twitter.com/en/docs/apps/overview) for instructions on how to create one. If you already have one, please go to your [Twitter app settings](https://developer.twitter.com/en/portal/projects-and-apps) and ensure that the _"Allow this app to be used to Sign in with Twitter?_” option is enabled.
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
+- You need to have a Twitter Application set up so it can be used as a social connection. If you don't have a Twitter Application, click [here](https://developer.twitter.com/en/docs/apps/overview) for instructions on how to create one. If you already have one, go to your [Twitter app settings](https://developer.twitter.com/en/portal/projects-and-apps) and ensure that the _"Allow this app to be used to Sign in with Twitter?_” option is enabled.
## Configuring Twitter social connection
diff --git a/docs/authentication/social-connections/xero.mdx b/docs/authentication/social-connections/xero.mdx
index 385173ffdf..8aefa329f5 100644
--- a/docs/authentication/social-connections/xero.mdx
+++ b/docs/authentication/social-connections/xero.mdx
@@ -18,7 +18,7 @@ For production instances, you will need to generate your own Client ID and Clien
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application guide](/docs/quickstarts/setup-clerk).
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
- You need to have a Xero developer account. To create one, [click here](https://developer.xero.com/).
## Configuring Xero social connection
diff --git a/docs/authentication/web3/coinbase-wallet.mdx b/docs/authentication/web3/coinbase-wallet.mdx
index d7e5f26bcf..82c4713450 100644
--- a/docs/authentication/web3/coinbase-wallet.mdx
+++ b/docs/authentication/web3/coinbase-wallet.mdx
@@ -18,7 +18,7 @@ description: Learn how to set up Web3 authentication with Coinbase Wallet.
Enabling [Coinbase Wallet](https://www.coinbase.com/wallet) as a Web3 provider allows your users to sign in and sign up to your Clerk application with their Coinbase Wallet. Both [Smart Wallet](https://www.coinbase.com/wallet/smart-wallet) and the [Coinbase Wallet browser extension](https://www.coinbase.com/wallet/downloads) are supported.
> [!WARNING]
-> This guide is for using Coinbase Wallet for authentication. If you are looking to connect users via [Coinbase.com](https://www.coinbase.com/), see [the guide for enabling Coinbase as a social provider.](/docs/authentication/social-connections/coinbase)
+> This guide is for using Coinbase Wallet for authentication. If you are looking to connect users via [Coinbase.com](https://www.coinbase.com/), see [the guide for enabling Coinbase as a social provider](/docs/authentication/social-connections/coinbase).
## Enable Coinbase Wallet as a Web3 provider
diff --git a/docs/backend-requests/handling/nodejs.mdx b/docs/backend-requests/handling/nodejs.mdx
index 301b2cae3a..046ecf5715 100644
--- a/docs/backend-requests/handling/nodejs.mdx
+++ b/docs/backend-requests/handling/nodejs.mdx
@@ -4,7 +4,7 @@ description: Learn how to handle authenticated requests with Clerk's Node SDK.
---
> [!CAUTION]
-> On January 8, 2025, the Node SDK will no longer be available. [Upgrade to the Express SDK.](/docs/upgrade-guides/node-to-express)
+> On January 8, 2025, the Node SDK will no longer be available. [Upgrade to the Express SDK](/docs/upgrade-guides/node-to-express).
## Node SDK Middleware
@@ -28,7 +28,7 @@ The Clerk Node SDK offers two authentication middlewares specifically for [Expre
'/protected-endpoint',
ClerkExpressWithAuth({
// Add options here
- // See the Middleware options section for more details
+ // See the Middleware options section for more information
}),
(req, res) => {
res.json(req.auth)
@@ -60,7 +60,7 @@ The Clerk Node SDK offers two authentication middlewares specifically for [Expre
'/protected-route',
ClerkExpressWithAuth({
// Add options here
- // See the Middleware options section for more details
+ // See the Middleware options section for more information
}),
(req: WithAuthProp, res: Response) => {
res.json(req.auth)
@@ -96,7 +96,7 @@ The Clerk Node SDK offers two authentication middlewares specifically for [Expre
'/protected-endpoint',
ClerkExpressRequireAuth({
// Add options here
- // See the Middleware options section for more details
+ // See the Middleware options section for more information
}),
(req, res) => {
res.json(req.auth)
@@ -132,7 +132,7 @@ The Clerk Node SDK offers two authentication middlewares specifically for [Expre
'/protected-route',
ClerkExpressRequireAuth({
// Add options here
- // See the Middleware options section for more details
+ // See the Middleware options section for more information
}),
(req: RequireAuthProp, res) => {
res.json(req.auth)
diff --git a/docs/backend-requests/resources/session-tokens.mdx b/docs/backend-requests/resources/session-tokens.mdx
index 1aacad3e1a..72faf320e2 100644
--- a/docs/backend-requests/resources/session-tokens.mdx
+++ b/docs/backend-requests/resources/session-tokens.mdx
@@ -36,4 +36,4 @@ You can also create custom tokens using a [JWT template](/docs/backend-requests/
If you're using the middleware provided by our Clerk SDKs, this is all handled automatically in every request. If you're not using the middleware, you can still use the respective helpers provided by the SDKs to validate the tokens.
-To learn how to manually verify a session token, please refer to the [dedicated guide](/docs/backend-requests/handling/manual-jwt).
+To learn how to manually verify a session token, refer to the [dedicated guide](/docs/backend-requests/handling/manual-jwt).
diff --git a/docs/components/authentication/sign-in.mdx b/docs/components/authentication/sign-in.mdx
index b180e73ebb..6b54a98f87 100644
--- a/docs/components/authentication/sign-in.mdx
+++ b/docs/components/authentication/sign-in.mdx
@@ -81,7 +81,7 @@ All props are optional.
- `transferable?`
- `boolean`
- Indicates whether or not sign in attempts are transferable to the sign up flow. Defaults to `true`. When set to `false`, prevents opaque sign ups when a user attempts to sign in via OAuth with an email that doesn't exist. See [OAuth account transfer flows](/docs/custom-flows/oauth-connections#o-auth-account-transfer-flows) for more details.
+ Indicates whether or not sign in attempts are transferable to the sign up flow. Defaults to `true`. When set to `false`, prevents opaque sign ups when a user attempts to sign in via OAuth with an email that doesn't exist. See [OAuth account transfer flows](/docs/custom-flows/oauth-connections#o-auth-account-transfer-flows) for more information.
## Usage with frameworks
@@ -92,7 +92,7 @@ The following example includes basic implementation of the `` componen
The following example demonstrates how you can use the `` component on a public page.
- If you would like to create a dedicated `/sign-in` page in your Next.js application, check out the [dedicated guide.](/docs/references/nextjs/custom-signup-signin-pages).
+ If you would like to create a dedicated `/sign-in` page in your Next.js application, see the [dedicated guide](/docs/references/nextjs/custom-signup-signin-pages).
```tsx {{ filename: 'app/page.tsx' }}
import { SignIn, useUser } from '@clerk/nextjs'
diff --git a/docs/components/authentication/sign-up.mdx b/docs/components/authentication/sign-up.mdx
index f7f47eef2d..5bdc635363 100644
--- a/docs/components/authentication/sign-up.mdx
+++ b/docs/components/authentication/sign-up.mdx
@@ -85,7 +85,7 @@ The following example includes basic implementation of the `` componen
The following example demonstrates how you can use the `` component on a public page.
- If you would like to create a dedicated `/sign-up` page in your Next.js application, check out the [dedicated guide.](/docs/references/nextjs/custom-signup-signin-pages).
+ If you would like to create a dedicated `/sign-up` page in your Next.js application, see the [dedicated guide](/docs/references/nextjs/custom-signup-signin-pages).
```tsx {{ filename: 'app/page.tsx' }}
import { SignUp, useUser } from '@clerk/nextjs'
diff --git a/docs/components/control/redirect-to-createorganization.mdx b/docs/components/control/redirect-to-createorganization.mdx
index 33e8eb7e36..ce58b33610 100644
--- a/docs/components/control/redirect-to-createorganization.mdx
+++ b/docs/components/control/redirect-to-createorganization.mdx
@@ -19,7 +19,7 @@ The `` component will navigate to the create org
- Please Sign In
+ Sign In
)
}
@@ -43,7 +43,7 @@ The `` component will navigate to the create org
- Please Sign In
+ Sign In
)
}
@@ -61,7 +61,7 @@ The `` component will navigate to the create org
-
Please sign in
+
Sign in
)
diff --git a/docs/components/control/redirect-to-organizationprofile.mdx b/docs/components/control/redirect-to-organizationprofile.mdx
index 055e1bc7e1..c11a07c037 100644
--- a/docs/components/control/redirect-to-organizationprofile.mdx
+++ b/docs/components/control/redirect-to-organizationprofile.mdx
@@ -19,7 +19,7 @@ The `` component will navigate to the organizat
- Please Sign In
+ Sign In
)
}
@@ -43,7 +43,7 @@ The `` component will navigate to the organizat
- Please Sign In
+ Sign In
)
}
@@ -61,7 +61,7 @@ The `` component will navigate to the organizat
-
Please sign in
+
Sign in
)
diff --git a/docs/components/control/redirect-to-userprofile.mdx b/docs/components/control/redirect-to-userprofile.mdx
index 894d83a30c..0ab7806ee6 100644
--- a/docs/components/control/redirect-to-userprofile.mdx
+++ b/docs/components/control/redirect-to-userprofile.mdx
@@ -25,7 +25,7 @@ To find your User Profile URL:
- Please Sign In
+ Sign In
)
}
@@ -44,7 +44,7 @@ To find your User Profile URL:
- Please Sign In
+ Sign In
)
}
@@ -62,7 +62,7 @@ To find your User Profile URL:
-
Please sign in
+
Sign in
)
diff --git a/docs/components/organization/create-organization.mdx b/docs/components/organization/create-organization.mdx
index 3454c910b0..48b8c091c8 100644
--- a/docs/components/organization/create-organization.mdx
+++ b/docs/components/organization/create-organization.mdx
@@ -5,7 +5,7 @@ description: Clerk's component is used to render an organ
-The `` component is used to render an organization creation UI that allows users to create brand new organizations within your application.
+The `` component is used to render an organization creation UI that allows users to create brand new organizations in your application.
## Properties
diff --git a/docs/components/organization/organization-switcher.mdx b/docs/components/organization/organization-switcher.mdx
index 4631c64094..94aa821185 100644
--- a/docs/components/organization/organization-switcher.mdx
+++ b/docs/components/organization/organization-switcher.mdx
@@ -9,7 +9,7 @@ The `` component allows a user to switch between their a
This component will show notifications to the user if they have organization [invitations](/docs/organizations/overview#organization-invitations) or [suggestions](/docs/organizations/overview#suggestions). Admins will be able to see notifications for [requests](/docs/organizations/overview#membership-requests) to join an organization.
-If you would like to learn how to hide a user's personal account in order to enforce an organization-centric application, see the [dedicated guide.](/docs/guides/force-organizations)
+If you would like to learn how to hide a user's personal account in order to enforce an organization-centric application, see the [dedicated guide](/docs/guides/force-organizations).
## `` properties
diff --git a/docs/components/user/user-button.mdx b/docs/components/user/user-button.mdx
index db405de874..df17409495 100644
--- a/docs/components/user/user-button.mdx
+++ b/docs/components/user/user-button.mdx
@@ -7,7 +7,7 @@ description: Clerk's component is used to render the familiar use
The `` component is used to render the familiar user button UI popularized by Google.
-Clerk is the only provider with multi-session support, allowing users to sign into multiple accounts at once and switch between them. For multi-session apps, the `` automatically supports instant account switching, without the need of a full page reload. For more information, you can check out the [Multi-session applications guide](/docs/custom-flows/multi-session-applications#overview).
+Clerk is the only provider with multi-session support, allowing users to sign into multiple accounts at once and switch between them. For multi-session apps, the `` automatically supports instant account switching, without the need of a full page reload. For more information, see the [dedicated guide on multi-session apps](/docs/custom-flows/multi-session-applications#overview).
## Properties
@@ -347,4 +347,4 @@ clerk.unmountUserButton(userButtonDiv)
To learn about how to customize Clerk components, see the [customization documentation](/docs/customization/overview).
-You can also [add custom actions and links to the `` menu.](/docs/customization/user-button)
+You can also [add custom actions and links to the `` menu](/docs/customization/user-button).
diff --git a/docs/custom-flows/email-links.mdx b/docs/custom-flows/email-links.mdx
index 56d5238fde..2d79e0441c 100644
--- a/docs/custom-flows/email-links.mdx
+++ b/docs/custom-flows/email-links.mdx
@@ -14,7 +14,7 @@ Email links are the default passwordless authentication strategy when using Cler
Your users will still be able to choose an alternative authentication (or verification) method even after they've clicked the email link they received in their inbox. Email links are simply the default authentication method for email address-based, passwordless authentication in Clerk.
> [!NOTE]
-> Looking for one-time code (OTP) authentication? Check out our [one-time code authentication](/docs/custom-flows/email-sms-otp) guide.
+> Looking for one-time code (OTP) authentication? See the [one-time code authentication guide](/docs/custom-flows/email-sms-otp).
## Email link flow
@@ -37,8 +37,8 @@ We take care of the boring stuff, like efficient polling, secure session managem
## Before you start
-- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out our [Set up your application](/docs/quickstarts/setup-clerk) guide.
-- You need to install the correct SDK for your application. You can find steps on how to do so through the [quickstart guides.](/docs/quickstarts/overview)
+- You need to create a Clerk Application in your [Clerk Dashboard](https://dashboard.clerk.com/). For more information, check out the [setup guide](/docs/quickstarts/setup-clerk).
+- You need to install the correct SDK for your application. For more information, see the [quickstart guides](/docs/quickstarts/overview).
## Set up email link authentication in Your Clerk application
diff --git a/docs/custom-flows/email-password-mfa.mdx b/docs/custom-flows/email-password-mfa.mdx
index f62557fe21..bd94a7aaa0 100644
--- a/docs/custom-flows/email-password-mfa.mdx
+++ b/docs/custom-flows/email-password-mfa.mdx
@@ -45,7 +45,7 @@ This guide will walk you through how to build a custom email/password sign-in fl
1. If the verification is successful, set the newly created session as the active session.
> [!TIP]
- > For this example to work, the user must have MFA enabled on their account. You need to add the ability for your users to manage their MFA settings. [Learn how to build a custom flow for managing multi-factor authentication.](/docs/custom-flows/email-password-mfa)
+ > For this example to work, the user must have MFA enabled on their account. You need to add the ability for your users to manage their MFA settings. See the [manage SMS-based MFA](/docs/custom-flows/manage-sms-based-mfa) or the [manage TOTP-based MFA](/docs/custom-flows/manage-totp-based-mfa) guide, depending on your needs.
diff --git a/docs/custom-flows/error-handling.mdx b/docs/custom-flows/error-handling.mdx
index d402febe8b..2ad75afb05 100644
--- a/docs/custom-flows/error-handling.mdx
+++ b/docs/custom-flows/error-handling.mdx
@@ -230,7 +230,7 @@ If you have [Account Lockout](/docs/security/user-lock-guide) enabled on your in
"errors": [
{
"message": "Account locked",
- "long_message": "Your account is locked. You will be able to try again in 30 minutes. For more information, please contact support.",
+ "long_message": "Your account is locked. You will be able to try again in 30 minutes. For more information, contact support.",
"code": "user_locked",
"meta": {
"lockout_expires_in_seconds": 1800
diff --git a/docs/custom-flows/forgot-password.mdx b/docs/custom-flows/forgot-password.mdx
index 0e164a9fe4..b0216471f7 100644
--- a/docs/custom-flows/forgot-password.mdx
+++ b/docs/custom-flows/forgot-password.mdx
@@ -113,7 +113,7 @@ For the sake of this guide, this example is written for Next.js App Router but i
>
{!successfulCreation && (
<>
-
+
### Enable Google as a social connection
- To use Google One Tap with Clerk, follow the steps in [the dedicated guide](/docs/authentication/social-connections/google#configuring-google-social-connection) to configure Google as a social connection in the Clerk Dashboard using custom credentials.
+ To use Google One Tap with Clerk, follow the steps in the [dedicated guide](/docs/authentication/social-connections/google#configuring-google-social-connection) to configure Google as a social connection in the Clerk Dashboard using custom credentials.
### Create the Google One Tap authentication flow
diff --git a/docs/custom-flows/manage-sms-based-mfa.mdx b/docs/custom-flows/manage-sms-based-mfa.mdx
index a81e88b3f1..b0e5cf4f11 100644
--- a/docs/custom-flows/manage-sms-based-mfa.mdx
+++ b/docs/custom-flows/manage-sms-based-mfa.mdx
@@ -17,7 +17,7 @@ One of the options that Clerk supports for MFA is **SMS verification codes**. Th
For your users to be able to enable MFA for their account, you need to enable MFA as an MFA authentication strategy in your Clerk application.
- 1. Navigate to the [Clerk Dashboard.](https://dashboard.clerk.com/last-active?path=user-authentication/multi-factor)
+ 1. Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/multi-factor).
1. In the navigation sidebar, select **User & Authentication > Multi-factor**.
1. Enable **SMS verification code** and **Backup codes** and select **Save**.
diff --git a/docs/custom-flows/manage-totp-based-mfa.mdx b/docs/custom-flows/manage-totp-based-mfa.mdx
index eb61decdb8..8f543eb150 100644
--- a/docs/custom-flows/manage-totp-based-mfa.mdx
+++ b/docs/custom-flows/manage-totp-based-mfa.mdx
@@ -17,7 +17,7 @@ One of the options that Clerk supports for MFA is **Authenticator applications (
For your users to be able to enable MFA for their account, you need to enable MFA as an MFA authentication strategy in your Clerk application.
- 1. Navigate to the [Clerk Dashboard.](https://dashboard.clerk.com/last-active?path=user-authentication/multi-factor)
+ 1. Navigate to the [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/multi-factor).
1. In the navigation sidebar, select **User & Authentication > Multi-factor**.
1. Enable **Authenticator application** and **Backup codes** and select **Save**.
diff --git a/docs/custom-flows/multi-session-applications.mdx b/docs/custom-flows/multi-session-applications.mdx
index 6498fa10f4..6d9d79e39d 100644
--- a/docs/custom-flows/multi-session-applications.mdx
+++ b/docs/custom-flows/multi-session-applications.mdx
@@ -86,13 +86,13 @@ To enable multi-session in your application, you need to configure it in the Cle
## Add a new session
-To add a new session, simply link to your existing sign-in flow. New sign-ins will automatically add to the list of available sessions on the client. To create a sign-in flow, please check one of the following popular guides:
+To add a new session, simply link to your existing sign-in flow. New sign-ins will automatically add to the list of available sessions on the client. To create a sign-in flow, see one of the following popular guides:
- [Email and password](/docs/custom-flows/email-password)
- [Passwordless authentication](/docs/custom-flows/email-sms-otp)
- [Social sign-in (OAuth)](/docs/authentication/social-connections/oauth)
-For more information on how Clerk's sign-in flow works, check out the [detailed sign-in guide](/docs/custom-flows/overview#sign-in-flow).
+For more information on how Clerk's sign-in flow works, see the [detailed sign-in guide](/docs/custom-flows/overview#sign-in-flow).
## Sign out all sessions
diff --git a/docs/customization/account-portal/overview.mdx b/docs/customization/account-portal/overview.mdx
index 7b5b6174f0..5b34a3f3a7 100644
--- a/docs/customization/account-portal/overview.mdx
+++ b/docs/customization/account-portal/overview.mdx
@@ -3,7 +3,7 @@ title: Account portal overview
description: The Account Portal offers a comprehensive solution for managing user authentication and profile management in your web application and is the fastest way to add Clerk's authentication to your application with minimal code required.
---
-The Account Portal in Clerk is a powerful feature that allows you to streamline the sign-in, sign-up, and profile management experience for your users, without having to build your own components or host your own pages. **To integrate the Account Portal with your application, check out the [setup guide](/docs/customization/account-portal/getting-started).**
+The Account Portal in Clerk is a powerful feature that allows you to streamline the sign-in, sign-up, and profile management experience for your users, without having to build your own components or host your own pages. **To integrate the Account Portal with your application, see the [setup guide](/docs/customization/account-portal/getting-started).**
@@ -21,7 +21,7 @@ The Account Portal uses Clerk's [prebuilt components](/docs/components/overview)
After a user has finished their flow in an Account Portal page, Clerk automatically redirects them back to your application along with the required authentication context. This way, users are automatically redirected to and from your application for a seamless experience.
-For each application environment, Clerk provides pages for sign-up, sign-in, user profile, organization profile, and organization creation flow. **To integrate the Account Portal with your application, check out the [setup guide](/docs/customization/account-portal/getting-started).**
+For each application environment, Clerk provides pages for sign-up, sign-in, user profile, organization profile, and organization creation flow. **To integrate the Account Portal with your application, see the [setup guide](/docs/customization/account-portal/getting-started).**
> [!IMPORTANT]
> These pages cannot be customized beyond the options provided in the [Clerk Dashboard](https://dashboard.clerk.com). If you need more customization such as [localization](/docs/customization/localization), consider using [prebuilt components](/docs/components/overview) or building your own [custom user interface](/docs/custom-flows/overview).
diff --git a/docs/customization/elements/guides/sign-in.mdx b/docs/customization/elements/guides/sign-in.mdx
index 72fa7c1efb..89c63d39af 100644
--- a/docs/customization/elements/guides/sign-in.mdx
+++ b/docs/customization/elements/guides/sign-in.mdx
@@ -280,5 +280,5 @@ description: Learn how to build a complete sign-in form with Clerk Elements.
Learn how to style your Clerk Elements components with the [styling guide](/docs/customization/elements/guides/styling).
- For more extensive customization of the UI, check out additional Clerk Elements components such as [``](/docs/customization/elements/reference/common#loading) and [``](/docs/customization/elements/reference/common#fieldstate).
+ For more extensive customization of the UI, see the additional Clerk Elements components such as [``](/docs/customization/elements/reference/common#loading) and [``](/docs/customization/elements/reference/common#fieldstate).
diff --git a/docs/customization/elements/guides/sign-up.mdx b/docs/customization/elements/guides/sign-up.mdx
index 914bd40dd0..5aed014cf7 100644
--- a/docs/customization/elements/guides/sign-up.mdx
+++ b/docs/customization/elements/guides/sign-up.mdx
@@ -285,5 +285,5 @@ description: Learn how to build a complete sign-up form with Clerk Elements.
Learn how to style your Clerk Elements components with the [styling guide](/docs/customization/elements/guides/styling).
- For more extensive customization of the UI, check out additional Clerk Elements components such as [``](/docs/customization/elements/reference/common#loading) and [``](/docs/customization/elements/reference/common#fieldstate).
+ For more extensive customization of the UI, see the additional Clerk Elements components such as [``](/docs/customization/elements/reference/common#loading) and [``](/docs/customization/elements/reference/common#fieldstate).
diff --git a/docs/customization/elements/overview.mdx b/docs/customization/elements/overview.mdx
index 71fb54cccc..b571fe7ad4 100644
--- a/docs/customization/elements/overview.mdx
+++ b/docs/customization/elements/overview.mdx
@@ -6,7 +6,7 @@ description: Learn how to use Clerk Elements to build custom UIs on top of the C
> [!WARNING]
> Clerk Elements is currently in beta with support for Next.js App Router. It is **not yet recommended for production use**.
>
-> If you have any feedback, please reach out to [beta-elements@clerk.dev](mailto:beta-elements@clerk.dev) or head over to the [GitHub Discussion](https://github.com/orgs/clerk/discussions/3315).
+> If you have any feedback, contact [beta-elements@clerk.dev](mailto:beta-elements@clerk.dev) or head over to the [GitHub Discussion](https://github.com/orgs/clerk/discussions/3315).
Clerk Elements is a library of unstyled, composable components that can be used to build custom UIs on top of the Clerk APIs without having to manage the underlying logic.
diff --git a/docs/customization/localization.mdx b/docs/customization/localization.mdx
index 261c04b9bb..3b51ede253 100644
--- a/docs/customization/localization.mdx
+++ b/docs/customization/localization.mdx
@@ -4,7 +4,7 @@ description: Use the Clerk localizations package to override and provide predefi
---
> [!WARNING]
-> This feature is currently experimental and may not behave as expected. If you encounter any issues, please reach out to [support](/contact/support){{ target: '_blank' }} with as much detail as possible.
+> This feature is currently experimental and may not behave as expected. If you encounter any issues, [contact support](/contact/support){{ target: '_blank' }} with as much detail as possible.
Clerk offers the ability to override the strings for all of the elements in each of the Clerk components. This allows you to provide localization for your users or change the wording to suit your brand.
diff --git a/docs/customization/user-button.mdx b/docs/customization/user-button.mdx
index 63c924494c..a1c17adf20 100644
--- a/docs/customization/user-button.mdx
+++ b/docs/customization/user-button.mdx
@@ -215,7 +215,7 @@ The following example demonstrates how to add an action, as well as a [custom pa
In the following example, the `` component is used to add a "Help" menu item to the `` component. The `open` prop is set to `"help"` to open the `/help` page when the menu item is selected.
- The `` component is used to render the `/help` page, and because its configured as a user profile page, the `` modal will be opened with the custom "Help" menu item. [Read more about custom pages.](/docs/customization/user-profile)
+ The `` component is used to render the `/help` page, and because its configured as a user profile page, the `` modal will be opened with the custom "Help" menu item. [Read more about custom pages](/docs/customization/user-profile).
```astro filename="pages/index.astro"
---
diff --git a/docs/deployments/changing-domains.mdx b/docs/deployments/changing-domains.mdx
index bb053f2afa..5ea13eb2c9 100644
--- a/docs/deployments/changing-domains.mdx
+++ b/docs/deployments/changing-domains.mdx
@@ -53,7 +53,7 @@ curl -XPOST -H 'Authorization: {{secret}}' -H "Content-type: application/json" -
}' 'https://api.clerk.com/v1/instance/change_domain'
```
-For more information on how to update your instance settings using the backend API, see our [backend API reference](/docs/reference/backend-api/tag/Beta-Features#operation/UpdateInstanceAuthConfig){{ target: '_blank' }}.
+For more information on how to update your instance settings using the backend API, see the [backend API reference](/docs/reference/backend-api/tag/Beta-Features#operation/UpdateInstanceAuthConfig){{ target: '_blank' }}.
### Update your publishable key
diff --git a/docs/deployments/deploy-astro.mdx b/docs/deployments/deploy-astro.mdx
index 3e2fda6aa6..227a204bb9 100644
--- a/docs/deployments/deploy-astro.mdx
+++ b/docs/deployments/deploy-astro.mdx
@@ -4,7 +4,7 @@ description: Learn how to deploy an Astro app to production with Clerk.
---
> [!WARNING]
-> This guide assumes that you have already installed Clerk in your application locally and are ready to deploy. If you haven't installed Clerk yet, see [the quickstart guide.](/docs/quickstarts/astro)
+> This guide assumes that you have already installed Clerk in your application locally and are ready to deploy. If you haven't installed Clerk yet, see [the quickstart guide](/docs/quickstarts/astro).
This guide will walk you through the steps to deploy your Astro app to production.
@@ -18,7 +18,7 @@ To deploy to a hosting platform, it's recommended to choose one of the [official
### Netlify
-Due to Netlify's caching strategies, one of Clerk's core mechanisms is unable to work as expected, resulting in infinite redirects that cause an app to fail. This also affects preview environments that use **development** API keys. It's recommended to use [production API keys with a new domain.](/docs/deployments/set-up-preview-environment#acquire-an-additional-root-domain)
+Due to Netlify's caching strategies, one of Clerk's core mechanisms is unable to work as expected, resulting in infinite redirects that cause an app to fail. This also affects preview environments that use **development** API keys. It's recommended to use [production API keys with a new domain](/docs/deployments/set-up-preview-environment#acquire-an-additional-root-domain).
Additionally, read [this section](#issues-with-edge-middleware) about **Edge middleware**.
diff --git a/docs/deployments/deploy-to-vercel.mdx b/docs/deployments/deploy-to-vercel.mdx
index 9e5399fdf4..8dac581c74 100644
--- a/docs/deployments/deploy-to-vercel.mdx
+++ b/docs/deployments/deploy-to-vercel.mdx
@@ -4,7 +4,7 @@ description: Learn how to deploy a Clerk app to Vercel.
---
> [!WARNING]
-> This guide assumes that you have already installed Clerk in your application locally and are ready to deploy. If you haven't installed Clerk yet, please see our [guide to installing Clerk in your application](/docs/quickstarts/setup-clerk) first.
+> This guide assumes that you have already installed Clerk in your application locally and are ready to deploy. If you haven't installed Clerk yet, see the [setup guide](/docs/quickstarts/setup-clerk).
If you haven't set up your application in Vercel yet, [set up a new Vercel project](#set-up-a-new-vercel-project).
@@ -32,7 +32,7 @@ If you already have a Vercel project for your application and need to integrate
## Vercel preview environment
-To configure Clerk within your Vercel preview environment, please see our guide for [configuring a preview environment](/docs/deployments/set-up-preview-environment).
+To configure Clerk within your Vercel preview environment, see the [guide for configuring a preview environment](/docs/deployments/set-up-preview-environment).
## Deploy to production
diff --git a/docs/deployments/environments.mdx b/docs/deployments/environments.mdx
index d7f6a9297f..f475466785 100644
--- a/docs/deployments/environments.mdx
+++ b/docs/deployments/environments.mdx
@@ -36,7 +36,7 @@ When deploying to production, you must first activate your `Production` environm
## Staging environments
-Clerk does not currently support staging instances in Clerk applications. However, you can set up a "staging environment" by creating a separate Clerk application with a separate domain. [Learn more.](/docs/deployments/set-up-staging)
+Clerk does not currently support staging instances in Clerk applications. However, you can set up a "staging environment" by creating a separate Clerk application with a separate domain. For more information, see the [staging guide](/docs/deployments/set-up-staging).
## Preview environments
diff --git a/docs/deployments/migrate-overview.mdx b/docs/deployments/migrate-overview.mdx
index b5dbe59558..e3196f04c6 100644
--- a/docs/deployments/migrate-overview.mdx
+++ b/docs/deployments/migrate-overview.mdx
@@ -12,7 +12,7 @@ Each of these have trade-offs you'll need to consider on behalf of for your appl
## Basic export / import
-With basic export / import, you are taking an export from your previous tool and importing data into Clerk. The most common way to handle this is by making use of the [`CreateUser`](/docs/reference/backend-api/tag/Users#operation/CreateUser){{ target: '_blank' }} Backend API endpoint. It's important to note that the `CreateUser` endpoint is rate limited. Please review our [Rate Limits](/docs/backend-requests/resources/rate-limits#backend-api-requests) page for more details.
+With basic export / import, you're taking an export from your previous tool and importing data into Clerk. The most common way to handle this is by making use of the [`CreateUser`](/docs/reference/backend-api/tag/Users#operation/CreateUser){{ target: '_blank' }} Backend API endpoint. It's important to note that the `CreateUser` endpoint is rate limited. For more information, see the [guide on rate limits](/docs/backend-requests/resources/rate-limits#backend-api-requests).
You'll also need to provide your `password_hasher` value (The hashing algorithm used to generate the password digest) and in some instances Clerk will transparently upgrade your users' password hashes to the more secure Bcrypt hashing algorithm. More details on this topic are available in the [Create a new user](/docs/reference/backend-api/tag/Users#operation/CreateUser!path=password_hasher\&t=request) Backend API Reference docs.
@@ -72,7 +72,7 @@ To use Clerk's migration script, clone the [repository](https://github.com/clerk
## Migration guides
-Clerk is hard at work writing up more and more specific migration guides and tools. If you have are interested in specific guides please provide more feedback at [https://feedback.clerk.com](https://feedback.clerk.com)
+Clerk is hard at work writing up more specific migration guides and tools. If you're interested in specific guides, contact us at [https://feedback.clerk.com](https://feedback.clerk.com)
- [Firebase](/docs/deployments/migrate-from-firebase)
diff --git a/docs/deployments/overview.mdx b/docs/deployments/overview.mdx
index 957c9fad70..1f8e9d28c6 100644
--- a/docs/deployments/overview.mdx
+++ b/docs/deployments/overview.mdx
@@ -67,7 +67,7 @@ The Clerk Dashboard home page will tell you what steps are still required to dep
### DNS records not propagating with Cloudflare
-Clerk uses a DNS check to validate this CNAME record. If this subdomain is reverse proxied behind a service that points to generic hostnames, such as Cloudflare, the DNS check will fail. Please set the DNS record for this subdomain to a "DNS only" mode on your host to prevent proxying.
+Clerk uses a DNS check to validate this CNAME record. If this subdomain is reverse proxied behind a service that points to generic hostnames, such as Cloudflare, the DNS check will fail. Set the DNS record for this subdomain to a "DNS only" mode on your host to prevent proxying.
### Deployment stuck in certificate issuance
@@ -85,4 +85,4 @@ If the command returns an empty response, your domain is correctly configured. I
### Incorrect domain
-If you accidentally set the wrong domain, you can change it through the Clerk Dashboard or the Backend API. For more information, see the [dedicated guide.](/docs/deployments/changing-domains)
+If you accidentally set the wrong domain, you can change it through the Clerk Dashboard or the Backend API. For more information, see the [dedicated guide](/docs/deployments/changing-domains).
diff --git a/docs/guides/add-onboarding-flow.mdx b/docs/guides/add-onboarding-flow.mdx
index 0591f2a733..9c7aa1df82 100644
--- a/docs/guides/add-onboarding-flow.mdx
+++ b/docs/guides/add-onboarding-flow.mdx
@@ -16,7 +16,7 @@ In this guide, you will learn how to:
For the sake of this guide, examples are written for Next.js App Router, but can be used with Next.js Pager Router as well. The examples have been pared down to the bare minimum to enable you to easily customize them to your needs.
> [!NOTE]
-> To see this guide in action, check out the [repository](https://github.com/clerk/clerk-nextjs-onboarding-sample-app/tree/main).
+> To see this guide in action, see the [repository](https://github.com/clerk/clerk-nextjs-onboarding-sample-app/tree/main).
## Add custom claims to your session token
@@ -137,7 +137,7 @@ NEXT_PUBLIC_CLERK_SIGN_UP_FORCE_REDIRECT_URL=/onboarding
## Use `publicMetadata` to track user onboarding state
-Each Clerk user has a `User` object that contains a `publicMetadata` property, which can be used to store custom data about the user. This information can be accessed on the client-side and can be used to drive application state. [Learn more about public metadata.](/docs/users/metadata#public-metadata)
+Each Clerk user has a `User` object that contains a `publicMetadata` property, which can be used to store custom data about the user. This information can be accessed on the client-side and can be used to drive application state. For more information, see the [guide on metadata](/docs/users/metadata#public-metadata).
You can use the user's `publicMetadata` to track the user's onboarding state. To do this, you will create:
diff --git a/docs/guides/authjs-migration.mdx b/docs/guides/authjs-migration.mdx
index 5b1aea726e..66dd42f541 100644
--- a/docs/guides/authjs-migration.mdx
+++ b/docs/guides/authjs-migration.mdx
@@ -301,7 +301,7 @@ This guide shows how to migrate an application using Auth.js (formerly NextAuth.
This walkthrough will help you move user data from your existing database to Clerk.
- To retain the user data in your database for easy querying, check out the documentation on [data synchronization with webhooks](/docs/integrations/webhooks/sync-data).
+ To retain the user data in your database for easy querying, see the [guide on data synchronization with webhooks](/docs/integrations/webhooks/sync-data).
1. Clone `github.com/clerk/migration-script`
diff --git a/docs/integrations/analytics/google-analytics.mdx b/docs/integrations/analytics/google-analytics.mdx
index 772f92af65..23a98d4bb6 100644
--- a/docs/integrations/analytics/google-analytics.mdx
+++ b/docs/integrations/analytics/google-analytics.mdx
@@ -34,13 +34,13 @@ To send events to Google Analytics servers, Clerk uses the [Measurement Protocol
- **Measurement ID**: The measurement ID associated with the data stream sending data to your Google Analytics 4 property. The format is **G-XXXXXXX** and can be found in the Google Analytics UI under **Admin → Data Streams → choose your stream → Measurement ID**.
-
+
#### Universal Analytics
- **Tracking ID**: The tracking ID is a string composed of your account number and the property index and is used to send data to the correct Google Analytics property. The format is **UA-YYYYYY-Z** and can be found in the Google Analytics UI under **Admin → Tracking Info → Tracking Code**.
-
+
### Include Clerk user ID
diff --git a/docs/integrations/databases/convex.mdx b/docs/integrations/databases/convex.mdx
index 9cc1199c12..d1ba3a3427 100644
--- a/docs/integrations/databases/convex.mdx
+++ b/docs/integrations/databases/convex.mdx
@@ -35,15 +35,15 @@ This tutorial assumes that you have already [set up a Clerk application](/docs/q
In the Clerk Dashboard, navigate to the [JWT Templates](https://dashboard.clerk.com/last-active?path=jwt-templates)page. Select the **New template** button to create a new template based on Convex.
- 
+ 
Once the Convex template is created, you will be redirected to the template's page. You can now configure the template to your needs.
- 
+ 
The Convex template will pre-populate the default audience (`aud`) claim required by Convex. You can include additional claims as necessary. [Shortcodes](/docs/backend-requests/making/jwt-templates#shortcodes) are available to make adding dynamic user values easy.
- 
+ 
By default, Clerk will sign the JWT with a private key automatically generated for your application, which is what most developers use for Convex. If you so choose, you can customize this key.
@@ -51,7 +51,7 @@ This tutorial assumes that you have already [set up a Clerk application](/docs/q
The next step is to configure Convex with the issuer domain provided by Clerk. From your Clerk **JWT template** screen, find the **Issuer** input and click to **Copy** the URL.
- 
+ 
In your `convex` folder, add an `auth.config.js` file with the following configuration:
@@ -161,5 +161,5 @@ This tutorial assumes that you have already [set up a Clerk application](/docs/q
### Finished!
- You now have a fully functioning React and Convex application with Clerk authentication. Be aware that Convex may require usage of their custom hooks and methods rather than Clerk's, such as using Convex's `useConvexAuth()` hook instead of Clerk's `useAuth()` hook in some cases. For more information on how to use Convex with Clerk, check out the [Convex docs](https://docs.convex.dev/auth/clerk).
+ You now have a fully functioning React and Convex application with Clerk authentication. Be aware that Convex may require usage of their custom hooks and methods rather than Clerk's, such as using Convex's `useConvexAuth()` hook instead of Clerk's `useAuth()` hook in some cases. For more information on how to use Convex with Clerk, see the [Convex docs](https://docs.convex.dev/auth/clerk).
diff --git a/docs/integrations/databases/fauna.mdx b/docs/integrations/databases/fauna.mdx
index 955a353379..c61e3817c9 100644
--- a/docs/integrations/databases/fauna.mdx
+++ b/docs/integrations/databases/fauna.mdx
@@ -23,7 +23,7 @@ description: Learn how to integrate Clerk into your Fauna application.
> [!IMPORTANT]
-> Check out the [demo repo](https://github.com/clerk/clerk-fauna-nextjs) for a full example of how to integrate Fauna with Clerk in a Next.js app.
+> See the [demo repo](https://github.com/clerk/clerk-fauna-nextjs) for a full example of how to integrate Fauna with Clerk in a Next.js app.
Integrating Fauna with Clerk gives you the benefits of using a Fauna database while leveraging Clerk's authentication, prebuilt components, and webhooks.
diff --git a/docs/integrations/databases/firebase.mdx b/docs/integrations/databases/firebase.mdx
index 7c880302fb..d480c25dbd 100644
--- a/docs/integrations/databases/firebase.mdx
+++ b/docs/integrations/databases/firebase.mdx
@@ -29,7 +29,7 @@ description: Learn how to integrate Clerk into your Firebase application.
Integrating Firebase with Clerk gives you the benefits of using Firebase's features while leveraging Clerk's authentication, prebuilt components, and webhooks.
> [!TIP]
-> Check out the [demo repo](https://github.com/clerk/clerk-firebase-nextjs) for a full example of how to integrate Firebase with Clerk in a Next.js app.
+> See the [demo repo](https://github.com/clerk/clerk-firebase-nextjs) for a full example of how to integrate Firebase with Clerk in a Next.js app.
### Configure the integration
diff --git a/docs/integrations/databases/grafbase.mdx b/docs/integrations/databases/grafbase.mdx
index 9e066640c2..5b4cd66399 100644
--- a/docs/integrations/databases/grafbase.mdx
+++ b/docs/integrations/databases/grafbase.mdx
@@ -3,28 +3,28 @@ title: Integrate Grafbase with Clerk
description: Learn how to integrate Clerk and Grafbase into your application
---
-The first step is to create a new Clerk application from your Clerk Dashboard if you haven’t done so already. You can choose whichever authentication strategy and social sign-in providers you prefer. For more information, check out our [Set up your application](/docs/quickstarts/setup-clerk) guide.
+The first step is to create a new Clerk application from your Clerk Dashboard if you haven’t done so already. You can choose whichever authentication strategy and social sign-in providers you prefer. For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
After your Clerk application has been created, go to the Clerk Dashboard and navigate to the **[JWT Templates](https://dashboard.clerk.com/last-active?path=jwt-templates)** page. Click on the **New template** button to create a new template based on Grafbase.
-
+
Once the Grafbase template is created, you will be redirected to the template's page. You can now configure the template to your needs.
-
+
The Grafbase template will pre-populate the default claims required by Grafbase. You can include additional claims as necessary. [Shortcodes](/docs/backend-requests/making/jwt-templates#shortcodes) are available to make adding dynamic user values easy.
> [!NOTE]
> If your GraphQL API restricts access based on groups, you’ll need to specify the users groups in the `groups` claim.
-
+
## Configure Grafbase
The next step is to configure Grafbase with the issuer domain provided by Clerk. From your Clerk **JWT template** screen, find the **Issuer** input and click to **Copy** the URL.
-
+
### Signed in user authentication
diff --git a/docs/integrations/databases/hasura.mdx b/docs/integrations/databases/hasura.mdx
index 03c865991a..3efd7c3d3b 100644
--- a/docs/integrations/databases/hasura.mdx
+++ b/docs/integrations/databases/hasura.mdx
@@ -3,19 +3,19 @@ title: Integrate Hasura with Clerk
description: Learn how to integrate Clerk into your Hasura application.
---
-The first step is to create a new Clerk application from your Clerk Dashboard if you haven’t done so already. You can choose whichever authentication strategy and social sign-in providers you prefer. For more information, check out our [Set up your application](/docs/quickstarts/setup-clerk) guide.
+The first step is to create a new Clerk application from your Clerk Dashboard if you haven’t done so already. You can choose whichever authentication strategy and social sign-in providers you prefer. For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
After your Clerk application has been created, go to the Clerk Dashboard and navigate to the **[JWT Templates](https://dashboard.clerk.com/last-active?path=jwt-templates)** page. Click on the **New template** button to create a new template based on Hasura.
-
+
Once the Hasura template is created, you will be redirected to the template's page. You can now configure the template to your needs.
-
+
The Hasura template will pre-populate the default claims required by Hasura. You can include additional claims as necessary. [Shortcodes](/docs/backend-requests/making/jwt-templates#shortcodes) are available to make adding dynamic user values easy.
-
+
By default, Clerk will sign the JWT with a private key automatically generated for your application, which is what most developers use for Hasura. If you so choose, you can customize this key.
@@ -25,7 +25,7 @@ The next step is to provide Hasura with the public keys used to verify the JWT i
You can find this URL in the Clerk Dashboard on the **[API keys](https://dashboard.clerk.com/last-active?path=api-keys)** page. Scroll down and click on **Advanced**. In the **JWT public key** section, copy the **JWKS URL**.
-
+
You can set up your project either with Hasura Cloud or you can [run the Hasura GraphQL engine locally using Docker Compose](https://hasura.io/docs/2.0/getting-started/docker-simple).
diff --git a/docs/integrations/databases/instantdb.mdx b/docs/integrations/databases/instantdb.mdx
index e87cf82021..daf647ecef 100644
--- a/docs/integrations/databases/instantdb.mdx
+++ b/docs/integrations/databases/instantdb.mdx
@@ -28,7 +28,7 @@ description: Learn how to integrate Clerk into your InstantDB application.
> [!IMPORTANT]
-> Check out the [demo repo](https://github.com/clerk/clerk-instantdb-nextjs) for a full example of how to integrate InstantDB with Clerk in a Next.js app.
+> See the [demo repo](https://github.com/clerk/clerk-instantdb-nextjs) for a full example of how to integrate InstantDB with Clerk in a Next.js app.
Integrating [InstantDB](https://www.instantdb.com/) with Clerk gives you the benefits of using an InstantDB database while leveraging Clerk's authentication, prebuilt components, and webhooks.
diff --git a/docs/integrations/databases/nhost.mdx b/docs/integrations/databases/nhost.mdx
index 6665e61aff..0fcdce4c44 100644
--- a/docs/integrations/databases/nhost.mdx
+++ b/docs/integrations/databases/nhost.mdx
@@ -3,19 +3,19 @@ title: Integrate Nhost with Clerk
description: Learn how to integrate Clerk into your Nhost project.
---
-The first step is to create a new Clerk application from your Clerk Dashboard if you haven’t done so already. You can choose whichever authentication strategy and social sign-in providers you prefer. For more information, check out our [Set up your application](/docs/quickstarts/setup-clerk) guide.
+The first step is to create a new Clerk application from your Clerk Dashboard if you haven’t done so already. You can choose whichever authentication strategy and social sign-in providers you prefer. For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
After your Clerk application has been created, go to the Clerk Dashboard and navigate to the **[JWT Templates](https://dashboard.clerk.com/last-active?path=jwt-templates)** page. Click on the **New template** button to create a new template based on Nhost.
-
+
Once the Nhost template is created, you will be redirected to the template's page. You can now configure the template to your needs.
-
+
The Nhost template will pre-populate the default claims required by Nhost and Hasura. You can include additional claims as necessary. [Shortcodes](/docs/backend-requests/making/jwt-templates#shortcodes) are available to make adding dynamic user values easy.
-
+
## Configure Nhost
@@ -23,11 +23,11 @@ The next step is to provide Nhost with the public keys used to verify the JWT is
You can find this URL in the Clerk Dashboard on the **[API keys](https://dashboard.clerk.com/last-active?path=api-keys)** page. Scroll down and click on **Advanced**. In the **JWT public key** section, copy the **JWKS URL**.
-
+
From your Nhost dashboard, navigate to **Settings** --> **Environment variables**.
-
+
Next to the **NOHST\_JWT\_SECRET**, click the **Edit** button and paste in the **JWKS URL** that you copied from the Clerk Dashboard.
diff --git a/docs/integrations/databases/supabase.mdx b/docs/integrations/databases/supabase.mdx
index a8705490dc..9798f54b58 100644
--- a/docs/integrations/databases/supabase.mdx
+++ b/docs/integrations/databases/supabase.mdx
@@ -23,7 +23,7 @@ description: Learn how to integrate Clerk into your Supabase application.
> [!IMPORTANT]
-> Check out the [demo repo](https://github.com/clerk/clerk-supabase-nextjs) for a full example of how to integrate Supabase with Clerk in a Next.js app.
+> See the [demo repo](https://github.com/clerk/clerk-supabase-nextjs) for a full example of how to integrate Supabase with Clerk in a Next.js app.
Integrating Supabase with Clerk gives you the benefits of using a Supabase database while leveraging Clerk's authentication, prebuilt components, and webhooks. To get the most out of Supabase with Clerk, you must implement custom [Row Level Security](https://supabase.com/docs/guides/auth/row-level-security) (RLS) policies.
diff --git a/docs/integrations/webhooks/debug-your-webhooks.mdx b/docs/integrations/webhooks/debug-your-webhooks.mdx
index 115aa800ad..f33817ae0a 100644
--- a/docs/integrations/webhooks/debug-your-webhooks.mdx
+++ b/docs/integrations/webhooks/debug-your-webhooks.mdx
@@ -89,13 +89,13 @@ The following table has some of the common response codes you might see and what
| - | - |
| `400` | Usually indicates the verification failed, but could be caused by other issues. |
| `401` | The request was not authorized. If your test in the [Test the Route Handler or API Route](#test-the-route-handler-or-api-route) section worked, you should not see this error. If you are seeing it, then you will need to configure your Middleware to accept the request. |
-| `404` | The URL for the webhook was not found. Check that your application is running and that [the endpoint is correct in the Clerk Dashboard.](/docs/integrations/webhooks/debug-your-webhooks#check-your-configuration-in-the-clerk-dashboard) |
+| `404` | The URL for the webhook was not found. Check that your application is running and that [the endpoint is correct in the Clerk Dashboard](/docs/integrations/webhooks/debug-your-webhooks#check-your-configuration-in-the-clerk-dashboard). |
| `405` | Your route is not accepting a `POST` request. All webhooks are `POST` requests and the route must accept them. Unless you are using the route for something else, you can restrict the route to `POST` requests only. |
-| `500` | The request made it to your application, but there is a code-related issue. This is likely a webhook verification issue or something in the webhook logic. Please see the following sections. |
+| `500` | The request made it to your application, but there is a code-related issue. This is likely a webhook verification issue or something in the webhook logic. See the following sections. |
## Debug webhook verification
-To verify the webhook, please see the [Create the endpoint in your application](/docs/integrations/webhooks/sync-data#create-the-endpoint-in-your-application) guide for a detailed code example. You can also visit the [guide](https://docs.svix.com/receiving/verifying-payloads/how) on verifying webhooks with the Svix library.
+To verify the webhook, see the [guide on webhooks](/docs/integrations/webhooks/sync-data#create-the-endpoint-in-your-application) for a detailed code example. You can also visit the [Svix guide on verifying payloads](https://docs.svix.com/receiving/verifying-payloads/how).
Diagnosing a problem in this part of the webhook can be challenging. Your best bet would be the liberal use of `console.log`. You could log out the following to check if the values are correct:
diff --git a/docs/integrations/webhooks/inngest.mdx b/docs/integrations/webhooks/inngest.mdx
index 2b643d007b..d92b4ffbc5 100644
--- a/docs/integrations/webhooks/inngest.mdx
+++ b/docs/integrations/webhooks/inngest.mdx
@@ -18,23 +18,23 @@ To follow this guide, you need an Inngest account (free tier is enough) and have
To create an Inngest webhook endpoint and add it to your Clerk account, open the [Webhooks](https://dashboard.clerk.com/last-active?path=webhooks) page at the Clerk dashboard. Next, select the **Add Endpoint** button.
-
+
On the next page, select the **Transformation template** tab and the **Inngest** template, then click on the **Connect to Inngest** button.
-
+
A popup window will appear to complete the setup. Select **Approve** to create the webhook.
-
+
After the popup window disappears, the Webhooks page will now display **Connected** with the webhook URL underneath. There is one more step to complete setup.
-
+
To complete the setup, scroll down and select **Create**.
-
+
You'll be redirected to the new endpoint. In your Inngest dashboard, you will see a new webhook created in your account's [production environment](https://app.inngest.com/env/production/manage/webhooks).
@@ -42,7 +42,7 @@ You'll be redirected to the new endpoint. In your Inngest dashboard, you will se
After setup, as webhook events are sent from Clerk to Inngest, new `clerk` events will appear in your [Inngest dashboard](https://app.inngest.com/env/production/events). Event names will be the prefixed `clerk/` followed by the event name. See [webhook events](/docs/integrations/webhooks/overview#supported-webhook-events) for a full list.
-
+
## Creating a function to sync a new user to a database
@@ -146,15 +146,15 @@ In your browser open [http://localhost:8288](http://localhost:8288) to see the I
To quickly get events to test within Dev Server, you can select any individual event from the **Events** tab then select the **Send to Dev Server**.
-
+
You'll now see the event in the Inngest Dev Server's **Stream** tab alongside any functions that it triggered.
-
+
From here you can select the event, replay it to re-run any functions or edit and replay to edit the event payload to test different types of events.
-
+
## Conclusion
diff --git a/docs/integrations/webhooks/overview.mdx b/docs/integrations/webhooks/overview.mdx
index ad04a9e64f..a7243739ad 100644
--- a/docs/integrations/webhooks/overview.mdx
+++ b/docs/integrations/webhooks/overview.mdx
@@ -7,7 +7,7 @@ A webhook is an _event-driven_ method of communication between applications.
Unlike typical APIs where you would need to poll for data very frequently to get it "real-time", webhooks only send data when there is an event to trigger the webhook. This makes webhooks seem "real-time", but it's important to note that they are asynchronous.
-For example, if you are onboarding a new user, you can't rely on the webhook delivery as part of that flow. Typically the delivery will happen quickly, but it's not guaranteed to be delivered immediately or at all. Webhooks are best used for things like sending a notification or updating a database, but not for synchronous flows where you need to know the webhook was delivered before moving on to the next step. If you need a synchronous flow, please see our Onboarding Guide as one example of implementing that.
+For example, if you are onboarding a new user, you can't rely on the webhook delivery as part of that flow. Typically the delivery will happen quickly, but it's not guaranteed to be delivered immediately or at all. Webhooks are best used for things like sending a notification or updating a database, but not for synchronous flows where you need to know the webhook was delivered before moving on to the next step. If you need a synchronous flow, see the [onboarding guide](/docs/guides/add-onboarding-flow) for an example.
## Clerk webhooks
@@ -86,7 +86,7 @@ The payload should always be treated as unsafe until you validate the incoming w
### Retry
-Svix will use a set schedule and retry any webhooks that fail. To see the up-to-date schedule, check out the [Svix Retry Schedule](https://docs.svix.com/retries).
+Svix will use a set schedule and retry any webhooks that fail. To see the up-to-date schedule, see the [Svix Retry Schedule](https://docs.svix.com/retries).
If Svix is attempting and failing to send a webhook, and that endpoint is removed or disabled from the **[Webhooks](https://dashboard.clerk.com/last-active?path=webhooks)** page of the Clerk Dashboard, then the attempts will also be disabled.
@@ -114,6 +114,6 @@ You can find a guide on how to use webhooks to sync your data to your database [
To ensure that the API route receiving the webhook can only be hit by your app, there are a few protections you can put in place:
-- **Verify the request signature**: Svix webhook requests are [signed](https://www.wikiwand.com/en/Digital_signature) and can be verified to ensure the request is not malicious. To learn more, check out Svix's guide on [how to verify webhooks with the svix libraries](https://docs.svix.com/receiving/verifying-payloads/how) or [how to verify webhooks manually](https://docs.svix.com/receiving/verifying-payloads/how-manual).
+- **Verify the request signature**: Svix webhook requests are [signed](https://www.wikiwand.com/en/Digital_signature) and can be verified to ensure the request is not malicious. To learn more, see Svix's guide on [how to verify webhooks with the svix libraries](https://docs.svix.com/receiving/verifying-payloads/how) or [how to verify webhooks manually](https://docs.svix.com/receiving/verifying-payloads/how-manual).
- **Only accept requests coming from [Svix's webhook IPs](https://docs.svix.com/webhook-ips.json)**: To further prevent attackers from flooding your servers or wasting your compute, you can ensure that your webhook-receiving api routes only accept requests coming from [Svix's webhook IPs](https://docs.svix.com/webhook-ips.json), rejecting all other requests.
diff --git a/docs/organizations/invitations.mdx b/docs/organizations/invitations.mdx
index 0f7a9fec80..82401ad079 100644
--- a/docs/organizations/invitations.mdx
+++ b/docs/organizations/invitations.mdx
@@ -5,7 +5,7 @@ description: Learn how to invite users to your organization.
Organization invitations allow you to add new members to your organization, granting them access to organization-specific features and resources.
-Once you create an invitation, Clerk sends an email to the invited user with a unique invitation link. When the user visits the organization invitation link, they will be redirected to the [Account Portal sign-in page](/docs/customization/account-portal/overview#sign-in). If the user is already signed in, they will be redirected to your application's homepage (`/`). If you want to redirect the user to a specific page in your application, you can [specify a redirect URL when creating the invitation.](#redirect-url)
+Once you create an invitation, Clerk sends an email to the invited user with a unique invitation link. When the user visits the organization invitation link, they will be redirected to the [Account Portal sign-in page](/docs/customization/account-portal/overview#sign-in). If the user is already signed in, they will be redirected to your application's homepage (`/`). If you want to redirect the user to a specific page in your application, you can [specify a redirect URL when creating the invitation](#redirect-url).
## Create an invitation
@@ -49,7 +49,7 @@ Use the following tabs to see examples for each method.
-Check out [the Backend API reference](https://clerk.com/docs/reference/backend-api/tag/Organization-Invitations#operation/CreateOrganizationInvitation) to see an example of the response.
+See the [Backend API guide](https://clerk.com/docs/reference/backend-api/tag/Organization-Invitations#operation/CreateOrganizationInvitation) for an example of the response.
### Redirect URL
diff --git a/docs/organizations/overview.mdx b/docs/organizations/overview.mdx
index bcccaf36ca..0f4474fde2 100644
--- a/docs/organizations/overview.mdx
+++ b/docs/organizations/overview.mdx
@@ -6,7 +6,7 @@ description: Learn about how to create and manage Clerk organizations and their
Organizations are a flexible and scalable way to manage users and their access to resources within your Clerk application. With organizations, you can assign specific roles and permissions to users, making them useful for managing projects, coordinating teams, or facilitating partnerships.
> [!NOTE]
-> To explore organizations in Clerk, check out this demo repo:
+> To explore organizations in Clerk, see the demo repo:
> [https://github.com/clerk/organizations-demo](https://github.com/clerk/organizations-demo)
## Enable organizations in your application
@@ -23,7 +23,7 @@ Once organizations are enabled, you will be presented with the default settings,
### Roles and permissions
-Roles determine a user's level of access and permissions within an organization. [Learn more about how roles and permissions work and how to create your own with Clerk.](/docs/organizations/roles-permissions)
+Roles determine a user's level of access and permissions within an organization. Learn more about [how roles and permissions work and how to create your own with Clerk](/docs/organizations/roles-permissions).
### Membership limit
@@ -82,7 +82,7 @@ If you would like to hide personal workspaces and require users to always have a
## Create an organization
-[You can create organizations in the Clerk Dashboard](#application-owner), or [your end users can create organizations in your application.](#application-user)
+[You can create organizations in the Clerk Dashboard](#application-owner), or [your end users can create organizations in your application](#application-user).
> [!WARNING]
> Clerk automatically deletes organizations that have no members after one hour.
@@ -110,9 +110,9 @@ With the Pro plan:
- In development instances, you can have an unlimited number of MAOs in a single Clerk application _for free_. Each MAO can have an unlimited number of members.
- In production instances, you can have up to 100 MAOs in a single Clerk application _for free_. Each MAO after the first 100 costs $1.00 per month. Each MAO can have an unlimited number of members.
-For more details on pricing, see [our pricing page](/pricing){{ target: '_blank' }}.
+For more information on pricing, see the [pricing page](/pricing){{ target: '_blank' }}.
-If you need more organizations or custom pricing, please contact [our sales team](/contact/sales){{ target: '_blank' }} to upgrade to the Enterprise plan.
+If you need more organizations or custom pricing, contact the [sales team](/contact/sales){{ target: '_blank' }} to upgrade to the Enterprise plan.
### Create an organization in your application
@@ -131,7 +131,7 @@ If you want to only configure this permission for a specific user, you can overr
When a user creates an organization, they become the organization's admin. As the organization's admin, they have full control over the organization, including the ability to update the organization's settings, invite users to join the organization, and manage the organization's members.
-A single user within one of your applications can create _up to_ 100 organizations in that application. If you need users to be able to create more organizations than this, [reach out to support](/contact/support){{ target: '_blank' }} and you can have the limit raised.
+A single user within one of your applications can create _up to_ 100 organizations in that application. If you need users to be able to create more organizations than this, [contact support](/contact/support){{ target: '_blank' }} to have the limit raised.
The easiest way to allow users to create organizations is to use the [``](/docs/components/organization/create-organization) and/or [``](/docs/components/organization/organization-switcher) components.
diff --git a/docs/organizations/roles-permissions.mdx b/docs/organizations/roles-permissions.mdx
index 190092cf4d..e5174ad494 100644
--- a/docs/organizations/roles-permissions.mdx
+++ b/docs/organizations/roles-permissions.mdx
@@ -21,7 +21,7 @@ For each instance, there are currently two default roles:
### Custom role
-You can create up to 10 custom organization roles per application instance to meet your application needs. If you need more than 10 roles, reach out to [support@clerk.dev](mailto:support@clerk.dev).
+You can create up to 10 custom organization roles per application instance to meet your application needs. If you need more than 10 roles, [contact support](/contact/support){{ target: '_blank' }}.
Custom roles can be granted permissions and access. For example, you can create a new role of **Billing** (`org:billing`) which can be used to group users who belong to a specific department of the organization and have permission to manage credit card information, invoices, and other resources related to billing.
diff --git a/docs/organizations/verified-domains.mdx b/docs/organizations/verified-domains.mdx
index 0645b1f849..1e9813cde2 100644
--- a/docs/organizations/verified-domains.mdx
+++ b/docs/organizations/verified-domains.mdx
@@ -37,7 +37,7 @@ Domains can be verified through an email verification code sent to an email that
An application instance may only have one verified domain of the same name, and an organization may only have one domain of the same name (verified or unverified).
-You can create up to 10 domains per organization to meet your needs. If you need more than 10 domains, reach out to [support@clerk.dev](mailto:support@clerk.dev).
+You can create up to 10 domains per organization to meet your needs. If you need more than 10 domains, [contact support](/contact/support){{ target: '_blank' }}.
### Custom flow
diff --git a/docs/organizations/verify-user-permissions.mdx b/docs/organizations/verify-user-permissions.mdx
index c4a73a3efc..a55dc6e764 100644
--- a/docs/organizations/verify-user-permissions.mdx
+++ b/docs/organizations/verify-user-permissions.mdx
@@ -74,7 +74,7 @@ The following examples work for both SSR and CSR.
The following example uses the `` component to only render the layout for users with the correct permission. If the user is not authorized, the component will not render its children.
> [!WARNING]
- > Be cautious when doing authorization checks in layouts, as these don't re-render on navigation, meaning the user session won't be checked on every route change. [Read more in the Next.js docs.](https://nextjs.org/docs/app/building-your-application/authentication#layouts-and-auth-checks)
+ > Be cautious when doing authorization checks in layouts, as these don't re-render on navigation, meaning the user session won't be checked on every route change. [Read more in the Next.js docs](https://nextjs.org/docs/app/building-your-application/authentication#layouts-and-auth-checks).
```tsx {{ filename: '/app/dashboard/settings/layout.tsx' }}
import type { PropsWithChildren } from 'react'
@@ -90,7 +90,7 @@ The following examples work for both SSR and CSR.
The following example uses `has()` to inspect a user's permissions granularly. If the user doesn't have the correct permission, `has()` returns `false`, causing the component to return `null` instead of rendering its children.
> [!WARNING]
- > Be cautious when doing authorization checks in layouts, as these don't re-render on navigation, meaning the user session won't be checked on every route change. [Read more in the Next.js docs.](https://nextjs.org/docs/app/building-your-application/authentication#layouts-and-auth-checks)
+ > Be cautious when doing authorization checks in layouts, as these don't re-render on navigation, meaning the user session won't be checked on every route change. [Read more in the Next.js docs](https://nextjs.org/docs/app/building-your-application/authentication#layouts-and-auth-checks).
```tsx {{ filename: '/app/dashboard/settings/layout.tsx' }}
import type { PropsWithChildren } from 'react'
diff --git a/docs/quickstarts/astro.mdx b/docs/quickstarts/astro.mdx
index 6c3eda1c7c..47849c8579 100644
--- a/docs/quickstarts/astro.mdx
+++ b/docs/quickstarts/astro.mdx
@@ -125,7 +125,7 @@ description: Add authentication and user management to your Astro app with Clerk
- [``](/docs/components/control/signed-in): Children of this component can only be seen while **signed in**.
- [``](/docs/components/control/signed-out): Children of this component can only be seen while **signed out**.
- [``](/docs/components/user/user-button): Shows the signed-in user's avatar. Selecting it opens a dropdown menu with account management options.
- - [``](/docs/components/unstyled/sign-in-button): An unstyled component that links to the sign-in page. In this example, since no props or [environment variables](/docs/deployments/clerk-environment-variables) are set for the sign-in URL, this component links to the [Account Portal sign-in page.](/docs/customization/account-portal/overview#sign-in)
+ - [``](/docs/components/unstyled/sign-in-button): An unstyled component that links to the sign-in page. In this example, since no props or [environment variables](/docs/deployments/clerk-environment-variables) are set for the sign-in URL, this component links to the [Account Portal sign-in page](/docs/customization/account-portal/overview#sign-in).
```astro {{ filename: 'src/layouts/SiteLayout.astro' }}
---
diff --git a/docs/quickstarts/fastify.mdx b/docs/quickstarts/fastify.mdx
index e41d30f720..20ace923c6 100644
--- a/docs/quickstarts/fastify.mdx
+++ b/docs/quickstarts/fastify.mdx
@@ -89,7 +89,7 @@ Learn how to integrate Clerk into your Fastify backend for secure user authentic
The following example registers the plugin for all routes. To register the plugin for specific routes only, refer to the [**Using Clerk for specific pages only**](/docs/quickstarts/fastify#using-clerk-for-specific-routes-only) section.
> [!IMPORTANT]
- > The `dotenv/config` module must be imported before any Clerk modules. This order is important because Clerk instances are created during the import process and rely on environment variables, such as API keys, to be initialized correctly. For more details, refer to the [Fastify docs](https://fastify.dev/docs/latest/Guides/Getting-Started/#loading-order-of-your-plugins).
+ > The `dotenv/config` module must be imported before any Clerk modules. This order is important because Clerk instances are created during the import process and rely on environment variables, such as API keys, to be initialized correctly. For more information, refer to the [Fastify docs](https://fastify.dev/docs/latest/Guides/Getting-Started/#loading-order-of-your-plugins).
```ts {{ filename: 'index.ts' }}
import 'dotenv/config'
diff --git a/docs/quickstarts/javascript.mdx b/docs/quickstarts/javascript.mdx
index 23eb217cbb..4975ea1a8b 100644
--- a/docs/quickstarts/javascript.mdx
+++ b/docs/quickstarts/javascript.mdx
@@ -125,7 +125,7 @@ Use the following tabs to choose your preferred method.
```
> [!NOTE]
- > Calling the `load()` method initializes Clerk. For more information on the `load()` method and what options you can pass to it, check out the [reference documentation](/docs/references/javascript/clerk/clerk#load).
+ > Calling the `load()` method initializes Clerk. For more information on the `load()` method and what options you can pass to it, see the [reference documentation](/docs/references/javascript/clerk/clerk#load).
### Add Clerk components to your app
diff --git a/docs/quickstarts/nextjs.mdx b/docs/quickstarts/nextjs.mdx
index 6a81913aa6..afa04c15e6 100644
--- a/docs/quickstarts/nextjs.mdx
+++ b/docs/quickstarts/nextjs.mdx
@@ -104,7 +104,7 @@ description: Add authentication and user management to your Next.js app with Cle
- [``](/docs/components/control/signed-in): Children of this component can only be seen while **signed in**.
- [``](/docs/components/control/signed-out): Children of this component can only be seen while **signed out**.
- [``](/docs/components/user/user-button): Shows the signed-in user's avatar. Selecting it opens a dropdown menu with account management options.
- - [``](/docs/components/unstyled/sign-in-button): An unstyled component that links to the sign-in page. In this example, since no props or [environment variables](/docs/deployments/clerk-environment-variables) are set for the sign-in URL, this component links to the [Account Portal sign-in page.](/docs/customization/account-portal/overview#sign-in)
+ - [``](/docs/components/unstyled/sign-in-button): An unstyled component that links to the sign-in page. In this example, since no props or [environment variables](/docs/deployments/clerk-environment-variables) are set for the sign-in URL, this component links to the [Account Portal sign-in page](/docs/customization/account-portal/overview#sign-in).
Select your preferred router to learn how to make this data available across your entire app:
diff --git a/docs/quickstarts/overview.mdx b/docs/quickstarts/overview.mdx
index 128ee15940..7012e38dea 100644
--- a/docs/quickstarts/overview.mdx
+++ b/docs/quickstarts/overview.mdx
@@ -1,6 +1,6 @@
---
title: Quickstarts
-description: Check out our Clerk getting started guides and tutorials.
+description: See the getting started guides and tutorials.
---
## Full Stack
diff --git a/docs/quickstarts/react.mdx b/docs/quickstarts/react.mdx
index fbe664f474..7f3eb37385 100644
--- a/docs/quickstarts/react.mdx
+++ b/docs/quickstarts/react.mdx
@@ -193,7 +193,7 @@ description: Add authentication and user management to your React app with Clerk
## Next step: Add routing with React Router
-React has many options for handling routing, and you are free to choose the option that suits you best. If you would like to learn how to integrate React Router's latest Data API-based router (also known as Data Router), see [the dedicated guide.](/docs/references/react/add-react-router)
+React has many options for handling routing, and you are free to choose the option that suits you best. If you would like to learn how to integrate React Router's latest Data API-based router (also known as Data Router), see the [dedicated guide](/docs/references/react/add-react-router).
## More resources
diff --git a/docs/quickstarts/remix.mdx b/docs/quickstarts/remix.mdx
index 16225f5b48..7ada6a65ca 100644
--- a/docs/quickstarts/remix.mdx
+++ b/docs/quickstarts/remix.mdx
@@ -198,7 +198,7 @@ Learn how to use Clerk to quickly and easily add secure authentication and user
- [``](/docs/components/control/signed-in): Children of this component can only be seen while **signed in**.
- [``](/docs/components/control/signed-out): Children of this component can only be seen while **signed out**.
- [``](/docs/components/user/user-button): Shows the signed-in user's avatar. Selecting it opens a dropdown menu with account management options.
- - [``](/docs/components/unstyled/sign-in-button): An unstyled component that links to the sign-in page. In this example, since no props or [environment variables](/docs/deployments/clerk-environment-variables) are set for the sign-in URL, this component links to the [Account Portal sign-in page.](/docs/customization/account-portal/overview#sign-in)
+ - [``](/docs/components/unstyled/sign-in-button): An unstyled component that links to the sign-in page. In this example, since no props or [environment variables](/docs/deployments/clerk-environment-variables) are set for the sign-in URL, this component links to the [Account Portal sign-in page](/docs/customization/account-portal/overview#sign-in)
```tsx {{ filename: 'routes/_index.tsx' }}
import {
diff --git a/docs/quickstarts/setup-clerk.mdx b/docs/quickstarts/setup-clerk.mdx
index 72d6879cc8..91bcee912c 100644
--- a/docs/quickstarts/setup-clerk.mdx
+++ b/docs/quickstarts/setup-clerk.mdx
@@ -23,7 +23,7 @@ Before you can start integrating Clerk into your application, you need to create
Once you are in the interactive authentication setup form, you will be asked to build your authentication flow. Here, Clerk provides various options for setting up your sign-up and sign-in flows. You can choose to use email, phone, or username as [identifiers](/docs/authentication/configuration/sign-up-sign-in-options#identifiers), and you can enable [social authentication providers](/docs/authentication/social-connections/overview).
- Once the application is created, you can also customize your authentication flow by selecting different authentication strategies, verification methods, and more. [Learn more about sign-up and sign-in options.](/docs/authentication/configuration/sign-up-sign-in-options)
+ Once the application is created, you can also customize your authentication flow by selecting different authentication strategies, verification methods, and more. [Learn more about sign-up and sign-in options](/docs/authentication/configuration/sign-up-sign-in-options).
### Integrate Clerk into your application
diff --git a/docs/quickstarts/tanstack-start.mdx b/docs/quickstarts/tanstack-start.mdx
index 039a6692a0..7ebc3e53b8 100644
--- a/docs/quickstarts/tanstack-start.mdx
+++ b/docs/quickstarts/tanstack-start.mdx
@@ -143,7 +143,7 @@ description: Learn how to use Clerk to quickly and easily add secure authenticat
- [``](/docs/components/control/signed-in): Children of this component can only be seen while **signed in**.
- [``](/docs/components/control/signed-out): Children of this component can only be seen while **signed out**.
- [``](/docs/components/user/user-button): Shows the signed-in user's avatar. Selecting it opens a dropdown menu with account management options.
- - [``](/docs/components/unstyled/sign-in-button): An unstyled component that links to the sign-in page. In this example, since no props or [environment variables](/docs/deployments/clerk-environment-variables) are set for the sign-in URL, this component links to the [Account Portal sign-in page.](/docs/customization/account-portal/overview#sign-in)
+ - [``](/docs/components/unstyled/sign-in-button): An unstyled component that links to the sign-in page. In this example, since no props or [environment variables](/docs/deployments/clerk-environment-variables) are set for the sign-in URL, this component links to the [Account Portal sign-in page](/docs/customization/account-portal/overview#sign-in).
```tsx {{ filename: 'app/routes/index.tsx' }}
import {
diff --git a/docs/references/astro/react.mdx b/docs/references/astro/react.mdx
index 1cc36ded9c..38eeb6e23e 100644
--- a/docs/references/astro/react.mdx
+++ b/docs/references/astro/react.mdx
@@ -5,7 +5,7 @@ description: Learn how to user Clerk inside an Astro app with React
Astro provides an [integration](https://docs.astro.build/en/guides/integrations-guide/react/) that enables server-side rendering and client-side hydration for your React components. This guide demonstrates how to use Clerk with Astro and React.
-If you have not set up your Astro application to work with Clerk, visit the [Astro quickstart.](/docs/quickstarts/astro)
+If you have not set up your Astro application to work with Clerk, see the [quickstart guide](/docs/quickstarts/astro).
### Install `@astrojs/react`
diff --git a/docs/references/astro/sign-in-store.mdx b/docs/references/astro/sign-in-store.mdx
index da877484f4..179d386d94 100644
--- a/docs/references/astro/sign-in-store.mdx
+++ b/docs/references/astro/sign-in-store.mdx
@@ -65,4 +65,4 @@ The possible values for the `status` property of the `SignIn` resource are liste
### Create a custom sign-in flow
-The `$signInStore` store can also be used to build fully custom sign-in flows, if Clerk's prebuilt components don't meet your specific needs or if you require more control over the authentication flow. Different sign-in flows include email and password, email and phone codes, email links, and multifactor (MFA). To learn more about using the `$signInStore` store to create custom flows, see the [custom flow guides.](/docs/custom-flows/overview)
+The `$signInStore` store can also be used to build fully custom sign-in flows, if Clerk's prebuilt components don't meet your specific needs or if you require more control over the authentication flow. Different sign-in flows include email and password, email and phone codes, email links, and multifactor (MFA). To learn more about using the `$signInStore` store to create custom flows, check out the [custom flow guides.](/docs/custom-flows/overview)
diff --git a/docs/references/astro/sign-up-store.mdx b/docs/references/astro/sign-up-store.mdx
index 6eb850e8b0..db0ea289bc 100644
--- a/docs/references/astro/sign-up-store.mdx
+++ b/docs/references/astro/sign-up-store.mdx
@@ -65,4 +65,4 @@ The possible values for the `status` property of the `SignUp` resource are liste
### Create a custom sign-up flow
-The `$signUpStore` store can also be used to build fully custom sign-up flows, if Clerk's prebuilt components don't meet your specific needs or if you require more control over the authentication flow. Different sign-up flows include email and password, email and phone codes, email links, and multifactor (MFA). To learn more about using the `$signUpStore` store to create custom flows, check out the [custom flow guides.](/docs/custom-flows/overview)
+The `$signUpStore` store can also be used to build fully custom sign-up flows, if Clerk's prebuilt components don't meet your specific needs or if you require more control over the authentication flow. Different sign-up flows include email and password, email and phone codes, email links, and multifactor (MFA). To learn more about using the `$signUpStore` store to create custom flows, see the [custom flow guides](/docs/custom-flows/overview).
diff --git a/docs/references/astro/user-store.mdx b/docs/references/astro/user-store.mdx
index bdf345223a..88bd83ce14 100644
--- a/docs/references/astro/user-store.mdx
+++ b/docs/references/astro/user-store.mdx
@@ -11,7 +11,7 @@ The `$userStore` store provides a convenient way to access current [`User`](/doc
The following example demonstrates how to use the `$userStore` store to access the `User` object. It returns `undefined` while Clerk is still loading and `null` if the user is not signed in.
-For more information, see the [`User` reference.](/docs/references/javascript/user/user#user-object){{ target: '_blank' }}
+For more information, see the [`User` reference](/docs/references/javascript/user/user#user-object){{ target: '_blank' }}.
```tsx {{ filename: 'user.tsx' }}
@@ -72,7 +72,7 @@ For more information, see the [`User` reference.](/docs/references/javascript/us
The following example demonstrates how to use the `$userStore` store to update the current user's data on the client-side.
-For more information on the `update()` method, see the [`User` reference.](/docs/references/javascript/user/user#update){{ target: '_blank' }}
+For more information on the `update()` method, see the [`User` reference](/docs/references/javascript/user/user#update){{ target: '_blank' }}.
```tsx {{ filename: 'user.tsx' }}
@@ -162,7 +162,7 @@ For more information on the `update()` method, see the [`User` reference.](/docs
The following example demonstrates how to use the `$userStore` store to reload the current user's data on the client-side.
-For more information on the `reload()` method, see the [`User` reference.](/docs/references/javascript/user/user#reload){{ target: '_blank' }}
+For more information on the `reload()` method, see the [`User` reference](/docs/references/javascript/user/user#reload){{ target: '_blank' }}.
```tsx {{ filename: 'user.tsx' }}
diff --git a/docs/references/backend/allowlist/create-allowlist-identifier.mdx b/docs/references/backend/allowlist/create-allowlist-identifier.mdx
index 5e226d5a38..cfdcb40e30 100644
--- a/docs/references/backend/allowlist/create-allowlist-identifier.mdx
+++ b/docs/references/backend/allowlist/create-allowlist-identifier.mdx
@@ -26,7 +26,7 @@ function createAllowlistIdentifier(
- `notify`
- `boolean`
- Whether the given identifier will receive an invitation to join the application. Note that this only works for email address and phone number identifiers. Not available for wildcard identifiers or Web3 wallet addresses. Defaults to `true`.
+ Whether the given identifier will receive an invitation to join the application. Note that this only works for email address and phone number identifiers. Not available for wildcard identifiers or Web3 wallet addresses. Defaults to `true`.
## Example
@@ -51,4 +51,4 @@ _AllowlistIdentifier {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/allowlist-identifiers`. See the [BAPI reference](/docs/reference/backend-api/tag/Allow-list-Block-list#operation/CreateAllowlistIdentifier){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/allowlist-identifiers`. See the [BAPI reference](/docs/reference/backend-api/tag/Allow-list-Block-list#operation/CreateAllowlistIdentifier){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/allowlist/delete-allowlist-identifier.mdx b/docs/references/backend/allowlist/delete-allowlist-identifier.mdx
index 299ff460d4..a55b5c4240 100644
--- a/docs/references/backend/allowlist/delete-allowlist-identifier.mdx
+++ b/docs/references/backend/allowlist/delete-allowlist-identifier.mdx
@@ -41,4 +41,4 @@ DeletedObject {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `DELETE/allowlist-identifiers/{identifier_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Allow-list-Block-list#operation/DeleteAllowlistIdentifier){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `DELETE/allowlist-identifiers/{identifier_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Allow-list-Block-list#operation/DeleteAllowlistIdentifier){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/allowlist/get-allowlist-identifier-list.mdx b/docs/references/backend/allowlist/get-allowlist-identifier-list.mdx
index 1eda5166bd..36f3566b29 100644
--- a/docs/references/backend/allowlist/get-allowlist-identifier-list.mdx
+++ b/docs/references/backend/allowlist/get-allowlist-identifier-list.mdx
@@ -37,4 +37,4 @@ console.log(response)
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/allowlist-identifiers`. See the [BAPI reference](/docs/reference/backend-api/tag/Allow-list-Block-list#operation/ListAllowlistIdentifiers){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/allowlist-identifiers`. See the [BAPI reference](/docs/reference/backend-api/tag/Allow-list-Block-list#operation/ListAllowlistIdentifiers){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/client/get-client.mdx b/docs/references/backend/client/get-client.mdx
index c2d1267d0f..fa3e347aa2 100644
--- a/docs/references/backend/client/get-client.mdx
+++ b/docs/references/backend/client/get-client.mdx
@@ -44,4 +44,4 @@ _Client {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/clients/{client_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Clients#operation/GetClient){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/clients/{client_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Clients#operation/GetClient){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/client/verify-client.mdx b/docs/references/backend/client/verify-client.mdx
index 149f198d74..4086691aaa 100644
--- a/docs/references/backend/client/verify-client.mdx
+++ b/docs/references/backend/client/verify-client.mdx
@@ -30,4 +30,4 @@ const response = await clerkClient.clients.verifyClient(token)
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/clients/verify`. See the [BAPI reference](/docs/reference/backend-api/tag/Clients#operation/VerifyClient){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/clients/verify`. See the [BAPI reference](/docs/reference/backend-api/tag/Clients#operation/VerifyClient){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/domains/delete-domain.mdx b/docs/references/backend/domains/delete-domain.mdx
index a0dba6dcbf..02e5008f7b 100644
--- a/docs/references/backend/domains/delete-domain.mdx
+++ b/docs/references/backend/domains/delete-domain.mdx
@@ -38,4 +38,4 @@ _DeletedObject {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `DELETE/domains/{domain_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Domains#operation/DeleteDomain){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `DELETE/domains/{domain_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Domains#operation/DeleteDomain){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/email-addresses/create-email-address.mdx b/docs/references/backend/email-addresses/create-email-address.mdx
index 6ceb5ec3bb..e4a1e9c6f1 100644
--- a/docs/references/backend/email-addresses/create-email-address.mdx
+++ b/docs/references/backend/email-addresses/create-email-address.mdx
@@ -74,4 +74,4 @@ _EmailAddress {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/email_addresses`. See the [BAPI reference](/docs/reference/backend-api/tag/Email-Addresses#operation/CreateEmailAddress){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/email_addresses`. See the [BAPI reference](/docs/reference/backend-api/tag/Email-Addresses#operation/CreateEmailAddress){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/email-addresses/delete-email-address.mdx b/docs/references/backend/email-addresses/delete-email-address.mdx
index 1dde543d30..76d39e9c6e 100644
--- a/docs/references/backend/email-addresses/delete-email-address.mdx
+++ b/docs/references/backend/email-addresses/delete-email-address.mdx
@@ -40,4 +40,4 @@ _DeletedObject {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `DELETE/email_addresses/{email_address_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Email-Addresses#operation/DeleteEmailAddress){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `DELETE/email_addresses/{email_address_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Email-Addresses#operation/DeleteEmailAddress){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/email-addresses/get-email-address.mdx b/docs/references/backend/email-addresses/get-email-address.mdx
index 0ac4e9fa03..45ce3544bb 100644
--- a/docs/references/backend/email-addresses/get-email-address.mdx
+++ b/docs/references/backend/email-addresses/get-email-address.mdx
@@ -52,4 +52,4 @@ _EmailAddress {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/email_addresses/{email_address_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Email-Addresses#operation/GetEmailAddress){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/email_addresses/{email_address_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Email-Addresses#operation/GetEmailAddress){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/email-addresses/update-email-address.mdx b/docs/references/backend/email-addresses/update-email-address.mdx
index 4c4c117f60..5d408bc358 100644
--- a/docs/references/backend/email-addresses/update-email-address.mdx
+++ b/docs/references/backend/email-addresses/update-email-address.mdx
@@ -79,4 +79,4 @@ As you can see in the response, the email address is now unverified.
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `PATCH/email_addresses/{email_address_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Email-Addresses#operation/UpdateEmailAddress){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `PATCH/email_addresses/{email_address_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Email-Addresses#operation/UpdateEmailAddress){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/invitations/create-invitation.mdx b/docs/references/backend/invitations/create-invitation.mdx
index 7e3367240e..8145991681 100644
--- a/docs/references/backend/invitations/create-invitation.mdx
+++ b/docs/references/backend/invitations/create-invitation.mdx
@@ -80,4 +80,4 @@ _Invitation {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/invitations`. See the [BAPI reference](/docs/reference/backend-api/tag/Invitations#operation/CreateInvitation){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/invitations`. See the [BAPI reference](/docs/reference/backend-api/tag/Invitations#operation/CreateInvitation){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/invitations/get-invitation-list.mdx b/docs/references/backend/invitations/get-invitation-list.mdx
index b5c92572b3..10c3668034 100644
--- a/docs/references/backend/invitations/get-invitation-list.mdx
+++ b/docs/references/backend/invitations/get-invitation-list.mdx
@@ -117,4 +117,4 @@ const { data, totalCount } = await clerkClient.invitations.getInvitationList({
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/invitations`. See the [BAPI reference](/docs/reference/backend-api/tag/Invitations#operation/ListInvitations){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/invitations`. See the [BAPI reference](/docs/reference/backend-api/tag/Invitations#operation/ListInvitations){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/invitations/revoke-invitation.mdx b/docs/references/backend/invitations/revoke-invitation.mdx
index 6df3962df6..2d9f5c2bd8 100644
--- a/docs/references/backend/invitations/revoke-invitation.mdx
+++ b/docs/references/backend/invitations/revoke-invitation.mdx
@@ -47,4 +47,4 @@ _Invitation {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/invitations/{invitation_id}/revoke`. See the [BAPI reference](/docs/reference/backend-api/tag/Invitations#operation/RevokeInvitation){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/invitations/{invitation_id}/revoke`. See the [BAPI reference](/docs/reference/backend-api/tag/Invitations#operation/RevokeInvitation){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/create-organization-invitation.mdx b/docs/references/backend/organization/create-organization-invitation.mdx
index aca551b00d..c816e57742 100644
--- a/docs/references/backend/organization/create-organization-invitation.mdx
+++ b/docs/references/backend/organization/create-organization-invitation.mdx
@@ -93,4 +93,4 @@ _OrganizationInvitation {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/organizations/{organization_id}/invitations`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Invitations#operation/CreateOrganizationInvitation){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/organizations/{organization_id}/invitations`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Invitations#operation/CreateOrganizationInvitation){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/create-organization-membership.mdx b/docs/references/backend/organization/create-organization-membership.mdx
index 26d82af632..f2fb9ed84c 100644
--- a/docs/references/backend/organization/create-organization-membership.mdx
+++ b/docs/references/backend/organization/create-organization-membership.mdx
@@ -91,4 +91,4 @@ _OrganizationMembership {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/organizations/{organization_id}/memberships`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Memberships#operation/CreateOrganizationMembership){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/organizations/{organization_id}/memberships`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Memberships#operation/CreateOrganizationMembership){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/create-organization.mdx b/docs/references/backend/organization/create-organization.mdx
index eb08dcb1bc..14b02dd2b4 100644
--- a/docs/references/backend/organization/create-organization.mdx
+++ b/docs/references/backend/organization/create-organization.mdx
@@ -86,4 +86,4 @@ _Organization {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/organizations`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/CreateOrganization){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/organizations`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/CreateOrganization){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/delete-organization-logo.mdx b/docs/references/backend/organization/delete-organization-logo.mdx
index 99c7230fec..d415df4dfa 100644
--- a/docs/references/backend/organization/delete-organization-logo.mdx
+++ b/docs/references/backend/organization/delete-organization-logo.mdx
@@ -47,4 +47,4 @@ _Organization {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `DELETE/organizations/{organization_id}/logo`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/DeleteOrganizationLogo){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `DELETE/organizations/{organization_id}/logo`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/DeleteOrganizationLogo){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/delete-organization-membership.mdx b/docs/references/backend/organization/delete-organization-membership.mdx
index 158bbb4c00..56d9fe5729 100644
--- a/docs/references/backend/organization/delete-organization-membership.mdx
+++ b/docs/references/backend/organization/delete-organization-membership.mdx
@@ -79,4 +79,4 @@ _OrganizationMembership {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `DELETE/organizations/{organization_id}/memberships/{user_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Memberships#operation/DeleteOrganizationMembership){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `DELETE/organizations/{organization_id}/memberships/{user_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Memberships#operation/DeleteOrganizationMembership){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/delete-organization.mdx b/docs/references/backend/organization/delete-organization.mdx
index 27c09c3750..b23bdebdbc 100644
--- a/docs/references/backend/organization/delete-organization.mdx
+++ b/docs/references/backend/organization/delete-organization.mdx
@@ -40,4 +40,4 @@ DeletedObject {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `DELETE/organizations/{organization_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/DeleteOrganization){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `DELETE/organizations/{organization_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/DeleteOrganization){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/get-organization-invitation-list.mdx b/docs/references/backend/organization/get-organization-invitation-list.mdx
index 97f2c9d9d5..28e507f361 100644
--- a/docs/references/backend/organization/get-organization-invitation-list.mdx
+++ b/docs/references/backend/organization/get-organization-invitation-list.mdx
@@ -130,4 +130,4 @@ const { data, totalCount } = await clerkClient.organizations.getOrganizationInvi
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/organizations/{organization_id}/invitations`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Invitations#operation/ListOrganizationInvitations){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/organizations/{organization_id}/invitations`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Invitations#operation/ListOrganizationInvitations){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/get-organization-invitation.mdx b/docs/references/backend/organization/get-organization-invitation.mdx
index 71bf2b3101..a2dee3269a 100644
--- a/docs/references/backend/organization/get-organization-invitation.mdx
+++ b/docs/references/backend/organization/get-organization-invitation.mdx
@@ -59,4 +59,4 @@ _OrganizationInvitation {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/organizations/{organization_id}/invitations/{invitation_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Invitations#operation/GetOrganizationInvitation){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/organizations/{organization_id}/invitations/{invitation_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Invitations#operation/GetOrganizationInvitation){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/get-organization-list.mdx b/docs/references/backend/organization/get-organization-list.mdx
index 334aff0e16..9eea6925e1 100644
--- a/docs/references/backend/organization/get-organization-list.mdx
+++ b/docs/references/backend/organization/get-organization-list.mdx
@@ -135,4 +135,4 @@ const { data, totalCount } = await clerkClient.organizations.getOrganizationList
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/organizations`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/ListOrganizations){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/organizations`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/ListOrganizations){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/get-organization-membership-list.mdx b/docs/references/backend/organization/get-organization-membership-list.mdx
index 5feedaa0f9..44a7828af3 100644
--- a/docs/references/backend/organization/get-organization-membership-list.mdx
+++ b/docs/references/backend/organization/get-organization-membership-list.mdx
@@ -114,4 +114,4 @@ const { data, totalCount } = await clerkClient.organizations.getOrganizationMemb
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/organizations/{organization_id}/memberships`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Memberships#operation/ListOrganizationMemberships){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/organizations/{organization_id}/memberships`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Memberships#operation/ListOrganizationMemberships){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/get-organization.mdx b/docs/references/backend/organization/get-organization.mdx
index fcf83ff2b4..4e8daac2c1 100644
--- a/docs/references/backend/organization/get-organization.mdx
+++ b/docs/references/backend/organization/get-organization.mdx
@@ -61,4 +61,4 @@ const response = await clerkClient.organizations.getOrganization({ slug })
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/organizations/{organization_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/GetOrganization){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/organizations/{organization_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/GetOrganization){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/revoke-organization-invitation.mdx b/docs/references/backend/organization/revoke-organization-invitation.mdx
index 2619bc0a87..fd592ecd11 100644
--- a/docs/references/backend/organization/revoke-organization-invitation.mdx
+++ b/docs/references/backend/organization/revoke-organization-invitation.mdx
@@ -71,4 +71,4 @@ _OrganizationInvitation {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/organizations/{organization_id}/invitations/{invitation_id}/revoke`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Invitations#operation/RevokeOrganizationInvitation){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/organizations/{organization_id}/invitations/{invitation_id}/revoke`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Invitations#operation/RevokeOrganizationInvitation){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/update-organization-logo.mdx b/docs/references/backend/organization/update-organization-logo.mdx
index b599a03144..c48f8d6309 100644
--- a/docs/references/backend/organization/update-organization-logo.mdx
+++ b/docs/references/backend/organization/update-organization-logo.mdx
@@ -72,4 +72,4 @@ _Organization {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `PUT/organizations/{organization_id}/logo`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/UploadOrganizationLogo){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `PUT/organizations/{organization_id}/logo`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/UploadOrganizationLogo){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/update-organization-membership-metadata.mdx b/docs/references/backend/organization/update-organization-membership-metadata.mdx
index a6bd830881..d46f78f7af 100644
--- a/docs/references/backend/organization/update-organization-membership-metadata.mdx
+++ b/docs/references/backend/organization/update-organization-membership-metadata.mdx
@@ -98,4 +98,4 @@ _OrganizationMembership {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `PATCH/organizations/{organization_id}/memberships/{user_id}/metadata`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Memberships#operation/UpdateOrganizationMembershipMetadata){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `PATCH/organizations/{organization_id}/memberships/{user_id}/metadata`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Memberships#operation/UpdateOrganizationMembershipMetadata){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/update-organization-membership.mdx b/docs/references/backend/organization/update-organization-membership.mdx
index 95f38dd2e8..977f311eb7 100644
--- a/docs/references/backend/organization/update-organization-membership.mdx
+++ b/docs/references/backend/organization/update-organization-membership.mdx
@@ -91,4 +91,4 @@ _OrganizationMembership {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `PATCH/organizations/{organization_id}/memberships/{user_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Memberships#operation/UpdateOrganizationMembership){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `PATCH/organizations/{organization_id}/memberships/{user_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Organization-Memberships#operation/UpdateOrganizationMembership){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/update-organization-metadata.mdx b/docs/references/backend/organization/update-organization-metadata.mdx
index 5a9b755517..880a7c8dde 100644
--- a/docs/references/backend/organization/update-organization-metadata.mdx
+++ b/docs/references/backend/organization/update-organization-metadata.mdx
@@ -72,4 +72,4 @@ _Organization {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `PATCH/organizations/{organization_id}/metadata`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/MergeOrganizationMetadata){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `PATCH/organizations/{organization_id}/metadata`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/MergeOrganizationMetadata){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/organization/update-organization.mdx b/docs/references/backend/organization/update-organization.mdx
index c096c7ea2e..de931931e2 100644
--- a/docs/references/backend/organization/update-organization.mdx
+++ b/docs/references/backend/organization/update-organization.mdx
@@ -86,4 +86,4 @@ _Organization {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `PATCH/organizations/{organization_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/UpdateOrganization){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `PATCH/organizations/{organization_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Organizations#operation/UpdateOrganization){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/overview.mdx b/docs/references/backend/overview.mdx
index 10f7d6a699..2dc9775297 100644
--- a/docs/references/backend/overview.mdx
+++ b/docs/references/backend/overview.mdx
@@ -68,7 +68,7 @@ To access a resource, you must first instantiate a `clerkClient` instance.
- If you are using Remix, please see the following section for how to instantiate `clerkClient`.
+ If you are using Remix, see the following section for how to instantiate `clerkClient`.
diff --git a/docs/references/backend/phone-numbers/create-phone-number.mdx b/docs/references/backend/phone-numbers/create-phone-number.mdx
index cd1b40b02a..8dba79c808 100644
--- a/docs/references/backend/phone-numbers/create-phone-number.mdx
+++ b/docs/references/backend/phone-numbers/create-phone-number.mdx
@@ -83,4 +83,4 @@ _PhoneNumber {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/phone_numbers`. See the [BAPI reference](/docs/reference/backend-api/tag/Phone-Numbers#operation/CreatePhoneNumber){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/phone_numbers`. See the [BAPI reference](/docs/reference/backend-api/tag/Phone-Numbers#operation/CreatePhoneNumber){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/phone-numbers/delete-phone-number.mdx b/docs/references/backend/phone-numbers/delete-phone-number.mdx
index 515e672e77..8503e1f24f 100644
--- a/docs/references/backend/phone-numbers/delete-phone-number.mdx
+++ b/docs/references/backend/phone-numbers/delete-phone-number.mdx
@@ -40,4 +40,4 @@ _DeletedObject {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `DELETE/phone_numbers/{phone_number_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Phone-Numbers#operation/DeletePhoneNumber){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `DELETE/phone_numbers/{phone_number_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Phone-Numbers#operation/DeletePhoneNumber){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/phone-numbers/get-phone-number.mdx b/docs/references/backend/phone-numbers/get-phone-number.mdx
index 6237d5682d..fccaad1b17 100644
--- a/docs/references/backend/phone-numbers/get-phone-number.mdx
+++ b/docs/references/backend/phone-numbers/get-phone-number.mdx
@@ -49,4 +49,4 @@ _PhoneNumber {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/phone_numbers/{phone_number_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Phone-Numbers#operation/GetPhoneNumber){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/phone_numbers/{phone_number_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Phone-Numbers#operation/GetPhoneNumber){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/phone-numbers/update-phone-number.mdx b/docs/references/backend/phone-numbers/update-phone-number.mdx
index f41e81525c..9d541c7dba 100644
--- a/docs/references/backend/phone-numbers/update-phone-number.mdx
+++ b/docs/references/backend/phone-numbers/update-phone-number.mdx
@@ -85,4 +85,4 @@ As you can see in the response, the phone number is now unverified.
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `PATCH/phone_numbers/{phone_number_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Phone-Numbers#operation/UpdatePhoneNumber){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `PATCH/phone_numbers/{phone_number_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Phone-Numbers#operation/UpdatePhoneNumber){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/redirect-urls/create-redirect-url.mdx b/docs/references/backend/redirect-urls/create-redirect-url.mdx
index c82c410662..fde86bc039 100644
--- a/docs/references/backend/redirect-urls/create-redirect-url.mdx
+++ b/docs/references/backend/redirect-urls/create-redirect-url.mdx
@@ -40,4 +40,4 @@ _RedirectUrl {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/redirect_urls`. See the [BAPI reference](/docs/reference/backend-api/tag/Redirect-URLs#operation/CreateRedirectURL){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/redirect_urls`. See the [BAPI reference](/docs/reference/backend-api/tag/Redirect-URLs#operation/CreateRedirectURL){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/redirect-urls/delete-redirect-url.mdx b/docs/references/backend/redirect-urls/delete-redirect-url.mdx
index 968b25c6e3..c4f9c6d6cb 100644
--- a/docs/references/backend/redirect-urls/delete-redirect-url.mdx
+++ b/docs/references/backend/redirect-urls/delete-redirect-url.mdx
@@ -40,4 +40,4 @@ _DeletedObject {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `DELETE/redirect_urls/{id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Redirect-URLs#operation/DeleteRedirectURL){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `DELETE/redirect_urls/{id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Redirect-URLs#operation/DeleteRedirectURL){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/redirect-urls/get-redirect-url-list.mdx b/docs/references/backend/redirect-urls/get-redirect-url-list.mdx
index 62fd8776ae..cbe153d467 100644
--- a/docs/references/backend/redirect-urls/get-redirect-url-list.mdx
+++ b/docs/references/backend/redirect-urls/get-redirect-url-list.mdx
@@ -36,4 +36,4 @@ console.log(response)
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/redirect_urls/{id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Redirect-URLs#operation/ListRedirectURLs){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/redirect_urls/{id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Redirect-URLs#operation/ListRedirectURLs){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/redirect-urls/get-redirect-url.mdx b/docs/references/backend/redirect-urls/get-redirect-url.mdx
index 1789c40b78..2e7f477de9 100644
--- a/docs/references/backend/redirect-urls/get-redirect-url.mdx
+++ b/docs/references/backend/redirect-urls/get-redirect-url.mdx
@@ -40,4 +40,4 @@ _RedirectUrl {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/redirect_urls/{id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Redirect-URLs#operation/GetRedirectURL){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/redirect_urls/{id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Redirect-URLs#operation/GetRedirectURL){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/saml-connections/create-saml-connection.mdx b/docs/references/backend/saml-connections/create-saml-connection.mdx
index 78954c741e..5fb2ed0f19 100644
--- a/docs/references/backend/saml-connections/create-saml-connection.mdx
+++ b/docs/references/backend/saml-connections/create-saml-connection.mdx
@@ -119,4 +119,4 @@ console.log(response)
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/saml_connections`. See the [BAPI reference](/docs/reference/backend-api/tag/SAML-Connections#operation/CreateSAMLConnection){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/saml_connections`. See the [BAPI reference](/docs/reference/backend-api/tag/SAML-Connections#operation/CreateSAMLConnection){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/saml-connections/delete-saml-connection.mdx b/docs/references/backend/saml-connections/delete-saml-connection.mdx
index d0cd76a249..a9eca69b4a 100644
--- a/docs/references/backend/saml-connections/delete-saml-connection.mdx
+++ b/docs/references/backend/saml-connections/delete-saml-connection.mdx
@@ -38,4 +38,4 @@ _DeletedObject {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `DELETE/saml_connections/{saml_connection_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/SAML-Connections#operation/DeleteSAMLConnection){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `DELETE/saml_connections/{saml_connection_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/SAML-Connections#operation/DeleteSAMLConnection){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/saml-connections/get-saml-connection-list.mdx b/docs/references/backend/saml-connections/get-saml-connection-list.mdx
index 615faf7045..795c443196 100644
--- a/docs/references/backend/saml-connections/get-saml-connection-list.mdx
+++ b/docs/references/backend/saml-connections/get-saml-connection-list.mdx
@@ -93,4 +93,4 @@ const { data, totalCount } = await clerkClient.samlConnections.getSamlConnection
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/saml_connections`. See the [BAPI reference](/docs/reference/backend-api/tag/SAML-Connections#operation/ListSAMLConnections){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/saml_connections`. See the [BAPI reference](/docs/reference/backend-api/tag/SAML-Connections#operation/ListSAMLConnections){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/saml-connections/get-saml-connection.mdx b/docs/references/backend/saml-connections/get-saml-connection.mdx
index 260675bb33..998dfb78fb 100644
--- a/docs/references/backend/saml-connections/get-saml-connection.mdx
+++ b/docs/references/backend/saml-connections/get-saml-connection.mdx
@@ -55,4 +55,4 @@ console.log(response)
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/saml_connections/{saml_connection_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/SAML-Connections#operation/GetSAMLConnection){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/saml_connections/{saml_connection_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/SAML-Connections#operation/GetSAMLConnection){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/saml-connections/update-saml-connection.mdx b/docs/references/backend/saml-connections/update-saml-connection.mdx
index f3223fd653..5e4bedea2c 100644
--- a/docs/references/backend/saml-connections/update-saml-connection.mdx
+++ b/docs/references/backend/saml-connections/update-saml-connection.mdx
@@ -146,4 +146,4 @@ console.log(response)
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `PATCH/saml_connections/{saml_connection_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/SAML-Connections#operation/UpdateSAMLConnection){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `PATCH/saml_connections/{saml_connection_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/SAML-Connections#operation/UpdateSAMLConnection){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/sessions/get-session-list.mdx b/docs/references/backend/sessions/get-session-list.mdx
index b1eb98854b..877e3d28f4 100644
--- a/docs/references/backend/sessions/get-session-list.mdx
+++ b/docs/references/backend/sessions/get-session-list.mdx
@@ -122,4 +122,4 @@ console.log(response)
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/sessions`. See the [BAPI reference](/docs/reference/backend-api/tag/Sessions){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/sessions`. See the [BAPI reference](/docs/reference/backend-api/tag/Sessions){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/sessions/get-session.mdx b/docs/references/backend/sessions/get-session.mdx
index 3bbc29c8bc..770419eb65 100644
--- a/docs/references/backend/sessions/get-session.mdx
+++ b/docs/references/backend/sessions/get-session.mdx
@@ -48,4 +48,4 @@ _Session {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/sessions/{session_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Sessions#operation/GetSession){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/sessions/{session_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Sessions#operation/GetSession){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/sessions/get-token.mdx b/docs/references/backend/sessions/get-token.mdx
index 5fc746d3a7..1cf51ff131 100644
--- a/docs/references/backend/sessions/get-token.mdx
+++ b/docs/references/backend/sessions/get-token.mdx
@@ -111,7 +111,7 @@ _Token {
> [!CAUTION]
- > On January 8, 2025, the Node SDK will no longer be available. [Upgrade to the Express SDK.](/docs/upgrade-guides/node-to-express)
+ > On January 8, 2025, the Node SDK will no longer be available. [Upgrade to the Express SDK](/docs/upgrade-guides/node-to-express).
{/* TODO: Update Node example - SDK is being deprecated */}
@@ -176,4 +176,4 @@ _Token {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/sessions/{session_id}/tokens/{template_name}`. See the [BAPI reference](/docs/reference/backend-api/tag/Sessions#operation/CreateSessionTokenFromTemplate){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/sessions/{session_id}/tokens/{template_name}`. See the [BAPI reference](/docs/reference/backend-api/tag/Sessions#operation/CreateSessionTokenFromTemplate){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/sessions/revoke-session.mdx b/docs/references/backend/sessions/revoke-session.mdx
index 53bbb66ef9..1bd321ff87 100644
--- a/docs/references/backend/sessions/revoke-session.mdx
+++ b/docs/references/backend/sessions/revoke-session.mdx
@@ -50,4 +50,4 @@ _Session {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/sessions/{session_id}/revoke`. See the [BAPI reference](/docs/reference/backend-api/tag/Sessions#operation/RevokeSession){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/sessions/{session_id}/revoke`. See the [BAPI reference](/docs/reference/backend-api/tag/Sessions#operation/RevokeSession){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/sign-in-tokens/create-sign-in-token.mdx b/docs/references/backend/sign-in-tokens/create-sign-in-token.mdx
index 201bb3bf18..393dc22caf 100644
--- a/docs/references/backend/sign-in-tokens/create-sign-in-token.mdx
+++ b/docs/references/backend/sign-in-tokens/create-sign-in-token.mdx
@@ -56,4 +56,4 @@ _SignInToken {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/sign_in_tokens`. See the [BAPI reference](/docs/reference/backend-api/tag/Sign-in-Tokens#operation/CreateSignInToken){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/sign_in_tokens`. See the [BAPI reference](/docs/reference/backend-api/tag/Sign-in-Tokens#operation/CreateSignInToken){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/sign-in-tokens/revoke-sign-in-token.mdx b/docs/references/backend/sign-in-tokens/revoke-sign-in-token.mdx
index 3f5b78523b..6c47d089de 100644
--- a/docs/references/backend/sign-in-tokens/revoke-sign-in-token.mdx
+++ b/docs/references/backend/sign-in-tokens/revoke-sign-in-token.mdx
@@ -41,4 +41,4 @@ _SignInToken {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/sign_in_tokens/{sign_in_token_id}/revoke`. See the [BAPI reference](/docs/reference/backend-api/tag/Sign-in-Tokens#operation/RevokeSignInToken){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/sign_in_tokens/{sign_in_token_id}/revoke`. See the [BAPI reference](/docs/reference/backend-api/tag/Sign-in-Tokens#operation/RevokeSignInToken){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/testing-tokens/create-testing-token.mdx b/docs/references/backend/testing-tokens/create-testing-token.mdx
index 8862ac55b2..ed03b348a4 100644
--- a/docs/references/backend/testing-tokens/create-testing-token.mdx
+++ b/docs/references/backend/testing-tokens/create-testing-token.mdx
@@ -25,4 +25,4 @@ _TestingToken {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/testing_tokens`. See the [BAPI reference](/docs/reference/backend-api/tag/Testing-Tokens#operation/CreateTestingToken){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/testing_tokens`. See the [BAPI reference](/docs/reference/backend-api/tag/Testing-Tokens#operation/CreateTestingToken){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/types/backend-user.mdx b/docs/references/backend/types/backend-user.mdx
index 6cb6258dd2..3e8c20b1ee 100644
--- a/docs/references/backend/types/backend-user.mdx
+++ b/docs/references/backend/types/backend-user.mdx
@@ -151,7 +151,7 @@ The Backend `User` object is similar to the `User` object as it holds informatio
- `unsafeMetadata`
- `{[string]: any}`
- Metadata that can be read and set from the Frontend API. One common use case for this attribute is to implement custom fields that will be attached to the `User` object. Please note that there is also an `unsafeMetadata` attribute in the [`SignUp`](/docs/references/javascript/sign-up/sign-up) object. The value of that field will be automatically copied to the user's unsafe metadata once the sign up is complete.
+ Metadata that can be read and set from the Frontend API. One common use case for this attribute is to implement custom fields that will be attached to the `User` object. There is also an `unsafeMetadata` attribute in the [`SignUp`](/docs/references/javascript/sign-up/sign-up) object. The value of that field will be automatically copied to the user's unsafe metadata once the sign up is complete.
---
diff --git a/docs/references/backend/user/ban-user.mdx b/docs/references/backend/user/ban-user.mdx
index 47afe2eaa1..8586fc9f91 100644
--- a/docs/references/backend/user/ban-user.mdx
+++ b/docs/references/backend/user/ban-user.mdx
@@ -90,4 +90,4 @@ _User {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/ban`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/BanUser){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/ban`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/BanUser){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/create-user.mdx b/docs/references/backend/user/create-user.mdx
index d2dd4c8873..79f132f202 100644
--- a/docs/references/backend/user/create-user.mdx
+++ b/docs/references/backend/user/create-user.mdx
@@ -96,7 +96,7 @@ function createUser(params: CreateUserParams): Promise
- `awscognito`
- When set, `password_digest` must be in the format of `awscognito###`.
- Upon a successful migration, `password_hasher` will be updated to `bcrypt`, and `password_digest` will be updated to a `bcrypt` hash.
- - See our [migration guide](https://clerk.com/docs/deployments/migrate-from-cognito) for usage details.
+ - See the [migration guide](https://clerk.com/docs/deployments/migrate-from-cognito) for usage details.
- [`bcrypt`](https://en.wikipedia.org/wiki/Bcrypt)
- When set, `password_digest` must be in the format of `$$$`
- [`bcrypt_sha256_django`](https://docs.djangoproject.com/en/4.0/topics/auth/passwords/)
@@ -148,7 +148,7 @@ function createUser(params: CreateUserParams): Promise
- When set, `password_digest` must be in the format of `$argon2i$v=19$m=4096,t=3,p=1$4t6CL3P7YiHBtwESXawI8Hm20zJj4cs7/4/G3c187e0$m7RQFczcKr5bIR0IIxbpO2P0tyrLjf3eUW3M3QSwnLc`
- For the argon2id case, the value of the algorithm in the first part of the digest is `argon2id`: `$argon2id$v=19$m=64,t=4,p=8$Z2liZXJyaXNo$iGXEpMBTDYQ8G/71tF0qGjxRHEmR3gpGULcE93zUJVU`
- If you need support for any particular hashing algorithm, [please let us know](https://clerk.com/support).
+ If you need support for any particular hashing algorithm, [contact support](https://clerk.com/support).
---
@@ -162,14 +162,14 @@ function createUser(params: CreateUserParams): Promise
- `skipPasswordRequirement?`
- `boolean`
- When set to `true`, password is not required anymore when creating the user and can be omitted. This is useful when you are trying to create a user that doesn't have a password, in an instance that is using passwords. Please note that you cannot use this flag if password is the only way for a user to sign into your instance.
+ When set to `true`, password is not required anymore when creating the user and can be omitted. This is useful when you are trying to create a user that doesn't have a password, in an instance that is using passwords. You cannot use this flag if password is the only way for a user to sign into your instance.
---
- `totpSecret?`
- `string`
- In case TOTP is configured on the instance, you can provide the secret to enable it on the newly created user without the need to reset it. Please note that currently the supported options are:
Period: 30 seconds
Code length: 6 digits
Algorithm: SHA1
+ In case TOTP is configured on the instance, you can provide the secret to enable it on the newly created user without the need to reset it. Currently, the supported options are:
Period: 30 seconds
Code length: 6 digits
Algorithm: SHA1
---
@@ -266,4 +266,4 @@ _User {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/users`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/CreateUser){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/users`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/CreateUser){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/delete-user-profile-image.mdx b/docs/references/backend/user/delete-user-profile-image.mdx
index 40e894c4ff..3ab6c167a4 100644
--- a/docs/references/backend/user/delete-user-profile-image.mdx
+++ b/docs/references/backend/user/delete-user-profile-image.mdx
@@ -84,4 +84,4 @@ _User {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/profile_image`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/SetUserProfileImage){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/profile_image`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/SetUserProfileImage){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/delete-user.mdx b/docs/references/backend/user/delete-user.mdx
index 7d7f1714b7..0d245b925e 100644
--- a/docs/references/backend/user/delete-user.mdx
+++ b/docs/references/backend/user/delete-user.mdx
@@ -43,4 +43,4 @@ _DeletedObject {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `DELETE/users/{user_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/DeleteUser){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `DELETE/users/{user_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/DeleteUser){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/disable-user-mfa.mdx b/docs/references/backend/user/disable-user-mfa.mdx
index db920871c1..dd2540c0a9 100644
--- a/docs/references/backend/user/disable-user-mfa.mdx
+++ b/docs/references/backend/user/disable-user-mfa.mdx
@@ -38,4 +38,4 @@ console.log(response)
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `DELETE/users/{user_id}/mfa`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/DisableMFA){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `DELETE/users/{user_id}/mfa`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/DisableMFA){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/get-count.mdx b/docs/references/backend/user/get-count.mdx
index b63cb23014..b4b16232e7 100644
--- a/docs/references/backend/user/get-count.mdx
+++ b/docs/references/backend/user/get-count.mdx
@@ -89,4 +89,4 @@ const response = await clerkClient.users.getCount({ query: 'test' })
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/users/count`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/GetUsersCount){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/users/count`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/GetUsersCount){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/get-organization-membership-list.mdx b/docs/references/backend/user/get-organization-membership-list.mdx
index b5ff495462..7780a1a142 100644
--- a/docs/references/backend/user/get-organization-membership-list.mdx
+++ b/docs/references/backend/user/get-organization-membership-list.mdx
@@ -108,4 +108,4 @@ const { data, totalCount } = await clerkClient.users.getOrganizationMembershipLi
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/users/{user_id}/organization_memberships`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/UsersGetOrganizationMemberships){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/users/{user_id}/organization_memberships`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/UsersGetOrganizationMemberships){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/get-user-list.mdx b/docs/references/backend/user/get-user-list.mdx
index e62de8b1c2..8d9864e8bc 100644
--- a/docs/references/backend/user/get-user-list.mdx
+++ b/docs/references/backend/user/get-user-list.mdx
@@ -216,4 +216,4 @@ const { data, totalCount } = await clerkClient.users.getUserList({
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/users`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/GetUserList){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/users`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/GetUserList){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/get-user-oauth-access-token.mdx b/docs/references/backend/user/get-user-oauth-access-token.mdx
index f98d3be554..e75f7979a1 100644
--- a/docs/references/backend/user/get-user-oauth-access-token.mdx
+++ b/docs/references/backend/user/get-user-oauth-access-token.mdx
@@ -67,4 +67,4 @@ You can also explore [the example](/docs/authentication/social-connections/oauth
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/users/{user_id}/oauth_access_tokens/{provider}`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/GetOAuthAccessToken){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/users/{user_id}/oauth_access_tokens/{provider}`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/GetOAuthAccessToken){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/get-user.mdx b/docs/references/backend/user/get-user.mdx
index 61bde15116..4122ea8d16 100644
--- a/docs/references/backend/user/get-user.mdx
+++ b/docs/references/backend/user/get-user.mdx
@@ -74,4 +74,4 @@ _User {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `GET/users/{user_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/GetUser){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `GET/users/{user_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/GetUser){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/lock-user.mdx b/docs/references/backend/user/lock-user.mdx
index b8c471401f..ea8a3b38ee 100644
--- a/docs/references/backend/user/lock-user.mdx
+++ b/docs/references/backend/user/lock-user.mdx
@@ -7,7 +7,7 @@ description: Use Clerk's Backend SDK to mark a user as locked, which means they
Marks the given [`User`](/docs/references/backend/types/backend-user) as locked, which means they are not allowed to sign in again until the lock expires.
-By default, lockout duration is 1 hour, but it can be configured in the application's [**Attack Protection**](https://dashboard.clerk.com/last-active?path=user-authentication/attack-protection) settings. For more details, see the [dedicated guide for customizing **Attack Protection** settings](/docs/security/customize-user-lockout).
+By default, lockout duration is 1 hour, but it can be configured in the application's [**Attack Protection**](https://dashboard.clerk.com/last-active?path=user-authentication/attack-protection) settings. For more information, see the [dedicated guide for customizing **Attack Protection** settings](/docs/security/customize-user-lockout).
```ts
function lockUser(userId: string): Promise
@@ -92,4 +92,4 @@ _User {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/lock`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/LockUser){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/lock`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/LockUser){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/unban-user.mdx b/docs/references/backend/user/unban-user.mdx
index c654df7787..5689fe57ca 100644
--- a/docs/references/backend/user/unban-user.mdx
+++ b/docs/references/backend/user/unban-user.mdx
@@ -90,4 +90,4 @@ _User {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/unban`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/UnbanUser){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/unban`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/UnbanUser){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/unlock-user.mdx b/docs/references/backend/user/unlock-user.mdx
index 799edf2db4..438ed78f78 100644
--- a/docs/references/backend/user/unlock-user.mdx
+++ b/docs/references/backend/user/unlock-user.mdx
@@ -90,4 +90,4 @@ _User {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/unlock`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/UnlockUser){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/unlock`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/UnlockUser){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/update-user-metadata.mdx b/docs/references/backend/user/update-user-metadata.mdx
index 0b4a2a7698..7101085538 100644
--- a/docs/references/backend/user/update-user-metadata.mdx
+++ b/docs/references/backend/user/update-user-metadata.mdx
@@ -96,4 +96,4 @@ _User {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `PATCH/users/{user_id}/metadata`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/UpdateUserMetadata){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `PATCH/users/{user_id}/metadata`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/UpdateUserMetadata){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/update-user-profile-image.mdx b/docs/references/backend/user/update-user-profile-image.mdx
index 426114b0a5..54d10cef50 100644
--- a/docs/references/backend/user/update-user-profile-image.mdx
+++ b/docs/references/backend/user/update-user-profile-image.mdx
@@ -92,4 +92,4 @@ _User {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/profile_image`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/SetUserProfileImage){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/profile_image`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/SetUserProfileImage){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/update-user.mdx b/docs/references/backend/user/update-user.mdx
index 20c1e0dbea..60a79b90e4 100644
--- a/docs/references/backend/user/update-user.mdx
+++ b/docs/references/backend/user/update-user.mdx
@@ -119,7 +119,7 @@ function updateUser(userId: string, params: UpdateUserParams): Promise
- `skipPasswordRequirement?`
- `boolean`
- When set to `true`, password is not required anymore when creating the user and can be omitted. This is useful when you are trying to create a user that doesn't have a password, in an instance that is using passwords. Please note that you cannot use this flag if password is the only way for a user to sign into your instance.
+ When set to `true`, password is not required anymore when creating the user and can be omitted. This is useful when you are trying to create a user that doesn't have a password, in an instance that is using passwords. You cannot use this flag if password is the only way for a user to sign into your instance.
---
@@ -133,7 +133,7 @@ function updateUser(userId: string, params: UpdateUserParams): Promise
- `totpSecret?`
- `string`
- In case TOTP is configured on the instance, you can provide the secret to enable it on the newly created user without the need to reset it. Please note that currently the supported options are:
Period: 30 seconds
Code length: 6 digits
Algorithm: SHA1
+ In case TOTP is configured on the instance, you can provide the secret to enable it on the newly created user without the need to reset it. Currently, the supported options are:
Period: 30 seconds
Code length: 6 digits
Algorithm: SHA1
---
@@ -314,7 +314,7 @@ _User {
> [!CAUTION]
- > On January 8, 2025, the Node SDK will no longer be available. [Upgrade to the Express SDK.](/docs/upgrade-guides/node-to-express)
+ > On January 8, 2025, the Node SDK will no longer be available. [Upgrade to the Express SDK](/docs/upgrade-guides/node-to-express).
{/* TODO: Update Node example - SDK is being deprecated */}
@@ -369,4 +369,4 @@ _User {
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `PATCH/users/{user_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/UpdateUser){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `PATCH/users/{user_id}`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/UpdateUser){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/verify-password.mdx b/docs/references/backend/user/verify-password.mdx
index 4e77a8ad70..069f1efb34 100644
--- a/docs/references/backend/user/verify-password.mdx
+++ b/docs/references/backend/user/verify-password.mdx
@@ -46,4 +46,4 @@ console.log(response)
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/verify_password`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/VerifyPassword){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/verify_password`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/VerifyPassword){{ target: '_blank' }} for more information.
diff --git a/docs/references/backend/user/verify-totp.mdx b/docs/references/backend/user/verify-totp.mdx
index aff35c8386..649aca2bc3 100644
--- a/docs/references/backend/user/verify-totp.mdx
+++ b/docs/references/backend/user/verify-totp.mdx
@@ -49,4 +49,4 @@ console.log(response)
## Backend API (BAPI) endpoint
-This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/verify_totp`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/VerifyTOTP){{ target: '_blank' }} for more details.
+This method in the SDK is a wrapper around the BAPI endpoint `POST/users/{user_id}/verify_totp`. See the [BAPI reference](/docs/reference/backend-api/tag/Users#operation/VerifyTOTP){{ target: '_blank' }} for more information.
diff --git a/docs/references/expo/use-local-credentials.mdx b/docs/references/expo/use-local-credentials.mdx
index 1f28e7ebf3..77286541fc 100644
--- a/docs/references/expo/use-local-credentials.mdx
+++ b/docs/references/expo/use-local-credentials.mdx
@@ -7,7 +7,7 @@ The `useLocalCredentials()` hook enables you to store a user's password credenti
> [!WARNING]
> This API is available only for [@clerk/clerk-expo v2](/docs/upgrade-guides/expo-v2/upgrade) >=2.2.0.
-> Be aware that this works only for sign-in attempts with the [password strategy.](/docs/authentication/configuration/sign-up-sign-in-options#authentication-strategies)
+> Be aware that this works only for sign-in attempts with the [password strategy](/docs/authentication/configuration/sign-up-sign-in-options#authentication-strategies).
## Returns
@@ -71,4 +71,4 @@ The `useLocalCredentials()` hook enables you to store a user's password credenti
## How to use the `useLocalCredentials()` hook
-To learn how to use the `useLocalCredentials()` hook, see the [dedicated guide.](/docs/references/expo/local-credentials)
+To learn how to use the `useLocalCredentials()` hook, see the [reference doc](/docs/references/expo/local-credentials).
diff --git a/docs/references/go/overview.mdx b/docs/references/go/overview.mdx
index f6a9ea88e3..787f15ffd4 100644
--- a/docs/references/go/overview.mdx
+++ b/docs/references/go/overview.mdx
@@ -118,4 +118,4 @@ for _, resource := range list.$Resource$s {
}
```
-For more usage details, check out the [examples](/docs/references/go/other-examples) or the library's [README file](https://github.com/clerk/clerk-sdk-go/tree/v2).
+For more usage details, see the [examples](/docs/references/go/other-examples) or the library's [README file](https://github.com/clerk/clerk-sdk-go/tree/v2).
diff --git a/docs/references/javascript/clerk/clerk.mdx b/docs/references/javascript/clerk/clerk.mdx
index c9612bb6b4..32ef63e9e3 100644
--- a/docs/references/javascript/clerk/clerk.mdx
+++ b/docs/references/javascript/clerk/clerk.mdx
@@ -289,7 +289,7 @@ Only one of the two properties are allowed to be set at a time.
Initializes the `Clerk` object and loads all necessary environment configuration and instance settings from the [Frontend API](/docs/reference/frontend-api){{ target: '_blank' }}.
-You must call this method before using the `Clerk` object in your code. Refer to the [ClerkJS installation](/docs/quickstarts/javascript) guide for more details.
+You must call this method before using the `Clerk` object in your code. Refer to the [quickstart guide](/docs/quickstarts/javascript) for more information.
```typescript
function load(options?: ClerkOptions): Promise
diff --git a/docs/references/javascript/clerk/handle-navigation.mdx b/docs/references/javascript/clerk/handle-navigation.mdx
index 103e2a8126..b4992cd863 100644
--- a/docs/references/javascript/clerk/handle-navigation.mdx
+++ b/docs/references/javascript/clerk/handle-navigation.mdx
@@ -192,7 +192,7 @@ function handleRedirectCallback(
- `transferable?`
- `boolean`
- Indicates whether or not sign in attempts are transferable to the sign up flow. Defaults to `true`. When set to `false`, prevents opaque sign ups when a user attempts to sign in via OAuth with an email that doesn't exist. See [OAuth account transfer flows](/docs/custom-flows/oauth-connections#o-auth-account-transfer-flows) for more details.
+ Indicates whether or not sign in attempts are transferable to the sign up flow. Defaults to `true`. When set to `false`, prevents opaque sign ups when a user attempts to sign in via OAuth with an email that doesn't exist. See [OAuth account transfer flows](/docs/custom-flows/oauth-connections#o-auth-account-transfer-flows) for more information.
## `handleUnauthenticated()`
diff --git a/docs/references/javascript/organization/members.mdx b/docs/references/javascript/organization/members.mdx
index 51a7c18dd8..33dae202e2 100644
--- a/docs/references/javascript/organization/members.mdx
+++ b/docs/references/javascript/organization/members.mdx
@@ -8,7 +8,7 @@ description: Learn about the methods on the Organization object that allow you t
These methods on the [`Organization`](/docs/references/javascript/organization/organization) object allow you to manage the memberships of an organization.
-To see how all these methods work together, check out the [comprehensive example](#organization-membership-methods-example).
+To see how all these methods work together, see the [comprehensive example](#organization-membership-methods-example).
## `getMemberships()`
diff --git a/docs/references/javascript/overview.mdx b/docs/references/javascript/overview.mdx
index 47333013a7..55031d0fdf 100644
--- a/docs/references/javascript/overview.mdx
+++ b/docs/references/javascript/overview.mdx
@@ -9,7 +9,7 @@ While we typically recommend using one of our framework SDK's, such as [Clerk Re
## Installation
-Please follow the instructions in the [ClerkJS quickstart](/docs/quickstarts/javascript) to add ClerkJS to your project.
+Follow the instructions in the [ClerkJS quickstart](/docs/quickstarts/javascript) to add ClerkJS to your project.
## Usage
diff --git a/docs/references/javascript/session.mdx b/docs/references/javascript/session.mdx
index 9e4e9b87bf..0b2e7bb766 100644
--- a/docs/references/javascript/session.mdx
+++ b/docs/references/javascript/session.mdx
@@ -14,7 +14,7 @@ In certain scenarios, a session might be replaced by another one. This is often
All sessions that are **expired**, **removed**, **replaced**, **ended** or **abandoned** are not considered valid.
> [!NOTE]
-> For more details regarding the different session states, see our documentation on [session management](/docs/authentication/configuration/session-options).
+> For more information regarding the different session states, see the [guide on session management](/docs/authentication/configuration/session-options).
## Properties
diff --git a/docs/references/javascript/sign-in/authenticate-with.mdx b/docs/references/javascript/sign-in/authenticate-with.mdx
index 8d4004251a..bd7949b32c 100644
--- a/docs/references/javascript/sign-in/authenticate-with.mdx
+++ b/docs/references/javascript/sign-in/authenticate-with.mdx
@@ -87,7 +87,7 @@ function authenticateWithWeb3(params: AuthenticateWithWeb3Params): Promise Promise`
- The method of how to generate the signature for the Web3 sign-in. See [`GenerateSignatureParams`](#generate-signature-params) for more details.
+ The method of how to generate the signature for the Web3 sign-in. See [`GenerateSignatureParams`](#generate-signature-params) for more information.
---
diff --git a/docs/references/javascript/sign-in/sign-in.mdx b/docs/references/javascript/sign-in/sign-in.mdx
index f4e916c3f7..f435a46aaf 100644
--- a/docs/references/javascript/sign-in/sign-in.mdx
+++ b/docs/references/javascript/sign-in/sign-in.mdx
@@ -8,7 +8,7 @@ The `SignIn` object holds the state of the current sign-in and provides helper m
The following steps outline the sign-in process:
1. Initiate the sign-in process by collecting the user's authentication information and passing the appropriate parameters to the [`create()`](#create) method.
-1. Prepare the [first factor verification.](#first-factor) Users _must_ complete a first factor verification. This can be something like providing a password, an email link, a one-time code (OTP), a Web3 wallet address, or providing proof of their identity through an external social account (SSO/OAuth).
+1. Prepare the [first factor verification](#first-factor). Users _must_ complete a first factor verification. This can be something like providing a password, an email link, a one-time code (OTP), a Web3 wallet address, or providing proof of their identity through an external social account (SSO/OAuth).
1. Attempt to complete the first factor verification.
1. Optionally, if you have enabled [multi-factor](/docs/authentication/configuration/sign-up-sign-in-options) for your application, you will need to prepare the [second factor verification](#second-factor) for users who have set up 2FA for their account.
1. Attempt to complete the second factor verification.
@@ -262,4 +262,4 @@ In addition to the methods listed above, the `SignIn` class also has the followi
## Example
-For examples of how to access the `SignUp` object and use the associated methods, see the [custom flow guides.](/docs/custom-flows/overview)
+For examples of how to access the `SignUp` object and use the associated methods, see the [custom flow guides](/docs/custom-flows/overview).
diff --git a/docs/references/javascript/sign-up/authenticate-with.mdx b/docs/references/javascript/sign-up/authenticate-with.mdx
index b645e0ca09..8f2f746c29 100644
--- a/docs/references/javascript/sign-up/authenticate-with.mdx
+++ b/docs/references/javascript/sign-up/authenticate-with.mdx
@@ -88,7 +88,7 @@ function authenticateWithWeb3(params: AuthenticateWithWeb3Params): Promise(opts: [GenerateSignatureParams](#generate-signature-params)) => Promise\
- The method of how to generate the signature for the Web3 sign-in. See [`GenerateSignatureParams`](#generate-signature-params) for more details.
+ The method of how to generate the signature for the Web3 sign-in. See [`GenerateSignatureParams`](#generate-signature-params) for more information.
---
diff --git a/docs/references/javascript/sign-up/sign-up.mdx b/docs/references/javascript/sign-up/sign-up.mdx
index c59bb5624d..6bdf2284e9 100644
--- a/docs/references/javascript/sign-up/sign-up.mdx
+++ b/docs/references/javascript/sign-up/sign-up.mdx
@@ -8,7 +8,7 @@ The `SignUp` object holds the state of the current sign-up and provides helper m
The following steps outline the sign-up process:
1. Initiate the sign-up process by collecting the user's authentication information and passing the appropriate parameters to the [`create()`](#create) method.
-1. Prepare the [verification.](#verification)
+1. Prepare the [verification](#verification).
1. Attempt to complete the verification.
1. If the verification is successful, set the newly created session as the active session by passing the `SignIn.createdSessionId` to the [`setActive()`](/docs/references/javascript/clerk/session-methods#set-active) method on the `Clerk` object.
@@ -167,42 +167,42 @@ function create(params: SignUpCreateParams): Promise
- `firstName`
- `string | null`
- The user's first name. This option is available only if name is selected in personal information. Please check the instance settings for more information.
+ The user's first name. This option is available only if name is selected in personal information. Check the instance settings for more information.
---
- `lastName`
- `string | null`
- The user's last name. This option is available only if name is selected in personal information. Please check the instance settings for more information.
+ The user's last name. This option is available only if name is selected in personal information. Check the instance settings for more information.
---
- `password`
- `string | null`
- The user's password. This option is available only if password-based authentication is selected. Please check the instance settings for more information.
+ The user's password. This option is available only if password-based authentication is selected. Check the instance settings for more information.
---
- `gender`
- `string | null`
- The user's gender. This option is available only if gender is selected in personal information. Please check the instance settings for more information.
+ The user's gender. This option is available only if gender is selected in personal information. Check the instance settings for more information.
---
- `emailAddress`
- `string | null`
- The user's email address. This option is available only if email address is selected in contact information. Keep in mind that the email address requires an extra verification process. Please check the instance settings for more information.
+ The user's email address. This option is available only if email address is selected in contact information. Keep in mind that the email address requires an extra verification process. Check the instance settings for more information.
---
- `phoneNumber`
- `string | null`
- The user's phone number. This option is available only if phone number is selected in contact information. Keep in mind that the phone number requires an extra verification process. Please check the instance settings for more information.
+ The user's phone number. This option is available only if phone number is selected in contact information. Keep in mind that the phone number requires an extra verification process. Check the instance settings for more information.
---
@@ -216,7 +216,7 @@ function create(params: SignUpCreateParams): Promise
- `username`
- `string | null`
- The user's username. This option is available only if usernames are enabled. Please check the instance settings for more information.
+ The user's username. This option is available only if usernames are enabled. Check the instance settings for more information.
---
@@ -364,4 +364,4 @@ In addition to the methods listed above, the `SignUp` class also has the followi
## Example
-For examples of how to access the `SignUp` object and use the associated methods, see the [custom flow guides.](/docs/custom-flows/overview)
+For examples of how to access the `SignUp` object and use the associated methods, see the [custom flow guides](/docs/custom-flows/overview).
diff --git a/docs/references/javascript/types/user-organization-invitation.mdx b/docs/references/javascript/types/user-organization-invitation.mdx
index e5173948d4..048fb2c518 100644
--- a/docs/references/javascript/types/user-organization-invitation.mdx
+++ b/docs/references/javascript/types/user-organization-invitation.mdx
@@ -85,4 +85,4 @@ function accept(): Promise
### Example
-To see an example of how to use the `accept()` method, check out the [Manage invitations](/docs/organizations/manage-invitations) custom flow guide.
+To see an example of how to use the `accept()` method, see the [custom flow guide for managing invitations](/docs/organizations/manage-invitations).
diff --git a/docs/references/javascript/user/totp.mdx b/docs/references/javascript/user/totp.mdx
index ccf2b096a9..8d346ea2d0 100644
--- a/docs/references/javascript/user/totp.mdx
+++ b/docs/references/javascript/user/totp.mdx
@@ -10,7 +10,7 @@ Clerk supports multi-factor authentication (MFA) using Time-based One-time Passw
These methods on the [`User`](/docs/references/javascript/user/user) object are related to TOTP functionality and allow you to generate and verify TOTP secrets, disable TOTP, and create backup codes for user authentication.
-To see how all these methods work together, check out the [comprehensive example](#totp-example).
+To see how all these methods work together, see the [comprehensive example](#totp-example).
## `createTOTP()`
diff --git a/docs/references/javascript/user/user.mdx b/docs/references/javascript/user/user.mdx
index e32470b17d..3485fdb00b 100644
--- a/docs/references/javascript/user/user.mdx
+++ b/docs/references/javascript/user/user.mdx
@@ -248,7 +248,7 @@ The ClerkJS SDK provides some helper [methods](#methods) on the `User` object to
- `unsafeMetadata`
- `{[string]: any} | null`
- Metadata that can be read and set from the Frontend API. One common use case for this attribute is to implement custom fields that will be attached to the `User` object. Please note that there is also an `unsafeMetadata` attribute in the [`SignUp`](/docs/references/javascript/sign-up/sign-up) object. The value of that field will be automatically copied to the user's unsafe metadata once the sign up is complete.
+ Metadata that can be read and set from the Frontend API. One common use case for this attribute is to implement custom fields that will be attached to the `User` object. There is also an `unsafeMetadata` attribute in the [`SignUp`](/docs/references/javascript/sign-up/sign-up) object. The value of that field will be automatically copied to the user's unsafe metadata once the sign up is complete.
---
diff --git a/docs/references/nextjs/auth.mdx b/docs/references/nextjs/auth.mdx
index 9cf89c08bd..d4558edaca 100644
--- a/docs/references/nextjs/auth.mdx
+++ b/docs/references/nextjs/auth.mdx
@@ -66,7 +66,7 @@ The following table describes how `auth.protect()` behaves based on user authent
### Examples
-`auth.protect()` can be used to check if a user is authenticated or authorized to access certain parts of your application or even entire routes. See detailed examples in [the dedicated guide.](/docs/organizations/verify-user-permissions)
+`auth.protect()` can be used to check if a user is authenticated or authorized to access certain parts of your application or even entire routes. See detailed examples in the [dedicated guide](/docs/organizations/verify-user-permissions).
## `redirectToSignIn()`
@@ -146,4 +146,4 @@ export async function GET() {
## Use `auth()` to protect your app
-You can protect certain parts of your application or even entire routes based on a user's authentication and/or authorization status. See detailed examples in [the dedicated guide.](/docs/organizations/verify-user-permissions)
+You can protect certain parts of your application or even entire routes based on a user's authentication and/or authorization status. See detailed examples in the [dedicated guide](/docs/organizations/verify-user-permissions).
diff --git a/docs/references/nextjs/custom-signup-signin-pages.mdx b/docs/references/nextjs/custom-signup-signin-pages.mdx
index a6f77e7b4a..024ec13927 100644
--- a/docs/references/nextjs/custom-signup-signin-pages.mdx
+++ b/docs/references/nextjs/custom-signup-signin-pages.mdx
@@ -5,13 +5,13 @@ description: Learn how to add custom sign-in and sign-up pages to your Next.js a
This guide shows you how to use the [``](/docs/components/authentication/sign-in) and [``](/docs/components/authentication/sign-up) components with the [Next.js optional catch-all route](https://nextjs.org/docs/pages/building-your-application/routing/dynamic-routes#catch-all-segments) in order to build custom sign-in and sign-up pages for your Next.js app.
-If the prebuilt components don't meet your specific needs or if you require more control over the logic, you can rebuild the existing Clerk flows using the Clerk API. For more information, see the [custom flow guides.](/docs/custom-flows/overview)
+If the prebuilt components don't meet your specific needs or if you require more control over the logic, you can rebuild the existing Clerk flows using the Clerk API. For more information, see the [custom flow guides](/docs/custom-flows/overview).
> [!NOTE]
> Watch the video version of this guide on the Clerk YouTube channel → [YouTube (4 minutes)](https://youtu.be/fsuHLafTYyg).
> [!NOTE]
-> Just getting started with Clerk and Next.js? Check out the [quickstart tutorial](/docs/quickstarts/nextjs)!
+> Just getting started with Clerk and Next.js? See the [quickstart tutorial](/docs/quickstarts/nextjs)!
{/* TODO: Update these Steps once Steps component accepts other headings types. These headings should be H2s. */}
diff --git a/docs/references/nextjs/read-session-data.mdx b/docs/references/nextjs/read-session-data.mdx
index 7ab00a712c..11d9cb5134 100644
--- a/docs/references/nextjs/read-session-data.mdx
+++ b/docs/references/nextjs/read-session-data.mdx
@@ -147,7 +147,7 @@ Under the hood, `currentUser()` uses the [`clerkClient`](/docs/references/backen
You can access the active session and user data in your `getServerSideProps` using the `getAuth()` helper.
> [!NOTE]
- > Please note the addition of `buildClerkProps` in the return statement, which informs the Clerk React helpers of the authentication state during server-side rendering (like `useAuth()`, ``, and ``).
+ > Note the addition of `buildClerkProps` in the return statement, which informs the Clerk React helpers of the authentication state during server-side rendering (like `useAuth()`, ``, and ``).
```tsx {{ filename: 'pages/example.tsx' }}
import { getAuth, buildClerkProps } from '@clerk/nextjs/server'
diff --git a/docs/references/nodejs/available-methods.mdx b/docs/references/nodejs/available-methods.mdx
index 302e23f705..764a1607ef 100644
--- a/docs/references/nodejs/available-methods.mdx
+++ b/docs/references/nodejs/available-methods.mdx
@@ -4,7 +4,7 @@ description: Learn how to use the Clerk Node.js SDK to interact with the Clerk A
---
> [!CAUTION]
-> On January 8, 2025, the Node SDK will no longer be available. [Upgrade to the Express SDK.](/docs/upgrade-guides/node-to-express)
+> On January 8, 2025, the Node SDK will no longer be available. [Upgrade to the Express SDK](/docs/upgrade-guides/node-to-express).
All resource operations are mounted as sub-APIs on the `clerkClient` object. You can find the full list of available operations in the [JavaScript Backend SDK](/docs/references/backend/overview) documentation. To access a resource, you must first instantiate a `clerkClient` instance.
diff --git a/docs/references/nodejs/overview.mdx b/docs/references/nodejs/overview.mdx
index 9642e5de41..2b2956acab 100644
--- a/docs/references/nodejs/overview.mdx
+++ b/docs/references/nodejs/overview.mdx
@@ -4,14 +4,14 @@ description: Learn how to integrate Node.js into your Clerk application.
---
> [!CAUTION]
-> On January 8, 2025, the Node SDK will no longer be available. [Upgrade to the Express SDK.](/docs/upgrade-guides/node-to-express)
+> On January 8, 2025, the Node SDK will no longer be available. [Upgrade to the Express SDK](/docs/upgrade-guides/node-to-express).
## Set up Clerk Node.js
### Create a Clerk application
- You need to create a Clerk application in your Clerk Dashboard before you can set up Clerk Node.js. For more information, check out our [Set up your application](/docs/quickstarts/setup-clerk) guide.
+ You need to create a Clerk application in your Clerk Dashboard before you can set up Clerk Node.js. For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
### Install `@clerk/clerk-sdk-node`
diff --git a/docs/references/react/add-react-router.mdx b/docs/references/react/add-react-router.mdx
index 9af1ce6d8f..a173040ae8 100644
--- a/docs/references/react/add-react-router.mdx
+++ b/docs/references/react/add-react-router.mdx
@@ -312,7 +312,7 @@ Learn how to add React Router to your application using React Router's new Data
- The `` is child of the root layout, renders nothing, and has a check to see if the `userId` exists. This will confirm that a user is signed in. If the `userId` is not truthy, then the user will be redirected to the `/sign-in` route to sign-in. That protects all pages in the `/dashboard` route. All children of `/dashboard` will be mounted inside of the `` component in the dashboard layout.
-Your application is setup with `react-router-dom` and ready for you to add more layouts and routes as needed! If you want to get started using a template from this guide, please clone the following repository and then checkout the `integrate-react-router-dom-using-data-router-method` branch.
+Your application is setup with `react-router-dom` and ready for you to add more layouts and routes as needed! If you want to get started using a template from this guide, clone the following repository and then checkout the `integrate-react-router-dom-using-data-router-method` branch.
- [Clerk + React Quickstart](https://github.com/clerk/clerk-react-quickstart)
diff --git a/docs/references/react/overview.mdx b/docs/references/react/overview.mdx
index bea8f589fb..4fa53bdcba 100644
--- a/docs/references/react/overview.mdx
+++ b/docs/references/react/overview.mdx
@@ -14,6 +14,6 @@ Clerk React provides a suite of [custom hooks](/docs/references/react/use-user).
## Setting up Clerk React
-You need to create a Clerk application in your Clerk Dashboard before you can set up Clerk React. For more information, check out [the dedicated guide.](/docs/quickstarts/setup-clerk)
+You need to create a Clerk application in your Clerk Dashboard before you can set up Clerk React. For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
Once a Clerk application has been created, you can install and start using Clerk React in your application. [The quickstart guide](/docs/quickstarts/react) will have all the information you need to get started.
diff --git a/docs/references/react/use-sign-in.mdx b/docs/references/react/use-sign-in.mdx
index 2d8cfe4c4a..c178a6a80d 100644
--- a/docs/references/react/use-sign-in.mdx
+++ b/docs/references/react/use-sign-in.mdx
@@ -3,7 +3,7 @@ title: '`useSignIn()`'
description: Clerk's useSignIn() hook provides access to the SignIn object, which allows you to check the current state of a sign-in.
---
-The `useSignIn()` hook provides access to the [`SignIn`](/docs/references/javascript/sign-in/sign-in) object, which allows you to check the current state of a sign-in. This is also useful for creating a [custom sign-in flow.](#create-a-custom-sign-in-flow-with-use-sign-in)
+The `useSignIn()` hook provides access to the [`SignIn`](/docs/references/javascript/sign-in/sign-in) object, which allows you to check the current state of a sign-in. This is also useful for creating a [custom sign-in flow](#create-a-custom-sign-in-flow-with-use-sign-in).
## `useSignIn()` returns
@@ -84,4 +84,4 @@ The `status` property of the `SignIn` object can be one of the following values:
### Create a custom sign-in flow with `useSignIn()`
-The `useSignIn()` hook can also be used to build fully custom sign-in flows, if Clerk's prebuilt components don't meet your specific needs or if you require more control over the authentication flow. Different sign-in flows include email and password, email and phone codes, email links, and multifactor (MFA). To learn more about using the `useSignIn()` hook to create custom flows, check out the [custom flow guides](/docs/custom-flows/overview).
+The `useSignIn()` hook can also be used to build fully custom sign-in flows, if Clerk's prebuilt components don't meet your specific needs or if you require more control over the authentication flow. Different sign-in flows include email and password, email and phone codes, email links, and multifactor (MFA). To learn more about using the `useSignIn()` hook to create custom flows, see the [custom flow guides](/docs/custom-flows/overview).
diff --git a/docs/references/react/use-sign-up.mdx b/docs/references/react/use-sign-up.mdx
index 00a7b85240..412f06df66 100644
--- a/docs/references/react/use-sign-up.mdx
+++ b/docs/references/react/use-sign-up.mdx
@@ -3,7 +3,7 @@ title: '`useSignUp()`'
description: Clerk's useSignUp() hook gives you access to the SignUp object, which allows you to check the current state of a sign-up.
---
-The `useSignUp()` hook gives you access to the [`SignUp`](/docs/references/javascript/sign-up/sign-up) object, which allows you to check the current state of a sign-up. This is also useful for creating a [custom sign-up flow.](#create-a-custom-sign-up-flow-with-use-sign-up)
+The `useSignUp()` hook gives you access to the [`SignUp`](/docs/references/javascript/sign-up/sign-up) object, which allows you to check the current state of a sign-up. This is also useful for creating a [custom sign-up flow](#create-a-custom-sign-up-flow-with-use-sign-up).
## `useSignUp()` returns
@@ -82,4 +82,4 @@ The `status` property of the `SignUp` object can be one of the following values:
### Create a custom sign-up flow with `useSignUp()`
-The `useSignUp()` hook can also be used to build fully custom sign-up flows, if Clerk's prebuilt components don't meet your specific needs or if you require more control over the authentication flow. Different sign-up flows include email and password, email and phone codes, email links, and multifactor (MFA). To learn more about using the `useSignUp()` hook to create custom flows, check out the [custom flow guides](/docs/custom-flows/overview).
+The `useSignUp()` hook can also be used to build fully custom sign-up flows, if Clerk's prebuilt components don't meet your specific needs or if you require more control over the authentication flow. Different sign-up flows include email and password, email and phone codes, email links, and multifactor (MFA). To learn more about using the `useSignUp()` hook to create custom flows, see the [custom flow guides](/docs/custom-flows/overview).
diff --git a/docs/references/remix/custom-signup-signin-pages.mdx b/docs/references/remix/custom-signup-signin-pages.mdx
index 3943858c38..b583e2a3da 100644
--- a/docs/references/remix/custom-signup-signin-pages.mdx
+++ b/docs/references/remix/custom-signup-signin-pages.mdx
@@ -5,12 +5,12 @@ description: Learn how to add custom sign-in and sign-up pages to your Remix app
This guide shows you how to use the [``](/docs/components/authentication/sign-in) and [``](/docs/components/authentication/sign-up) components with the [Remix optional route](https://reactrouter.com/en/main/route/route#optional-segments) in order to build custom sign-in and sign-up pages for your Remix app.
-If Clerk's prebuilt components don't meet your specific needs or if you require more control over the logic, you can rebuild the existing Clerk flows using the Clerk API. For more information, check out the [custom flows](/docs/custom-flows/overview) guides.
+If Clerk's prebuilt components don't meet your specific needs or if you require more control over the logic, you can rebuild the existing Clerk flows using the Clerk API. For more information, see the [custom flow guides](/docs/custom-flows/overview).
The functionality of the components are controlled by the instance settings you specify in your [Clerk Dashboard](https://dashboard.clerk.com).
> [!NOTE]
-> Just getting started with Clerk and Remix? Check out the [quickstart tutorial](/docs/quickstarts/remix)!
+> Just getting started with Clerk and Remix? See the [quickstart tutorial](/docs/quickstarts/remix)!
## Build your sign-up page
diff --git a/docs/references/ruby/overview.mdx b/docs/references/ruby/overview.mdx
index 3820bf6764..1e5a8b7a57 100644
--- a/docs/references/ruby/overview.mdx
+++ b/docs/references/ruby/overview.mdx
@@ -6,7 +6,7 @@ description: Learn how to integrate Ruby into your Clerk application.
### Create a Clerk application
- You need to create a Clerk application in your Clerk Dashboard before you can set up Clerk Ruby. For more information, check out our [Set up your application](/docs/quickstarts/setup-clerk) guide.
+ You need to create a Clerk application in your Clerk Dashboard before you can set up Clerk Ruby. For more information, see the [setup guide](/docs/quickstarts/setup-clerk).
### Install Ruby
@@ -92,7 +92,7 @@ description: Learn how to integrate Ruby into your Clerk application.
end
```
- Refer to the [Faraday documentation](https://lostisland.github.io/faraday/#/) for details.
+ For more information, see [Faraday's documentation](https://lostisland.github.io/faraday/#/).
#### Environment variables
diff --git a/docs/references/sdk/backend-only.mdx b/docs/references/sdk/backend-only.mdx
index 788b53c43f..92ffd575c5 100644
--- a/docs/references/sdk/backend-only.mdx
+++ b/docs/references/sdk/backend-only.mdx
@@ -3,7 +3,7 @@ title: Backend-only SDK
description: A reference for implementing a backend-only Clerk SDK
---
-When creating a backend-only SDK, you have two options for implementing the [BAPI](/docs/references/sdk/terminology) endpoints: either [develop a backend SDK that encompasses all BAPI endpoints](#implementation-bapi) or [create an SDK tailored for an existing backend framework.](#implementation-node-js-backend-framework)
+When creating a backend-only SDK, you have two options for implementing the [BAPI](/docs/references/sdk/terminology) endpoints: either [develop a backend SDK that encompasses all BAPI endpoints](#implementation-bapi) or [create an SDK tailored for an existing backend framework](#implementation-node-js-backend-framework).
The source of truth for all BAPI endpoints is the [BAPI OpenAPI spec](https://clerk.com/docs/reference/backend-api). For Node.js backend frameworks, you can build on top of the [JavaScript Backend SDK](/docs/references/backend/overview).
@@ -116,7 +116,7 @@ You can manually create a wrapper library around the [BAPI OpenAPI](https://cler
```
> [!TIP]
- > Check out the Next.js [`getAuth()`](/docs/references/nextjs/get-auth) reference to see how it's implemented.
+ > See the Next.js [`getAuth()`](/docs/references/nextjs/get-auth) reference to see how it's implemented.
### Create a `requireAuth` helper
diff --git a/docs/references/sdk/conventions.mdx b/docs/references/sdk/conventions.mdx
index 646e918a62..1213a92c74 100644
--- a/docs/references/sdk/conventions.mdx
+++ b/docs/references/sdk/conventions.mdx
@@ -19,7 +19,7 @@ Add **“Clerk”** as a prefix or postfix into the name as it’ll make the SDK
## Environment variables
-Any environment variable used in the context of Clerk should be prefixed with `CLERK_`. [Learn more about Clerk environment variables.](/docs/deployments/clerk-environment-variables)
+Any environment variable used in the context of Clerk should be prefixed with `CLERK_`. [Learn more about Clerk environment variables](/docs/deployments/clerk-environment-variables).
> [!NOTE]
> Depending on your framework, you’ll need to add a prefix to environment variables that should be available on the frontend. For example, `PUBLIC_`, `VITE_` or `NEXT_PUBLIC`. These alterations are fine.
@@ -123,4 +123,4 @@ Your SDK will require your users to have Node.js installed and use the framework
Security is important at Clerk and thus all Clerk SDKs are published with provenance statements. This allows you to publicly establish where a package was built and who published a package, which can increase supply-chain security for your packages.
-Please read npm's guide on [generating provenance statements](https://docs.npmjs.com/generating-provenance-statements).
+Read npm's guide on [generating provenance statements](https://docs.npmjs.com/generating-provenance-statements).
diff --git a/docs/references/sdk/fullstack.mdx b/docs/references/sdk/fullstack.mdx
index 1de5c99fe9..46736e14c6 100644
--- a/docs/references/sdk/fullstack.mdx
+++ b/docs/references/sdk/fullstack.mdx
@@ -23,7 +23,7 @@ A fullstack SDK combines the [frontend-only SDK](/docs/references/sdk/frontend-o
## Implementation
-Please check out the respective [frontend-only SDK](/docs/references/sdk/frontend-only) and [backend-only SDK](/docs/references/sdk/backend-only) implementation instructions.
+See the respective [frontend-only SDK](/docs/references/sdk/frontend-only) and [backend-only SDK](/docs/references/sdk/backend-only) implementation instructions.
In addition to these instructions, you'll need to go through the following steps to support all required features.
diff --git a/docs/references/sdk/terminology.mdx b/docs/references/sdk/terminology.mdx
index 8a4768e864..65b0c4f889 100644
--- a/docs/references/sdk/terminology.mdx
+++ b/docs/references/sdk/terminology.mdx
@@ -15,7 +15,7 @@ A consistent terminology should be used across all user interactions with Clerk'
| BAPI | [Backend API of Clerk](/docs/reference/backend-api){{ target: '_blank' }}. Currently set to `https://api.clerk.com`. A restful CRUD API for the server-side. |
| Secret key | Your app’s secret key for use in the backend. Do not expose this on the frontend with a public environment variable. Allows for CRUD operations. |
| Publishable key | Your app’s publishable key for use in the frontend. |
-| Instances | When creating an app, you’re provided with two instances: Development and Production. [Learn more.](/docs/deployments/environments) |
+| Instances | When creating an app, you’re provided with two instances: Development and Production. [Learn more](/docs/deployments/environments). |
| Hotloading ClerkJS | `@clerk/clerk-js`, or ClerkJS, is the foundational JavaScript library for all frontend JS SDKs, e.g. used in `@clerk/clerk-react`. When you install `@clerk/clerk-react` through npm, you don’t install `@clerk/clerk-js`. Instead, once the React code is executed in the browser, the React SDK adds a `