[docs] fixed a few typos in internal_general_arch.md This closes #602
Project: http://git-wip-us.apache.org/repos/asf/flink/repo Commit: http://git-wip-us.apache.org/repos/asf/flink/commit/e2a00183 Tree: http://git-wip-us.apache.org/repos/asf/flink/tree/e2a00183 Diff: http://git-wip-us.apache.org/repos/asf/flink/diff/e2a00183 Branch: refs/heads/master Commit: e2a00183eb539889d7a5053c49b2a296de79add0 Parents: f7ec859 Author: Akshay Dixit <[email protected]> Authored: Wed Apr 15 18:56:55 2015 +0530 Committer: mbalassi <[email protected]> Committed: Fri Apr 17 16:01:34 2015 +0200 ---------------------------------------------------------------------- docs/internal_general_arch.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/flink/blob/e2a00183/docs/internal_general_arch.md ---------------------------------------------------------------------- diff --git a/docs/internal_general_arch.md b/docs/internal_general_arch.md index ec07056..2386a2e 100644 --- a/docs/internal_general_arch.md +++ b/docs/internal_general_arch.md @@ -26,8 +26,8 @@ under the License. ## The Processes When the Flink system is started, it bring up the *JobManager* and one or more *TaskManagers*. The JobManager -is the coordinator of the Flink system, while the TaskManagers are the worksers that execute parts of the -parallel programs. When starting the systen in *local* mode, a single JobManager and TaskManager are brought +is the coordinator of the Flink system, while the TaskManagers are the workers that execute parts of the +parallel programs. When starting the system in *local* mode, a single JobManager and TaskManager are brought up within the same JVM. When a program is submitted, a client is created that performs the pre-processing and turns the program @@ -43,7 +43,7 @@ illustrates the different actors in the system very coarsely. An alternative view on the system is given by the stack below. The different layers of the stack build on top of each other and raise the abstraction level of the program representations they accept: -- The **runtime** layer receive a program in the form of a *JobGraph*. A JobGraph is a generic parallel +- The **runtime** layer receives a program in the form of a *JobGraph*. A JobGraph is a generic parallel data flow with arbitrary tasks that consume and produce data streams. - The **optimizer** and **common api** layer takes programs in the form of operator DAGs. The operators are
