Fix doc build failures

elastic · Jun 11, 2024 · 344d2e5 · 344d2e5
1 parent 53e6fdd
commit 344d2e5
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 8 deletions.
diff --git a/...2-14/prebuilt-rule-8-12-14-potential-persistence-via-file-modification.asciidoc b/...2-14/prebuilt-rule-8-12-14-potential-persistence-via-file-modification.asciidoc
@@ -58,10 +58,10 @@ To configure the Elastic FIM integration, follow these steps:
 2. Once the Elastic Agent is installed, navigate to the Elastic Security app in Kibana.
 3. In the Kibana home page, click on "Integrations" in the left sidebar.
 4. Search for "File Integrity Monitoring" in the search bar and select the integration.
-6. Provide a name and optional description for the integration.
-7. Select the appropriate agent policy for your Linux system or create a new one.
-8. Configure the FIM policy by specifying the paths that you want to monitor for file modifications. You can use the same paths mentioned in the `query` field of the rule. Note that FIM does not accept wildcards in the paths, so you need to specify the exact paths you want to monitor.
-9. Save the configuration and the Elastic Agent will start monitoring the specified paths for file modifications.
+5. Provide a name and optional description for the integration.
+6. Select the appropriate agent policy for your Linux system or create a new one.
+7. Configure the FIM policy by specifying the paths that you want to monitor for file modifications. You can use the same paths mentioned in the `query` field of the rule. Note that FIM does not accept wildcards in the paths, so you need to specify the exact paths you want to monitor.
+8. Save the configuration and the Elastic Agent will start monitoring the specified paths for file modifications.
 
 For more details on configuring the Elastic FIM integration, you can refer to the https://docs.elastic.co/integrations/fim[Elastic FIM documentation].
 

diff --git a/...rebuilt-rules/rule-details/potential-persistence-via-file-modification.asciidoc b/...rebuilt-rules/rule-details/potential-persistence-via-file-modification.asciidoc
@@ -58,10 +58,10 @@ To configure the Elastic FIM integration, follow these steps:
 2. Once the Elastic Agent is installed, navigate to the Elastic Security app in Kibana.
 3. In the Kibana home page, click on "Integrations" in the left sidebar.
 4. Search for "File Integrity Monitoring" in the search bar and select the integration.
-6. Provide a name and optional description for the integration.
-7. Select the appropriate agent policy for your Linux system or create a new one.
-8. Configure the FIM policy by specifying the paths that you want to monitor for file modifications. You can use the same paths mentioned in the `query` field of the rule. Note that FIM does not accept wildcards in the paths, so you need to specify the exact paths you want to monitor.
-9. Save the configuration and the Elastic Agent will start monitoring the specified paths for file modifications.
+5. Provide a name and optional description for the integration.
+6. Select the appropriate agent policy for your Linux system or create a new one.
+7. Configure the FIM policy by specifying the paths that you want to monitor for file modifications. You can use the same paths mentioned in the `query` field of the rule. Note that FIM does not accept wildcards in the paths, so you need to specify the exact paths you want to monitor.
+8. Save the configuration and the Elastic Agent will start monitoring the specified paths for file modifications.
 
 For more details on configuring the Elastic FIM integration, you can refer to the https://docs.elastic.co/integrations/fim[Elastic FIM documentation].