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

cfrg · Sep 26, 2024 · b02c29d · b02c29d
1 parent 35f4bf4
commit b02c29d
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/draft-irtf-cfrg-cpace.html b/draft-irtf-cfrg-cpace.html
@@ -1730,10 +1730,10 @@ <h3 id="name-optional-cpace-inputs">
 </li>
           <li class="normal" id="section-3.1-2.3">
             <p id="section-3.1-2.3.1">Associated data fields (ADa and ADb).
-These fields can be used to authenticate associated data alongside the CPace protocol.
+These fields can be used for authenticating associated data alongside the CPace protocol.
 The ADa and ADb will be sent in clear text as part of the protocol messages.
 ADa and ADb will become authenticated in a CPace protocol run as
-both parties will only agree on a common key if they have the same view on ADa and ADb.<a href="#section-3.1-2.3.1" class="pilcrow">¶</a></p>
+both parties will only agree on a common key if they have had the same view on ADa and ADb.<a href="#section-3.1-2.3.1" class="pilcrow">¶</a></p>
 <p id="section-3.1-2.3.2">
 If an application cannot integrate the party identities as part of CI, party identities (A,B) SHOULD be included in ADa and ADb instead
 (see <a href="#sec-considerations-ids" class="auto internal xref">Section 9.1</a>).<a href="#section-3.1-2.3.2" class="pilcrow">¶</a></p>

diff --git a/draft-irtf-cfrg-cpace.txt b/draft-irtf-cfrg-cpace.txt
@@ -355,12 +355,12 @@ Table of Contents
       information.  Both parties will only establish a common session
       key if they initiated the protocol with the same view of CI.
 
-   *  Associated data fields (ADa and ADb).  These fields can be used to
-      authenticate associated data alongside the CPace protocol.  The
-      ADa and ADb will be sent in clear text as part of the protocol
+   *  Associated data fields (ADa and ADb).  These fields can be used
+      for authenticating associated data alongside the CPace protocol.
+      The ADa and ADb will be sent in clear text as part of the protocol
       messages.  ADa and ADb will become authenticated in a CPace
       protocol run as both parties will only agree on a common key if
-      they have the same view on ADa and ADb.
+      they have had the same view on ADa and ADb.
 
       If an application cannot integrate the party identities as part of
       CI, party identities (A,B) SHOULD be included in ADa and ADb