DISINTEREST->STOP_SENDING in HTTP doc

draft-ietf-quic-http.md

@@ -276,11 +276,11 @@ A server can send a complete response prior to the client sending an entire
 request if the response does not depend on any portion of the request that has
 not been sent and received. When this is true, a server MAY request that the
 client abort transmission of a request without error by triggering a QUIC
-DISINTEREST with error code HTTP_EARLY_RESPONSE, sending a complete response,
+STOP_SENDING with error code HTTP_EARLY_RESPONSE, sending a complete response,
 and cleanly closing its streams. Clients MUST NOT discard complete responses as
-a result of receiving a DISINTEREST, though clients can always discard responses
-at their discretion for other reasons.  Servers SHOULD NOT abort a response in
-progress as a result of receiving a solicited RST_STREAM.
+a result of receiving a STOP_SENDING, though clients can always discard
+responses at their discretion for other reasons.  Servers SHOULD NOT abort a
+response in progress as a result of receiving a solicited RST_STREAM.
 
 ### Header Compression
 
@@ -379,7 +379,7 @@ frames sent on the control stream, and response body (if any) sent via the
 corresponding data stream.
 
 If a promised push stream is not needed by the client, the client SHOULD send a
-QUIC DISINTEREST on the promised stream with an appropriate error code (e.g.
+QUIC STOP_SENDING on the promised stream with an appropriate error code (e.g.
 HTTP_PUSH_REFUSED, HTTP_PUSH_ALREADY_IN_CACHE; see {{errors}}).  This asks the
 server not to transfer the data and indicates that it will be discarded upon
 receipt.