Fixing some errors
@@ -213,7 +213,7 @@ contain a `WindowProcessor`.
The `FilterProcessor` is implemented with an [ExpressionExecutor](https://github.com/wso2/siddhi/blob/master/modules/siddhi-core/src/main/java/org/wso2/siddhi/core/executor/ExpressionExecutor.java)
that returns a boolean value. Expressions have a tree structure, and
they are processed based on the Depth First Search algorithm. To achieve high performance, Siddhi currently depends on the user
-to formulate the least successful case in the leftmost side of the condition, thereby increasing the chance of an early detection of an error.
+to formulate the least successful case in the leftmost side of the condition, thereby increasing the chance of an early `false` detection.
The condition expression `price >= 100 and ( Symbol == 'IBM' or Symbol == 'MSFT' )` is represented as shown below.
@@ -246,14 +246,14 @@ To achieve temporal processing,Siddhi uses the following four type of events:
* **Expired Events**: Events that have expired from a window.
-* **Timer Events**: Events that inform the query about an update of an execution time. These events are usually generated by schedulers.
+* **Timer Events**: Events that inform the query about an update of execution time. These events are usually generated by schedulers.
* **Reset Events**: Events that resets the Siddhi query states.
In Siddhi, when an event comes into a [WindowProcessor](https://github.com/wso2/siddhi/blob/master/modules/siddhi-core/src/main/java/org/wso2/siddhi/core/query/processor/stream/window/WindowProcessor.java),
it creates an appropriate expired event corresponding to the incoming current event with the expiring timestamp, and stores that
event in the window. The `WindowProcessor` also forwards the current event to the next processor for further processing.
-t uses a scheduler or such to determine when to emit the events it has in memory. During that time, it emits these events as expired events. If it emits all the events in the memory at once, it emits a single reset event in one go instead of sending one expired event for each event it has stored to reset. For each current event emitted from a window, a corresponding expired event must be emitted. If not, a common reset event must be emitted.
+It uses a scheduler or such to determine when to emit the events it has in memory. During that time, it emits these events as expired events. If it needs to emit all the events in the memory at once, it emits a single reset event interred of sending one expired event for each event it has stored, such that it can reset the states in one go. For each current event emitted from a window, a corresponding expired event must be emitted. If not, a common reset event must be emitted.
This is vital in Siddhi because Siddhi relies on these events to calculate the Aggregations at the `QuerySelector`.
In the `QuerySelector`, the arrived current events increase the aggregation values, expired events decrease the values, and
reset events reset the aggregation calculation.
