diff --git a/draft-ietf-quic-recovery.md b/draft-ietf-quic-recovery.md
index 6e7e3654a0..d94ac8afa6 100644
--- a/draft-ietf-quic-recovery.md
+++ b/draft-ietf-quic-recovery.md
@@ -683,12 +683,12 @@ client receives Handshake or 1-RTT packets prior to obtaining Handshake keys,
 it may assume some or all of the server's Initial packets were lost.
 
 To speed up handshake completion under these conditions, an endpoint MAY, for a
-limited number of occasions per each connection, send a packet containing
+limited number of times per connection, send a packet containing
 unacknowledged CRYPTO data earlier than the PTO expiry, subject to the address
 validation limits in Section 8.1 of {{QUIC-TRANSPORT}}. Doing so at most once
 for each connection is adequate to quickly recover from a single packet loss.
-Endpoints that do not cease retransmitting packets in response to
-unauthenticated data risk creating an infinite exchange of packets.
+An endpoint that always retransmits packets in response to receiving packets
+that it cannot process risks creating an infinite exchange of packets.
 
 Endpoints can also use coalesced packets (see Section 12.2 of
 {{QUIC-TRANSPORT}}) to ensure that each datagram elicits at least one