Deploy to GitHub pages

italia · Dec 12, 2023 · 53a0be3 · 53a0be3
1 parent a4e0932
commit 53a0be3
Show file tree

Hide file tree

Showing 5 changed files with 3 additions and 3 deletions.
diff --git a/credential-revocation/en/.doctrees/environment.pickle b/credential-revocation/en/.doctrees/environment.pickle
diff --git a/credential-revocation/en/.doctrees/revocation-lists.doctree b/credential-revocation/en/.doctrees/revocation-lists.doctree
diff --git a/credential-revocation/en/_sources/revocation-lists.rst.txt b/credential-revocation/en/_sources/revocation-lists.rst.txt
@@ -335,7 +335,7 @@ The Non-Revocation Attestation MUST contain the expiration datetime after which
 The Non-Revocation Attestation enables offline use cases as it MUST be statically validated using the cryptographic signature of the Issuer. 
 Relying Parties MUST reject an expired Non-Revocation Attestation and, in the case of valid Attestations, they MAY still reject them according to their own policies (e.g., if the issue date doesn't meet their security requirements). 
 
-The following diagram shows how the Wallet Instance MUST request a Non-Revocation Attestation to the Issuer.
+The following diagram shows how the Wallet Instance requests a Non-Revocation Attestation to the Issuer.
 
 .. _fig_Low-Level-Flow-Revocation-Attestation:
 .. figure:: ../../images/Low-Level-Flow-Revocation-Attestation.svg
@@ -357,7 +357,7 @@ The following diagram shows how the Wallet Instance MUST request a Non-Revocatio
     &client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-client-attestation
     &client_assertion=$WIA~WIA-PoP
 
-For a non-normative example of Credential Proof of Possession see :ref:`the one provided in the prevoius section <Credential_pop_jwt_ex>`.
+For a non-normative example of Credential Proof of Possession see :ref:`the one provided in the prevoius section <credential_pop_jwt_ex>`.
 
 **Step 2 (PoP verification)**: The Issuer verifies the signature of the PoP JWTs using the public key that was attested in the Wallet Instance Attestation and the Credential, which is the proof that the Wallet Instance owns the private keys associated with the Wallet Instance Attestation and Credential. Therefore the Wallet Instance is entitled to request its Non-Revocation Attestation.
 

diff --git a/credential-revocation/en/revocation-lists.html b/credential-revocation/en/revocation-lists.html
@@ -1359,7 +1359,7 @@ <h3>Credential Revocation HTTP Response<a class="headerlink" href="#credential-r
 The Non-Revocation Attestation MUST contain the expiration datetime after which the digital Credential MUST NOT be considered valid anymore.
 The Non-Revocation Attestation enables offline use cases as it MUST be statically validated using the cryptographic signature of the Issuer.
 Relying Parties MUST reject an expired Non-Revocation Attestation and, in the case of valid Attestations, they MAY still reject them according to their own policies (e.g., if the issue date doesn't meet their security requirements).</p>
-<p>The following diagram shows how the Wallet Instance MUST request a Non-Revocation Attestation to the Issuer.</p>
+<p>The following diagram shows how the Wallet Instance requests a Non-Revocation Attestation to the Issuer.</p>
 <figure class="align-center" id="id5" style="width: 100%">
 <span id="fig-low-level-flow-revocation-attestation"></span><a class="reference external image-reference" href="https://www.plantuml.com/plantuml/svg/PSr1ImCn40NWUtx5K3mek7WNAYsUreDTQd4lmZ9cHmna9p4pSV7YRtTQiANqEE_bork9Oj4wHOTL4zVfdOhB5WKVChB2eiSOIQ5bKMHF2q21EPo_QKKgbKCLd9i3D0yGxg7RlEpWpfnMWK9VbKIlVQ6HM0F68PUKFfPNZyUaIzrJlxi57uC50ugGhIGUz2VJPRpis_Llj-bkdFkVVCKOHbG2gnghtXYGHpXDW6s0ZPo8TNlmdBZPqdVokF_Qt5gLH0_N4PYOZMn9Sc8XE_JpN5ww5V5Of_W7"><img alt="_images/Low-Level-Flow-Revocation-Attestation.svg" src="_images/Low-Level-Flow-Revocation-Attestation.svg" /></a>
 <figcaption>

diff --git a/credential-revocation/it/.doctrees/environment.pickle b/credential-revocation/it/.doctrees/environment.pickle