Run format

docs/authentication/enterprise-connections/oidc/custom-provider.mdx

@@ -32,14 +32,15 @@ To make the setup process easier, it's recommended to keep two browser tabs open
   1. Under **OpenID Connect (OIDC)**, select **Custom OIDC Provider**.
   1. Add the **Name** of the connection.
   1. Add the **Key** of the provider. This is the provider's unique identifier (cannot be changed after creation).
-  1. Add the **Specific Domain** that you want to allow this connection for. This is the domain of the users you want to allow to sign in to your app.
+  1. Enter the **Domain**. This is the email domain of the users you want to allow to sign in to your application. Optionally, select an **Organization**.
   1. Select **Add connection**. You will be redirected to the connection's configuration page. Keep this page open.
 
   ## Configure your IdP
 
   1. If necessary, create a new application in your IdP.
   1. In the connection's configuration page of the Clerk Dashboard, copy the **Authorized redirect URI**.
   1. Add the value to your IdP's whitelisted URLs.
+  1. Find your application's **Discovery Endpoint**, **Client ID**, and **Client Secret** and copy them.
 
   ## Set the Discovery Endpoint, Client ID, and Client Secret in Clerk
 

docs/references/backend/saml-connections/create-saml-connection.mdx

@@ -31,7 +31,7 @@ function createSamlConnection(params: CreateSamlConnectionParams): Promise<SamlC
 
   The domain of your organization. Sign in flows using an email with this domain will use this SAML Connection. For example: `'clerk.dev'`
 
- ---
+  ---
 
   - `organizationId?`
   - `string`