Fix PR comments

wso2 · Mar 7, 2024 · aed9f1b · aed9f1b
1 parent 716965e
commit aed9f1b
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/...esign/api-policies/regular-gateway-policies/jwt-claim-based-access-validator.md b/...esign/api-policies/regular-gateway-policies/jwt-claim-based-access-validator.md
@@ -15,15 +15,15 @@ To apply this policy, follow the below steps:
 
     Configure the custom claim name and value. If required, configure a regex so the claim value will be validated using it.
 
-    In the policy configuring panel that appear from the right, select `Apply to all resources` option if you wish to attach the disable chunking policy to each and every resource of the current API. If you only wish to attach the policy to a particular API operation, leave the checkbox as it is. Then, click on **Save** button.
+    In the policy configuring panel that appears from the right, select `Apply to all resources` option if you wish to attach the JWT claim based access validation policy to each and every resource of the current API. If you only wish to attach the policy to a particular API operation, leave the checkbox as it is. Then, click on **Save** button.
 
     [![JWT claim based access validator]({{base_path}}/assets/img/design/api-policies/configure-jwt-claim-based-access-validation-policy.png)]({{base_path}}/assets/img/design/api-policies/configure-jwt-claim-based-access-validation-policy.png)
 
 4.  Finally, scroll down and click on the **Save** button in order to apply the attached policies to the API.
 
     [![JWT claim based access validator]({{base_path}}/assets/img/design/api-policies/save-attached-policies.png)]({{base_path}}/assets/img/design/api-policies/save-attached-policies.png)
 
-Once the API is deployed and published, every request goes to this API resource will be validated against the custom claim comes in the access token before sending it to the backend.
+Once the API is deployed and published, every request that goes to this API resource will be validated against the custom claim that comes in the access token before sending it to the backend.
 
 !!! tip
 To invert the above validation, you can tick the **Allow flow when claims are not matching** of the policy. This will only allow the flow if the claim values are not matching.