Original text:
Abstract This document defines the core behavior for Media over QUIC Transport <del> (MOQT), a media transport protocol over QUIC.  MOQT allows a producer of media to publish data and have it consumed via subscription by a multiplicity of endpoints.  It supports intermediate content distribution networks and is designed for high scale and low latency distribution. </del>  1. <del> Media Over QUIC Transport (MOQT) is a transport protocol that utilizes the QUIC network protocol QUIC, either directly or via WebTransport WebTransport, for the dissemination of media.  MOQT utilizes a publish/subscribe workflow in which producers of media publish data in response to subscription requests from a multiplicity of endpoints.  MOQT supports wide range of use-cases with different </del>  resiliency and latency (live, interactive) needs without compromising the scalability and cost effectiveness associated with content delivery networks.

Reviewer comments:
Given this also runs over WebTransport, it's best to avoid QUIC unless it's specifically referring to the transport.
Though MOQT is optimized for QUIC, it technically can go over WebTransport over HTTP/1 or HTTP/2. There are a number of cases when QUIC is used when it could be something else and in most cases, specifying QUIC is not critical to the design. For example "Consumer: A QUIC endpoint receiving media over the network." Also, the definitions in 1.2 frequently reference terms defined later in the list.
Absolutely. Stream prioritization and congestion control is better with QUIC, and thus can support lower latencies, but MoQ over TCP should still work well enough.
For what its worth, we did did say during chartering that were were not going to focus on solving any of the problems that happen with fallback to TCP. Clearly we are not going to go and brak whatever fallback WebTransport does, but they key thing is this work when then WebTransport is over QUIC, not other cases
I completely agree. This is an editorial point that there are times when 'QUIC' is used when it may not actually be QUIC. In many cases, just removing that word makes the sentence both slightly more accurate and shorter.

Revised text:
Abstract This document defines the core behavior for Media over QUIC Transport  <ins> (MOQT), a media transport protocol designed to operate over QUIC and WebTransport, which have similar functionality.  MOQT allows a producer of media to publish data and have it consumed via subscription by a multiplicity of endpoints.  It supports intermediate content distribution networks and is designed for high scale and low latency distribution. </ins> 1.  <ins> Media Over QUIC Transport (MOQT) is a protocol that is optimized for the QUIC protocol QUIC, either directly or via WebTransport WebTransport, for the dissemination of media.  MOQT utilizes a publish/subscribe workflow in which producers of media publish data in response to subscription requests from a multiplicity of endpoints.  MOQT supports wide range of use-cases with different </ins> resiliency and latency (live, interactive) needs without compromising the scalability and cost effectiveness associated with content delivery networks.