wso2 · pavinduLakshan · Jul 13, 2026 · Jul 12, 2026 · Jul 12, 2026
diff --git a/en/asgardeo/docs/apis/organization-apis/restapis/association-management-by-admin.yaml b/en/asgardeo/docs/apis/organization-apis/restapis/association-management-by-admin.yaml
@@ -502,7 +502,7 @@ components:
           example: 1
           description: |
             This represents whether the API should stop processing the operations if any of them fail. The subsequent
-            operations after the the fail count is reached will not be processed.
+            operations after the fail count is reached will not be processed.
             If set to 0 or not set, the API will continue processing the operations even if some of them fail.
         operations:
           type: array

diff --git a/en/asgardeo/docs/apis/restapis/association-management-by-admin.yaml b/en/asgardeo/docs/apis/restapis/association-management-by-admin.yaml
@@ -502,7 +502,7 @@ components:
           example: 1
           description: |
             This represents whether the API should stop processing the operations if any of them fail. The subsequent
-            operations after the the fail count is reached will not be processed.
+            operations after the fail count is reached will not be processed.
             If set to 0 or not set, the API will continue processing the operations even if some of them fail.
         operations:
           type: array

diff --git a/en/asgardeo/docs/apis/restapis/user-account-recovery.yaml b/en/asgardeo/docs/apis/restapis/user-account-recovery.yaml
@@ -17,7 +17,7 @@ paths:
         notifications.
 
         - Use the returned __recoveryCode__ and the __channelId__ with
-        __username recover api__ to confirm the the username recovery and to
+        __username recover api__ to confirm the username recovery and to
         receive recovery notifications via the channel specified by the user.
 
         <b>Scope(Permission) required:</b> `internal_user_recovery_create`

diff --git a/en/identity-server/7.0.0/docs/apis/restapis/user-account-recovery-v1.yaml b/en/identity-server/7.0.0/docs/apis/restapis/user-account-recovery-v1.yaml
@@ -27,7 +27,7 @@ paths:
         notifications.
 
         - Use the returned __recoveryCode__ and the __channelId__ with
-        __username recover api__ to confirm the the username recovery and to
+        __username recover api__ to confirm the username recovery and to
         receive recovery notifications via the channel specified by the user.
 
         <b>Scope(Permission) required:</b> `internal_user_recovery_create`

diff --git a/en/identity-server/7.0.0/docs/apis/restapis/user-account-recovery-v2.yaml b/en/identity-server/7.0.0/docs/apis/restapis/user-account-recovery-v2.yaml
@@ -17,7 +17,7 @@ paths:
         notifications.
 
         - Use the returned __recoveryCode__ and the __channelId__ with
-        __username recover api__ to confirm the the username recovery and to
+        __username recover api__ to confirm the username recovery and to
         receive recovery notifications via the channel specified by the user.
 
         <b>Scope(Permission) required:</b> `internal_user_recovery_create`

diff --git a/...cs/deploy/configure/databases/data-dictionary/user-management-related-tables.md b/...cs/deploy/configure/databases/data-dictionary/user-management-related-tables.md
@@ -9,12 +9,12 @@
 table. `UM_ID` is the auto generated tenant ID. Following are the columns
 of the table.

 -   `UM_ID`
 -   `UM_DOMAIN_NAME`
 -   `UM_EMAIL`
 -   `UM_ACTIVE`
 -   `UM_CREATED_DATE`
 -   `UM_USER_CONFIG`

 ---

@@ -24,9 +24,9 @@
 default for a tenant, there are three domains as `PRIMARY`, `SYSTEM`, and
 `INTERNAL`. If a secondary userstore is added for a tenant, the userstore domain details for that also will get stored in this table.

 -   `UM_DOMAIN_ID`
 -   `UM_DOMAIN_NAME`
 -   `UM_TENANT_ID`  

 ---

@@ -36,7 +36,7 @@
 user details will be stored in this table upon user creation. Following
 are the columns of the table.

 -   `UM_ID`
 -   `UM_USER_ID`
 -   `UM_USER_NAME`
 -   `UM_USER_PASSWORD`
@@ -286,7 +286,7 @@
 
 ## UM_SYSTEM_USER_ROLE
 
-Storing the system roles assigned to the the system users is done with
+Storing the system roles assigned to the system users is done with
 this table. `UM_USER_NAME` contains the username of the system user.
 `UM_ROLE_ID` contains the ID of the system role which points to the `UM_ID` column of the `UM_SYSTEM_ROLE` table. The `wso2.anonymous.role`
 system role is by default assigned to the `wso2.anonymous.user` system

diff --git a/en/identity-server/7.0.0/docs/get-started/try-your-own-app/java-ee-saml.md b/en/identity-server/7.0.0/docs/get-started/try-your-own-app/java-ee-saml.md
@@ -56,7 +56,7 @@ Follow the steps given below to initialize the SAML agent.
 
 ### Create the configuration file
 
-To initialize the SAML agent, you need a property file with the configurations such as the the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file.
+To initialize the SAML agent, you need a property file with the configurations such as the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file.
 
 Create a file named **sample-app.properties** inside the **<YOUR_APP>/src/main/resources** directory, using the content below.
 

diff --git a/en/identity-server/7.1.0/docs/apis/restapis/user-account-recovery-v1.yaml b/en/identity-server/7.1.0/docs/apis/restapis/user-account-recovery-v1.yaml
@@ -27,7 +27,7 @@ paths:
         notifications.
 
         - Use the returned __recoveryCode__ and the __channelId__ with
-        __username recover api__ to confirm the the username recovery and to
+        __username recover api__ to confirm the username recovery and to
         receive recovery notifications via the channel specified by the user.
 
         <b>Scope(Permission) required:</b> `internal_user_recovery_create`

diff --git a/en/identity-server/7.1.0/docs/apis/restapis/user-account-recovery-v2.yaml b/en/identity-server/7.1.0/docs/apis/restapis/user-account-recovery-v2.yaml
@@ -17,7 +17,7 @@ paths:
         notifications.
 
         - Use the returned __recoveryCode__ and the __channelId__ with
-        __username recover api__ to confirm the the username recovery and to
+        __username recover api__ to confirm the username recovery and to
         receive recovery notifications via the channel specified by the user.
 
         <b>Scope(Permission) required:</b> `internal_user_recovery_create`

diff --git a/en/identity-server/7.1.0/docs/complete-guides/nextjs/register-an-application.md b/en/identity-server/7.1.0/docs/complete-guides/nextjs/register-an-application.md
@@ -29,6 +29,6 @@ Make a note of the following values from the **Protocol** and **Info** tabs of t
 
 * **`client-id`** from the **Protocol** tab.
 * **`client-secret`** from the **Protocol** tab.
-* **`issuer`** from from the **Info** tab.
+* **`issuer`** from the **Info** tab.
 
 {% include "../../../../../includes/complete-guides/nextjs/register-an-application.md" %}
diff --git a/...cs/deploy/configure/databases/data-dictionary/user-management-related-tables.md b/...cs/deploy/configure/databases/data-dictionary/user-management-related-tables.md
@@ -286,7 +286,7 @@ using the respective permalinks. Following are the columns of the table.
 
 ## UM_SYSTEM_USER_ROLE
 
-Storing the system roles assigned to the the system users is done with
+Storing the system roles assigned to the system users is done with
 this table. `UM_USER_NAME` contains the username of the system user.
 `UM_ROLE_ID` contains the ID of the system role which points to the `UM_ID` column of the `UM_SYSTEM_ROLE` table. The `wso2.anonymous.role`
 system role is by default assigned to the `wso2.anonymous.user` system

diff --git a/en/identity-server/7.1.0/docs/get-started/try-your-own-app/java-ee-saml.md b/en/identity-server/7.1.0/docs/get-started/try-your-own-app/java-ee-saml.md
@@ -56,7 +56,7 @@ Follow the steps given below to initialize the SAML agent.
 
 ### Create the configuration file
 
-To initialize the SAML agent, you need a property file with the configurations such as the the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file.
+To initialize the SAML agent, you need a property file with the configurations such as the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file.
 
 Create a file named **sample-app.properties** inside the **<YOUR_APP>/src/main/resources** directory, using the content below.
 

diff --git a/en/identity-server/7.1.0/docs/guides/multitenancy/manage-tenants.md b/en/identity-server/7.1.0/docs/guides/multitenancy/manage-tenants.md
@@ -75,7 +75,7 @@ Follow the steps given below to add a new root organization from the {{ product_
       </tbody>
     </table>
 
-5. Once a new root organization is created, it will be listed in the the **Root Organization** listing page as shown below.
+5. Once a new root organization is created, it will be listed in the **Root Organization** listing page as shown below.
 
     ![Root Organization Listing]({{base_path}}/assets/img/guides/multitenancy/root-organizaiton-listing.png)
 

diff --git a/...ty-server/7.2.0/docs/apis/organization-apis/restapis/association-management-by-admin.yaml b/...ty-server/7.2.0/docs/apis/organization-apis/restapis/association-management-by-admin.yaml
@@ -502,7 +502,7 @@ components:
           example: 1
           description: |
             This represents whether the API should stop processing the operations if any of them fail. The subsequent
-            operations after the the fail count is reached will not be processed.
+            operations after the fail count is reached will not be processed.
             If set to 0 or not set, the API will continue processing the operations even if some of them fail.
         operations:
           type: array

diff --git a/en/identity-server/7.2.0/docs/apis/restapis/association-management-by-admin.yaml b/en/identity-server/7.2.0/docs/apis/restapis/association-management-by-admin.yaml
@@ -502,7 +502,7 @@ components:
           example: 1
           description: |
             This represents whether the API should stop processing the operations if any of them fail. The subsequent
-            operations after the the fail count is reached will not be processed.
+            operations after the fail count is reached will not be processed.
             If set to 0 or not set, the API will continue processing the operations even if some of them fail.
         operations:
           type: array

diff --git a/en/identity-server/7.2.0/docs/apis/restapis/user-account-recovery-v1.yaml b/en/identity-server/7.2.0/docs/apis/restapis/user-account-recovery-v1.yaml
@@ -27,7 +27,7 @@ paths:
         notifications.
 
         - Use the returned __recoveryCode__ and the __channelId__ with
-        __username recover api__ to confirm the the username recovery and to
+        __username recover api__ to confirm the username recovery and to
         receive recovery notifications via the channel specified by the user.
 
         <b>Scope(Permission) required:</b> `internal_user_recovery_create`

diff --git a/en/identity-server/7.2.0/docs/apis/restapis/user-account-recovery-v2.yaml b/en/identity-server/7.2.0/docs/apis/restapis/user-account-recovery-v2.yaml
@@ -17,7 +17,7 @@ paths:
         notifications.
 
         - Use the returned __recoveryCode__ and the __channelId__ with
-        __username recover api__ to confirm the the username recovery and to
+        __username recover api__ to confirm the username recovery and to
         receive recovery notifications via the channel specified by the user.
 
         <b>Scope(Permission) required:</b> `internal_user_recovery_create`

diff --git a/en/identity-server/7.2.0/docs/complete-guides/nextjs/register-an-application.md b/en/identity-server/7.2.0/docs/complete-guides/nextjs/register-an-application.md
@@ -29,6 +29,6 @@ Make a note of the following values from the **Protocol** and **Info** tabs of t
 
 * **`client-id`** from the **Protocol** tab.
 * **`client-secret`** from the **Protocol** tab.
-* **`issuer`** from from the **Info** tab.
+* **`issuer`** from the **Info** tab.
 
 {% include "../../../../../includes/complete-guides/nextjs/register-an-application.md" %}
diff --git a/...cs/deploy/configure/databases/data-dictionary/user-management-related-tables.md b/...cs/deploy/configure/databases/data-dictionary/user-management-related-tables.md
@@ -286,7 +286,7 @@ using the respective permalinks. Following are the columns of the table.
 
 ## UM_SYSTEM_USER_ROLE
 
-Storing the system roles assigned to the the system users is done with
+Storing the system roles assigned to the system users is done with
 this table. `UM_USER_NAME` contains the username of the system user.
 `UM_ROLE_ID` contains the ID of the system role which points to the `UM_ID` column of the `UM_SYSTEM_ROLE` table. The `wso2.anonymous.role`
 system role is by default assigned to the `wso2.anonymous.user` system

diff --git a/en/identity-server/7.2.0/docs/get-started/try-your-own-app/java-ee-saml.md b/en/identity-server/7.2.0/docs/get-started/try-your-own-app/java-ee-saml.md
@@ -56,7 +56,7 @@ Follow the steps given below to initialize the SAML agent.
 
 ### Create the configuration file
 
-To initialize the SAML agent, you need a property file with the configurations such as the the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file.
+To initialize the SAML agent, you need a property file with the configurations such as the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file.
 
 Create a file named **sample-app.properties** inside the **<YOUR_APP>/src/main/resources** directory, using the content below.
 

diff --git a/en/identity-server/7.2.0/docs/guides/multitenancy/manage-tenants.md b/en/identity-server/7.2.0/docs/guides/multitenancy/manage-tenants.md
@@ -82,7 +82,7 @@ Follow the steps given below to add a new root organization from the {{ product_
     !!! note
         Keep the **Organization Name** field blank to use the **Organization Handle** (tenant domain) as the name.
 
-5. Once a new root organization is created, it will be listed in the the **Root Organization** listing page as shown below.
+5. Once a new root organization is created, it will be listed in the **Root Organization** listing page as shown below.
 
     ![Root Organization Listing]({{base_path}}/assets/img/guides/multitenancy/root-organizaiton-listing.png)
 

diff --git a/...ty-server/7.3.0/docs/apis/organization-apis/restapis/association-management-by-admin.yaml b/...ty-server/7.3.0/docs/apis/organization-apis/restapis/association-management-by-admin.yaml
@@ -502,7 +502,7 @@ components:
           example: 1
           description: |
             This represents whether the API should stop processing the operations if any of them fail. The subsequent
-            operations after the the fail count is reached will not be processed.
+            operations after the fail count is reached will not be processed.
             If set to 0 or not set, the API will continue processing the operations even if some of them fail.
         operations:
           type: array

diff --git a/en/identity-server/7.3.0/docs/apis/restapis/association-management-by-admin.yaml b/en/identity-server/7.3.0/docs/apis/restapis/association-management-by-admin.yaml
@@ -502,7 +502,7 @@ components:
           example: 1
           description: |
             This represents whether the API should stop processing the operations if any of them fail. The subsequent
-            operations after the the fail count is reached will not be processed.
+            operations after the fail count is reached will not be processed.
             If set to 0 or not set, the API will continue processing the operations even if some of them fail.
         operations:
           type: array

diff --git a/en/identity-server/7.3.0/docs/apis/restapis/user-account-recovery-v1.yaml b/en/identity-server/7.3.0/docs/apis/restapis/user-account-recovery-v1.yaml
@@ -27,7 +27,7 @@ paths:
         notifications.
 
         - Use the returned __recoveryCode__ and the __channelId__ with
-        __username recover api__ to confirm the the username recovery and to
+        __username recover api__ to confirm the username recovery and to
         receive recovery notifications via the channel specified by the user.
 
         <b>Scope(Permission) required:</b> `internal_user_recovery_create`

diff --git a/en/identity-server/7.3.0/docs/apis/restapis/user-account-recovery-v2.yaml b/en/identity-server/7.3.0/docs/apis/restapis/user-account-recovery-v2.yaml
@@ -17,7 +17,7 @@ paths:
         notifications.
 
         - Use the returned __recoveryCode__ and the __channelId__ with
-        __username recover api__ to confirm the the username recovery and to
+        __username recover api__ to confirm the username recovery and to
         receive recovery notifications via the channel specified by the user.
 
         <b>Scope(Permission) required:</b> `internal_user_recovery_create`

diff --git a/...ity-server/next/docs/apis/organization-apis/restapis/association-management-by-admin.yaml b/...ity-server/next/docs/apis/organization-apis/restapis/association-management-by-admin.yaml
@@ -502,7 +502,7 @@ components:
           example: 1
           description: |
             This represents whether the API should stop processing the operations if any of them fail. The subsequent
-            operations after the the fail count is reached will not be processed.
+            operations after the fail count is reached will not be processed.
             If set to 0 or not set, the API will continue processing the operations even if some of them fail.
         operations:
           type: array

diff --git a/en/identity-server/next/docs/apis/restapis/association-management-by-admin.yaml b/en/identity-server/next/docs/apis/restapis/association-management-by-admin.yaml
@@ -502,7 +502,7 @@ components:
           example: 1
           description: |
             This represents whether the API should stop processing the operations if any of them fail. The subsequent
-            operations after the the fail count is reached will not be processed.
+            operations after the fail count is reached will not be processed.
             If set to 0 or not set, the API will continue processing the operations even if some of them fail.
         operations:
           type: array

diff --git a/en/identity-server/next/docs/apis/restapis/user-account-recovery-v1.yaml b/en/identity-server/next/docs/apis/restapis/user-account-recovery-v1.yaml
@@ -27,7 +27,7 @@ paths:
         notifications.
 
         - Use the returned __recoveryCode__ and the __channelId__ with
-        __username recover api__ to confirm the the username recovery and to
+        __username recover api__ to confirm the username recovery and to
         receive recovery notifications via the channel specified by the user.
 
         <b>Scope(Permission) required:</b> `internal_user_recovery_create`

diff --git a/en/identity-server/next/docs/apis/restapis/user-account-recovery-v2.yaml b/en/identity-server/next/docs/apis/restapis/user-account-recovery-v2.yaml
@@ -17,7 +17,7 @@ paths:
         notifications.
 
         - Use the returned __recoveryCode__ and the __channelId__ with
-        __username recover api__ to confirm the the username recovery and to
+        __username recover api__ to confirm the username recovery and to
         receive recovery notifications via the channel specified by the user.
 
         <b>Scope(Permission) required:</b> `internal_user_recovery_create`

diff --git a/en/identity-server/next/docs/complete-guides/nextjs/register-an-application.md b/en/identity-server/next/docs/complete-guides/nextjs/register-an-application.md
@@ -29,6 +29,6 @@ Make a note of the following values from the **Protocol** and **Info** tabs of t
 
 * **`client-id`** from the **Protocol** tab.
 * **`client-secret`** from the **Protocol** tab.
-* **`issuer`** from from the **Info** tab.
+* **`issuer`** from the **Info** tab.
 
 {% include "../../../../../includes/complete-guides/nextjs/register-an-application.md" %}
diff --git a/...cs/deploy/configure/databases/data-dictionary/user-management-related-tables.md b/...cs/deploy/configure/databases/data-dictionary/user-management-related-tables.md
@@ -286,7 +286,7 @@ using the respective permalinks. Following are the columns of the table.
 
 ## UM_SYSTEM_USER_ROLE
 
-Storing the system roles assigned to the the system users is done with
+Storing the system roles assigned to the system users is done with
 this table. `UM_USER_NAME` contains the username of the system user.
 `UM_ROLE_ID` contains the ID of the system role which points to the `UM_ID` column of the `UM_SYSTEM_ROLE` table. The `wso2.anonymous.role`
 system role is by default assigned to the `wso2.anonymous.user` system

diff --git a/en/identity-server/next/docs/get-started/try-your-own-app/java-ee-saml.md b/en/identity-server/next/docs/get-started/try-your-own-app/java-ee-saml.md
@@ -56,7 +56,7 @@ Follow the steps given below to initialize the SAML agent.
 
 ### Create the configuration file
 
-To initialize the SAML agent, you need a property file with the configurations such as the the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file.
+To initialize the SAML agent, you need a property file with the configurations such as the {{ product_name }} endpoints. The {{ product_name }} SAML agent reads the configurations from this file.
 
 Create a file named **sample-app.properties** inside the **<YOUR_APP>/src/main/resources** directory, using the content below.
 

diff --git a/en/identity-server/next/docs/guides/multitenancy/manage-tenants.md b/en/identity-server/next/docs/guides/multitenancy/manage-tenants.md
@@ -82,7 +82,7 @@ Follow the steps given below to add a new root organization from the {{ product_
     !!! note
         Keep the **Organization Name** field blank to use the **Organization Handle** (tenant domain) as the name.
 
-5. Once a new root organization is created, it will be listed in the the **Root Organization** listing page as shown below.
+5. Once a new root organization is created, it will be listed in the **Root Organization** listing page as shown below.
 
     ![Root Organization Listing]({{base_path}}/assets/img/guides/multitenancy/root-organizaiton-listing.png)
 

diff --git a/en/includes/complete-guides/angular/register-an-application.md b/en/includes/complete-guides/angular/register-an-application.md
@@ -20,6 +20,6 @@ Next, complete the wizard popup by providing a suitable name and an authorized r
 Make a note of the following values from the **Protocol** and **Info** tabs of the registered application. You will need them to configure the authentication SDK
 
 * **`client-id`** from the **Protocol** tab.
-* **`issuer`** from from the **Info** tab.
+* **`issuer`** from the **Info** tab.
 
 In this step, we have ve registered our Angular app as an application in the {{product_name}} console and generated the required metadata. Next, we will create a Angular app.
diff --git a/en/includes/complete-guides/fesecurity/public-clients.md b/en/includes/complete-guides/fesecurity/public-clients.md
@@ -31,7 +31,7 @@
 
 This process ensures that if an attacker were to intercept the authorization code during the authorization phase, they wouldn't be able to exchange it for tokens. This is because they wouldn't possess the code verifier, a secret known only to the legitimate client. Since the code verifier is generated dynamically and is used only once, even if an attacker somehow obtains it, it would be useless for future requests.
 
-PKCE is an important security improvement for frontend applications but at the same time it sounds like an extra burden for you to generate and process all these code challenges and code verifiers by yourself.  The good news here is, following the security best practices such as secure by design, secure by default, most of the the frontend authentication SDKs automatically enable PKCE extension for you. For instance, WSO2 Identity Platform React SDK enables PKCE extension for your apps by default. Here is how you can enable it manually by setting the enable PKCE option to true in the WSO2 Identity Platform SDK configuration:
+PKCE is an important security improvement for frontend applications but at the same time it sounds like an extra burden for you to generate and process all these code challenges and code verifiers by yourself.  The good news here is, following the security best practices such as secure by design, secure by default, most of the frontend authentication SDKs automatically enable PKCE extension for you. For instance, WSO2 Identity Platform React SDK enables PKCE extension for your apps by default. Here is how you can enable it manually by setting the enable PKCE option to true in the WSO2 Identity Platform SDK configuration:
 
 
 ```javascript title="src/main.jsx" hl_lines="9"

diff --git a/en/includes/quick-starts/springboot.md b/en/includes/quick-starts/springboot.md
@@ -24,7 +24,7 @@ Make a note of the following values from the **Protocol** and **Info** tabs of t
 
 - **`client-id`** from the **Protocol** tab. 
 - **`client-secret`** from the **Protocol** tab. 
-- **`issuer`** from from the **Info** tab.
+- **`issuer`** from the **Info** tab.
 
 ## Create a Spring Boot app using Spring Initializr
 

diff --git a/en/includes/references/extend/federation/write-a-custom-federated-authenticator.md b/en/includes/references/extend/federation/write-a-custom-federated-authenticator.md
@@ -295,7 +295,7 @@ To configure the custom federated authenticator for the application:
 
 3. Select the sign in option configured.
 
-4. Enter the credentials of the the new user created in the partner identity server.
+4. Enter the credentials of the new user created in the partner identity server.
 
 The user is successfully authenticated by the partner Identity Server.