Adding clarity

Author: ankitscribbles

articles/iot-central/howto-create-event-rules.md

@@ -61,10 +61,10 @@ Condition defines the criteria that is monitored by the rule.
 
 1. Optionally, you can also set **Count** as **Aggregation** and provide the corresponding threshold.
 
-    - Without aggregation, the rule triggers for each event data point that meets the condition. For example, if the rule is configured to trigger when a 'Fan Motor Error' event occurs then the rule will trigger almost instantaneously when the device reports that event.
-    - If Count is used as an aggregate function, then you have to  provide a **Threshold** and an **Aggregate time window** over which the condition needs to be evaluated. In this case, the count of events are aggregated and the rule will trigger only if the aggregated event count matches the threshold.
+    - Without aggregation, the rule triggers for each event data point that meets the condition. For example, if you configure the rule's condition to trigger when a 'Fan Motor Error' event occurs then the rule will trigger almost immediately when the device reports that event.
+    - If Count is used as an aggregate function, then you have to  provide a **Threshold** and an **Aggregate time window** over which the condition needs to be evaluated. In this case, the count of events is aggregated and the rule will trigger only if the aggregated event count matches the threshold.
 
-    For example, if you want to alert when there are more than three device events within 5 minutes, then select the event and set the aggregate function as "count",  operator as "greater than", and "threshold" as 3. Set "Aggregation time period" as "5 minutes". The rule triggers when more than three events are sent by the device within 5 minutes. The rule evaluation frequency is the same as the **Aggregate time window**, which means the rule is  evaluated once every 5 minutes in this example. 
+    For example, if you want to alert when there are more than three device events within 5 minutes, then select the event and set the aggregate function as "count",  operator as "greater than", and "threshold" as 3. Set "Aggregation time period" as "5 minutes". The rule triggers when more than three events are sent by the device within 5 minutes. The rule evaluation frequency is the same as the **Aggregate time window**, which means, in this example, the rule is  evaluated once every 5 minutes. 
 
     ![Add Event Condition](media\howto-create-event-rules\Aggregate_Condition_Filled_Out.png)
 

articles/iot-central/howto-create-telemetry-rules.md

@@ -58,7 +58,7 @@ Condition defines the criteria that is monitored by the rule.
 
 1. Next, choose **Aggregation**, **Operator**, and provide a **Threshold** value.
     - Aggregation is optional. Without aggregation, the rule triggers for each telemetry data point that meets the condition. For example, if the rule is configured to trigger when temperature is above 80 then the rule will trigger almost instantly when the device reports temperature > 80.
-    - If an aggregate function like Average, Min, Max, Count is chosen then, the user must provide an **Aggregate time window** over which the condition needs to be evaluated. For example, if you set the period as "5 minutes" and your rule looks for Average temperature above 80, the rule triggers when the average temperature is above 80 for at least 5 minutes. The rule evaluation frequency is the same as the **Aggregate time window**, which means the rule is evaluated once every 5 minutes in this example.
+    - If an aggregate function like Average, Min, Max, Count is chosen then, the user must provide an **Aggregate time window** over which the condition needs to be evaluated. For example, if you set the period as "5 minutes" and your rule looks for Average temperature above 80, the rule triggers when the average temperature is above 80 for at least 5 minutes. The rule evaluation frequency is the same as the **Aggregate time window**, which means, in this example, the rule is evaluated once every 5 minutes.
 
     >[!NOTE]
     >More than one telemetry measurement can be added under **Condition**. When multiple conditions are specified, all the conditions must be met for the rule to trigger. Each conditon gets joined by an 'AND' clause implicitly. When using aggregate, every measurement must be aggregated.