Apply suggestions from code review

docs/en/trust.rst

@@ -403,10 +403,10 @@ giving the references of the metadata protocol for each of these.
 
 
 .. note::
-    In instances where a Credential Issuer also functions as an Authorization Server, 
-    it is imperative for the Entity to incorporate both 
+    In instances where a PID/EAA Provider implements both the Credential Issuer and the Authorization Server, 
+    it MUST incorporate both 
     ``oauth_authorization_server`` and ``openid_credential_issuer`` within its metadata types.
-    Other implementations may divide the Credential Issuer from the Authorization Server.
+    Other implementations may divide the Credential Issuer from the Authorization Server, when this happens the Credential Issuer metadata MUST contain the `authorization_servers` parameters, including the Authorization Server unique identifier.
     Furthermore, should there be a necessity for User Authentication by the Credential Issuer,
     it is mandatory to include the relevant metadata type, either ``openid_relying_party`` 
     or ``wallet_relying_party``.