[Docs] Fix typos

Author: koic

blog/content/posts/client_registration/index.md

@@ -58,9 +58,9 @@ For example, a malicious client could claim to be `Claude Desktop` on the consen
 
 ## Improving Client Registration in MCP
 
-For MCP users, a common pattern is to connect to an MCP server by using its URL directly in a MCP client.
+For MCP users, a common pattern is to connect to an MCP server by using its URL directly in an MCP client.
 
-This goes against the typical OAuth authorization pattern because the user is selecting the resource server to connect to rather than the client developer. This problem is compounded by the fact that there is an unbounded number of authorization servers that a MCP server may use, meaning that clients need to be able to complete the authorization flow regardless of the provider used.
+This goes against the typical OAuth authorization pattern because the user is selecting the resource server to connect to rather than the client developer. This problem is compounded by the fact that there is an unbounded number of authorization servers that an MCP server may use, meaning that clients need to be able to complete the authorization flow regardless of the provider used.
 
 Some client developers have implemented pre-registration with a select few authorization servers. In this scenario, the client doesn't need to rely on DCR when it detects an authorization server it knows. However, this is a solution that doesn't scale given the breadth of the MCP ecosystem - it's impossible to have every client be registered with every authorization server there is.
 To mitigate this challenge, we set out to outline some of the goals that we wanted to achieve with improving the client registration experience:

docs/clients.mdx

@@ -964,7 +964,7 @@ MooPoint is a web-based AI chat platform built for developers and advanced users
 
 ### Needle
 
-[Needle](https://needle.app) is a RAG worflow platform that also works as an MCP client, letting you connect and use MCP servers in seconds.
+[Needle](https://needle.app) is a RAG workflow platform that also works as an MCP client, letting you connect and use MCP servers in seconds.
 
 **Key features:**
 

docs/community/sep-guidelines.mdx

@@ -44,7 +44,7 @@ Each SEP must have an **SEP author** -- someone who writes the SEP using the sty
 
 SEPs should be submitted as a GitHub Issue in the [specification repository](https://github.com/modelcontextprotocol/modelcontextprotocol). The standard SEP workflow is:
 
-1. You, the SEP author, create a [well-formatted](#sep-format) GitHub Issue with the `SEP` and `proposal` tags. The SEP number is the same as the GitHub Issue number, the two can be used interchangably.
+1. You, the SEP author, create a [well-formatted](#sep-format) GitHub Issue with the `SEP` and `proposal` tags. The SEP number is the same as the GitHub Issue number, the two can be used interchangeably.
 2. Find a Core Maintainer or Maintainer to sponsor your proposal. Core Maintainers and Maintainers will regularly go over the list of open proposals to determine which proposals to sponsor. You can tag relevant maintainers from [the maintainer list](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md) in your proposal.
 3. Once a sponsor is found, the GitHub Issue is assigned to the sponsor. The sponsor will add the `draft` tag, ensure the SEP number is in the title, and assign a milestone.
 4. The sponsor will informally review the proposal and may request changes based on community feedback. When ready for formal review, the sponsor will add the `in-review` tag.

docs/docs/tutorials/security/authorization.mdx

@@ -97,7 +97,7 @@ If the registration succeeds, the authorization server will return a JSON blob w
 <Tip>
 **No DCR or Pre-Registration**
 
-In case a MCP client connects to a MCP server that doesn't use an authorization server that supports DCR and the client is not pre-registered with said authorization server, it's the responsibility of the client developer to provide an affordance for the end-user to enter client information manually.
+In case an MCP client connects to an MCP server that doesn't use an authorization server that supports DCR and the client is not pre-registered with said authorization server, it's the responsibility of the client developer to provide an affordance for the end-user to enter client information manually.
 
 </Tip>
 

docs/specification/draft/basic/index.mdx

@@ -184,7 +184,7 @@ Consumers of icon metadata **MUST** take appropriate security precautions when h
 - Fetch icons without credentials. Do not send cookies, `Authorization` headers, or client credentials.
 - Verify that icon URIs are from the same origin as the server. This minimizes the risk of exposing data or tracking information to third-parties.
 - Exercise caution when fetching and rendering icons as the payload **MAY** contain executable content (e.g., SVG with [embedded JavaScript](https://www.w3.org/TR/SVG11/script.html) or [extended capabilities](https://www.w3.org/TR/SVG11/extend.html)).
-  - Consumers **MAY** choose to disallow specific file types or otherwize sanitize icon files before rendering.
+  - Consumers **MAY** choose to disallow specific file types or otherwise sanitize icon files before rendering.
 - Validate MIME types and file contents before rendering. Treat the MIME type information as advisory. Detect content type via magic bytes; reject on mismatch or unknown types.
   - Maintain a strict allowlist of image types.
 

docs/specification/draft/basic/security_best_practices.mdx

@@ -363,7 +363,7 @@ Local MCP servers with inadequate restrictions or from untrusted sources introdu
 
 #### Mitigation
 
-If a MCP client supports one-click local MCP server configuration, it **MUST** implement proper consent mechanisms prior to executing commands.
+If an MCP client supports one-click local MCP server configuration, it **MUST** implement proper consent mechanisms prior to executing commands.
 
 **Pre-Configuration Consent**