Apply additional documentation grammar and style fixes

Addressing remaining issues from comprehensive review:

**Title Case Improvements:**
- Step titles now consistent with title case (List Your Connection, Choose Your Connections, Upgrade the Connection to Domain-Level)

**Formatting & Punctuation:**
- Hyphenated compound adjectives (username-and-password, Auth0-powered)
- Sentence restructuring (split linked text from preceding text with periods)

**Capitalization:**
- AI Agents → AI agents (lowercase for consistency)
- Single Sign On → Single Sign-On (hyphenated)

**Grammar & Style:**
- Added commas after introductory phrases
- Fixed markdown backticks for code references (`client_id`)
- Consistent punctuation in numbered lists

Files updated:
- config-tenant-settings.mdx (title case, hyphenation)
- testing-instructions.mdx (hyphenated adjective)
- create-custom-token-exchange-profile.mdx (list consistency)
- overview.mdx (punctuation in conjunctions)
- why-auth-for-mcp.mdx (capitalization, punctuation, hyphenation)
- resource-param-compatibility-profile.mdx (sentence structure)
- registering-your-mcp-client-application.mdx (markdown formatting, list consistency)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: btiernay

auth4genai/mcp/guides/registering-your-mcp-client-application.mdx

@@ -17,7 +17,7 @@ You can register your client in two ways: statically or dynamically. For most sc
 This method is recommended because it offers several key advantages:
 
 * **Enhanced Security**: You explicitly approve every client, preventing unauthorized or malicious applications from registering themselves and accessing your system.
-* **Predictable Configuration**: The client_id and other settings are known in advance, simplifying deployment and configuration management.
+* **Predictable Configuration**: The `client_id` and other settings are known in advance, simplifying deployment and configuration management.
 * **Clear Auditing**: There is a clear, auditable trail for every client created, linking it to a specific developer or team.
 * **Principle of Least Privilege**: You can precisely configure the exact permissions (scopes) and settings for each client from the outset.
 

auth4genai/mcp/guides/resource-param-compatibility-profile.mdx

@@ -44,7 +44,7 @@ Once the **Resource Parameter Compatibility Profile** is enabled, Auth0 will use
   />
 </Frame>
 
-If both the `resource` and `audience` are available, the `audience` will still be used. Auth0 will not forward the `resource` to upstream Identity Providers (IdPs), [learn more](./resource-param-compatibility-profile#resource-parameter-forwarding-to-upstream-identity-provider-idp).
+If both the `resource` and `audience` are available, the `audience` will still be used. Auth0 will not forward the `resource` to upstream Identity Providers (IdPs). [Learn more](./resource-param-compatibility-profile#resource-parameter-forwarding-to-upstream-identity-provider-idp).
 
 *RFC 8707 requires the `resource` parameter to [be an absolute URI](https://www.rfc-editor.org/rfc/rfc8707.html#name-resource-parameter), to conform with RFC 8707, we recommend defining your resource server identifiers (API identifiers) in [URI format](https://datatracker.ietf.org/doc/html/rfc3986). Using an absolute URI as the identifier of your MCP Server is also a requirement from the MCP Authorization specification.*
 

auth4genai/mcp/intro/overview.mdx

@@ -183,5 +183,5 @@ Auth for MCP delivers a more secure and scalable authentication and authorizatio
   cta="Request to join the Early Access Program"
   vertical>
 
-Auth for MCP is currently available in Early Access. To join the Early Access program, please complete this form and we'll reach out to you when your request is processed.
+Auth for MCP is currently available in Early Access. To join the Early Access program, please complete this form, and we'll reach out to you when your request is processed.
 </Card>

auth4genai/mcp/intro/why-auth-for-mcp.mdx

@@ -32,9 +32,9 @@ MCP offers practical advantages, such as standardized interfaces for LLMs to int
   />
 </Frame>
 
-Auth0 allows your users to securely interact with trusted agents without worrying about LLMs gaining access to sensitive information like access tokens: Auth0 enforces scoped, identity-bound, least-privilege access for AI Agents, both first-party and third-party APIs.
+Auth0 allows your users to securely interact with trusted agents without worrying about LLMs gaining access to sensitive information like access tokens: Auth0 enforces scoped, identity-bound, least-privilege access for AI agents, both first-party and third-party APIs.
 
-Auth0 manages consent flows and per-client permissions and secures credentials via Token Vault and Token Exchange while making it possible to audit logs and keep track of lifecycle events.
+Auth0 manages consent flows and per-client permissions, secures credentials via Token Vault and Token Exchange while making it possible to audit logs and keep track of lifecycle events.
 
 The MCP specification highlights several key OAuth 2.1 features that Auth0 provides:
 
@@ -50,7 +50,7 @@ Auth0 is a flexible, drop-in solution to add authentication and authorization se
 - Username and password
 - [Passwordless and Passkeys](https://auth0.com/docs/authenticate/passwordless)
 - [Social Login (Google, Meta, Microsoft, GitHub, etc.)](https://auth0.com/docs/authenticate/passwordless#social-login)
-- [Corporate credentials and Single Sign On (SSO)](https://auth0.com/docs/authenticate/single-sign-on) for B2B AI applications
+- [Corporate credentials and Single Sign-On (SSO)](https://auth0.com/docs/authenticate/single-sign-on) for B2B AI applications
 - And more.
 
 Auth0 also provides the following features for enhanced security and scalability:

auth4genai/snippets/mcp/get-started/config-tenant/config-tenant-settings.mdx

@@ -4,18 +4,18 @@
   <Accordion title="1. Promote the connection to a domain-level connection">
     To allow third-party clients like MCP Inspector to use a connection such as a username-and-password database or a social connection, you need to promote the connection to a domain-level connection. [Learn more about enabling third-party applications](https://auth0.com/docs/get-started/applications/confidential-and-public-applications/enable-third-party-applications).
     <Steps>
-      <Step title="List your connection">
+      <Step title="List Your Connection">
         List your connections to get their IDs
         ```shell
         auth0 api get connections
         ```
       </Step>
-      <Step title="Choose your connections">
+      <Step title="Choose Your Connections">
         From the list, identify which connections you want to use for the MCP server and copy the ID.
-          * For the username and password database, look for the connection with the strategy `auth0`.
+          * For the username-and-password database, look for the connection with the strategy `auth0`.
           * For the Google social connection, look for the connection with the strategy `google-oauth2`.
       </Step>
-      <Step title="Upgrade the connection to a domain-level connection">
+      <Step title="Upgrade the Connection to Domain-Level">
         For each of those specific connection IDs, run the following command to mark it as a domain-level connection. Replace `YOUR_CONNECTION_ID` with the actual ID (e.g., `con_XXXXXXXXXXXXXXXX`).
 
         ```shell wrap lines

auth4genai/snippets/mcp/get-started/testing-instructions.mdx

@@ -3,7 +3,7 @@
 Now that your MCP server is up and running, you can test it by using tools like [MCP Inspector](https://modelcontextprotocol.io/docs/tools/inspector).
 
 <Card
-  title="Learn how to test your Auth0 powered MCP server"
+  title="Learn how to test your Auth0-powered MCP server"
   href="/mcp/guides/test-your-mcp-server-with-mcp-inspector"
   icon="book"
   iconType="solid"