diff --git a/articles/api/authentication/_change-password.md b/articles/api/authentication/_change-password.md
index c543017fc1..00e44b2854 100644
--- a/articles/api/authentication/_change-password.md
+++ b/articles/api/authentication/_change-password.md
@@ -1,5 +1,5 @@
 # Change Password
-
+<!-- markdownlint-disable MD001 MD012 MD012 -->
 ```http
 POST https://${account.namespace}/dbconnections/change_password
 Content-Type: application/json
@@ -64,7 +64,7 @@ Note: This endpoint only works for database connections.
 
 | Parameter        | Description |
 |:-----------------|:------------|
-| `client_id` | The `client_id` of your client. We strongly recommend including a Client ID so that the email template knows from which client the request was triggered. |
+| `client_id` | The `client_id` of your client. |
 | `email` <br/><span class="label label-danger">Required</span> | The user's email address. |
 | `connection` <br/><span class="label label-danger">Required</span> | The name of the database connection configured to your client. |
 | `organization` | The `organization_id` of the Organization associated with the user. |
diff --git a/articles/api/authentication/_sign-up.md b/articles/api/authentication/_sign-up.md
index fb6bbd2035..46e637c7bd 100644
--- a/articles/api/authentication/_sign-up.md
+++ b/articles/api/authentication/_sign-up.md
@@ -1,4 +1,5 @@
 # Signup
+<!-- markdownlint-disable MD001 MD012 MD012 -->
 
 ```http
 POST https://${account.namespace}/dbconnections/signup
@@ -85,7 +86,7 @@ This endpoint only works for database connections.
 
 | Parameter        | Description |
 |:-----------------|:------------|
-| `client_id` <br/><span class="label label-danger">Required</span> | The `client_id` of your client. |
+| `client_id` | The `client_id` of your client. |
 | `email` <br/><span class="label label-danger">Required</span> | The user's email address. |
 | `password` <br/><span class="label label-danger">Required</span> | The user's desired password. |
 | `connection` <br/><span class="label label-danger">Required</span> | The name of the database configured to your client. |
diff --git a/articles/api/authentication/api-authz/_highly-regulated.md b/articles/api/authentication/api-authz/_highly-regulated.md
index e9170a0461..0181295d99 100644
--- a/articles/api/authentication/api-authz/_highly-regulated.md
+++ b/articles/api/authentication/api-authz/_highly-regulated.md
@@ -1,3 +1,4 @@
+<!-- markdownlint-disable MD024 MD031 -->
 # Authorization Code Flow with Enhanced Privacy Protection
 
 ## Push Authorization Requests (PAR)
@@ -84,7 +85,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 the 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.