Merge pull request #5829 from mmafrar/fix/english-wording-typos

Fix: Correct English typos in Identity Server documentation

Author: himeshsiriwardana

en/asgardeo/docs/get-started/try-it-application.md

@@ -10,7 +10,7 @@ The following guide explains how you can quickly test login with Asgardeo using
 
 ## Asgardeo Try It app
 
-**Try It** is a test application that we have already set up and configured for you to quicky integrate authenticators and see how Asgardeo login works with applications.
+**Try It** is a test application that we have already set up and configured for you to quickly integrate authenticators and see how Asgardeo login works with applications.
 
 Let's try a simple login flow in the Asgardeo Try It application:
 
@@ -36,7 +36,7 @@ You can use the various authenticators Asgardeo offers to customize the login fl
     ![Try It application]({{base_path}}/assets/img/get-started/custom-login-flow.png){: width="700" style="display: block; margin: 0; border: 0.3px solid lightgrey;"}
 
     !!! note
-        Follow the guides below to learn how to configure the authention flows.
+        Follow the guides below to learn how to configure the authentication flows.
 
         - [Add Social login]({{base_path}}/guides/authentication/social-login/)
         - [Add Passwordless login]({{base_path}}/guides/authentication/passwordless-login/)

en/asgardeo/docs/get-started/try-samples/qsg-saml-webapp-java-ee.md

@@ -39,7 +39,7 @@ Follow these steps given below to register the sample Java EE web application in
           <td>Select <b>SAML</b>.</td>
       </tr>
       <tr>
-          <td>Configruation type</td>
+          <td>Configuration type</td>
           <td>Select <b>Manual</b> (Learn more about [SAML configuration types]({{base_path}}/guides/applications/register-saml-web-app/))</td>
       </tr>
     <tr>
@@ -57,7 +57,7 @@ Follow these steps given below to register the sample Java EE web application in
       </td>
     </tr>
     </table>
-5. Click **Register** to complete the registration.
+4. Click **Register** to complete the registration.
 
 !!! tip
     To provide a better experience for the user, it is recommended to configure an access URL for the application. You can set an access URL from the **General** tab of the application. (For this sample application, the access URL is <code>https://localhost:8080/sample-app</code>).
@@ -99,7 +99,7 @@ Follow the steps given below to configure the sample app.
         This will extract the contents of the **war** file. </br>
       If your Tomcat server is set to auto-deploy applications, you can skip this step.
 
-    ```bash 
+    ```bash
     sh catalina.sh start
     ```
 
@@ -112,7 +112,7 @@ Follow the steps given below to configure the sample app.
         - Update the **SAML2.IdPEntityId** parameter with the Asgardeo issuer, which is `api.asgardeo.io/t/{organization_name}`.
         - **SAML2.SPEntityId** should match the issuer name entered when registering the application in Asgardeo.
 
-    ```saml   
+    ```saml
     SAML2.AssertionConsumerURL=http://localhost:8080/sample-app/home.jsp
     SAML2.SPEntityId=sample-issuer
     SAML2.IdPEntityId=api.asgardeo.io/t/{organization_name}
@@ -134,6 +134,7 @@ Follow the steps given below to configure the sample app.
     ErrorPage=/error.jsp
     SAML2SSOURL=samlsso
     ```
+
     <table>
       <thead>
         <tr>
@@ -287,7 +288,7 @@ Follow the steps given below to configure the sample app.
 
 5. In the `{TOMCAT_HOME}/bin` folder, run the following commands to restart the Tomcat server for the configurations to take effect:
 
-    ```bash 
+    ```bash
     sh catalina.sh stop
     sh catalina.sh start
     ```

en/asgardeo/docs/guides/asgardeo-logs/diagnostic-logs.md

@@ -65,6 +65,7 @@ executeStep(1, {
 })
 ...
 ```
+
 Once a user succeeds the first login step, the debug log appears in the logs portal as shown below.
 
 ![Debug logs in conditional authentication]({{base_path}}/assets/img/guides/asgardeo-logs/debug-log-conditional-auth.png){: width="550" style="border: 0.3px solid lightgrey;"}
@@ -78,12 +79,14 @@ Conditional authentication scripts can generate two types of error logs in the l
 - Application errors that occur due to syntax errors in the conditional authentication script.
 
     For example, your conditional authentication script may have a syntax error that the editor does not flag as shown below.
+
     ```java
     .....
     var allowedGroups = ['Supplier'];
-    Log.info('Allowed groups: ' + alowedGroups.toString());
+    Log.info('Allowed groups: ' + allowedGroups.toString());
     .....
     ```
+
     Once a user attempts to log in, the error is logged in the logs portal as shown below.
 
     ![Error logs due to syntax in conditional authentication]({{base_path}}/assets/img/guides/asgardeo-logs/error-log-syntax-error-conditional-auth.png){: width="700" style="border: 0.3px solid lightgrey;"}
@@ -107,6 +110,7 @@ Conditional authentication scripts can generate two types of error logs in the l
     })
     ...
     ```
+
     Once an unauthorized user attempts to log in, the error is logged in the logs portal as shown.
 
     ![Error logs in conditional authentication]({{base_path}}/assets/img/guides/asgardeo-logs/error-log-conditional-auth.png){: width="700" style="border: 0.3px solid lightgrey;"}

en/asgardeo/docs/guides/authentication/mfa/add-duo-login.md

@@ -13,7 +13,7 @@ Before you begin, ensure you have the following:
 
 ## Configure Duo Security Application
 
-1. Log in to the [Duo Securty admin panel](https://admin.duosecurity.com/login). 
+1. Log in to the [Duo Security admin panel](https://admin.duosecurity.com/login).
 2. Click **Applications** from the left panel and then click the **Protect an Application** button.
 
     ![Create duo security app]({{base_path}}/assets/img/guides/mfa/duo/add-duo-security-app.png){: style="display: block; margin: 0; border: 0.3px solid lightgrey;"}
@@ -28,8 +28,8 @@ Before you begin, ensure you have the following:
 
 Next, you need to register Duo as a connection in Asgardeo. To do so, follow the steps below.
 
-1. Log in to the [Asgardeo Console](https://console.asgardeo.io/) as an adminstrator.
-2. Navigate to **Connections** from the left-hand panel 
+1. Log in to the [Asgardeo Console](https://console.asgardeo.io/) as an administrator.
+2. Navigate to **Connections** from the left-hand panel
 3. Click **New Connection** and select **Duo** from the listed templates.
 4. Provide a Name for the Duo connection (e.g., "Duo Security").
 5. Enter the **Client ID**, **Client secret**, and **API hostname**, that you obtained from the Duo Admin Panel.
@@ -42,16 +42,16 @@ The created Duo connection should be added as an MFA option to the login flow of
 1. On the [Asgardeo Console](https://console.asgardeo.io/), navigate to **Applications**.
 2. Select the application for which you want to enable Duo MFA.
 3. Go to the **Login Flow** section. Username and Password will be added as the default login method.
-4. Click on the **+ icon** to add a new step to the login flow. 
+4. Click on the **+ icon** to add a new step to the login flow.
 5. Click on the **+ Add Sign In Option** button in step 2.
-6. Select the Duo connection from the authenticator list and click **Add**. 
+6. Select the Duo connection from the authenticator list and click **Add**.
 7. Save the changes by clicking the **Update** button.
 
 ## Test the Integration
 
 Finally, you need to verify that Duo has been successfully integrated and is functioning correctly as a second-factor authentication method. To do so,
 
-1. Access the sample application and click on **Login** button. 
+1. Access the sample application and click on **Login** button.
 
     ![React sample app login]({{base_path}}/assets/img/guides/mfa/duo/react-sample-app-login.png){: style="display: block; margin: 0; border: 0.3px solid lightgrey;"}
 

en/identity-server/5.10.0/docs/develop/writing-a-custom-event-handler.md

@@ -1,20 +1,20 @@
 # Writing a Custom Event Handler
 
-The WSO2 Identity Server eventing framework can be used to trigger events such as user operation events like `PRE_SET_USER_CLAIMS`,`POST_ADD_USER`. A full list of the sample events can be found below. The eventing framework also supports handlers which can be used to do operations upon a triggered event. For instance, an event handler can be used to validate the changed user password against previously used entries when a `PRE_UPDATE_CREDENTIAL` event is triggered. 
+The WSO2 Identity Server eventing framework can be used to trigger events such as user operation events like `PRE_SET_USER_CLAIMS`,`POST_ADD_USER`. A full list of the sample events can be found below. The eventing framework also supports handlers which can be used to do operations upon a triggered event. For instance, an event handler can be used to validate the changed user password against previously used entries when a `PRE_UPDATE_CREDENTIAL` event is triggered.
 
 ## What is an event handler?
 
-An event handler is used to perform an operation based on the published events. 
+An event handler is used to perform an operation based on the published events.
 
 For instance, an event handler can be used to send an email after a user addition. The following sequence of operations are executed while adding a user.
 
 1. Publish the `PRE_ADD_USER` event — The subscribed handlers will be executed for the pre-add user event.
-2. Execute the `AddUser` operation — The user will be persisted to the user store (LDAP or JBDC user store).
+2. Execute the `AddUser` operation — The user will be persisted to the user store (LDAP or JDBC user store).
 3. Publish the `POST_ADD_USER` event — The subscribed handlers will be executed for the post-add user event.
 
 Therefore, the email can be sent through an event handler that is subscribed to the `POST_ADD_USER` event.
 
-The following list is a list of sample events. 
+The following list is a list of sample events.
 
 - `PRE_AUTHENTICATION`
 - `POST_AUTHENTICATION`
@@ -52,11 +52,11 @@ The following list is a list of sample events.
 
 ## Writing an event handler
 
-To write a new event handler, you must extend the `org.wso2.carbon.identity.event.handler.AbstractEventHandler`. 
+To write a new event handler, you must extend the `org.wso2.carbon.identity.event.handler.AbstractEventHandler`.
 
-1. Override the `getName()` method to set the name for the event handler and the `getPriority()` method can be used to set the priory of the event handler. The handlers will be executed based on the priority.
+1. Override the `getName()` method to set the name for the event handler and the `getPriority()` method can be used to set the priority of the event handler. The handlers will be executed based on the priority.
 
-    ```
+    ```java
     public String getName() {
     return "emailSender";
     }
@@ -67,9 +67,9 @@ To write a new event handler, you must extend the `org.wso2.carbon.identity.even
     }
     ```
 
-2. To execute the expected operation, override the `handleEvent()` method. The `event.getEventProperties()` method can be used to get the parameters related to the user operations. 
+2. To execute the expected operation, override the `handleEvent()` method. The `event.getEventProperties()` method can be used to get the parameters related to the user operations.
 
-    ```
+    ```java
     @Override
     public void handleEvent(Event event) throws IdentityEventException {
 
@@ -83,11 +83,11 @@ To write a new event handler, you must extend the `org.wso2.carbon.identity.even
     String[] roleList = (String[]) eventProperties.get(IdentityEventConstants.EventProperty.ROLE_LIST);
     ```
 
-## Registering the event handler 
+## Registering the event handler
 
 Register the event handler in the service component as follows.
 
-```
+```java
 protected void activate(ComponentContext context) {
     try {
         BundleContext bundleContext = context.getBundleContext();
@@ -102,7 +102,7 @@ class.getName(),new SampleEventHandler(), null);
 
 Add the event handler configuration to the `<IS_HOME>/repository/conf/deployment.toml` file. The events that need to subscribe to the handler can be listed in subscriptions.
 
-```
+```toml
 [[event_handler]]
 name= "emailSender"
 subscriptions =["POST_ADD_USER"]

en/identity-server/5.10.0/docs/setup/changing-datasource-consent-management.md

@@ -1,16 +1,16 @@
 # Changing the Default Datasource for Consent Management
 
-WSO2 Identity Server is shipped with an embedded H2 database for storing data. 
-These default databases are located in the `<IS_HOME>/repository/database` directory 
+WSO2 Identity Server is shipped with an embedded H2 database for storing data.  
+These default databases are located in the `<IS_HOME>/repository/database` directory  
 of the product pack.
 
-By default Consent Management data is stored in the identity database (IDENTITY_DB) with 
-Identity and UMA data. However, you can separate consent specific data into a separate 
+By default Consent Management data is stored in the identity database (IDENTITY_DB) with  
+Identity and UMA data. However, you can separate consent specific data into a separate  
 data-source to any database type that is supported by WSO2 Identity Server.
 
 !!! note
-    For more information about databases, see 
-    [Working with Databases](../../setup/working-with-databases) and 
+    For more information about databases, see  
+    [Working with Databases](../../setup/working-with-databases) and  
     [Setting Up Separate Databases for Clustering](../../setup/setting-up-separate-databases-for-clustering).
 
 Following are the sample configuration for each database type.
@@ -26,7 +26,7 @@ Following are the sample configuration for each database type.
         driver = "org.postgresql.Driver"
         jmx_enable=false
         ```
-        
+
     2. Executing database scripts. 
 
         Navigate to `<IS-HOME>/dbscripts`. Execute the scripts in the following file, against 
@@ -45,7 +45,7 @@ Following are the sample configuration for each database type.
         driver = "com.mysql.jdbc.Driver"
         jmx_enable=false
         ```
-        
+
     2. Executing database scripts. 
 
         Navigate to `<IS-HOME>/dbscripts`. Execute the scripts in the following file, against 
@@ -64,7 +64,7 @@ Following are the sample configuration for each database type.
         driver = "com.ibm.db2.jcc.DB2Driver"
         jmx_enable=false
         ```
-        
+
     2. Executing database scripts. 
 
         Navigate to `<IS-HOME>/dbscripts`. Execute the scripts in the following file, against 
@@ -83,7 +83,7 @@ Following are the sample configuration for each database type.
         driver = "com.microsoft.sqlserver.jdbc.SQLServerDriver"
         jmx_enable=false
         ```
-        
+
     2. Executing database scripts. 
 
         Navigate to `<IS-HOME>/dbscripts`. Execute the scripts in the following file, against 
@@ -102,7 +102,7 @@ Following are the sample configuration for each database type.
         driver = "oracle.jdbc.OracleDriver"
         jmx_enable=false
         ```
-        
+
     2. Executing database scripts. 
 
         Navigate to `<IS-HOME>/dbscripts`. Execute the scripts in the following file, against 
@@ -226,7 +226,7 @@ as a single transaction.</p>
 
 
 Once when we separate out consent database from `WSO2IdentityDB`, we need to add the 
-following configuration to the `deployement.toml` to specify WSO2 Identity Server to 
+following configuration to the `deployment.toml` to specify WSO2 Identity Server to 
 use a separate data-source instead of default `IDENTITY_DB`.
 
 ```
@@ -259,4 +259,4 @@ data_source="jdbc/WSO2CONSENT_DB"
 
     [authentication.consent]
     data_source="jdbc/WSO2CONSENT_DB"
-    ``` 
+    ```

en/identity-server/5.10.0/docs/setup/jmx-based-monitoring.md

@@ -274,7 +274,7 @@ monitor the performance of the datasource using this MBean. The
 ![](../assets/img/53125400/57747100.png) 
 
 **Example:** If you have JMX enabled for the default Carbon datasources
-in the ` deployement.toml ` file, the [JDBC connection pool
+in the ` deployment.toml ` file, the [JDBC connection pool
 parameters](http://tomcat.apache.org/tomcat-9.0-doc/jdbc-pool.html) that
 are configured for the Carbon datasource will be listed as attributes as
 shown below. See the