Apply suggestions from code review

italia · Oct 4, 2024 · a8525bd · a8525bd
1 parent d5deb94
commit a8525bd
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/en/remote-flow.rst b/docs/en/remote-flow.rst
@@ -504,9 +504,9 @@ Revocation Checks
 
 The revocation mechanisms that the Relying Parties MUST implement are defined in the section (:ref:`Revocations <revocation-lists.rst>`).
 
-In the context of Digital Credential evaluation, any Relying Parties (RPs) establishes internal policies that define the meaning and value of presented credentials. This is particularly important in scenarios where a Credential may be suspended but still holds value for certain purposes. For example, a suspended mobile driving license might still be valid for verifying the age of the holder.
+In the context of Digital Credential evaluation, any Relying Parties (RPs) establishes internal policies that define the meaning and value of presented Credentials. This is particularly important in scenarios where a Credential may be suspended but still holds value for certain purposes. For example, a suspended mobile driving license might still be valid for verifying the age of the holder.
 
-The process begins with the RP requesting specific Credentials from the holder. This request should align with the RP's requirements and the context in which the Credentials will be used. The Holder then responds by releasing the requested Credentials.
+The process begins with the RP requesting specific Credentials from the Holder. This request should align with the Relying Party's requirements and the context in which the Credentials will be used. The Holder then responds by releasing the requested Credentials.
 
 Upon receiving the Credentials, the Relying Party evaluates their validity and value based on its internal policies. This evaluation considers the current status of the Credential (e.g., active, suspended, revoked) and the specific use case for which the Credential is being presented.