Be explicit about avoiding flow control issues

draft-ietf-masque-h3-datagram.md

@@ -370,8 +370,9 @@ violation of these requirements MUST treat the HTTP message as malformed.
 
 When processing capsules, a receiver might be tempted to accumulate the full
 length of the capsule value in the data stream before handling it. This approach
-can consume flow control in underlying layers, which might lead to deadlocks if
-the capsule data exhausts the flow control window.
+SHOULD be avoided, because it can consume flow control in underlying layers, and
+that might lead to deadlocks if the capsule data exhausts the flow control
+window.
 
 
 ## Error Handling
@@ -484,8 +485,9 @@ into memory.
 
 Since QUIC DATAGRAM frames are required to fit within a QUIC packet,
 implementations that reencode DATAGRAM capsules into QUIC DATAGRAM frames might
-be tempted to accumulate the entire capsule before reencoding it. This can cause
-flow control problems; see {{capsule-protocol}}.
+be tempted to accumulate the entire capsule in the stream before reencoding it.
+This SHOULD be avoided, because it can cause flow control problems; see
+{{capsule-protocol}}.
 
 Note that it is possible for an HTTP extension to use HTTP Datagrams without
 using the Capsule Protocol. For example, if an HTTP extension that uses HTTP