You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by fh...@apache.org on 2019/09/03 08:12:35 UTC

[flink] branch release-1.8 updated: [hotfix][docs] Minor fixes in operations playground.

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

fhueske pushed a commit to branch release-1.8
in repository https://gitbox.apache.org/repos/asf/flink.git


The following commit(s) were added to refs/heads/release-1.8 by this push:
     new b79c199  [hotfix][docs] Minor fixes in operations playground.
b79c199 is described below

commit b79c19948562ad7ca73e4230a8a817429c1a0381
Author: Fabian Hueske <fh...@apache.org>
AuthorDate: Tue Sep 3 10:11:37 2019 +0200

    [hotfix][docs] Minor fixes in operations playground.
    
    [ci skip]
---
 docs/tutorials/docker-playgrounds/flink-operations-playground.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/tutorials/docker-playgrounds/flink-operations-playground.md b/docs/tutorials/docker-playgrounds/flink-operations-playground.md
index 3c5effc..df16f95 100644
--- a/docs/tutorials/docker-playgrounds/flink-operations-playground.md
+++ b/docs/tutorials/docker-playgrounds/flink-operations-playground.md
@@ -82,7 +82,7 @@ output of the Flink job should show 1000 views per page and window.
 The playground environment is set up in just a few steps. We will walk you through the necessary 
 commands and show how to validate that everything is running correctly.
 
-We assume that you have that you have [docker](https://docs.docker.com/) (1.12+) and
+We assume that you have [Docker](https://docs.docker.com/) (1.12+) and
 [docker-compose](https://docs.docker.com/compose/) (2.1+) installed on your machine.
 
 The required configuration files are available in the 
@@ -204,7 +204,7 @@ docker-compose exec kafka kafka-console-consumer.sh \
 
 Now that you learned how to interact with Flink and the Docker containers, let's have a look at 
 some common operational tasks that you can try out on our playground.
-All of these tasks are independent of each other, i.e.i you can perform them in any order. 
+All of these tasks are independent of each other, i.e. you can perform them in any order. 
 Most tasks can be executed via the [CLI](#flink-cli) and the [REST API](#flink-rest-api).
 
 ### Listing Running Jobs
@@ -277,7 +277,7 @@ an external resource).
 docker-compose kill taskmanager
 {% endhighlight %}
 
-After a few seconds, Flink will notice the loss of the TaskManager, cancel the affected Job, and 
+After a few seconds, the Flink Master will notice the loss of the TaskManager, cancel the affected Job, and 
 immediately resubmit it for recovery.
 When the Job gets restarted, its tasks remain in the `SCHEDULED` state, which is indicated by the 
 counts in the gray colored square (see screenshot below).