Script updating gh-pages from b4213af. [ci skip]

define-terms/draft-ietf-quic-http.html

@@ -789,7 +789,7 @@ <h2 id="rfc.section.4.1">
 <p id="rfc.section.4.1.p.9">A response MAY consist of multiple messages when and only when one or more informational responses (1xx; see <a href="#RFC7231" class="xref">[RFC7231]</a>, Section 6.2) precede a final response to the same request.  Non-final responses do not contain a payload body or trailers.</p>
 <p id="rfc.section.4.1.p.10">An HTTP request/response exchange fully consumes a bidirectional QUIC stream.  After sending a request, a client MUST close the stream for sending.  Unless using the CONNECT method (see <a href="#the-connect-method" class="xref">Section 4.2</a>), clients MUST NOT make stream closure dependent on receiving a response to their request. After sending a final response, the server MUST close the stream for sending. At this point, the QUIC stream is fully closed.</p>
 <p id="rfc.section.4.1.p.11">When a stream is closed, this indicates the end of an HTTP message. Because some messages are large or unbounded, endpoints SHOULD begin processing partial HTTP messages once enough of the message has been received to make progress.  If a client stream terminates without enough of the HTTP message to provide a complete response, the server SHOULD abort its response with the error code HTTP_INCOMPLETE_REQUEST.</p>
-<p id="rfc.section.4.1.p.12">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 abort reading the receiving part of the request stream with error code HTTP_EARLY_RESPONSE, sending a complete response, and cleanly closing the sending part of the stream.  Clients MUST NOT discard complete responses as a result of having their request terminated abruptly, though clients can always discard responses at their discretion for other reasons.</p>
+<p id="rfc.section.4.1.p.12">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 abort reading the receiving part of the request stream with error code HTTP_EARLY_RESPONSE, send a complete response, and cleanly close the sending part of the stream. Clients MUST NOT discard complete responses as a result of having their request terminated abruptly, though clients can always discard responses at their discretion for other reasons.</p>
 <h3 id="rfc.section.4.1.1">
 <a href="#rfc.section.4.1.1">4.1.1.</a> <a href="#header-formatting" id="header-formatting">Header Formatting and Compression</a>
 </h3>

define-terms/draft-ietf-quic-http.txt

@@ -630,8 +630,8 @@ Internet-Draft                   HTTP/3                        June 2019
    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 abort reading the receiving part of the request stream
-   with error code HTTP_EARLY_RESPONSE, sending a complete response, and
-   cleanly closing the sending part of the stream.  Clients MUST NOT
+   with error code HTTP_EARLY_RESPONSE, send a complete response, and
+   cleanly close the sending part of the stream.  Clients MUST NOT
    discard complete responses as a result of having their request
    terminated abruptly, though clients can always discard responses at
    their discretion for other reasons.