Update draft-ietf-quic-transport.md

draft-ietf-quic-transport.md

@@ -2860,13 +2860,13 @@ valid frames? -->
 ### Sending ACK Frames
 
 An endpoint MUST NOT send more than one packet containing only an ACK frame per
-received non ACK-eliciting packet(ie: one containing only ACK or PADDING frames).
-An endpoint MUST NOT send a packet containing only an ACK frame in response to a
-non ACK-eliciting packet, even if there are packet gaps which precede the
-received packet. This prevents an indefinite feedback loop of ACKs, which may
-prevent the connection from ever becoming idle. The endpoint MUST however
-acknowledge non ACK-eliciting packets when sending ACK frames in response to
-other packets.
+received non ACK-eliciting packet(ie: one containing only ACK and/or PADDING
+frames).  An endpoint MUST NOT send a packet containing only an ACK frame in
+response to a non ACK-eliciting packet, even if there are packet gaps which
+precede the received packet. This prevents an indefinite feedback loop of ACKs,
+which may prevent the connection from ever becoming idle. The endpoint MUST
+however acknowledge non ACK-eliciting packets when sending ACK frames in
+response to other packets.
 
 Packets containing PADDING frames are considered to be in flight for congestion
 control purposes {{QUIC-RECOVERY}}. Sending only PADDING frames might cause the