diff --git a/draft-ietf-quic-http.md b/draft-ietf-quic-http.md
index f1334e3a13..bdf200319c 100644
--- a/draft-ietf-quic-http.md
+++ b/draft-ietf-quic-http.md
@@ -2348,7 +2348,7 @@ the settings identifier space in HTTP/3 is substantially larger (62 bits versus
 16 bits), so many HTTP/3 settings have no equivalent HTTP/2 code point. See
 {{iana-settings}}.
 
-As QUIC streams might arrive out-of-order, endpoints are advised to not wait for
+As QUIC streams might arrive out of order, endpoints are advised to not wait for
 the peers' settings to arrive before responding to other streams.  See
 {{settings-initialization}}.
 
diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md
index b12b89ae59..5a6ad92f18 100644
--- a/draft-ietf-quic-transport.md
+++ b/draft-ietf-quic-transport.md
@@ -1781,7 +1781,7 @@ Because there is no flow control of CRYPTO frames, an endpoint could
 potentially force its peer to buffer an unbounded amount of data.
 
 Implementations MUST support buffering at least 4096 bytes of data received in
-out of order CRYPTO frames. Endpoints MAY choose to allow more data to be
+out-of-order CRYPTO frames. Endpoints MAY choose to allow more data to be
 buffered during the handshake. A larger limit during the handshake could allow
 for larger keys or credentials to be exchanged. An endpoint's buffer size does
 not need to remain constant during the life of the connection.