Script updating gh-pages from e3b59da. [ci skip]

draft-vesco-vcauthtls.html

@@ -1398,7 +1398,7 @@ <h3 id="name-mutual-authentication-with-">
 <a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-mutual-authentication-with-" class="section-name selfRef">Mutual authentication with Verifiable Credentials</a>
         </h3>
 <p id="section-6.2-1">This example shows a TLS 1.3 handshake with mutual authenitcation. Both client and server select their  Verifiable Credential for authentication.
-The client sends the did_methods extension along with the server_certificate_type extension set to VC as the first option. The server sends the server_certificate_type set to VC, the client_cert_type set to VC and the CertificateRequest message together with the did_methods extension with a set of DID Methods both endpoints have in common. Both client and server send their Verifiable Credential into their respective Certificate message.<a href="#section-6.2-1" class="pilcrow">¶</a></p>
+The client sends the did_methods extension along with the server_certificate_type extension set to VC as the first option. The server sends the server_certificate_type set to VC, the client_cert_type set to VC and the CertificateRequest message together with the did_methods extension with a set of DID Methods both endpoints have in common. Both client and server send their Verifiable Credential into their respective Certificate messages.<a href="#section-6.2-1" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="mutual-authentication-with-client-using-verifiable-credential-and-server-using-x509-certificate">
@@ -1409,7 +1409,7 @@ <h3 id="name-mutual-authentication-with-c">
 <p id="section-6.3-1">This example shows a TLS 1.3 handshake with mutual authentication that combines the use of Verifiable Credential and X.509 certificate. The client uses a Verifiable Credential, and the server uses an X.509 certificate.
 The client expresses its willingness to process an X.509 certificate from the server. In addition, it expresses the capability to be authenticated with a Verifiable Credential or an X.509 certificate.
 The server selects X.509 certificate to authenticate with the client and Verifiable Credential for client authentication. Then, the server sends the CertificateRequest message together with the did_methods extension with a set of DID Methods of its choice.
-The server sends its X.509 certificate and the client its Verifiable Credential into their respective Certificate message.<a href="#section-6.3-1" class="pilcrow">¶</a></p>
+The server sends its X.509 certificate and the client its Verifiable Credential into their respective Certificate messages.<a href="#section-6.3-1" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="mutual-authentication-with-client-using-x509-certificate-and-server-using-verifiable-credential">

draft-vesco-vcauthtls.txt

@@ -357,7 +357,7 @@ Table of Contents
    client_cert_type set to VC and the CertificateRequest message
    together with the did_methods extension with a set of DID Methods
    both endpoints have in common.  Both client and server send their
-   Verifiable Credential into their respective Certificate message.
+   Verifiable Credential into their respective Certificate messages.
 
 6.3.  Mutual authentication with Client using Verifiable Credential and
       Server using X.509 Certificate
@@ -374,7 +374,7 @@ Table of Contents
    message together with the did_methods extension with a set of DID
    Methods of its choice.  The server sends its X.509 certificate and
    the client its Verifiable Credential into their respective
-   Certificate message.
+   Certificate messages.
 
 6.4.  Mutual authentication with Client using X.509 Certificate and
       Server using Verifiable Credential