Update docs/docs/tutorials/security/authorization.mdx

Co-authored-by: Cliff Hall <[email protected]>

Author: localden

docs/docs/tutorials/security/authorization.mdx

@@ -79,9 +79,9 @@ 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. 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.
+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. 
 
-If the authorization server does support DCR, the client will send a request to the `registration_endpoint` with its information:
+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:
 
 ```json
 {