Original text:
HTTP semantics (SEMANTICS) are used for a broad range of services on the Internet.  These semantics have most commonly been used with <del> HTTP/1.1, over a variety of transport and session layers, and with HTTP/2 over TLS.  HTTP/3 supports the same semantics over a new </del>  transport protocol, QUIC. 1.1. HTTP/1.1 (HTTP11) uses whitespace-delimited text fields to convey HTTP messages.  While these exchanges are human-readable, using whitespace for message formatting leads to parsing complexity and <del> excessive tolerance of variant behavior.  Because HTTP/1.x does not include a multiplexing layer, multiple TCP connections are often used to service requests in parallel.  However, that has a negative impact on congestion control and network efficiency, since TCP does not share congestion control across multiple connections. </del>  HTTP/2 (HTTP2) introduced a binary framing and multiplexing layer to improve latency without modifying the transport layer.  However, same packet as the QUIC CONNECTION_CLOSE frame improves the chances of the frame being received by clients.  5.4. For various reasons, the QUIC transport could indicate to the

Reviewer comments:
Address multiple editorial comments.
NAME said
NAME said
The text currently says: Transport makes the following addition, in : That might be worth reiterating in HTTP/3.
NAME said
Two separate questions. I'm fine generalizing it to HTTP/1.x. The link between the first two sentences is the fact that HTTP/1.x uses human-readable whitespace-delimited fields, but those attributes make parsing inconsistent; subsequent versions of HTTP/2 went a different direction. If you're talking about the second and third, that could easily be a paragraph split; it's a change of idea under the umbrella of major changes of direction from H1 to H2+.

Revised text:
HTTP semantics (SEMANTICS) are used for a broad range of services on the Internet.  These semantics have most commonly been used with  <ins> HTTP/1.1 and HTTP/2.  HTTP/1.1 has been used over a variety of transport and session layers, while HTTP/2 has been used primarily with TLS over TCP.  HTTP/3 supports the same semantics over a new </ins> transport protocol, QUIC. 1.1. HTTP/1.1 (HTTP11) uses whitespace-delimited text fields to convey HTTP messages.  While these exchanges are human-readable, using whitespace for message formatting leads to parsing complexity and  <ins> excessive tolerance of variant behavior. Because HTTP/1.1 does not include a multiplexing layer, multiple TCP connections are often used to service requests in parallel.  However, that has a negative impact on congestion control and network efficiency, since TCP does not share congestion control across multiple connections. </ins> HTTP/2 (HTTP2) introduced a binary framing and multiplexing layer to improve latency without modifying the transport layer.  However, same packet as the QUIC CONNECTION_CLOSE frame improves the chances of the frame being received by clients. <ins> If there are open streams that have not been explicitly closed, they are implicitly closed when the connection is closed; see Section 10.2 of QUIC-TRANSPORT. </ins> 5.4. For various reasons, the QUIC transport could indicate to the