Updates yourdomain to your-domain (#2684)

Author: manovotny

docs/guides/development/deployment/chrome-extension.mdx

@@ -32,7 +32,7 @@ For Clerk production instances, there must be a domain associated with the insta
 ```env {{ filename: '.env.production' }}
 PLASMO_PUBLIC_CLERK_PUBLISHABLE_KEY={{pub_key}}
 CLERK_FRONTEND_API={{fapi_url}}
-PLASMO_PUBLIC_CLERK_SYNC_HOST=https://yourdomain.com
+PLASMO_PUBLIC_CLERK_SYNC_HOST=https://your-domain.com
 ```
 
 ## Add production domain to `host_permissions`
@@ -52,7 +52,7 @@ The following example shows how to configure `host_permissions` for production:
   "manifest": {
     "key": "$CRX_PUBLIC_KEY",
     "permissions": ["cookies", "storage"],
-    "host_permissions": ["https://<yourdomain>/*", "$CLERK_FRONTEND_API/*"]
+    "host_permissions": ["https://<your-domain>/*", "$CLERK_FRONTEND_API/*"]
   }
 }
 ```

docs/guides/development/mcp/connect-mcp-client.mdx

@@ -26,7 +26,7 @@ To complete the integration, you'll need to connect an MCP-compatible client to
 ### Development vs. Production Setup
 
 - **Development**: Start your MCP server by running `npm run dev` and use `http://localhost:3000/mcp` as your server URL.
-- **Production**: Use your deployed URL (e.g. `https://yourdomain.com/mcp`) for security and proper functionality.
+- **Production**: Use your deployed URL (e.g. `https://your-domain.com/mcp`) for security and proper functionality.
   > [!WARNING]
   > Always use HTTPS URLs in production environments. HTTP connections are not secure and may not work with all MCP clients.
 

docs/guides/development/sdk-development/terminology.mdx

@@ -11,7 +11,7 @@ A consistent terminology should be used across all user interactions with Clerk'
 | Session | A [session](/docs/reference/javascript/session){{ target: '_blank' }} is a secure representation of the authentication state of the current user. Each client can hold multiple sessions on the same device. This is identical to how Gmail works in a browser. |
 | User | A user represents the current user of the session. The [`User`](/docs/reference/javascript/user){{ target: '_blank' }} object holds all the basic user information e.g. name, email addresses, phone numbers, etc… including their public, private, and unsafe metadata. |
 | Organization | An [organization](/docs/reference/javascript/organization){{ target: '_blank' }} represents the current organization of the session. Users can belong to many organizations. One of them will be the [active organization](!active-organization) of the session. |
-| FAPI | [Frontend API of Clerk](https://clerk.com/docs/reference/frontend-api). Example: `https://random-name.clerk.accounts.dev` (Production example: `https://clerk.yourdomain.com`). FAPI is the primary API for Clerk’s UI components. Every Clerk development/production instance has a dedicated FAPI. This is the authentication, session, user & organization management API you or your users will interact with. |
+| FAPI | [Frontend API of Clerk](https://clerk.com/docs/reference/frontend-api). Example: `https://random-name.clerk.accounts.dev` (Production example: `https://clerk.your-domain.com`). FAPI is the primary API for Clerk’s UI components. Every Clerk development/production instance has a dedicated FAPI. This is the authentication, session, user & organization management API you or your users will interact with. |
 | 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. |

docs/guides/development/troubleshooting/email-deliverability.mdx

@@ -33,7 +33,7 @@ Every domain name (i.e. `example.com`, `clerk.com`, etc.) has its own reputation
 
 ### Setup a real email address
 
-Email providers will check if there's an actual mailbox behind the "from address" of an email. By default, Clerk will send your emails from [notifications@yourdomain.com](mailto:notifications@yourdomain.com). You should make sure that you set up a mailbox at this email address. If you'd like to use a different "from address", you can change its value via our [Backend API](/docs/reference/backend-api/tag/beta-features/patch/beta_features/instance_settings){{ target: '_blank' }}.
+Email providers will check if there's an actual mailbox behind the "from address" of an email. By default, Clerk will send your emails from [notifications@your-domain.com](mailto:notifications@your-domain.com). You should make sure that you set up a mailbox at this email address. If you'd like to use a different "from address", you can change its value via our [Backend API](/docs/reference/backend-api/tag/beta-features/patch/beta_features/instance_settings){{ target: '_blank' }}.
 
 ### Email content
 

docs/guides/sessions/sync-host.mdx

@@ -33,12 +33,12 @@ Clerk allows you to sync the authentication state from your web app to your Chro
     </Tab>
 
     <Tab>
-      Add `PLASMO_PUBLIC_CLERK_SYNC_HOST` to your `.env.production` file. The value should be the [domain that your Clerk Frontend API](https://dashboard.clerk.com/last-active?path=domains) runs on. For example, `https://clerk.yourdomain.com`.
+      Add `PLASMO_PUBLIC_CLERK_SYNC_HOST` to your `.env.production` file. The value should be the [domain that your Clerk Frontend API](https://dashboard.clerk.com/last-active?path=domains) runs on. For example, `https://clerk.your-domain.com`.
 
       ```env {{ filename: '.env.production', mark: [3] }}
       PLASMO_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_live_123
-      CLERK_FRONTEND_API=https://clerk.yourdomain.com
-      PLASMO_PUBLIC_CLERK_SYNC_HOST=https://clerk.yourdomain.com
+      CLERK_FRONTEND_API=https://clerk.your-domain.com
+      PLASMO_PUBLIC_CLERK_SYNC_HOST=https://clerk.your-domain.com
       ```
     </Tab>
   </Tabs>