Deployed 3c521bd to 1.4.0 with MkDocs 1.6.1 and mike 2.1.3

1.4.0/404.html

@@ -12,7 +12,7 @@
 
 
       <link rel="icon" href="/assets/images/favicon.png">
-      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.46">
+      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.48">
 
 
 

1.4.0/annexes/annex-1/annex-1-definitions/index.html

@@ -12,7 +12,7 @@
 
 
       <link rel="icon" href="../../../assets/images/favicon.png">
-      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.46">
+      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.48">
 
 
 

1.4.0/annexes/annex-2/annex-2-high-level-requirements/index.html

@@ -12,7 +12,7 @@
 
 
       <link rel="icon" href="../../../assets/images/favicon.png">
-      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.46">
+      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.48">
 
 
 

1.4.0/annexes/annex-3/annex-3.01-pid-rulebook/index.html

@@ -12,7 +12,7 @@
 
 
       <link rel="icon" href="../../../assets/images/favicon.png">
-      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.46">
+      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.48">
 
 
 

1.4.0/annexes/annex-3/annex-3.02-mDL-rulebook/index.html

@@ -12,7 +12,7 @@
 
 
       <link rel="icon" href="../../../assets/images/favicon.png">
-      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.46">
+      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.48">
 
 
 

1.4.0/arf/index.html

@@ -14,7 +14,7 @@
 
 
       <link rel="icon" href="../assets/images/favicon.png">
-      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.46">
+      <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.48">
 
 
 
@@ -4443,7 +4443,7 @@ <h4 id="622-wallet-provider-registration-and-notification">6.2.2 Wallet Provider
 <p>The Wallet Solution provided by the Wallet Provider is certified by a
 Notified Body. The certification process is described in <a href="#7-security-and-data-protection">chapter 7</a>.</p>
 <p>If the registration and notification processes are successful, the trust
-anchors of the Wallet Provider are included in a Wallet Providers Trusted
+anchors of the Wallet Provider are included in a Wallet Provider Trusted
 List. During issuance of a PID or an attestation, the PID Provider or
 the Attestation Provider can use these trust anchors to verify the
 authenticity of a Wallet Trust Evidence signed by the Wallet Provider,
@@ -4458,7 +4458,7 @@ <h4 id="622-wallet-provider-registration-and-notification">6.2.2 Wallet Provider
 <h4 id="623-wallet-provider-suspension-or-withdrawal">6.2.3 Wallet Provider suspension or withdrawal</h4>
 <p>Under specific conditions, a Registrar may decide to suspend or withdraw
 a Wallet Provider. This means the Wallet Provider is taken off from the
-Wallet Providers Trusted List. The conditions for this will be specified
+Wallet Provider Trusted List. The conditions for this will be specified
 by each Registrar. As a result of de-registration, PID Providers,
 Attestation Providers and Relying Parties will no longer trust the trust
 anchors of the Wallet Provider and will therefore refuse to interact
@@ -5023,13 +5023,13 @@ <h5 id="6622-wallet-instance-authenticates-the-pid-provider-or-attestation-provi
 <h5 id="6623-pid-provider-or-attestation-provider-validates-the-eudi-wallet-instance">6.6.2.3 PID Provider or Attestation Provider validates the EUDI Wallet Instance</h5>
 <p><strong>Verifies the authenticity of the Wallet Instance</strong></p>
 <p>As shown in figure 6, a PID Provider or an Attestation Provider
-downloads the Wallet Providers Trusted List(s) it needs from the relevant
+downloads the Wallet Provider Trusted List(s) it needs from the relevant
 Registrar(s), possibly after having located them via the Commission
 common trust infrastructure.</p>
 <p>Note:</p>
 <ul>
 <li>It is not mandatory for PID Providers or Attestation Providers to
-    possess all Wallet Providers Trusted Lists, if there are multiple.
+    possess all Wallet Provider Trusted Lists, if there are multiple.
     This is because it is not mandatory for a PID Provider or an
     Attestation Provider to accept all certified Wallet Solutions in the
     EUDI Wallet ecosystem. Each PID Provider or Attestation Provider
@@ -5500,7 +5500,7 @@ <h5 id="66310-relying-party-authenticates-the-wallet-instance-and-the-wallet-pro
 </li>
 <li>
 <p>verifies the signature over the WIA using the Wallet Provider trust
-    anchor obtained from the Wallet Providers Trusted List.</p>
+    anchor obtained from the Wallet Provider Trusted List.</p>
 </li>
 <li>
 <p>verifies that the Wallet Instance is in possession of the private