Corrected a minor typographical error.
@@ -253,7 +253,7 @@ To achieve temporal processing,Siddhi uses the following four type of events:
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.
-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.
+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 instead of sending one expired event for each event it has stored, so 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.
