diff --git a/draft-ietf-avtcore-rtp-over-quic.html b/draft-ietf-avtcore-rtp-over-quic.html
index b3435be..89b6fa2 100644
--- a/draft-ietf-avtcore-rtp-over-quic.html
+++ b/draft-ietf-avtcore-rtp-over-quic.html
@@ -1436,8 +1436,8 @@ <h3 id="name-whats-in-scope-for-this-spe">
 UDP, SCTP, DTLS, etc. That is, we expect RoQ to be used in contexts in
 which a signaling protocol is used to announce or negotiate a media
 encapsulation and the associated transport parameters (such as IP address, port
-number). RoQ is not intended as a stand-alone media transport,
-although QUIC transport parameters could be statically configured.<a href="#section-1.2-2" class="pilcrow">¶</a></p>
+number). RoQ is not intended as a stand-alone media transport, although media
+transport parameters could be statically configured.<a href="#section-1.2-2" class="pilcrow">¶</a></p>
 <p id="section-1.2-3">The above implies that RoQ is targeted at peer-to-peer operation; but
 it may also be used in client-server-style settings, e.g., when talking to a
 conference server as described in RFC 7667 (<span>[<a href="#RFC7667" class="cite xref">RFC7667</a>]</span>), or, if RoQ
diff --git a/draft-ietf-avtcore-rtp-over-quic.txt b/draft-ietf-avtcore-rtp-over-quic.txt
index c268b24..bdcf44d 100644
--- a/draft-ietf-avtcore-rtp-over-quic.txt
+++ b/draft-ietf-avtcore-rtp-over-quic.txt
@@ -189,7 +189,7 @@ Table of Contents
    protocol is used to announce or negotiate a media encapsulation and
    the associated transport parameters (such as IP address, port
    number).  RoQ is not intended as a stand-alone media transport,
-   although QUIC transport parameters could be statically configured.
+   although media transport parameters could be statically configured.
 
    The above implies that RoQ is targeted at peer-to-peer operation; but
    it may also be used in client-server-style settings, e.g., when