new key possibly

auth0 · Aug 19, 2024 · 0e4bf0f · 0e4bf0f
1 parent 0d806a1
commit 0e4bf0f
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/articles/api/authentication/api-authz/_highly-regulated.md b/articles/api/authentication/api-authz/_highly-regulated.md
@@ -84,7 +84,7 @@ Content-Type: application/json
 ```
 
 ::: note
- To use Highly Regulated Identity features, you must have an Enterprise Plan with the Highly Regulated Identity add-on. To learn more, read [Auth0 Pricing](https://auth0.com/pricing) for details.
+ 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.