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

lamps-wg · Nov 8, 2024 · 3482c01 · 3482c01
1 parent 39d25fa
commit 3482c01
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/draft-ietf-lamps-rfc6712bis.html b/draft-ietf-lamps-rfc6712bis.html
@@ -1439,7 +1439,7 @@ <h3 id="name-general-form">
 implications.  As described in <a href="#sect-5" class="auto internal xref">Section 5</a>, 301 (Moved Permanently) status code
 could be misused for permanent denial of service.<a href="#section-3.3-2" class="pilcrow">¶</a></p>
 <p id="section-3.3-3">All applicable Client Error 4xx or Server Error 5xx status codes
-<span class="bcp14">MAY</span> be used to inform the client about errors. Note that whenever
+<span class="bcp14">MAY</span> be used to inform the client about errors. Whenever
 a client receives an HTTP response with a status code in the 2xx,
 4xx, or 5xx ranges, it <span class="bcp14">MUST</span> support handling response message
 content containing a CMP response PKIMessage.<a href="#section-3.3-3" class="pilcrow">¶</a></p>

diff --git a/draft-ietf-lamps-rfc6712bis.txt b/draft-ietf-lamps-rfc6712bis.txt
@@ -243,10 +243,10 @@ Table of Contents
    status code could be misused for permanent denial of service.
 
    All applicable Client Error 4xx or Server Error 5xx status codes MAY
-   be used to inform the client about errors.  Note that whenever a
-   client receives an HTTP response with a status code in the 2xx, 4xx,
-   or 5xx ranges, it MUST support handling response message content
-   containing a CMP response PKIMessage.
+   be used to inform the client about errors.  Whenever a client
+   receives an HTTP response with a status code in the 2xx, 4xx, or 5xx
+   ranges, it MUST support handling response message content containing
+   a CMP response PKIMessage.
 
 3.4.  Header Fields