HRI update and fix on second redirect

articles/api/authentication/api-authz/_highly-regulated.md

@@ -1,5 +1,5 @@
 # Authorization Code Flow with Enhanced Privacy Protection
-
+<!-- markdownlint-disable MD024 MD031 -->
 ## Push Authorization Requests (PAR)
 
 <%= include('../../../_includes/_http-method', {
@@ -84,7 +84,7 @@ Content-Type: application/json
 ```
 
 ::: note
-Highly Regulated Identity is currently available for Enterprise customers under Limited Early Access. To learn more about this program, contact [Auth0 Support](http://support.auth0.com/). 
+ To use Highly Regulated Identity features, you must have an Enterprise Plan with Highly Regulated Identity add-on. Refer to [Auth0 Pricing](https://auth0.com/pricing) for details.
 :::
 
 Authorization Code Flow with [Pushed Authorization Requests (PAR)](/get-started/authentication-and-authorization-flow/authorization-code-flow/authorization-code-flow-with-par) uses the `/oauth/par` endpoint to allow applications to send the authorization parameters usually sent in a `GET` request to `/authorize`. PAR uses a POST method from the backend to keep parameter values secure. The `/oauth/par` endpoint accepts all authorization parameters which can be proivided to `/authorize`. Assuming the call to the `/oauth/par` endpoint is valid, Auth0 will respond with a `redirect_uri` value that can be used as a parameter for the `/authorize` endpoint.

config/redirects.js

@@ -7679,9 +7679,7 @@ const redirects = [
     to: '/secure/tokens/access-tokens',
   },
   {
-    from: [
-      '/secure/tokens/access-tokens/token-binding',
-    ],
+    from: ['/secure/tokens/access-tokens/token-binding'],
     to: '/get-started/applications/configure-sender-constraining',
   },
   {