klion26 commented on a change in pull request #9648:
URL: https://github.com/apache/flink/pull/9648#discussion_r447418939
##########
File path: docs/try-flink/flink-operations-playground.zh.md
##########
@@ -1,6 +1,6 @@
---
-title: "Flink 运维操场"
-nav-title: 'Flink 运维操场'
+title: "Flink操作场景"
Review comment:
```suggestion
title: "Flink 操作场景"
```
中文和英文中间需要有空格，详情可以参考[translation
wiki](https://cwiki.apache.org/confluence/display/FLINK/Flink+Translation+Specifications)
其他地方也一起修改一下。
修改完成之后，可以在本地执行 `./docs/docker/run.sh` 然后再执行 `./build_docs.sh -p` 打开
localhost:4000 查看最终的效果
##########
File path: docs/try-flink/flink-operations-playground.zh.md
##########
@@ -23,80 +23,71 @@ specific language governing permissions and limitations
under the License.
-->
-There are many ways to deploy and operate Apache Flink in various
environments. Regardless of this
-variety, the fundamental building blocks of a Flink Cluster remain the same,
and similar
-operational principles apply.
+在多环境下部署和操作Apache Flink可以有很多种方式，抛开这种多样性而言，Flink集群的基本构建方式和操作原则仍然是相同的。
Review comment:
`在多环境下部署和操作Apache Flink可以有很多种方式` 这个地方如果改成 `Apache Flink
可以以多种方式在不同的环境中部署` 会好一点吗？
##########
File path: docs/try-flink/flink-operations-playground.zh.md
##########
@@ -23,80 +23,71 @@ specific language governing permissions and limitations
under the License.
-->
-There are many ways to deploy and operate Apache Flink in various
environments. Regardless of this
-variety, the fundamental building blocks of a Flink Cluster remain the same,
and similar
-operational principles apply.
+在多环境下部署和操作Apache Flink可以有很多种方式，抛开这种多样性而言，Flink集群的基本构建方式和操作原则仍然是相同的。
-In this playground, you will learn how to manage and run Flink Jobs. You will
see how to deploy and
-monitor an application, experience how Flink recovers from Job failure, and
perform everyday
-operational tasks like upgrades and rescaling.
+在这篇文章里，你将会学习如何管理和运行Flink任务，了解如何部署和监控应用程序、Flink如何从失败作业中进行恢复，同时你还会学习如何执行一些日常操作任务，如升级和扩容。
{% if site.version contains "SNAPSHOT" %}
<p style="border-radius: 5px; padding: 5px" class="bg-danger">
<b>
- NOTE: The Apache Flink Docker images used for this playground are only
available for
- released versions of Apache Flink.
+ 注意：本文中使用的Apache Flink Docker镜像仅适用于Apache Flink发行版。
</b><br>
- Since you are currently looking at the latest SNAPSHOT
- version of the documentation, all version references below will not work.
- Please switch the documentation to the latest released version via the
release picker which you
- find on the left side below the menu.
+ 由于你目前正在浏览快照版的文档，因此下文中引用的分支可能已经不存在了。
+ 请先通过左侧菜单下方的版本选择器切换到发行版文档再查看。
</p>
{% endif %}
* This will be replaced by the TOC
{:toc}
-## Anatomy of this Playground
+## 场景说明
-This playground consists of a long living
-[Flink Session Cluster]({{ site.baseurl
}}/concepts/glossary.html#flink-session-cluster) and a Kafka
-Cluster.
+这篇文章中的所有操作都是基于一个
+[Flink Session Cluster]({{ site.baseurl
}}/concepts/glossary.html#flink-session-cluster) 和一个Kafka集群进行的，
+我们会在下文带领大家一起搭建这两个集群。
-A Flink Cluster always consists of a
-[JobManager]({{ site.baseurl }}/concepts/glossary.html#flink-jobmanager) and
one or more
-[Flink TaskManagers]({{ site.baseurl
}}/concepts/glossary.html#flink-taskmanager). The JobManager
-is responsible for handling [Job]({{ site.baseurl
}}/concepts/glossary.html#flink-job) submissions,
-the supervision of Jobs as well as resource management. The Flink TaskManagers
are the worker
-processes and are responsible for the execution of the actual
-[Tasks]({{ site.baseurl }}/concepts/glossary.html#task) which make up a Flink
Job. In this
-playground you will start with a single TaskManager, but scale out to more
TaskManagers later.
-Additionally, this playground comes with a dedicated *client* container, which
we use to submit the
-Flink Job initially and to perform various operational tasks later on. The
*client* container is not
-needed by the Flink Cluster itself but only included for ease of use.
+一个Flink集群总是包含一个
+[JobManager]({{ site.baseurl }}/concepts/glossary.html#flink-jobmanager)
以及一个或多个
+[Flink TaskManager]({{ site.baseurl
}}/concepts/glossary.html#flink-taskmanager)。JobManager
+负责处理 [Job]({{ site.baseurl }}/concepts/glossary.html#flink-job) 提交、
+Job监控以及资源管理。Flink TaskManager 运行worker进程，
+负责实际任务
+[Tasks]({{ site.baseurl }}/concepts/glossary.html#task) 的执行，而这些任务共同组成了一个 Flink
Job。 在这篇文章中，
+我们会先运行一个 TaskManager，接下来会扩容到多个 TaskManager。
+另外，这里我们会使用一个 *客户端* 容器（已废弃）来提交Flink Job，
Review comment:
这个地方的 `已废弃` 是从什么地方翻译过来的呢？ dedicated 是指专门的？
##########
File path: docs/try-flink/flink-operations-playground.zh.md
##########
@@ -1,6 +1,6 @@
---
-title: "Flink 运维操场"
-nav-title: 'Flink 运维操场'
+title: "Flink操作场景"
+nav-title: 'Flink操作场景'
Review comment:
```suggestion
nav-title: 'Flink 操作场景'
```
##########
File path: docs/try-flink/flink-operations-playground.zh.md
##########
@@ -23,80 +23,71 @@ specific language governing permissions and limitations
under the License.
-->
-There are many ways to deploy and operate Apache Flink in various
environments. Regardless of this
-variety, the fundamental building blocks of a Flink Cluster remain the same,
and similar
-operational principles apply.
+在多环境下部署和操作Apache Flink可以有很多种方式，抛开这种多样性而言，Flink集群的基本构建方式和操作原则仍然是相同的。
-In this playground, you will learn how to manage and run Flink Jobs. You will
see how to deploy and
-monitor an application, experience how Flink recovers from Job failure, and
perform everyday
-operational tasks like upgrades and rescaling.
+在这篇文章里，你将会学习如何管理和运行Flink任务，了解如何部署和监控应用程序、Flink如何从失败作业中进行恢复，同时你还会学习如何执行一些日常操作任务，如升级和扩容。
{% if site.version contains "SNAPSHOT" %}
<p style="border-radius: 5px; padding: 5px" class="bg-danger">
<b>
- NOTE: The Apache Flink Docker images used for this playground are only
available for
- released versions of Apache Flink.
+ 注意：本文中使用的Apache Flink Docker镜像仅适用于Apache Flink发行版。
</b><br>
- Since you are currently looking at the latest SNAPSHOT
- version of the documentation, all version references below will not work.
- Please switch the documentation to the latest released version via the
release picker which you
- find on the left side below the menu.
+ 由于你目前正在浏览快照版的文档，因此下文中引用的分支可能已经不存在了。
+ 请先通过左侧菜单下方的版本选择器切换到发行版文档再查看。
</p>
{% endif %}
* This will be replaced by the TOC
{:toc}
-## Anatomy of this Playground
+## 场景说明
-This playground consists of a long living
-[Flink Session Cluster]({{ site.baseurl
}}/concepts/glossary.html#flink-session-cluster) and a Kafka
-Cluster.
+这篇文章中的所有操作都是基于一个
+[Flink Session Cluster]({{ site.baseurl
}}/concepts/glossary.html#flink-session-cluster) 和一个Kafka集群进行的，
Review comment:
现在社区建议使用的链接形式为
`{%link concepts/glossary.zh.md}#flink-session-cluster`
本文其他链接也一起修改一下吧
具体可以参考 [mail
list](http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Reminder-Prefer-link-tag-in-documentation-td42362.html)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
