Merge pull request #202 from quicwg/mirjak-patch-18

ACK packet carrying frame

draft-ietf-quic-ack-frequency.md

@@ -412,10 +412,10 @@ On sending an update to the peer's `max_ack_delay`, an endpoint can use this new
 value in later computations of its Probe Timeout (PTO) period; see {{Section 5.2.1
 of QUIC-RECOVERY}}.
 
-Until the frame is acknowledged, the endpoint MUST use the greater of the
-current `max_ack_delay` and the value that is in flight when computing the PTO
-period. Doing so avoids spurious PTOs that can be caused by an update that
-increases the peer's `max_ack_delay`.
+Until the packet carrying this frame is acknowledged, the endpoint MUST use the
+greater of the current `max_ack_delay` and the value that is in flight when
+computing the PTO period. Doing so avoids spurious PTOs that can be caused by an
+update that increases the peer's `max_ack_delay`.
 
 While it is expected that endpoints will have only one ACK_FREQUENCY frame in
 flight at any given time, this extension does not prohibit having more than one