Script updating gh-pages from 2ba39b6. [ci skip]

christian-post-wglc-review/draft-ietf-core-groupcomm-bis.html

@@ -2459,7 +2459,7 @@ <h4 id="name-tcp-tls-and-websockets">
           </h4>
 <p id="section-3.9.4-1">Because it supports unicast only, <span>[<a href="#RFC8323" class="cite xref">RFC8323</a>]</span> (CoAP over TCP, TLS, and WebSockets) has a restricted scope as a transport for CoAP group communication. This is limited to the use of block-wise transfer discussed in <a href="#sec-block-wise" class="auto internal xref">Section 3.8</a>.<a href="#section-3.9.4-1" class="pilcrow">¶</a></p>
 <p id="section-3.9.4-2">That is, after the first group request including the Block2 Option and sent over UDP, the following unicast CoAP requests targeting individual servers to retrieve further blocks may be sent over TCP or WebSockets, possibly protected with TLS.<a href="#section-3.9.4-2" class="pilcrow">¶</a></p>
-<p id="section-3.9.4-3">This requires the individually addressed servers to also support CoAP over TCP/TLS/WebSockets for the targeted resource. While those transports do not support multicast, it is possible to rely on multicast for discovering that a server has those transports available and that they allow accessing the targeted resource, possibly with block-wise transfer used for random access to blocks within the resource reprentation. Such discovering can rely on means defined in <span>[<a href="#I-D.ietf-core-transport-indication" class="cite xref">I-D.ietf-core-transport-indication</a>]</span>.<a href="#section-3.9.4-3" class="pilcrow">¶</a></p>
+<p id="section-3.9.4-3">This requires the individually addressed servers to also support CoAP over TCP/TLS/WebSockets for the targeted resource. While those transports do not support multicast, it is possible to rely on multicast for discovering that a server has those transports available and that they allow accessing the targeted resource, possibly with block-wise transfer used for random access to blocks within the resource representation. Such discovering can rely on means defined in <span>[<a href="#I-D.ietf-core-transport-indication" class="cite xref">I-D.ietf-core-transport-indication</a>]</span>.<a href="#section-3.9.4-3" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="other-transports">

christian-post-wglc-review/draft-ietf-core-groupcomm-bis.txt

@@ -1911,8 +1911,8 @@ Table of Contents
    multicast for discovering that a server has those transports
    available and that they allow accessing the targeted resource,
    possibly with block-wise transfer used for random access to blocks
-   within the resource reprentation.  Such discovering can rely on means
-   defined in [I-D.ietf-core-transport-indication].
+   within the resource representation.  Such discovering can rely on
+   means defined in [I-D.ietf-core-transport-indication].
 
 3.9.5.  Other Transports