Script updating gh-pages from 9c7fb15. [ci skip]

Author: ID Bot

mbj-aaron/draft-ietf-oauth-rfc8725bis.html

@@ -1791,7 +1791,7 @@ <h3 id="name-validate-issuer-and-subject">
  application  <span class="bcp14">MUST</span> validate that
 the subject value corresponds to a valid subject and/or issuer-subject pair at the application.
 This may include confirming that the issuer is trusted by the application.
-Note that <span><a href="https://rfc-editor.org/rfc/rfc9700#section-4.15" class="relref">Section 4.15</a> of [<a href="#RFC9700" class="cite xref">RFC9700</a>]</span> discusses the possibility of
+In the OAuth context, <span><a href="https://rfc-editor.org/rfc/rfc9700#section-4.15" class="relref">Section 4.15</a> of [<a href="#RFC9700" class="cite xref">RFC9700</a>]</span> discusses the possibility of
 confusing user identifier and client ID values.
 If the issuer, subject, or the pair are invalid, the application
   <span class="bcp14">MUST</span> reject the JWT.<a href="#section-3.8-3" class="pilcrow">¶</a></p>

mbj-aaron/draft-ietf-oauth-rfc8725bis.txt

@@ -511,10 +511,10 @@ Table of Contents
    application MUST validate that the subject value corresponds to a
    valid subject and/or issuer-subject pair at the application.  This
    may include confirming that the issuer is trusted by the application.
-   Note that Section 4.15 of [RFC9700] discusses the possibility of
-   confusing user identifier and client ID values.  If the issuer,
-   subject, or the pair are invalid, the application MUST reject the
-   JWT.
+   In the OAuth context, Section 4.15 of [RFC9700] discusses the
+   possibility of confusing user identifier and client ID values.  If
+   the issuer, subject, or the pair are invalid, the application MUST
+   reject the JWT.
 
 3.9.  Use and Validate Audience