clarified typo fix

Signed-off-by: Maia Iyer <[email protected]>

Author: maia-iyer

docs/specification/draft/basic/authorization.mdx

@@ -148,8 +148,8 @@ Any MCP authorization servers that _do not_ support Dynamic Client Registration
 alternative ways to obtain a client ID (and, if applicable, client credentials). For one of
 these authorization servers, MCP clients will have to either:
 
-1. Hardcode a client ID (and, if applicable, client credentials) specifically for that authorization
-   server, or
+1. Hardcode a client ID (and, if applicable, client credentials) specifically for the MCP client to use when
+   interacting with that authorization server, or
 2. Present a UI to users that allows them to enter these details, after registering an
    OAuth client themselves (e.g., through a configuration interface hosted by the
    server).