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

Author: ID Bot

log-number-security-considerations/draft-ietf-plants-merkle-tree-certs.html

@@ -5288,7 +5288,7 @@ <h4 id="name-limiting-issuance-logs">
 <a href="#section-12.2.2" class="section-number selfRef">12.2.2. </a><a href="#name-limiting-issuance-logs" class="section-name selfRef">Limiting Issuance Logs</a>
           </h4>
 <p id="section-12.2.2-1">While multiple issuance logs help mitigate log failures, as described above, they introduce transparency risks. If a CA violates the requirement to only use one issuance log at a time, it might add an entry in some far future log number. To be accepted in transparency-enforcing relying parties, the log state must still be cosigned. However, monitors may not know which log numbers to monitor.<a href="#section-12.2.2-1" class="pilcrow">¶</a></p>
-<p id="section-12.2.2-2">PKIs with transparency requirements SHOULD mitigate this by only accepting a limited range of log numbers in relying parties, transparency cosigners, or both. This limit MAY be set to a fixed value or a rolling value that is updated whenever the CA switches its current log. Fixed values require committing to a limit of recoverable log failures during the lifetime of a CA.<a href="#section-12.2.2-2" class="pilcrow">¶</a></p>
+<p id="section-12.2.2-2">PKIs with transparency requirements SHOULD mitigate this by only accepting a limited range of log numbers in relying parties, transparency cosigners, or both. This limit MAY be set to a fixed value or a rolling value that is updated whenever the CA switches its current log. Fixed values require committing to a limit of recoverable log failures over the lifetime of a CA.<a href="#section-12.2.2-2" class="pilcrow">¶</a></p>
 <p id="section-12.2.2-3">Log number limits in relying parties can be implemented by revoking all serial numbers above some threshold. (See <a href="#revoked-ranges" class="auto internal xref">Section 7.5</a>.)<a href="#section-12.2.2-3" class="pilcrow">¶</a></p>
 </section>
 </div>

log-number-security-considerations/draft-ietf-plants-merkle-tree-certs.txt

@@ -3077,7 +3077,7 @@ Table of Contents
    transparency cosigners, or both.  This limit MAY be set to a fixed
    value or a rolling value that is updated whenever the CA switches its
    current log.  Fixed values require committing to a limit of
-   recoverable log failures during the lifetime of a CA.
+   recoverable log failures over the lifetime of a CA.
 
    Log number limits in relying parties can be implemented by revoking
    all serial numbers above some threshold.  (See Section 7.5.)