capitalize clerk features

Author: alexisintech

docs/guides/organizations/add-members/invitations.mdx

@@ -1,62 +1,62 @@
 ---
-title: Invite users to your organization
-description: Send, manage, and track user invitations within your multi-tenant SaaS using Clerk organizations.
+title: Invite users to your Organization
+description: Send, manage, and track user invitations within your multi-tenant SaaS using Clerk Organizations.
 metadata:
-  title: Send and manage organization invitations via Clerk
+  title: Send and manage Organization invitations via Clerk
 ---
 
-Organization invitations let you add new members to your organization. When you send an invitation, Clerk sends an email to the invited user with a unique invitation link. When the user visits the organization invitation link, Clerk redirects them to the [Account Portal sign-in page](/docs/guides/customizing-clerk/account-portal#sign-in). If the user is already signed in, Clerk redirects them 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).
+Organization invitations let you add new members to your Organization. When you send an invitation, Clerk sends an email to the invited user with a unique invitation link. When the user visits the Organization invitation link, Clerk redirects them to the [Account Portal sign-in page](/docs/guides/customizing-clerk/account-portal#sign-in). If the user is already signed in, Clerk redirects them 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).
 
-By default, only [admins](/docs/guides/organizations/control-access/roles-and-permissions#default-roles) can invite users to an organization.
+By default, only [admins](/docs/guides/organizations/control-access/roles-and-permissions#default-roles) can invite users to an Organization.
 
 This feature requires that [**Email** is enabled](/docs/guides/configure/auth-strategies/sign-up-sign-in-options#email), as Clerk uses the user's email address to send the invitation. You can still disable **Email** as a sign-in option if you do not want users to be able to sign-in with their email address.
 
 To configure your application's **Email** settings, navigate to the [**User & authentication**](https://dashboard.clerk.com/~/user-authentication/user-and-authentication) page in the Clerk Dashboard.
 
 ## When to use invitations
 
-Invitations work well when you need precise control over who joins your organization and which role they receive. This approach fits scenarios where:
+Invitations work well when you need precise control over who joins your Organization and which Role they receive. This approach fits scenarios where:
 
 - Teams are small and members are known in advance.
 - Onboarding requires manual approval or review.
-- Specific roles need to be assigned during the invitation.
+- Specific Roles need to be assigned during the invitation.
 
-If you want to streamline enrollment for users with company email addresses, consider [verified domains](/docs/guides/organizations/add-members/verified-domains), which can automatically invite users based on their email domain. If customers require centralized authentication through their Identity Provider, use [enterprise SSO](/docs/guides/organizations/add-members/sso).
+If you want to streamline enrollment for users with company email addresses, consider [Verified Domains](/docs/guides/organizations/add-members/verified-domains), which can automatically invite users based on their email domain. If customers require centralized authentication through their Identity Provider, use [Enterprise SSO](/docs/guides/organizations/add-members/sso).
 
 ## Create an invitation
 
-Clerk's [prebuilt components](/docs/reference/components/overview) and [Account Portal pages](/docs/guides/customizing-clerk/account-portal) manage all organization invitation flows, including creating, managing, and accepting invitations.
+Clerk's [prebuilt components](/docs/reference/components/overview) and [Account Portal pages](/docs/guides/customizing-clerk/account-portal) manage all Organization invitation flows, including creating, managing, and accepting invitations.
 
 However, if you want to build custom flows, see the following sections.
 
 ### Client-side
 
-To create an organization invitation on the client-side, see the [dedicated guide](/docs/guides/development/custom-flows/organizations/manage-organization-invitations). Note that this uses the [`organizations.inviteMember()`](/docs/reference/javascript/organization#invite-member) method, which does not let you specify a redirect URL; it will always redirect to the Account Portal sign-in page. If you want to specify a redirect URL, you must create the invitation on the server-side.
+To create an Organization invitation on the client-side, see the [dedicated guide](/docs/guides/development/custom-flows/organizations/manage-organization-invitations). Note that this uses the [`organizations.inviteMember()`](/docs/reference/javascript/organization#invite-member) method, which does not let you specify a redirect URL; it will always redirect to the Account Portal sign-in page. If you want to specify a redirect URL, you must create the invitation on the server-side.
 
 ### Server-side
 
-To create organization invitations on the server-side, use the [Backend API](/docs/reference/backend-api/tag/organization-invitations/post/organizations/\{organization_id}/invitations){{ target: '_blank' }} either by using a cURL command or the [JS Backend SDK](/docs/js-backend/getting-started/quickstart). The JS Backend SDK is a wrapper around the Backend API that makes it easier to interact with the API.
+To create Organization invitations on the server-side, use the [Backend API](/docs/reference/backend-api/tag/organization-invitations/post/organizations/\{organization_id}/invitations){{ target: '_blank' }} either by using a cURL command or the [JS Backend SDK](/docs/js-backend/getting-started/quickstart). The JS Backend SDK is a wrapper around the Backend API that makes it easier to interact with the API.
 
 Use the following tabs to see examples for each method.
 
 <Tabs items={["cURL", "JS Backend SDK"]}>
   <Tab>
-    The following example demonstrates how to create an organization invitation using cURL.
+    The following example demonstrates how to create an Organization invitation using cURL.
 
     <SignedIn>
       - Your Secret Key is already injected into the code snippet.
-      - Replace the `org_123` with the ID of the organization you want to invite the user to.
+      - Replace the `org_123` with the ID of the Organization you want to invite the user to.
       - Replace the `user_123` with the ID of the user who is inviting the other user.
       - Replace the email address with the email address you want to invite.
       - Replace the `role` with the role you want to assign to the invited user.
     </SignedIn>
 
     <SignedOut>
       - Replace `YOUR_SECRET_KEY` with your Clerk Secret Key. You can find your Secret Key on the [**API Keys**](https://dashboard.clerk.com/~/api-keys) page in the Clerk Dashboard.
-      - Replace the `org_123` with the ID of the organization you want to invite the user to.
+      - Replace the `org_123` with the ID of the Organization you want to invite the user to.
       - Replace the `user_123` with the ID of the user who is inviting the other user.
       - Replace the email address with the email address you want to invite.
-      - Replace the `role` with the role you want to assign to the invited user.
+      - Replace the `role` with the Role you want to assign to the invited user.
     </SignedOut>
 
     ```bash {{ filename: 'terminal' }}
@@ -97,7 +97,7 @@ Once the user visits the invitation link, they will be redirected to the page yo
 
 ### Invitation metadata
 
-You can also add metadata to an invitation when creating the invitation through the Backend API. Once the invited user signs up using the invitation link, Clerk stores the **invitation** metadata (`OrganizationInvitation.publicMetadata`) in the organization **membership's** metadata (`OrganizationMembership.publicMetadata`). For more details on organization membership metadata, see the [OrganizationMembership](/docs/reference/javascript/types/organization-membership) reference.
+You can also add metadata to an invitation when creating the invitation through the Backend API. Once the invited user signs up using the invitation link, Clerk stores the **invitation** metadata (`OrganizationInvitation.publicMetadata`) in the Organization **membership's** metadata (`OrganizationMembership.publicMetadata`). For more details on Organization membership metadata, see the [OrganizationMembership](/docs/reference/javascript/types/organization-membership) reference.
 
 To add metadata to an invitation, add the `public_metadata` parameter when creating the invitation.
 
@@ -151,15 +151,15 @@ Use the following tabs to see examples for each method.
   </Tab>
 
   <Tab>
-    To use the JS Backend SDK to revoke an organization invitation, see the [`revokeOrganizationInvitation()`](/docs/reference/backend/organization/revoke-organization-invitation) reference documentation.
+    To use the JS Backend SDK to revoke an Organization invitation, see the [`revokeOrganizationInvitation()`](/docs/reference/backend/organization/revoke-organization-invitation) reference documentation.
   </Tab>
 </Tabs>
 
 ## Next steps
 
-Now that you know how to invite users to your organization, you can:
+Now that you know how to invite users to your Organization, you can:
 
-- [Configure verified domains](/docs/guides/organizations/add-members/verified-domains) to automatically invite users based on their email domain
-- [Set up enterprise SSO](/docs/guides/organizations/add-members/sso) for centralized authentication through an Identity Provider
-- [Set up roles and permissions](/docs/guides/organizations/control-access/roles-and-permissions) to control what invited users can access
+- [Configure Verified Domains](/docs/guides/organizations/add-members/verified-domains) to automatically invite users based on their email domain
+- [Set up Enterprise SSO Connections](/docs/guides/organizations/add-members/sso) for centralized authentication through an Identity Provider
+- [Set up Roles and Permissions](/docs/guides/organizations/control-access/roles-and-permissions) to control what invited users can access
 - [Add metadata to invitations](/docs/guides/organizations/metadata) for tracking or custom workflows