Script updating gh-pages from 234249c. [ci skip]

draft-ietf-quic-transport.html

@@ -1102,16 +1102,16 @@ <h2 id="rfc.section.2.4">
 <p></p>
 
 <ul>
-<li>write data, understanding when stream flow control credit (<a href="#data-flow-control" class="xref">Section 4.1</a>) has successfully been reserved to send the written data</li>
+<li>write data, understanding when stream flow control credit (<a href="#data-flow-control" class="xref">Section 4.1</a>) has successfully been reserved to send the written data;</li>
 <li>end the stream (clean termination), resulting in a STREAM frame (<a href="#frame-stream" class="xref">Section 19.8</a>) with the FIN bit set; and</li>
-<li>reset the stream (abrupt termination), resulting in a RESET_STREAM frame (<a href="#frame-reset-stream" class="xref">Section 19.4</a>), even if the stream was already ended.</li>
+<li>reset the stream (abrupt termination), resulting in a RESET_STREAM frame (<a href="#frame-reset-stream" class="xref">Section 19.4</a>), if the stream was not already in a terminal state.</li>
 </ul>
 <p id="rfc.section.2.4.p.4">On the receiving part of a stream, application protocols need to be able to:</p>
 <p></p>
 
 <ul>
-<li>read data</li>
-<li>abort reading of the stream and request closure, possibly resulting in a STOP_SENDING frame (<a href="#frame-stop-sending" class="xref">Section 19.5</a>)</li>
+<li>read data; and</li>
+<li>abort reading of the stream and request closure, possibly resulting in a STOP_SENDING frame (<a href="#frame-stop-sending" class="xref">Section 19.5</a>).</li>
 </ul>
 <p id="rfc.section.2.4.p.6">Applications also need to be informed of state changes on streams, including when the peer has opened or reset a stream, when a peer aborts reading on a stream, when new data is available, and when data can or cannot be written to the stream due to flow control.</p>
 <h1 id="rfc.section.3">

draft-ietf-quic-transport.txt

@@ -602,14 +602,14 @@ Internet-Draft           QUIC Transport Protocol            October 2019
 
    o  write data, understanding when stream flow control credit
       (Section 4.1) has successfully been reserved to send the written
-      data
+      data;
 
    o  end the stream (clean termination), resulting in a STREAM frame
       (Section 19.8) with the FIN bit set; and
 
    o  reset the stream (abrupt termination), resulting in a RESET_STREAM
-      frame (Section 19.4), even if the stream was already ended.
-
+      frame (Section 19.4), if the stream was not already in a terminal
+      state.
 
 
 
@@ -621,10 +621,10 @@ Internet-Draft           QUIC Transport Protocol            October 2019
    On the receiving part of a stream, application protocols need to be
    able to:
 
-   o  read data
+   o  read data; and
 
    o  abort reading of the stream and request closure, possibly
-      resulting in a STOP_SENDING frame (Section 19.5)
+      resulting in a STOP_SENDING frame (Section 19.5).
 
    Applications also need to be informed of state changes on streams,
    including when the peer has opened or reset a stream, when a peer