Merge pull request #6084 from KingSajxxd/fix-typos-spelling-grammar

pavinduLakshan · web-flow · commit 5d7f80ac8aa0 · 2026-04-22T21:22:41.000+05:30
diff --git a/en/identity-server/5.10.0/docs/administer/deployment-checklist.md b/en/identity-server/5.10.0/docs/administer/deployment-checklist.md
@@ -35,7 +35,7 @@ Deployment</a></li>
 <td><div class="content-wrapper">
 <p>By default, WSO2 products identify the hostname of the current machine through the Java API. However, this value 
 sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname 
-by setting the relavent parameter in the <code>               &lt;PRODUCT_HOME&gt;/repository/conf/deployment.toml     
+by setting the relevant parameter in the <code>               &lt;PRODUCT_HOME&gt;/repository/conf/deployment.toml     
     
      </code> file.</p>
 <div class="code panel pdl" style="border-width: 1px;">
diff --git a/en/identity-server/5.10.0/docs/learn/configuring-identity-analytics.md b/en/identity-server/5.10.0/docs/learn/configuring-identity-analytics.md
@@ -148,4 +148,4 @@ Let's create some basic authentication statistics. To do this, log in to the WSO
 
     ![is-analytics-login-attempts](../assets/img/learn/is-analytics-login-attempts.png)
 
-You have succesfully enabled WSO2 IS Analytics and published statistics to the dashboard. For more information on what you can do with IS analytics, see [Analytics](../../learn/analytics).
+You have successfully enabled WSO2 IS Analytics and published statistics to the dashboard. For more information on what you can do with IS analytics, see [Analytics](../../learn/analytics).
diff --git a/en/identity-server/5.10.0/docs/learn/configuring-multi-tenancy.md b/en/identity-server/5.10.0/docs/learn/configuring-multi-tenancy.md
@@ -43,14 +43,14 @@ Repeat steps 4-5 and create a tenant called "pickup-taxis.com" with different ad
 
 You can now log in to each tenant using the relevant tenant admin's credentials and create users and roles in the tenant. Note that you are managing two separate sets of users and roles for each tenant using one instance of WSO2 Identity Server.
 
-1. Sign out of the Management Console and sign in using the `pickup-eats` admin credentitals.
+1. Sign out of the Management Console and sign in using the `pickup-eats` admin credentials.
 
     - `Username:` jane@pickup-eats.com
     - `Password:` jane123
 
 2. Create a new user called **Cameron**. For instructions on how to create a user, see [Adding Users and Roles](../../learn/adding-users-and-roles#create-a-user). 
 
-You have succesfully created a user in the `pickup-eats` tenant. Now repeat step 1-2 and create a user in the `pickup-taxis` tenant as well. 
+You have successfully created a user in the `pickup-eats` tenant. Now repeat steps 1-2 and create a user in the `pickup-taxis` tenant as well. 
 
 ## Try it out
 
diff --git a/en/identity-server/5.10.0/docs/learn/configuring-roles-for-an-identity-provider.md b/en/identity-server/5.10.0/docs/learn/configuring-roles-for-an-identity-provider.md
@@ -44,6 +44,6 @@ following.
       role_claim_value_attribute_separator=","
     ```
     
-    If this is not configured and if the **no MulitAttributeSeparator** is
-    configured, the default seperator will be " **,,,** ".
+    If this is not configured and if the **no MultiAttributeSeparator** is
+    configured, the default separator will be " **,,,** ".
     
diff --git a/en/identity-server/5.10.0/docs/learn/provisioning-patterns.md b/en/identity-server/5.10.0/docs/learn/provisioning-patterns.md
@@ -43,7 +43,7 @@ mentioned user attributes.
         salesforce outbound provisioning connector.
 
 4.  Edit the outbound provisioning connector configuration of the
-    identity provider and enter a provisioning pattern and seperator for
+    identity provider and enter a provisioning pattern and separator for
     the following fields.
 
     -   **Provisioning Pattern** - Enter a combination of user
diff --git a/en/identity-server/5.11.0/docs/administer/deployment-checklist.md b/en/identity-server/5.11.0/docs/administer/deployment-checklist.md
@@ -35,7 +35,7 @@ Deployment</a></li>
 <td><div class="content-wrapper">
 <p>By default, WSO2 products identify the hostname of the current machine through the Java API. However, this value 
 sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname 
-by setting the relavent parameter in the <code>               &lt;PRODUCT_HOME&gt;/repository/conf/deployment.toml     
+by setting the relevant parameter in the <code>               &lt;PRODUCT_HOME&gt;/repository/conf/deployment.toml     
     
      </code> file.</p>
 <div class="code panel pdl" style="border-width: 1px;">
diff --git a/en/identity-server/5.11.0/docs/learn/configuring-identity-analytics.md b/en/identity-server/5.11.0/docs/learn/configuring-identity-analytics.md
@@ -118,4 +118,4 @@ Let's create some basic authentication statistics. To do this, log in to the WSO
 
     ![is-analytics-login-attempts](../assets/img/learn/is-analytics-login-attempts.png)
 
-You have succesfully enabled WSO2 IS Analytics and published statistics to the dashboard. For more information on what you can do with IS analytics, see [Analytics](../../learn/analytics).
+You have successfully enabled WSO2 IS Analytics and published statistics to the dashboard. For more information on what you can do with IS analytics, see [Analytics](../../learn/analytics).
diff --git a/en/identity-server/5.11.0/docs/learn/configuring-multi-tenancy.md b/en/identity-server/5.11.0/docs/learn/configuring-multi-tenancy.md
@@ -43,14 +43,14 @@ Repeat steps 4-5 and create a tenant called "pickup-taxis.com" with different ad
 
 You can now log in to each tenant using the relevant tenant admin's credentials and create users and roles in the tenant. Note that you are managing two separate sets of users and roles for each tenant using one instance of WSO2 Identity Server.
 
-1. Sign out of the Management Console and sign in using the `pickup-eats` admin credentitals.
+1. Sign out of the Management Console and sign in using the `pickup-eats` admin credentials.
 
     - `Username:` jane@pickup-eats.com
     - `Password:` jane123
 
 2. Create a new user called **Cameron**. For instructions on how to create a user, see [Adding Users and Roles](../../learn/adding-users-and-roles#create-a-user). 
 
-You have succesfully created a user in the `pickup-eats` tenant. Now repeat step 1-2 and create a user in the `pickup-taxis` tenant as well. 
+You have successfully created a user in the `pickup-eats` tenant. Now repeat steps 1-2 and create a user in the `pickup-taxis` tenant as well. 
 
 ## Try it out
 
diff --git a/en/identity-server/5.11.0/docs/learn/configuring-roles-for-an-identity-provider.md b/en/identity-server/5.11.0/docs/learn/configuring-roles-for-an-identity-provider.md
@@ -44,6 +44,6 @@ following.
       role_claim_value_attribute_separator=","
     ```
     
-    If this is not configured and if the **no MulitAttributeSeparator** is
-    configured, the default seperator will be " **,,,** ".
+    If this is not configured and if the **no MultiAttributeSeparator** is
+    configured, the default separator will be " **,,,** ".
     
diff --git a/en/identity-server/5.11.0/docs/learn/provisioning-patterns.md b/en/identity-server/5.11.0/docs/learn/provisioning-patterns.md
@@ -43,7 +43,7 @@ mentioned user attributes.
         salesforce outbound provisioning connector.
 
 4.  Edit the outbound provisioning connector configuration of the
-    identity provider and enter a provisioning pattern and seperator for
+    identity provider and enter a provisioning pattern and separator for
     the following fields.
 
     -   **Provisioning Pattern** - Enter a combination of user
diff --git a/en/identity-server/5.9.0/docs/administer/deployment-checklist.md b/en/identity-server/5.9.0/docs/administer/deployment-checklist.md
@@ -35,7 +35,7 @@ Deployment</a></li>
 <td><div class="content-wrapper">
 <p>By default, WSO2 products identify the hostname of the current machine through the Java API. However, this value 
 sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname 
-by setting the relavent parameter in the <code>               &lt;PRODUCT_HOME&gt;/repository/conf/deployment.toml     
+by setting the relevant parameter in the <code>               &lt;PRODUCT_HOME&gt;/repository/conf/deployment.toml     
     
      </code> file.</p>
 <div class="code panel pdl" style="border-width: 1px;">
diff --git a/en/identity-server/5.9.0/docs/develop/using-the-scim-2.0-rest-apis.md b/en/identity-server/5.9.0/docs/develop/using-the-scim-2.0-rest-apis.md
@@ -387,7 +387,7 @@ This API deletes a user using the user's unique ID. It returns
 
 **Responses**
 
--   HTTP 204 - User has been succesfully deleted
+-   HTTP 204 - User has been successfully deleted
 -   HTTP 401 - Unauthorized
 -   HTTP 404 - Valid user is not found
 
@@ -2288,7 +2288,7 @@ HTTP/1.1 204 NOT IMPLEMENTED
 </table>
 
 **Response** 
--	HTTP 204 - User has been succesfully deleted
+-	HTTP 204 - User has been successfully deleted
 -	HTTP 401 - Unauthorized
 -	HTTP 404 - Valid user is not found
 
diff --git a/en/identity-server/5.9.0/docs/learn/configuring-identity-analytics.md b/en/identity-server/5.9.0/docs/learn/configuring-identity-analytics.md
@@ -93,4 +93,4 @@ Let's create some basic authentication statistics. To do this, log in to the WSO
 
     ![is-analytics-login-attempts](../assets/img/learn/is-analytics-login-attempts.png)
 
-You have succesfully enabled WSO2 IS Analytics and published statistics to the dashboard. For more information on what you can do with IS analytics, see [Analytics](../../learn/analytics).
+You have successfully enabled WSO2 IS Analytics and published statistics to the dashboard. For more information on what you can do with IS analytics, see [Analytics](../../learn/analytics).
diff --git a/en/identity-server/5.9.0/docs/learn/configuring-multi-tenancy.md b/en/identity-server/5.9.0/docs/learn/configuring-multi-tenancy.md
@@ -22,7 +22,7 @@ In order to do this, Pickup can set up two tenants that share access to the same
     wso2server.bat run
     ```
 
-3. Access the [WSO2 Identity Server Management Console] (https://localhost:9443/carbon) as an administrator (credentials: admin/admin).
+3. Access the [WSO2 Identity Server Management Console](https://localhost:9443/carbon) as an administrator (credentials: admin/admin).
 
 4. On the **Configure** tab of the Management Console, click **Add New Tenant**. 
 
@@ -43,14 +43,14 @@ Repeat steps 4-5 and create a tenant called "pickup-taxis.com" with different ad
 
 You can now log in to each tenant using the relevant tenant admin's credentials and create users and roles in the tenant. Note that you are managing two separate sets of users and roles for each tenant using one instance of WSO2 Identity Server.
 
-1. Sign out of the Management Console and sign in using the `pickup-eats` admin credentitals.
+1. Sign out of the Management Console and sign in using the `pickup-eats` admin credentials.
 
     - `Username:` jane@pickup-eats.com
     - `Password:` jane123
 
 2. Create a new user called **Cameron**. For instructions on how to create a user, see [Adding Users and Roles](../../learn/adding-users-and-roles#create-a-user). 
 
-You have succesfully created a user in the `pickup-eats` tenant. Now repeat step 1-2 and create a user in the `pickup-taxis` tenant as well. 
+You have successfully created a user in the `pickup-eats` tenant. Now repeat steps 1-2 and create a user in the `pickup-taxis` tenant as well. 
 
 ## Try it out
 
diff --git a/en/identity-server/5.9.0/docs/learn/configuring-multifactor-authentication.md b/en/identity-server/5.9.0/docs/learn/configuring-multifactor-authentication.md
@@ -162,4 +162,4 @@ You have now added and configured the service provider.
 
     ![authenticate-with-smsotp](../assets/img/tutorials/authenticating-with-smsotp.png)
 
-You are redirected to the Pickup Dispatch home page. You have succesfully configured and logged in using multifactor authentication.
+You are redirected to the Pickup Dispatch home page. You have successfully configured and logged in using multifactor authentication.
diff --git a/en/identity-server/5.9.0/docs/learn/configuring-roles-for-an-identity-provider.md b/en/identity-server/5.9.0/docs/learn/configuring-roles-for-an-identity-provider.md
@@ -44,6 +44,6 @@ following.
       role_claim_value_attribute_separator=","
     ```
     
-    If this is not configured and if the **no MulitAttributeSeparator** is
-    configured, the default seperator will be " **,,,** ".
+    If this is not configured and if the **no MultiAttributeSeparator** is
+    configured, the default separator will be " **,,,** ".
     
diff --git a/en/identity-server/5.9.0/docs/learn/provisioning-patterns.md b/en/identity-server/5.9.0/docs/learn/provisioning-patterns.md
@@ -43,7 +43,7 @@ mentioned user attributes.
         salesforce outbound provisioning connector.
 
 4.  Edit the outbound provisioning connector configuration of the
-    identity provider and enter a provisioning pattern and seperator for
+    identity provider and enter a provisioning pattern and separator for
     the following fields.
 
     -   **Provisioning Pattern** - Enter a combination of user
diff --git a/en/identity-server/6.0.0/docs/deploy/deployment-checklist.md b/en/identity-server/6.0.0/docs/deploy/deployment-checklist.md
@@ -35,7 +35,7 @@ Deployment</a></li>
 <td><div class="content-wrapper">
 <p>By default, WSO2 Identity Server identifies the hostname of the current machine through the Java API. However, this value 
 sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname 
-by setting the relavent parameter in the <code>               &lt;IS_HOME&gt;/repository/conf/deployment.toml     
+by setting the relevant parameter in the <code>               &lt;IS_HOME&gt;/repository/conf/deployment.toml     
     
      </code> file.</p>
 <div class="code panel pdl" style="border-width: 1px;">
diff --git a/en/identity-server/6.0.0/docs/guides/identity-federation/roles-idp.md b/en/identity-server/6.0.0/docs/guides/identity-federation/roles-idp.md
@@ -32,4 +32,4 @@ To configure the roles of the identity provider:
     role_claim_value_attribute_separator=","
     ```
     
-    If this is not configured and if the **no MulitAttributeSeparator** is configured, the default separator will be " **,,,** ".
+    If this is not configured and if the **no MultiAttributeSeparator** is configured, the default separator will be " **,,,** ".
diff --git a/en/identity-server/6.0.0/docs/guides/identity-lifecycles/provisioning-patterns.md b/en/identity-server/6.0.0/docs/guides/identity-lifecycles/provisioning-patterns.md
@@ -42,7 +42,7 @@ mentioned user attributes.
         salesforce outbound provisioning connector.
 
 4. Edit the outbound provisioning connector configuration of the
-    identity provider and enter a provisioning pattern and seperator for
+    identity provider and enter a provisioning pattern and separator for
     the following fields.
 
     - **Provisioning Pattern** - Enter a combination of user
diff --git a/en/identity-server/6.1.0/docs/deploy/deployment-checklist.md b/en/identity-server/6.1.0/docs/deploy/deployment-checklist.md
@@ -35,7 +35,7 @@ Deployment</a></li>
 <td><div class="content-wrapper">
 <p>By default, WSO2 Identity Server identifies the hostname of the current machine through the Java API. However, this value 
 sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname 
-by setting the relavent parameter in the <code>               &lt;IS_HOME&gt;/repository/conf/deployment.toml     
+by setting the relevant parameter in the <code>               &lt;IS_HOME&gt;/repository/conf/deployment.toml     
     
      </code> file.</p>
 <div class="code panel pdl" style="border-width: 1px;">
diff --git a/en/identity-server/6.1.0/docs/guides/identity-federation/roles-idp.md b/en/identity-server/6.1.0/docs/guides/identity-federation/roles-idp.md
@@ -32,4 +32,4 @@ To configure the roles of the identity provider:
     role_claim_value_attribute_separator=","
     ```
     
-    If this is not configured and if the **no MulitAttributeSeparator** is configured, the default separator will be " **,,,** ".
+    If this is not configured and if the **no MultiAttributeSeparator** is configured, the default separator will be " **,,,** ".
diff --git a/en/identity-server/6.1.0/docs/guides/identity-lifecycles/provisioning-patterns.md b/en/identity-server/6.1.0/docs/guides/identity-lifecycles/provisioning-patterns.md
@@ -42,7 +42,7 @@ mentioned user attributes.
         salesforce outbound provisioning connector.
 
 4. Edit the outbound provisioning connector configuration of the
-    identity provider and enter a provisioning pattern and seperator for
+    identity provider and enter a provisioning pattern and separator for
     the following fields.
 
     - **Provisioning Pattern** - Enter a combination of user
diff --git a/en/identity-server/7.0.0/docs/deploy/deployment-checklist.md b/en/identity-server/7.0.0/docs/deploy/deployment-checklist.md
@@ -24,7 +24,7 @@
           <tr class="even">
                <td>Hostname</td>
                <td>
-                    By default, WSO2 Identity Server identifies the hostname of the current machine through the Java API. However, this value sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname by setting the relavent parameter in the <code>&lt;IS_HOME&gt;/repository/conf/deployment.toml</code> file. <br />
+                    By default, WSO2 Identity Server identifies the hostname of the current machine through the Java API. However, this value sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname by setting the relevant parameter in the <code>&lt;IS_HOME&gt;/repository/conf/deployment.toml</code> file. <br />
                     <b> Related Topics </b>
                     <li><a href="{{base_path}}/deploy/change-the-hostname">Change the hostname</a></li>
                </td>
diff --git a/en/identity-server/7.1.0/docs/deploy/deployment-checklist.md b/en/identity-server/7.1.0/docs/deploy/deployment-checklist.md
@@ -24,7 +24,7 @@
           <tr class="even">
                <td>Hostname</td>
                <td>
-                    By default, WSO2 Identity Server identifies the hostname of the current machine through the Java API. However, this value sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname by setting the relavent parameter in the <code>&lt;IS_HOME&gt;/repository/conf/deployment.toml</code> file. <br />
+                    By default, WSO2 Identity Server identifies the hostname of the current machine through the Java API. However, this value sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname by setting the relevant parameter in the <code>&lt;IS_HOME&gt;/repository/conf/deployment.toml</code> file. <br />
                     <b> Related Topics </b>
                     <li><a href="{{base_path}}/deploy/change-the-hostname">Change the hostname</a></li>
                </td>
diff --git a/en/identity-server/7.2.0/docs/deploy/deployment-checklist.md b/en/identity-server/7.2.0/docs/deploy/deployment-checklist.md
@@ -24,7 +24,7 @@
           <tr class="even">
                <td>Hostname</td>
                <td>
-                    By default, WSO2 Identity Server identifies the hostname of the current machine through the Java API. However, this value sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname by setting the relavent parameter in the <code>&lt;IS_HOME&gt;/repository/conf/deployment.toml</code> file. <br />
+                    By default, WSO2 Identity Server identifies the hostname of the current machine through the Java API. However, this value sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname by setting the relevant parameter in the <code>&lt;IS_HOME&gt;/repository/conf/deployment.toml</code> file. <br />
                     <b> Related Topics </b>
                     <li><a href="{{base_path}}/deploy/change-the-hostname">Change the hostname</a></li>
                </td>
diff --git a/en/identity-server/next/docs/deploy/deployment-checklist.md b/en/identity-server/next/docs/deploy/deployment-checklist.md
@@ -24,7 +24,7 @@
           <tr class="even">
                <td>Hostname</td>
                <td>
-                    By default, WSO2 Identity Server identifies the hostname of the current machine through the Java API. However, this value sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname by setting the relavent parameter in the <code>&lt;IS_HOME&gt;/repository/conf/deployment.toml</code> file. <br />
+                    By default, WSO2 Identity Server identifies the hostname of the current machine through the Java API. However, this value sometimes yields erroneous results on some environments. Therefore, users are recommended to configure the hostname by setting the relevant parameter in the <code>&lt;IS_HOME&gt;/repository/conf/deployment.toml</code> file. <br />
                     <b> Related Topics </b>
                     <li><a href="{{base_path}}/deploy/change-the-hostname">Change the hostname</a></li>
                </td>

Original file line number	Diff line number	Diff line change
`@@ -148,4 +148,4 @@ Let's create some basic authentication statistics. To do this, log in to the WSO`
`148`	`148`
`149`	`149`	`![is-analytics-login-attempts](../assets/img/learn/is-analytics-login-attempts.png)`
`150`	`150`
`151`		`-You have succesfully enabled WSO2 IS Analytics and published statistics to the dashboard. For more information on what you can do with IS analytics, see [Analytics](../../learn/analytics).`
	`151`	`+You have successfully enabled WSO2 IS Analytics and published statistics to the dashboard. For more information on what you can do with IS analytics, see [Analytics](../../learn/analytics).`
Original file line number	Diff line number	Diff line change
`@@ -118,4 +118,4 @@ Let's create some basic authentication statistics. To do this, log in to the WSO`
`118`	`118`
`119`	`119`	`![is-analytics-login-attempts](../assets/img/learn/is-analytics-login-attempts.png)`
`120`	`120`
`121`		`-You have succesfully enabled WSO2 IS Analytics and published statistics to the dashboard. For more information on what you can do with IS analytics, see [Analytics](../../learn/analytics).`
	`121`	`+You have successfully enabled WSO2 IS Analytics and published statistics to the dashboard. For more information on what you can do with IS analytics, see [Analytics](../../learn/analytics).`