Deploying to main from @ 93b44449fe81ba83827bb386192bf37623d97fe7 🚀

Author: ahus1

extensions.html

@@ -283,7 +283,7 @@ <h5 class="card-title">Home IdP Discovery</h5>
                                     <div class="d-flex align-items-center">
                                         <img src="resources/images/github.png" width="16px" alt="GitHub logo"
                                              class="me-2"/>
-                                        <span>313 stars</span>
+                                        <span>314 stars</span>
                                     </div>
                                 </div>
                         </div>
@@ -402,7 +402,7 @@ <h5 class="card-title">MFA Plugin collection</h5>
                                     <div class="d-flex align-items-center">
                                         <img src="resources/images/github.png" width="16px" alt="GitHub logo"
                                              class="me-2"/>
-                                        <span>225 stars</span>
+                                        <span>226 stars</span>
                                     </div>
                                 </div>
                         </div>
@@ -679,7 +679,7 @@ <h5 class="card-title">GitHub SSH key mapper</h5>
                                     <div class="d-flex align-items-center">
                                         <img src="resources/images/github.png" width="16px" alt="GitHub logo"
                                              class="me-2"/>
-                                        <span>19 stars</span>
+                                        <span>20 stars</span>
                                     </div>
                                 </div>
                         </div>

nightly/securing-apps/token-exchange.html

@@ -606,8 +606,8 @@ <h3 id="_standard-token-exchange-comparison"><a class="anchor" href="#_standard-
 <tbody>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Internal-internal token exchange</strong></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Supported. Implemented as per rfc8693</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Preview support. Loose implementation of rfc8693. It is recommended to use V2 instead</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Supported. Implemented as per RFC 8693</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Preview support. Loose implementation of RFC 8693. It is recommended to use V2 instead</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Allowed <code>subject_token_type</code></strong></p></td>
@@ -617,7 +617,7 @@ <h3 id="_standard-token-exchange-comparison"><a class="anchor" href="#_standard-
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Allowed <code>requested_token_type</code></strong></p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Access token (default), Refresh token, ID token</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Access token, Refresh token (default), SAML2 assertion</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Access token, Refresh token (default), SAML 2.0 assertion</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Behavior of <code>scope</code> parameter</strong></p></td>
@@ -652,12 +652,12 @@ <h3 id="_standard-token-exchange-comparison"><a class="anchor" href="#_standard-
 <td class="tableblock halign-left valign-top"><p class="tableblock">Not available for access nor refresh tokens</p></td>
 </tr>
 <tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Delegation per rfc8693</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Delegation per RFC 8693</strong></p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Not supported yet</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Not supported</p></td>
 </tr>
 <tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Resource parameter per rfc8693</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Resource parameter per RFC 8693</strong></p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Not supported yet</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Not supported</p></td>
 </tr>

nightly/server/reverseproxy.html

@@ -134,7 +134,7 @@ <h2 id="_configure_the_reverse_proxy_headers"><a class="anchor" href="#_configur
 <p>By default if the option is not specified, no reverse proxy headers are parsed. This should be used when no proxy is in use or with https passthrough.</p>
 </li>
 <li>
-<p><code>forwarded</code> enables parsing of the <code>Forwarded</code> header as per <a href="https://www.rfc-editor.org/rfc/rfc7239.html">RFC7239</a>.</p>
+<p><code>forwarded</code> enables parsing of the <code>Forwarded</code> header as per <a href="https://www.rfc-editor.org/rfc/rfc7239.html">RFC 7239</a>.</p>
 </li>
 <li>
 <p><code>xforwarded</code> enables parsing of non-standard <code>X-Forwarded-*</code> headers, such as <code>X-Forwarded-For</code>, <code>X-Forwarded-Proto</code>, <code>X-Forwarded-Host</code>, and <code>X-Forwarded-Port</code>.</p>
@@ -329,7 +329,7 @@ <h2 id="_exposed_path_recommendations"><a class="anchor" href="#_exposed_path_re
 <td class="tableblock halign-left valign-top"><p class="tableblock">/.well-known/</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">/.well-known/</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Yes</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">This path is needed to resolve Authorization Server Metadata and other information via RFC8414.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">This path is needed to resolve Authorization Server Metadata and other information via RFC 8414.</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">/metrics</p></td>
@@ -356,7 +356,7 @@ <h2 id="_exposed_path_recommendations"><a class="anchor" href="#_exposed_path_re
 <i class="fa icon-note" title="Note"></i>
 </td>
 <td class="content">
-If you configured a <code>http-relative-path</code> on the server, proceed as follows to use discovery wih RFC8414: Configure a reverse proxy to map the <code>/.well-known/</code> path without the prefix to the path with the prefix on the server.
+If you configured a <code>http-relative-path</code> on the server, proceed as follows to use discovery wih RFC 8414: Configure a reverse proxy to map the <code>/.well-known/</code> path without the prefix to the path with the prefix on the server.
 </td>
 </tr>
 </table>