feedback updates

Author: patriciasantaana

src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx

@@ -34,4 +34,4 @@ As an example, to send the header `x-send-jwt-claim-user` request header to the
 4. Enter a rule name and a filter expression, if applicable.
 5. Choose **Set dynamic**.
 6. Set the header name.
-7. Set the value to `lookup_json_string(http.request.jwt.claims["<TOKEN_CONFIGURATION_ID>"][0], "claim_name")`, where `<TOKEN_CONFIGURATION_ID>` is your token configuration ID found in JWT Validation and `claim_name` is the JWT claim you want to add to the header.
+7. Set the value to `lookup_json_string(http.request.jwt.claims["<TOKEN_CONFIGURATION_ID>"][0], "claim_name")`, where `<TOKEN_CONFIGURATION_ID>` is your token configuration ID found in JWT Validation and `claim_name` is the [JWT claim](/ruleset-engine/rules-language/fields/dynamic-fields/#json-web-tokens-validation-claims) you want to add to the header.

src/content/docs/ruleset-engine/rules-language/fields/dynamic-fields.mdx

@@ -514,15 +514,15 @@ Identifies whether a request comes from a worker or not. When a request comes fr
 
 ## JSON Web Tokens Validation claims
 
-[API Shield](/api-shield/) users can now create [Custom Rules](/waf/custom-rules/) using claims present in tokens processed by [JSON Web Tokens Validation](/api-shield/security/jwt-validation/).
+[API Shield](/api-shield/) users can now create [custom rules](/waf/custom-rules/) using claims present in tokens processed by [JSON Web Tokens Validation](/api-shield/security/jwt-validation/).
 
 ### `aud` (audience)
 
 `http.request.jwt.claims.aud` `Map<Array<String>>` <br />
 `http.request.jwt.claims.aud.names` `Array<String>` <br />
 `http.request.jwt.claims.aud.values` `Array<String>` <br />
 
-The `aud` (audience) claim identifies the recipients that the JWT is intended for. Each principal intended to process the JWT must identify itself with a value in the audience claim. In the general case, the `aud` value is an array of case-sensitive strings, each containing a StringOrURI value.
+The `aud` (audience) claim identifies the recipients that the JSON Web Token (JWT) is intended for. Each principal intended to process the JWT must identify itself with a value in the audience claim. In the general case, the `aud` value is an array of case-sensitive strings, each containing a `StringOrURI` value.
 
 <Render file="jwt-claims" product="api-shield" />
 
@@ -532,7 +532,7 @@ The `aud` (audience) claim identifies the recipients that the JWT is intended fo
 `http.request.jwt.claims.iat.sec.names` `Array<String>` <br />
 `http.request.jwt.claims.iat.sec.values` `Array<Integer>` <br />
 
-The `iat` (issued at) claim identifies the time at which the JWT was issued.
+The `iat` (issued at) claim identifies the time (number of seconds) at which the JWT was issued.
 
 <Render file="jwt-claims" product="api-shield" />
 
@@ -562,7 +562,7 @@ The `jti` (JWT ID) claim provides a unique identifier for the JWT.
 `http.request.jwt.claims.nbf.sec.names` `Array<String>` <br />
 `http.request.jwt.claims.nbf.sec.values` `Array<Integer>` <br />
 
-The `nbf` (not before) claim identifies the time before which the JWT must not be accepted for processing.
+The `nbf` (not before) claim identifies the time (number of seconds) before which the JWT must not be accepted for processing.
 
 <Render file="jwt-claims" product="api-shield" />
 

src/content/partials/api-shield/jwt-claims.mdx

@@ -3,4 +3,4 @@
 
 ---
 
-Refer to the [Registered Claim Names](https://datatracker.ietf.org/doc/html/rfc7519#section-4.1) for more information.
+Refer to the [Registered Claim Names](https://datatracker.ietf.org/doc/html/rfc7519#section-4.1) in RFC 7519 for more information.