You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by wa...@apache.org on 2022/06/01 01:44:47 UTC

[flink] branch release-1.15 updated: [hotfix][doc] fix typo and enlarge image

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

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


The following commit(s) were added to refs/heads/release-1.15 by this push:
     new 1b2fb4f3781 [hotfix][doc] fix typo and enlarge image
1b2fb4f3781 is described below

commit 1b2fb4f378168353dedc26cff0f8923d742c6f18
Author: Jing Ge <ge...@gmail.com>
AuthorDate: Tue May 31 07:40:59 2022 +0200

    [hotfix][doc] fix typo and enlarge image
    
    This closes #19848.
---
 docs/content/docs/deployment/overview.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/content/docs/deployment/overview.md b/docs/content/docs/deployment/overview.md
index 247605ee811..019cd7b6aac 100644
--- a/docs/content/docs/deployment/overview.md
+++ b/docs/content/docs/deployment/overview.md
@@ -183,7 +183,7 @@ Flink can execute applications in one of three ways:
 
 
 <!-- Image source: https://docs.google.com/drawings/d/1EfloufuOp1A7YDwZmBEsHKRLIrrbtRkoWRPcfZI5RYQ/edit?usp=sharing -->
-{{< img class="img-fluid" width="80%" style="margin: 15px" src="/fig/deployment_modes.svg" alt="Figure for Deployment Modes" >}}
+{{< img class="img-fluid" width="100%" style="margin: 15px" src="/fig/deployment_modes.svg" alt="Figure for Deployment Modes" >}}
 
 ### Application Mode
     
@@ -196,7 +196,7 @@ network bandwidth to download dependencies and ship binaries to the cluster, and
 
 Building on this observation, the *Application Mode* creates a cluster per submitted application, but this time,
 the `main()` method of the application is executed by the *JobManager*. Creating a cluster per application can be 
-seen as creating a session cluster shared only among the jobs of a particular application, and torn down when
+seen as creating a session cluster shared only among the jobs of a particular application, and turning down when
 the application finishes. With this architecture, the *Application Mode* provides the same resource isolation
 and load balancing guarantees as the *Per-Job* mode, but at the granularity of a whole application.