Script updating gh-pages from 9be1813. [ci skip]

ianswett-onpacketreceived/draft-ietf-quic-recovery.html

@@ -2621,10 +2621,10 @@ <h2 id="name-on-sending-a-packet">
         <h2 id="name-on-receiving-a-datagram">
 <a href="#section-a.6" class="section-number selfRef">A.6. </a><a href="#name-on-receiving-a-datagram" class="section-name selfRef">On Receiving a Datagram</a>
         </h2>
-<p id="section-a.6-1">Receiving a datagram might allow the server to send additional data if the
-server was previously blocked by the anti-amplification limits; see
-<a href="#before-address-validation" class="xref">Section 5.2.2.1</a>. This is necessary even if none of the packets in
-the datagram are successfully processed.<a href="#section-a.6-1" class="pilcrow">¶</a></p>
+<p id="section-a.6-1">Receiving a datagram might allow the server to send if the
+server was previously blocked by the anti-amplification limits.
+This is necessary even if none of the packets in the datagram
+are successfully processed.<a href="#section-a.6-1" class="pilcrow">¶</a></p>
 <p id="section-a.6-2">Pseudocode for OnDatagramReceived follows:<a href="#section-a.6-2" class="pilcrow">¶</a></p>
 <div class="artwork art-text alignLeft" id="section-a.6-3">
 <pre>

ianswett-onpacketreceived/draft-ietf-quic-recovery.txt

@@ -1643,10 +1643,10 @@ Internet-Draft             QUIC Loss Detection                  May 2020
 
 A.6.  On Receiving a Datagram
 
-   Receiving a datagram might allow the server to send additional data
-   if the server was previously blocked by the anti-amplification
-   limits; see Section 5.2.2.1.  This is necessary even if none of the
-   packets in the datagram are successfully processed.
+   Receiving a datagram might allow the server to send if the server was
+   previously blocked by the anti-amplification limits.  This is
+   necessary even if none of the packets in the datagram are
+   successfully processed.
 
    Pseudocode for OnDatagramReceived follows: