Hyperlint Automation Fix

Author: hyperlint-ai[bot]

src/content/docs/agents/model-context-protocol/authorization.mdx

@@ -130,10 +130,10 @@ You can use the auth provider to:
 - Allow users to authenticate to your MCP server through email, social logins, SSO (single sign-on), and MFA (multi-factor authentication).
 - Define scopes and permissions that directly map to your MCP tools.
 - Present users with a consent page corresponding with the requested permissions.
-- Enforce the permissions so that agents can only invoke permitted tools.  
+- Enforce the permissions so that agents can only invoke permitted tools.
 
 #### Stytch
-Get started with a [remote MCP server that uses Stytch](https://stytch.com/docs/guides/connected-apps/mcp-servers) to allow users to sign in with email, Google login or enterprise SSO and authorize their AI agent to view and manage their company’s OKRs on their behalf. Stytch will handle restricting the scopes granted to the AI agent based on the user’s role and permissions within their organization. When authorizing the MCP Client, each user will see a consent page that outlines the permissions that the agent is requesting that they are able to grant based on their role.
+Get started with a [remote MCP server that uses Stytch](https://stytch.com/docs/guides/connected-apps/mcp-servers) to allow users to sign in with email, Google login or enterprise SSO and authorize their AI agent to view and manage their companys OKRs on their behalf. Stytch will handle restricting the scopes granted to the AI agent based on the users role and permissions within their organization. When authorizing the MCP Client, each user will see a consent page that outlines the permissions that the agent is requesting that they are able to grant based on their role.
 
 [![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/ai/tree/main/demos/mcp-stytch-b2b-okr-manager)
 
@@ -144,7 +144,7 @@ For more consumer use cases, deploy a remote MCP server for a To Do app that use
 #### Auth0
 Get started with a remote MCP server that uses Auth0 to authenticate users through email, social logins, or enterprise SSO to interact with their todos and personal data through AI agents. The MCP server securely connects to API endpoints on behalf of users, showing exactly which resources the agent will be able to access once it gets consent from the user. In this implementation, access tokens are automatically refreshed during long running interactions.
 
-To set it up, first deploy the protected API endpoint: 
+To set it up, first deploy the protected API endpoint:
 
 [![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-auth0/todos-api)
 
@@ -190,7 +190,7 @@ function requirePermission(permission, handler) {
   return async (request, context) => {
     // Check if user has the required permission
     const userPermissions = context.props.permissions || [];
-    
+    const userPermissions = context.props.permissions || [];
     if (!userPermissions.includes(permission)) {
       return {
         content: [{ type: "text", text: `Permission denied: requires ${permission}` }],