Merge pull request modelcontextprotocol#529 from deanyxu/spec/authorization-typo

Fix typo in draft authorization specification

Author: localden

docs/specification/draft/basic/authorization.mdx

@@ -53,15 +53,15 @@ while maintaining simplicity:
    MCP clients **MUST** use the OAuth 2.0 Authorization Server Metadata.
 
 ### 2.2 Roles
-A protected MCP server acts as a [OAuth 2.1 resource server](https://www.ietf.org/archive/id/draft-ietf-oauth-v2-1-12.html#name-roles),
+A protected MCP server acts as an [OAuth 2.1 resource server](https://www.ietf.org/archive/id/draft-ietf-oauth-v2-1-12.html#name-roles),
 capable of accepting and responding to protected resource requests using access tokens.
 
 An MCP client acts as an [OAuth 2.1 client](https://www.ietf.org/archive/id/draft-ietf-oauth-v2-1-12.html#name-roles),
 making protected resource requests on behalf of a resource owner.
 
 The authorization server is responsible for interacting with the user (if necessary) and issuing access tokens for use at the MCP server.
 The implementation details of the authorization server are beyond the scope of this specification. It may be hosted with the
-resource server or a separate entity. Section [2.3 Authorization Server Discovery](#2-3-authorizaton-server-discovery)
+resource server or a separate entity. Section [2.3 Authorization Server Discovery](#2-3-authorization-server-discovery)
 specifies how an MCP server indicates the location of its corresponding authorization server to a client.
 
 ### 2.3 Authorization Server Discovery