Active voice

Author: nastasha-solomon

docs/detections/rules-ui-create.asciidoc

@@ -826,7 +826,7 @@ TIP: Avoid setting long time ranges with short rule intervals, or the rule previ
 
 NOTE: This option is only offered for {esql} and event correlation rules.
 
-When previewing a rule, you can also learn about its {es} queries, which are submitted when the rule runs. This information can be helpful for identifying and troubleshooting potential rule issues. You can also use it to confirm that your rule is retrieving the expected data.    
+When previewing a rule, you can also learn about its {es} queries, which are submitted when the rule runs. This information can help you identify and troubleshoot potential rule issues. You can also use it to confirm that your rule is retrieving the expected data.   
 
 To learn more about your rule's {es} queries, preview its results and do the following:
 
@@ -835,6 +835,6 @@ To learn more about your rule's {es} queries, preview its results and do the fol
 . Expand each row to learn more about the {es} queries that the rule submits each time it executes. The following details are provided:
 ** When the rule execution started, and how long it took to complete
 ** A brief explanation of what the {es} queries do
-** The actual {es} queries that the rule submits to indices containing events that are used during rule execution  
+** The actual {es} queries that the rule submits to indices containing events that are used during the rule execution  
 +
 TIP: Run the queries in Dev Tools (**{kib}** -> **Management** -> **Dev Tools**) to determine if your rule is retrieving the expected data. For example, to test your rule’s exceptions, run the rule’s {es} queries, which will also contain exceptions added to the rule. If your rule’s exceptions are working as intended, the query will not return events that should be ignored.

docs/serverless/rules/rules-ui-create.mdx

@@ -883,7 +883,7 @@ To interact with the rule preview:
 This option is only offered for ((esql)) and event correlation rules.
 </DocCallOut>
 
-When previewing a rule, you can also learn about its ((es)) queries, which are submitted when the rule runs. This information can be helpful for identifying and troubleshooting potential rule issues. You can also use it to confirm that your rule is retrieving the expected data.   
+When previewing a rule, you can also learn about its ((es)) queries, which are submitted when the rule runs. This information can help you identify and troubleshoot potential rule issues. You can also use it to confirm that your rule is retrieving the expected data.   
 
 To learn more about your rule's ((es)) queries, preview its results and do the following:
 
@@ -892,7 +892,7 @@ To learn more about your rule's ((es)) queries, preview its results and do the f
 1. Expand each row to learn more about the ((es)) queries that the rule submits each time it executes. The following details are provided:
     * When it started, and how long it took to complete
     * A brief explanation of what the ((es)) queries do
-    * The actual ((es)) queries that the rule submits to indices containing events that are used during rule execution   
+    * The actual ((es)) queries that the rule submits to indices containing events that are used during the rule execution  
 
         <DocCallOut title="Tip">
         Run the queries in Console (**Developer tools** -> **Console**) to determine if your rule is retrieving the expected data. For example, to test your rule’s exceptions, run the rule’s ((es)) queries, which will also contain exceptions added to the rule. If your rule’s exceptions are working as intended, the query will not return events that should be ignored.