chore: change wording and move periods outside of links

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
 
@@ -515,7 +515,7 @@ pnpm add @clerk/nextjs
 
 The image below shows what this example looks like once rendered.
 
-![An example of a <CodeBlockTabs /> component with three tabs options for 'npm', 'yarn', and 'pnpm'. Each tab shows a code example of how to install the @clerk/nextjs package.](/.github/media/code-block-tabs.png)
+![An example of a <CodeBlockTabs /> component with three tabs options for 'npm', 'yarn', and 'pnpm'. Each tab shows a code example of how to install the @clerk/nextjs package](/.github/media/code-block-tabs.png).
 
 ### `<Tabs />`
 

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
 

docs/advanced-usage/satellite-domains.mdx

@@ -35,7 +35,7 @@ To access authentication state from a satellite domain, users will be transparen
   When building your sign-in flow, you must configure it to run within your primary application, e.g. on `/sign-in`.
 
   > [!NOTE]
-  > For more information about creating your application, check out Clerk's [detailed guide](/docs/quickstarts/setup-clerk).
+  > For more information about creating your application, see the [detailed guide](/docs/quickstarts/setup-clerk).
 
   ### Add your first satellite domain
 
@@ -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.
 </Steps>
 
-If you have any questions about satellite domains, or you're having any trouble setting this up, please contact [[email protected]](mailto:[email protected])
+If you have any questions about satellite domains, or you're having any trouble setting this up, contact [[email protected]](mailto:[email protected])

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 [Set up your application 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
   </Tabs>
 
   > [!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
 
@@ -325,4 +325,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 Clerk's Frontend API from your proxy!
 </Steps>
 
-If you have any questions about proxying, or you're having any trouble setting this up, please contact [[email protected]](mailto:[email protected]).
+If you have any questions about proxying, or you're having any trouble setting this up, contact [[email protected]](mailto:[email protected]).

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 the corresponding [documentation page](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.
 

docs/authentication/configuration/session-options.mdx

@@ -63,4 +63,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 [Customize your session token](/docs/backend-requests/making/custom-session-token) guide.

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).

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).
+See the detailed guide for information on [how to set up your application](/docs/quickstarts/setup-clerk).

docs/authentication/saml/account-linking.mdx

@@ -14,7 +14,7 @@ In the following sections, we'll look at the different scenarios that can occur
 > [!NOTE]
 > Email addresses from SAML providers are considered verified by default.
 
-![Flow chart of the SAML SSO account linking process in various scenarios.](/docs/images/authentication/account-linking-flow-saml.webp)
+![Flow chart of the SAML SSO account linking process in various scenarios](/docs/images/authentication/account-linking-flow-saml.webp).
 
 ### Email is verified in Clerk
 

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
 

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
 

docs/authentication/saml/overview.mdx

@@ -50,4 +50,4 @@ 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.

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 [Set up your application 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

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 [Set up your application 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

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 [Set up your application 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

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 [Set up your application 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

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 [Set up your application 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

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 [Set up your application 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

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 [Set up your application 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

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 [Set up your application 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

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 [Set up your application 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