Update docs/specification/draft/basic/authorization.mdx

Co-authored-by: Tyler James Leonhardt <[email protected]>

Author: localden

docs/specification/draft/basic/authorization.mdx

@@ -128,7 +128,6 @@ If the `scope` parameter is absent, clients **SHOULD** apply the fallback behavi
 
 #### Authorization Server Metadata Discovery
 
-
 To handle different issuer URL formats and ensure interoperability with both OAuth 2.0 Authorization Server Metadata and OpenID Connect Discovery 1.0 specifications, MCP clients **MUST** attempt multiple well-known endpoints when discovering authorization server metadata.
 
 The discovery approach is based on [RFC8414 Section 3.1 "Authorization Server Metadata Request"](https://datatracker.ietf.org/doc/html/rfc8414#section-3.1) for OAuth 2.0 Authorization Server Metadata discovery and [RFC8414 Section 5 "Compatibility Notes"](https://datatracker.ietf.org/doc/html/rfc8414#section-5) for OpenID Connect Discovery 1.0 interoperability.