This is an automated email from the ASF dual-hosted git repository.

sewen pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git

commit 7b46f6046a909e20f1bd9083c5913a394cc578b0
Author: Humberto Rodríguez A <rhumber...@users.noreply.github.com>
AuthorDate: Fri Apr 26 16:31:51 2019 +0200

    [hotfix] [docs] Fix typo in "Window Operator" documentation
    
    Before: ... windows together if `their` are closer to each
    After: ... windows together if `they` are closer to each
    
    This closes #8285
---
 docs/dev/stream/operators/windows.md    | 2 +-
 docs/dev/stream/operators/windows.zh.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/dev/stream/operators/windows.md 
b/docs/dev/stream/operators/windows.md
index 5861463..d317b2e 100644
--- a/docs/dev/stream/operators/windows.md
+++ b/docs/dev/stream/operators/windows.md
@@ -371,7 +371,7 @@ Dynamic gaps are specified by implementing the 
`SessionWindowTimeGapExtractor` i
 
 <span class="label label-danger">Attention</span> Since session windows do not 
have a fixed start and end,
 they are  evaluated differently than tumbling and sliding windows. Internally, 
a session window operator
-creates a new window for each arriving record and merges windows together if 
their are closer to each other
+creates a new window for each arriving record and merges windows together if 
they are closer to each other
 than the defined gap.
 In order to be mergeable, a session window operator requires a merging 
[Trigger](#triggers) and a merging
 [Window Function](#window-functions), such as `ReduceFunction`, 
`AggregateFunction`, or `ProcessWindowFunction`
diff --git a/docs/dev/stream/operators/windows.zh.md 
b/docs/dev/stream/operators/windows.zh.md
index 2f32d8a..45ef36f 100644
--- a/docs/dev/stream/operators/windows.zh.md
+++ b/docs/dev/stream/operators/windows.zh.md
@@ -371,7 +371,7 @@ Dynamic gaps are specified by implementing the 
`SessionWindowTimeGapExtractor` i
 
 <span class="label label-danger">Attention</span> Since session windows do not 
have a fixed start and end,
 they are  evaluated differently than tumbling and sliding windows. Internally, 
a session window operator
-creates a new window for each arriving record and merges windows together if 
their are closer to each other
+creates a new window for each arriving record and merges windows together if 
they are closer to each other
 than the defined gap.
 In order to be mergeable, a session window operator requires a merging 
[Trigger](#triggers) and a merging
 [Window Function](#window-functions), such as `ReduceFunction`, 
`AggregateFunction`, or `ProcessWindowFunction`

Reply via email to