Address suggested edits

Author: DonOmalVindula

en/identity-server/6.1.0/docs/guides/access-delegation/jwt-token-generation-without-revoking-existing-tokens.md renamed to en/identity-server/6.1.0/docs/guides/access-delegation/generate-jwt-tokens-without-revoking-existing-tokens.md

@@ -1,4 +1,4 @@
-# JSON Web Token generation without revoking existing tokens
+# Generate JSON Web Tokens without revoking existing tokens
 
 !!! note
     Instead of configuring the **JSON Web Token (JWT)** token in the
@@ -12,19 +12,17 @@
 
     ![jwt-token-issuer]({{base_path}}/assets/img/guides/jwt-token-issuer.png)
 
-When WSO2 Identity Server receives a request to generate a new JWT, it issues a token based on the **application, user, scope, and binding** combination. If the server receives another request for the same combination, it revokes the existing token and returns a new one.
+When WSO2 Identity Server receives a request to generate a new JSON Web Token (JWT), it issues a token based on the application, user, scope, and binding combination. If the server receives another request for the same combination, it revokes the existing token and returns a new one.
 
-If you want to generate a JWT without revoking the existing token,
-add and configure the following property in the `deployment.toml` file found in the `<IS_HOME>/repository/conf` folder.
+If you want to generate a JWT without revoking the existing token, add and configure the following property in the `<IS_HOME>/repository/conf/deployment.toml` file.
 
 ```toml
 [oauth.jwt.renew_token_without_revoking_existing]
 enable = true
 ```
 
 !!! Note
-    This feature support token requests with the `client_crendetials` grant type by default. If you need to enable for
-    other grant types, add the following configuration to `deployment.toml` file.
+    This feature supports token requests with the `client_crendetials` grant type by default. If you need to enable for other grant types, add the following configuration to the same `<IS_HOME>/repository/conf/deployment.toml` file.
 
     ```toml
     [oauth.jwt.renew_token_without_revoking_existing]
@@ -33,6 +31,4 @@ enable = true
     ```
 
 !!! Warning
-    Enabling this feature could lead to an exponential growth of tokens.
-    Make sure to configure token clean up scripts with proper time limits.
-    See [Remove Unused Tokens from the Database](../../../deploy/remove-unused-tokens-from-the-database/) for details.
+    Enabling this feature could lead to an exponential growth of tokens. Make sure to configure token clean up scripts with proper time limits. See [Remove Unused Tokens from the Database]({{base_path}}/deploy/remove-unused-tokens-from-the-database/) for details.

en/identity-server/6.1.0/mkdocs.yml

@@ -219,7 +219,7 @@ nav:
         - OAuth 2.0 Token Hashing: guides/access-delegation/oauth-token-hashing.md
         - Revoke OAuth Tokens: guides/access-delegation/oauth-token-revocation.md
         - Mutual TLS for OAuth clients: guides/access-delegation/mutual-tls-for-oauth-clients.md
-        - JWT Token generation without revoking existing tokens: guides/access-delegation/jwt-token-generation-without-revoking-existing-tokens.md
+        - Generate JWT tokens without revoking existing tokens: guides/access-delegation/generate-jwt-tokens-without-revoking-existing-tokens.md
       - Consent Management:
         - Manage user consent: guides/consent-mgt/manage-user-consent.md
         - Manage consent puposes: guides/consent-mgt/manage-consent-purposes.md

en/identity-server/7.0.0/docs/deploy/generate-jwt-tokens-without-revoking-existing-tokens.md

@@ -0,0 +1,22 @@
+# Generate JSON Web Tokens without revoking existing tokens
+
+When WSO2 Identity Server receives a request to generate a new JSON Web Token (JWT), it issues a token based on the application, user, scope, and binding combination. If the server receives another request for the same combination, it revokes the existing token and returns a new one.
+
+If you want to generate a JWT without revoking the existing token, add and configure the following property in the `<IS_HOME>/repository/conf/deployment.toml` file.
+
+```toml
+[oauth.jwt.renew_token_without_revoking_existing]
+enable = true
+```
+
+!!! Note
+    This feature supports token requests with the `client_crendetials` grant type by default. If you need to enable for other grant types, add the following configuration to the same `<IS_HOME>/repository/conf/deployment.toml` file.
+
+    ```toml
+    [oauth.jwt.renew_token_without_revoking_existing]
+    enable = true
+    allowed_grant_types = ["client_credentials","password", ...]
+    ```
+
+!!! Warning
+    Enabling this feature could lead to an exponential growth of tokens. Make sure to configure token clean up scripts with proper time limits. See [Remove Unused Tokens from the Database]({{base_path}}/deploy/remove-unused-tokens-from-the-database/) for details.

en/identity-server/7.0.0/docs/deploy/jwt-token-generation-without-revoking-existing-tokens.md

@@ -746,7 +746,7 @@ nav:
           - Token persistence: deploy/token-persistence.md
           - Remove unused tokens from the database: deploy/remove-unused-tokens-from-the-database.md
           - Enable assertions in access tokens: deploy/enable-assertions-in-access-tokens.md
-          - JWT token generation without revoking existing tokens: deploy/jwt-token-generation-without-revoking-existing-tokens.md
+          - Generate JWT tokens without revoking existing tokens: deploy/generate-jwt-tokens-without-revoking-existing-tokens.md
         #- Configure rsync for Deployment Synchronization: deploy/configuring-rsync-for-deployment-synchronization.md
         - Enable hostname verification: deploy/enable-hostname-verification.md
         - Transport Level Security:

en/identity-server/7.0.0/mkdocs.yml

@@ -0,0 +1,22 @@
+# Generate JSON Web Tokens without revoking existing tokens
+
+When WSO2 Identity Server receives a request to generate a new JSON Web Token (JWT), it issues a token based on the application, user, scope, and binding combination. If the server receives another request for the same combination, it revokes the existing token and returns a new one.
+
+If you want to generate a JWT without revoking the existing token, add and configure the following property in the `<IS_HOME>/repository/conf/deployment.toml` file.
+
+```toml
+[oauth.jwt.renew_token_without_revoking_existing]
+enable = true
+```
+
+!!! Note
+    This feature supports token requests with the `client_crendetials` grant type by default. If you need to enable for other grant types, add the following configuration to the same `<IS_HOME>/repository/conf/deployment.toml` file.
+
+    ```toml
+    [oauth.jwt.renew_token_without_revoking_existing]
+    enable = true
+    allowed_grant_types = ["client_credentials","password", ...]
+    ```
+
+!!! Warning
+    Enabling this feature could lead to an exponential growth of tokens. Make sure to configure token clean up scripts with proper time limits. See [Remove Unused Tokens from the Database]({{base_path}}/deploy/remove-unused-tokens-from-the-database/) for details.

en/identity-server/7.1.0/docs/deploy/generate-jwt-tokens-without-revoking-existing-tokens.md

@@ -819,7 +819,7 @@ nav:
               - Token persistence: deploy/token-persistence.md
               - Remove unused tokens from the database: deploy/remove-unused-tokens-from-the-database.md
               - Enable assertions in access tokens: deploy/enable-assertions-in-access-tokens.md
-              - JWT token generation without revoking existing tokens: deploy/jwt-token-generation-without-revoking-existing-tokens.md
+              - Generate JWT tokens without revoking existing tokens: deploy/generate-jwt-tokens-without-revoking-existing-tokens.md
           #- Configure rsync for Deployment Synchronization: deploy/configuring-rsync-for-deployment-synchronization.md
           - Enable hostname verification: deploy/enable-hostname-verification.md
           - Transport Level Security: