Fix step numbering and product names in ELK guides

en/identity-server/7.1.0/docs/deploy/elk-analytics-for-adaptive-authentication.md

@@ -1,6 +1,6 @@
 # Add MFA based on ELK-risk
 
-The following guide shows you how to prepare the WSO2 Identity server for adaptive authentication using ELK analytics.
+The following guide shows you how to prepare WSO2 Identity Server for adaptive authentication using ELK analytics.
 
 ## Prerequisite
 
@@ -14,9 +14,9 @@ Follow the steps below to configure the analytics engine in WSO2 Identity Server
 
 2. Select the relevant application and go to its **Login Flow** tab.
 
-5. In the **Predefined Flows** > **Conditional Login Flows** section, click on the **`settings`** icon in the **ELK-Risk-Based** template.
+3. In the **Predefined Flows** > **Conditional Login Flows** section, click on the **`settings`** icon in the **ELK-Risk-Based** template.
 
-2. Configure the following properties.
+4. Configure the following properties.
    ![elk-analytics-engine-properties]({{base_path}}/assets/img/elk-analytics/risk-based-adaptive-authentication/risk-based-adaptive-authentication-4.png){: width="800" style="display: block; margin-left: 0;"}
 
       <table>
@@ -63,7 +63,7 @@ Follow the steps below to configure the analytics engine in WSO2 Identity Server
       </tbody>
       </table>
 
-3. Click **Update** to save the changes.
+5. Click **Update** to save the changes.
 
 ## Add Elasticsearch certificate to WSO2 Identity Server
 
@@ -80,4 +80,4 @@ To import the certificate, open a terminal window and run the following command.
 
 ## What's Next?
 
-Now that you have prepared WSO2 Identity server for adaptive authentication using ELK analytics, [try an ELK-based adaptive authentication scenario]({{base_path}}/guides/authentication/conditional-auth/elk-risk-based-template).
+Now that you have prepared WSO2 Identity Server for adaptive authentication using ELK analytics, [try an ELK-based adaptive authentication scenario]({{base_path}}/guides/authentication/conditional-auth/elk-risk-based-template).

en/identity-server/7.1.0/docs/deploy/elk-analytics-installation-guide.md

@@ -6,14 +6,14 @@
 
 Follow the steps below to enable ELK-based analytics in WSO2 Identity Server.
 
-1. Download and install WSO2 Identity Server.
+1. Download and install {{product_name}}.
 
     !!! note
         For detailed information, see [Install WSO2 Identity Server]({{base_path}}/deploy/get-started/install/).
 
 2. Open the `deployment.toml` file found in the `<IS_HOME>/repository/conf/` directory and add the following configuration.
 
     ```
     [analytics.elk]
     enable=true
     ```
@@ -29,7 +29,7 @@
 
     - Add the following appender configurations:
 
         ```
         appender.ANALYTICS_EVENT_LOGFILE.type = RollingFile
         appender.ANALYTICS_EVENT_LOGFILE.name = ANALYTICS_EVENT_LOGFILE
         appender.ANALYTICS_EVENT_LOGFILE.fileName =${sys:carbon.home}/repository/logs/analytics_events.log
@@ -52,11 +52,11 @@
             To change the name of the log file and its location, change the **fileName** and **filePattern** parameters accordingly.
 
     - Add `org.wso2.carbon.event.output.adapter.logger.LoggerEventAdapter` to the list of all loggers as follows:
         ```
         loggers = {other loggers}, org-wso2-carbon-event-output-adapter-logger-LoggerEventAdapter
         ```
     - Add the following logger configurations.
         ```
         logger.org-wso2-carbon-event-output-adapter-logger-LoggerEventAdapter.name = org.wso2.carbon.event.output.adapter.logger.LoggerEventAdapter
         logger.org-wso2-carbon-event-output-adapter-logger-LoggerEventAdapter.level = INFO
         logger.org-wso2-carbon-event-output-adapter-logger-LoggerEventAdapter.appenderRef.CUSTOM_LOGFILE.ref = ANALYTICS_EVENT_LOGFILE
@@ -80,8 +80,8 @@
     !!! note
         Take note of the password generated for the `elastic` user.
 
 ### Install Filebeat
 1. [Install Filebeat](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-installation-configuration.html#installation){:target="_blank"} according to your operating system.
 
 2. Open the **filebeat.yml** file in the root directory and add this [configuration](https://github.com/wso2-extensions/identity-elk-integration/blob/main/filebeat/filebeat.yml){:target="_blank"}.
 
@@ -89,7 +89,7 @@
         - Replace `<IS_HOME>` with the location of your WSO2 Identity Server installation.
         - To configure Filebeat to mask sensitive information in logs, follow this [guide]({{base_path}}/deploy/monitor/elk-mask-sensitive-information-in-logs).
 
 
 ### Install Logstash
 
 1. [Install Logstash](https://www.elastic.co/guide/en/logstash/current/installing-logstash.html){:target="_blank"} according to your operating system.
@@ -128,20 +128,20 @@
 
 4. Under **Stack Management** > **Data**, click **Index Management** and go to its **Index Templates** tab.
 
-4. Under the **Index patterns** column, if you have any index patterns created under the following names, delete them before moving to the next step.
+5. Under the **Index patterns** column, if you have any index patterns created under the following names, delete them before moving to the next step.
 
      - wso2-iam-alert-auth*
      - wso2-iam-alert-session*
      - wso2-iam-auth-raw*
      - wso2-iam-session-raw*
      - wso2-iam-session-time-series*
 
-5. Download the artifact file [here](https://github.com/wso2-extensions/identity-elk-integration/blob/main/kibana/saved-objects/kibana-8-x-auth-and-session.ndjson){: target="_blank"}.
+6. Download the artifact file [here](https://github.com/wso2-extensions/identity-elk-integration/blob/main/kibana/saved-objects/kibana-8-x-auth-and-session.ndjson){: target="_blank"}.
 
-6. Under **Stack Management** > **Kibana**, click **Saved Objects**.
+7. Under **Stack Management** > **Kibana**, click **Saved Objects**.
 
-7. Click **Import**, add the downloaded artifact file as an import object, and click **Import**.
+8. Click **Import**, add the downloaded artifact file as an import object, and click **Import**.
 
-8. Once import is complete, click **Done**.
+9. Once import is complete, click **Done**.
 
-9. On the left navigation panel, under **Analytics**, click **Dashboards** to view the created **Auth** and **Session** dashboards.
+10. On the left navigation panel, under **Analytics**, click **Dashboards** to view the created **Auth** and **Session** dashboards.