Deploy to GitHub pages

seqs.html

@@ -1224,7 +1224,7 @@
 <dd class="workgroup">OpenID Connect A/B</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2024-09-20" class="published">20 September 2024</time>
+<time datetime="2024-09-30" class="published">30 September 2024</time>
     </dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
@@ -1712,7 +1712,7 @@ <h2 id="name-wallet-architecture-entity-">
           </tr>
         </tbody>
       </table>
-<p id="section-7-3"><strong>Table 1</strong>: Federation Trust Chain and Wallet Attestation are separate things, where the Wallet Attestation is linked to its Issuer attested within the Trust Chain.<a href="#section-7-3" class="pilcrow">¶</a></p>
+<p id="section-7-3"><strong>Table 1</strong>: Map of the Federation Entity Types and corresponding metadata types for the Wallet architectures.<a href="#section-7-3" class="pilcrow">¶</a></p>
 <p id="section-7-4">The Credential Issuer is an OAuth 2.0 Protected Resource Server and it MAY also implement, within the same Entity, an OAuth 2.0 Authorization Server. According to <span>[<a href="#OpenID4VCI" class="cite xref">OpenID4VCI</a>]</span>, the Authorization Server can be external to the Entity that implements the Credential Endpoint, therefore the use of <code>oauth_authorization_server</code> is OPTIONAL.<a href="#section-7-4" class="pilcrow">¶</a></p>
 <div id="openid-wallet-provider-entity-type">
 <section id="section-7.1">