This is an automated email from the ASF dual-hosted git repository.
kurt pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new ae2b82f [hotfix][doc] Typo fixups in the concepts/runtime part of the
website. (#11740)
ae2b82f is described below
commit ae2b82f549c7669f41018594d5b7c6f5e56545e2
Author: Etienne Chauchot <echauc...@apache.org>
AuthorDate: Wed Apr 15 08:22:20 2020 +0200
[hotfix][doc] Typo fixups in the concepts/runtime part of the website.
(#11740)
---
docs/concepts/flink-architecture.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/concepts/flink-architecture.md
b/docs/concepts/flink-architecture.md
index 3bc14dd..183c170 100644
--- a/docs/concepts/flink-architecture.md
+++ b/docs/concepts/flink-architecture.md
@@ -44,7 +44,7 @@ The Flink runtime consists of two types of processes:
tasks, coordinates checkpoints, coordinates recovery on failures, etc.
There is always at least one *Flink Master*. A high-availability setup
- might have multiple *Flink Masters*, one of which one is always the
+ might have multiple *Flink Masters*, one of which is always the
*leader*, and the others are *standby*.
- The *TaskManagers* (also called *workers*) execute the *tasks* (or more
@@ -102,7 +102,7 @@ certain amount of reserved managed memory. Note that no CPU
isolation happens
here; currently slots only separate the managed memory of tasks.
By adjusting the number of task slots, users can define how subtasks are
-isolated from each other. Having one slot per TaskManager means each task
+isolated from each other. Having one slot per TaskManager means that each task
group runs in a separate JVM (which can be started in a separate container, for
example). Having multiple slots means more subtasks share the same JVM. Tasks
in the same JVM share TCP connections (via multiplexing) and heartbeat
