Script updating gh-pages from 6e4aa69. [ci skip]

lamps-wg · Oct 7, 2024 · 74af059 · 74af059
1 parent 0168fbd
commit 74af059
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/editorial-changes-to-rfc4210bis/draft-ietf-lamps-rfc6712bis.html b/editorial-changes-to-rfc4210bis/draft-ietf-lamps-rfc6712bis.html
@@ -1243,7 +1243,7 @@ <h2 id="name-introduction">
 <p id="section-1-6">The Certificate Management Protocol (CMP) <span>[<a href="#I-D.ietf-lamps-rfc4210bis" class="cite xref">I-D.ietf-lamps-rfc4210bis</a>]</span> requires a well-defined
 transfer mechanism to enable End Entities (EEs), Registration
 Authorities (RAs), and Certification Authorities (CAs) to pass
-PKIMessage sequences between them.<a href="#section-1-6" class="pilcrow">¶</a></p>
+PKIMessage structures between them.<a href="#section-1-6" class="pilcrow">¶</a></p>
 <p id="section-1-7">The first version of the CMP specification <span>[<a href="#RFC2510" class="cite xref">RFC2510</a>]</span> included a brief
 description of a simple transfer protocol layer on top of TCP.  Its
 features were simple transfer-level error handling and a mechanism to
@@ -1472,7 +1472,7 @@ <h3 id="name-pushing-of-announcements">
 repositories storing the announced information, such as directory
 services.  Those services listen for incoming messages, utilizing the
 same HTTP Request-URI scheme as defined in <a href="#sect-3.6" class="auto internal xref">Section 3.6</a>.<a href="#section-3.7-4" class="pilcrow">¶</a></p>
-<p id="section-3.7-5">The following CMP message types are announcements that may be pushed by a
+<p id="section-3.7-5">The following types of PKIMessage are announcements that may be pushed by a
 CA.  The prefixed numbers reflect ASN.1 numbering of the respective
 element.<a href="#section-3.7-5" class="pilcrow">¶</a></p>
 <div class="alignLeft art-text artwork" id="section-3.7-6">

diff --git a/editorial-changes-to-rfc4210bis/draft-ietf-lamps-rfc6712bis.txt b/editorial-changes-to-rfc4210bis/draft-ietf-lamps-rfc6712bis.txt
@@ -113,7 +113,7 @@ Table of Contents
    The Certificate Management Protocol (CMP) [I-D.ietf-lamps-rfc4210bis]
    requires a well-defined transfer mechanism to enable End Entities
    (EEs), Registration Authorities (RAs), and Certification Authorities
-   (CAs) to pass PKIMessage sequences between them.
+   (CAs) to pass PKIMessage structures between them.
 
    The first version of the CMP specification [RFC2510] included a brief
    description of a simple transfer protocol layer on top of TCP.  Its
@@ -304,8 +304,8 @@ Table of Contents
    services.  Those services listen for incoming messages, utilizing the
    same HTTP Request-URI scheme as defined in Section 3.6.
 
-   The following CMP message types are announcements that may be pushed
-   by a CA.  The prefixed numbers reflect ASN.1 numbering of the
+   The following types of PKIMessage are announcements that may be
+   pushed by a CA.  The prefixed numbers reflect ASN.1 numbering of the
    respective element.
 
       [15] CA Key Update Announcement