Script updating gh-pages from 6c8fe1a. [ci skip]

Author: ID Bot

low-hanging-adfruit/draft-ietf-anima-rfc8366bis.html

@@ -3053,7 +3053,8 @@ <h3 id="name-yang-module-security-consid">
 of <span>[<a href="#RFC5652" class="cite xref">RFC5652</a>]</span>), though details for how to do this are outside
 the scope of this document.<a href="#section-11.4-2" class="pilcrow">¶</a></p>
 <p id="section-11.4-3">The use of YANG to define data structures, via the "sx:structure"
-extension <span>[<a href="#RFC8791" class="cite xref">RFC8791</a>]</span>, is relatively new and distinct from the traditional use of
+extension <span>[<a href="#RFC8791" class="cite xref">RFC8791</a>]</span>, is relatively new and distinct from the conventional
+use of
 YANG to define an API accessed by network management protocols such as
 NETCONF <span>[<a href="#RFC6241" class="cite xref">RFC6241</a>]</span> and RESTCONF <span>[<a href="#RFC8040" class="cite xref">RFC8040</a>]</span>. For this reason, this
 security considerations section does not follow the template described

low-hanging-adfruit/draft-ietf-anima-rfc8366bis.txt

@@ -1764,7 +1764,7 @@ Table of Contents
 
    The use of YANG to define data structures, via the "sx:structure"
    extension [RFC8791], is relatively new and distinct from the
-   traditional use of YANG to define an API accessed by network
+   conventional use of YANG to define an API accessed by network
    management protocols such as NETCONF [RFC6241] and RESTCONF
    [RFC8040].  For this reason, this security considerations section
    does not follow the template described by Section 3.7 of