From c9227a2d4c48df03f7a1f5a56eac4f7ff0909f3c Mon Sep 17 00:00:00 2001
From: ID Bot <idbot@example.com>
Date: Wed, 29 Nov 2023 22:51:27 +0000
Subject: [PATCH] Script updating gh-pages from 81d4aa7. [ci skip]

---
 draft-ietf-quic-ack-frequency.html | 6 ++----
 draft-ietf-quic-ack-frequency.txt  | 7 +++----
 2 files changed, 5 insertions(+), 8 deletions(-)

diff --git a/draft-ietf-quic-ack-frequency.html b/draft-ietf-quic-ack-frequency.html
index c6037e8a..2e9bb040 100644
--- a/draft-ietf-quic-ack-frequency.html
+++ b/draft-ietf-quic-ack-frequency.html
@@ -1342,10 +1342,8 @@ <h2 id="name-negotiating-extension-use">
 receiving ACK_FREQUENCY frames.  If an endpoint sends the transport parameter,
 the peer is allowed to send ACK_FREQUENCY frames independent of whether it also
 sends the min_ack_delay transport parameter or not.<a href="#section-3-4" class="pilcrow">¶</a></p>
-<p id="section-3-5">Receiving a min_ack_delay transport parameter indicates that the peer might send
-ACK_FREQUENCY frames in the future. Until an ACK_FREQUENCY frame is received,
-receiving this transport parameter does not cause the endpoint to
-change its acknowledgement behavior.<a href="#section-3-5" class="pilcrow">¶</a></p>
+<p id="section-3-5">Until an ACK_FREQUENCY frame is received, sending the min_ack_delay transport
+parameter does not cause the endpoint to change its acknowledgement behavior.<a href="#section-3-5" class="pilcrow">¶</a></p>
 <p id="section-3-6">Endpoints MUST NOT remember the value of the min_ack_delay transport parameter
 they received for use in a subsequent connection. Consequently, ACK_FREQUENCY
 frames cannot be sent in 0-RTT packets, as per <span><a href="https://rfc-editor.org/rfc/rfc9000#section-7.4.1" class="relref">Section 7.4.1</a> of [<a href="#QUIC-TRANSPORT" class="cite xref">QUIC-TRANSPORT</a>]</span>.<a href="#section-3-6" class="pilcrow">¶</a></p>
diff --git a/draft-ietf-quic-ack-frequency.txt b/draft-ietf-quic-ack-frequency.txt
index 2856c646..1f18499e 100644
--- a/draft-ietf-quic-ack-frequency.txt
+++ b/draft-ietf-quic-ack-frequency.txt
@@ -189,10 +189,9 @@ Table of Contents
    independent of whether it also sends the min_ack_delay transport
    parameter or not.
 
-   Receiving a min_ack_delay transport parameter indicates that the peer
-   might send ACK_FREQUENCY frames in the future.  Until an
-   ACK_FREQUENCY frame is received, receiving this transport parameter
-   does not cause the endpoint to change its acknowledgement behavior.
+   Until an ACK_FREQUENCY frame is received, sending the min_ack_delay
+   transport parameter does not cause the endpoint to change its
+   acknowledgement behavior.
 
    Endpoints MUST NOT remember the value of the min_ack_delay transport
    parameter they received for use in a subsequent connection.