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

draft-ietf-oauth-browser-based-apps.html

@@ -1372,7 +1372,7 @@ <h2 id="name-introduction">
 <p id="section-1-1">This specification describes different architectural patterns for implementing OAuth 2.0 clients in applications executing in a browser. The specification outlines the security challenges for browser-based applications and analyzes how different patterns address these challenges.<a href="#section-1-1" class="pilcrow">¶</a></p>
 <p id="section-1-2">For native application developers using OAuth 2.0 and OpenID Connect, an IETF BCP
 (best current practice) was published that guides integration of these technologies.
-This document is formally known as RFC8252 or BCP212, but often referred to as "AppAuth" after
+This document is formally known as <span>[<a href="#RFC8252" class="cite xref">RFC8252</a>]</span> or BCP212, but often referred to as "AppAuth" after
 the OpenID Foundation-sponsored set of libraries that assist developers in adopting
 these practices. <span>[<a href="#RFC8252" class="cite xref">RFC8252</a>]</span> makes specific recommendations for how to securely implement OAuth clients in native
 applications, including incorporating additional OAuth extensions where needed.<a href="#section-1-2" class="pilcrow">¶</a></p>

draft-ietf-oauth-browser-based-apps.txt

@@ -136,7 +136,7 @@ Table of Contents
    For native application developers using OAuth 2.0 and OpenID Connect,
    an IETF BCP (best current practice) was published that guides
    integration of these technologies.  This document is formally known
-   as RFC8252 or BCP212, but often referred to as "AppAuth" after the
+   as [RFC8252] or BCP212, but often referred to as "AppAuth" after the
    OpenID Foundation-sponsored set of libraries that assist developers
    in adopting these practices.  [RFC8252] makes specific
    recommendations for how to securely implement OAuth clients in native