Update authorization.mdx

Author: localden

docs/docs/tutorials/security/authorization.mdx

@@ -79,7 +79,7 @@ and retrieve another set of metadata properties that will allow it to know the e
 <Step title="Client Registration">
 With all the metadata out of the way, the client now needs to make sure that it's registered with the authorization server. This can be done in two ways.
 
-First, the client can be **pre-registered** with a given authorization server, in which case it can have embedded client registration information that it uses to complete the authorization flow. 
+First, the client can be **pre-registered** with a given authorization server, in which case it can have embedded client registration information that it uses to complete the authorization flow.
 
 Alternatively, the client can use **Dynamic Client Registration** (DCR) to dynamically register itself with the authorization server. The latter scenario requires the authorization server to support DCR. If the authorization server does support DCR, the client will send a request to the `registration_endpoint` with its information:
 
@@ -243,7 +243,6 @@ When you open the client details, go to **Credentials** and take note of the **C
 **Handling Secrets**
 
 Never embed client credentials directly in your code. We recommend using environment variables or specialized solutions for secret storage.
-
 </Warning>
 
 With Keycloak configured, every time the authorization flow is triggered, your MCP server will receive a token like this: