Fix typos (modelcontextprotocol#724)

Closes modelcontextprotocol#380
Closes modelcontextprotocol#448
Closes modelcontextprotocol#471
Closes modelcontextprotocol#492

Co-authored-by: Rahul Lashkari <[email protected]>
Co-authored-by: Dimitris Tsapakidis <[email protected]>
Co-authored-by: Jayde Mitchell <[email protected]>
Co-authored-by: Jose Sebastian <[email protected]>
Co-authored-by: "Yaroslav O. Halchenko" <[email protected]>
Co-authored-by: Den Delimarsky 🌺 <[email protected]>

Author: 7 people

docs/clients.mdx

@@ -590,7 +590,7 @@ Programmatically assemble prompts for LLMs using [GenAIScript](https://microsoft
 - Full support of all major MCP features (tools, prompts, resources, and subscriptions)
 - Fast, seamless UI for debugging MCP capabilities
 - MCP config integration (Claude, VSCode, etc.) for fast first-time experience in testing MCPs
-- Integration with history, varibles, and collections for re-use and collaboration
+- Integration with history, variables, and collections for reuse and collaboration
 
 ### Slack MCP Client
 
@@ -735,7 +735,7 @@ Theia AI and Theia IDE's MCP integration provide users with flexibility, making
 
 ### Witsy
 
-[Witsy](https://github.com/nbonamy/witsy) is an AI desktop assistant, supoorting Anthropic models and MCP servers as LLM tools.
+[Witsy](https://github.com/nbonamy/witsy) is an AI desktop assistant, supporting Anthropic models and MCP servers as LLM tools.
 
 **Key features:**
 

docs/quickstart/client.mdx

@@ -3,7 +3,7 @@ title: "For Client Developers"
 description: "Get started building your own client that can integrate with all MCP servers."
 ---
 
-In this tutorial, you'll learn how to build a LLM-powered chatbot client that connects to MCP servers. It helps to have gone through the [Server quickstart](/quickstart/server) that guides you through the basic of building your first server.
+In this tutorial, you'll learn how to build an LLM-powered chatbot client that connects to MCP servers. It helps to have gone through the [Server quickstart](/quickstart/server) that guides you through the basics of building your first server.
 
 <Tabs>
 <Tab title="Python">

docs/quickstart/server.mdx

@@ -1085,7 +1085,7 @@ Create a new boot starter application using the `spring-ai-starter-mcp-client` d
 ```
 
 and set the `spring.ai.mcp.client.stdio.servers-configuration` property to point to your `claude_desktop_config.json`.
-You can re-use the existing Anthropic Desktop configuration:
+You can reuse the existing Anthropic Desktop configuration:
 
 ```properties
 spring.ai.mcp.client.stdio.servers-configuration=file:PATH/TO/claude_desktop_config.json
@@ -1573,7 +1573,7 @@ await app.RunAsync();
 
 <Note>
 
-When creating the `ApplicationHostBuilder`, ensure you use `CreateEmptyApplicationBuilder` instead of `CreateDefaultBuilder`. This ensures that the server does not write any additional messages to the console. This is only neccessary for servers using STDIO transport.
+When creating the `ApplicationHostBuilder`, ensure you use `CreateEmptyApplicationBuilder` instead of `CreateDefaultBuilder`. This ensures that the server does not write any additional messages to the console. This is only necessary for servers using STDIO transport.
 
 </Note>
 

docs/sdk/java/mcp-server.mdx

@@ -508,7 +508,7 @@ var mcpServer = McpServer.async(mcpServerTransportProvider)
 </Tabs>
 
 The `McpSchema.CompletionReference` definition defines the type (`PromptRefernce` or `ResourceRefernce`) and the identifier for the completion specification (e.g handler).
-The handler function processes requests and returns the complition response.
+The handler function processes requests and returns the completion response.
 The first argument is `McpAsyncServerExchange` for client interaction, and the second argument is a `CompleteRequest` instance.
 
 Check the [using completion](/sdk/java/mcp-client#using-completion) to learn how to use the completion capabilities on the client side.

docs/specification/draft/basic/authorization.mdx

@@ -286,7 +286,7 @@ MCP clients **MUST** have redirect URIs registered with the authorization server
 Authorization servers **MUST** validate exact redirect URIs against pre-registered values to prevent redirection attacks.
 
 MCP clients **SHOULD** use and verify state parameters in the authorization code flow
-and discard any results that do not include or have a mis-match with the original state.
+and discard any results that do not include or have a mismatch with the original state.
 
 Authorization servers **MUST** take precautions to prevent redirecting user agents to untrusted URI's, following suggestions laid out in [OAuth 2.1 Section 7.12.2](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-v2-1-12#section-7.12.2)