diff --git a/docs/en/start-v2/docker/docker.md b/docs/en/start-v2/docker/docker.md
index fd927deabbd..111df5b20c9 100644
--- a/docs/en/start-v2/docker/docker.md
+++ b/docs/en/start-v2/docker/docker.md
@@ -3,7 +3,7 @@
 sidebar_position: 3
 -------------------
 
-# Set Up with Docker
+# Set Up With Docker
 
 <!-- TODO -->
 -->
diff --git a/docs/en/start-v2/kubernetes/kubernetes.mdx b/docs/en/start-v2/kubernetes/kubernetes.mdx
index ebf2afc9ab8..b40e561ec72 100644
--- a/docs/en/start-v2/kubernetes/kubernetes.mdx
+++ b/docs/en/start-v2/kubernetes/kubernetes.mdx
@@ -7,11 +7,11 @@ import TabItem from '@theme/TabItem';
 
 # Set Up with Kubernetes
 
-This section provides a quick guide to using SeaTunnel with Kubernetes.
+This section provides a quick guide to use SeaTunnel with Kubernetes.
 
 ## Prerequisites
 
-We assume that you have a local installations of the following:
+We assume that you have one local installation as follow:
 
 - [docker](https://docs.docker.com/)
 - [kubernetes](https://kubernetes.io/)
@@ -19,7 +19,7 @@ We assume that you have a local installations of the following:
 
 So that the `kubectl` and `helm` commands are available on your local system.
 
-For kubernetes [minikube](https://minikube.sigs.k8s.io/docs/start/) is our choice, at the time of writing this we are using version v1.23.3. You can start a cluster with the following command:
+Take kubernetes [minikube](https://minikube.sigs.k8s.io/docs/start/) as an example, you can start a cluster with the following command:
 
 ```bash
 minikube start --kubernetes-version=v1.23.3
@@ -27,7 +27,7 @@ minikube start --kubernetes-version=v1.23.3
 
 ## Installation
 
-### SeaTunnel docker image
+### SeaTunnel Docker Image
 
 To run the image with SeaTunnel, first create a `Dockerfile`:
 
@@ -58,7 +58,7 @@ Then run the following commands to build the image:
 ```bash
 docker build -t seatunnel:2.3.6-flink-1.13 -f Dockerfile .
 ```
-Image `seatunnel:2.3.6-flink-1.13` need to be present in the host (minikube) so that the deployment can take place.
+Image `seatunnel:2.3.6-flink-1.13` needs to be present in the host (minikube) so that the deployment can take place.
 
 Load image to minikube via:
 ```bash
@@ -114,7 +114,7 @@ Then run the following commands to build the image:
 ```bash
 docker build -t seatunnel:2.3.6 -f Dockerfile .
 ```
-Image `seatunnel:2.3.6` need to be present in the host (minikube) so that the deployment can take place.
+Image `seatunnel:2.3.6` needs to be present in the host (minikube) so that the deployment can take place.
 
 Load image to minikube via:
 ```bash
@@ -125,7 +125,7 @@ minikube image load seatunnel:2.3.6
 </Tabs>
 
 
-### Deploying the operator
+### Deploying The Operator
 
 <Tabs
   groupId="engine-type"
@@ -191,7 +191,7 @@ none
   ]}>
 <TabItem value="flink">
 
-In this guide we are going to use [seatunnel.streaming.conf](https://github.com/apache/seatunnel/blob/2.3.6-release/config/v2.streaming.conf.template):
+In this guide we will use [seatunnel.streaming.conf](https://github.com/apache/seatunnel/blob/2.3.6-release/config/v2.streaming.conf.template):
 
 ```conf
 env {
@@ -291,7 +291,7 @@ kubectl apply -f seatunnel-flink.yaml
 
 <TabItem value="Zeta (local-mode)">
 
-In this guide we are going to use [seatunnel.streaming.conf](https://github.com/apache/seatunnel/blob/2.3.6-release/config/v2.streaming.conf.template):
+In this guide we will use [seatunnel.streaming.conf](https://github.com/apache/seatunnel/blob/2.3.6-release/config/v2.streaming.conf.template):
 
 ```conf
 env {
@@ -366,7 +366,7 @@ kubectl apply -f seatunnel.yaml
 
 <TabItem value="Zeta (cluster-mode)">
 
-In this guide we are going to use [seatunnel.streaming.conf](https://github.com/apache/seatunnel/blob/2.3.6-release/config/v2.streaming.conf.template):
+In this guide we will use [seatunnel.streaming.conf](https://github.com/apache/seatunnel/blob/2.3.6-release/config/v2.streaming.conf.template):
 
 ```conf
 env {
@@ -572,7 +572,7 @@ spec:
 ```bash
 kubectl apply -f seatunnel-cluster.yml
 ```
-Then modify the seatunnel configuration in pod using the following command
+Then modify the seatunnel configuration in pod using the following command:
 
 ```bash
 kubectl edit cm hazelcast
@@ -768,5 +768,5 @@ Happy SeaTunneling!
 
 ## What's More
 
-For now, you are already taking a quick look at SeaTunnel, you could see [connector](/category/connector) to find all source and sink SeaTunnel supported.
+For now, you have taken a quick look at SeaTunnel, and you can see [connector](/category/connector) to find all sources and sinks SeaTunnel supported.
 Or see [deployment](../deployment.mdx) if you want to submit your application in another kind of your engine cluster.
diff --git a/docs/en/start-v2/locally/deployment.md b/docs/en/start-v2/locally/deployment.md
index 4e063eafd50..69cf5164e95 100644
--- a/docs/en/start-v2/locally/deployment.md
+++ b/docs/en/start-v2/locally/deployment.md
@@ -16,9 +16,9 @@ Before starting to download SeaTunnel, you need to ensure that you have installe
 
 ## Step 2: Download SeaTunnel
 
-Go to the [seatunnel download page](https://seatunnel.apache.org/download) to download the latest version of the release version installation package `seatunnel-<version>-bin.tar.gz`.
+Visit the [SeaTunnel Download Page](https://seatunnel.apache.org/download) to download the latest binary package `seatunnel-<version>-bin.tar.gz`.
 
-Or you can also download it through the terminal.
+Or you can also download it through the terminal:
 
 ```shell
 export version="2.3.6"
@@ -26,21 +26,21 @@ wget "https://archive.apache.org/dist/seatunnel/${version}/apache-seatunnel-${ve
 tar -xzvf "apache-seatunnel-${version}-bin.tar.gz"
 ```
 
-## Step 3: Download the connector plug-in
+## Step 3: Download The Connector Plugins
 
-Starting from the 2.2.0-beta version, the binary package no longer provides the connector dependency by default. Therefore, when using it for the first time, you need to execute the following command to install the connector: (Of course, you can also manually download the connector from the [Apache Maven Repository](https://repo.maven.apache.org/maven2/org/apache/seatunnel/), and then move it to the `connectors/seatunnel` directory).
+Starting from the 2.2.0-beta version, the binary package no longer provides the connector dependencies by default. Therefore, when using it for the first time, you need to execute the following command to install the connectors (Of course, you can also manually download the connector from the [Apache Maven Repository](https://repo.maven.apache.org/maven2/org/apache/seatunnel/), and then move it to the `connectors/seatunnel` directory) :
 
 ```bash
-sh bin/install-plugin.sh 2.3.6
+sh bin/install-plugin.sh
 ```
 
-If you need a specific connector version, taking 2.3.6 as an example, you need to execute the following command.
+If you need a specific connector version, taking 2.3.6 as an example, you need to execute the following command:
 
 ```bash
 sh bin/install-plugin.sh 2.3.6
 ```
 
-Usually you don't need all the connector plugins, so you can specify the plugins you need through configuring `config/plugin_config`, for example, if you only need the `connector-console` plugin, then you can modify the plugin.properties configuration file as follows.
+Usually you don't need all connector plugins, so you can specify the plugins you need through configuring `config/plugin_config`. For example, if you only need the `connector-console` plugin, you can modify the plugin.properties configuration file as follows:
 
 ```plugin_config
 --seatunnel-connectors--
@@ -61,14 +61,14 @@ You can find all supported connectors and the corresponding plugin_config config
 
 :::tip Tip
 
-If you want to install connector plugins by manually downloading connectors, you only need to download the connector plugins you need and place them in the `${SEATUNNEL_HOME}/connectors/` directory
+If you want to install connector plugins by manually downloading connectors, you only need to download the related connector plugins and place them in the `${SEATUNNEL_HOME}/connectors/` directory.
 
 :::
 
-Now you have completed the download of the SeaTunnel installation package and the download of the connector plug-in. Next, you can choose different running modes according to your needs to run or deploy SeaTunnel.
+Now you have downloaded the SeaTunnel binary package and the connector plugins. Next, you can choose different engine option to run synchronization tasks.
 
-If you use Flink to run the synchronization task, in this mode, there is no need to deploy the SeaTunnel Engine service cluster. You can refer to [Quick Start of SeaTunnel Flink Engine](quick-start-flink.md) to run your synchronization task.
+If you use Flink to run the synchronization task, there is no need to deploy the SeaTunnel Engine service cluster. You can refer to [Quick Start of SeaTunnel Flink Engine](quick-start-flink.md) to run your synchronization task.
 
-If you use Spark to run the synchronization task, in this mode, there is no need to deploy the SeaTunnel Engine service cluster. You can refer to [Quick Start of SeaTunnel Spark Engine](quick-start-spark.md) to run your synchronization task.
+If you use Spark to run the synchronization task, there is no need to deploy the SeaTunnel Engine service cluster. You can refer to [Quick Start of SeaTunnel Spark Engine](quick-start-spark.md) to run your synchronization task.
 
-If you use the SeaTunnel Engine (Zeta) that comes with SeaTunnel to run tasks, you need to deploy the SeaTunnel Engine service first. Refer to [Deployment of SeaTunnel Engine (Zeta) Service](quick-start-seatunnel-engine.md).
+If you use the builtin SeaTunnel Engine (Zeta) to run tasks, you need to deploy the SeaTunnel Engine service first. Refer to [Deployment of SeaTunnel Engine (Zeta) Service](quick-start-seatunnel-engine.md).
diff --git a/docs/en/start-v2/locally/quick-start-flink.md b/docs/en/start-v2/locally/quick-start-flink.md
index 2a7482ca222..fcb5ab40930 100644
--- a/docs/en/start-v2/locally/quick-start-flink.md
+++ b/docs/en/start-v2/locally/quick-start-flink.md
@@ -5,18 +5,17 @@ sidebar_position: 3
 
 # Quick Start With Flink
 
-## Step 1: Deployment SeaTunnel And Connectors
+## Step 1: Deploy SeaTunnel And Connectors
 
-Before starting, make sure you have downloaded and deployed SeaTunnel as described in [deployment](deployment.md)
+Before starting, make sure you have downloaded and deployed SeaTunnel as described in [Deployment](deployment.md)
 
 ## Step 2: Deployment And Config Flink
 
-Please [download Flink](https://flink.apache.org/downloads.html) first(**required version >= 1.12.0**). For more information you could see [Getting Started: standalone](https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/resource-providers/standalone/overview/)
+Please [Download Flink](https://flink.apache.org/downloads.html) first(**required version >= 1.12.0**). For more information you can see [Getting Started: Standalone](https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/resource-providers/standalone/overview/)
 
-**Configure SeaTunnel**: Change the setting in `config/seatunnel-env.sh`, it is base on the path your engine install at [deployment](deployment.md).
-Change `FLINK_HOME` to the Flink deployment dir.
+**Configure SeaTunnel**: Change the setting in `${SEATUNNEL_HOME}/config/seatunnel-env.sh` and set `FLINK_HOME` to the Flink deployment dir.
 
-## Step 3: Add Job Config File to define a job
+## Step 3: Add Job Config File To Define A Job
 
 Edit `config/v2.streaming.conf.template`, which determines the way and logic of data input, processing, and output after seatunnel is started.
 The following is an example of the configuration file, which is the same as the example application mentioned above.
@@ -59,30 +58,30 @@ sink {
 
 ```
 
-More information about config please check [config concept](../../concept/config.md)
+More information about config please check [Config Concept](../../concept/config.md)
 
 ## Step 4: Run SeaTunnel Application
 
-You could start the application by the following commands
+You can start the application by the following commands:
 
-flink version between `1.12.x` and `1.14.x`
+Flink version between `1.12.x` and `1.14.x`
 
 ```shell
 cd "apache-seatunnel-${version}"
 ./bin/start-seatunnel-flink-13-connector-v2.sh --config ./config/v2.streaming.conf.template
 ```
 
-flink version between `1.15.x` and `1.16.x`
+Flink version between `1.15.x` and `1.16.x`
 
 ```shell
 cd "apache-seatunnel-${version}"
 ./bin/start-seatunnel-flink-15-connector-v2.sh --config ./config/v2.streaming.conf.template
 ```
 
-**See The Output**: When you run the command, you could see its output in your console. You can think this
-is a sign that the command ran successfully or not.
+**See The Output**: When you run the command, you can see its output in your console. This
+is a sign to determine whether the command ran successfully or not.
 
-The SeaTunnel console will prints some logs as below:
+The SeaTunnel console will print some logs as below:
 
 ```shell
 fields : name, age
@@ -107,7 +106,7 @@ row=16 : SGZCr, 94186144
 
 ## What's More
 
-For now, you are already take a quick look about SeaTunnel with Flink, you could see [connector](/docs/category/connector-v2) to find all
-source and sink SeaTunnel supported. Or see [SeaTunnel With Flink](../../other-engine/flink.md) if you want to know more about SeaTunnel Run With Flink.
+For now, you have taken a quick look about SeaTunnel with Flink, and you can see [Connector](/docs/category/connector-v2) to find all
+sources and sinks SeaTunnel supported. Or see [SeaTunnel With Flink](../../other-engine/flink.md) if you want to know more about SeaTunnel With Flink.
 
-SeaTunnel have an own engine named `Zeta` and `Zeta` is the default engine of SeaTunnel. You can follow [Quick Start](quick-start-seatunnel-engine.md) to configure and run a data synchronization job.
+SeaTunnel have a builtin engine named `Zeta`, and it's the default engine of SeaTunnel. You can follow [Quick Start](quick-start-seatunnel-engine.md) to configure and run a data synchronization job.
diff --git a/docs/en/start-v2/locally/quick-start-seatunnel-engine.md b/docs/en/start-v2/locally/quick-start-seatunnel-engine.md
index dff334624af..10814f0050f 100644
--- a/docs/en/start-v2/locally/quick-start-seatunnel-engine.md
+++ b/docs/en/start-v2/locally/quick-start-seatunnel-engine.md
@@ -5,11 +5,11 @@ sidebar_position: 2
 
 # Quick Start With SeaTunnel Engine
 
-## Step 1: Deployment SeaTunnel And Connectors
+## Step 1: Deploy SeaTunnel And Connectors
 
-Before starting, make sure you have downloaded and deployed SeaTunnel as described in [deployment](deployment.md)
+Before starting, make sure you have downloaded and deployed SeaTunnel as described in [Deployment](deployment.md)
 
-## Step 2: Add Job Config File to define a job
+## Step 2: Add Job Config File To Define A Job
 
 Edit `config/v2.batch.config.template`, which determines the way and logic of data input, processing, and output after seatunnel is started.
 The following is an example of the configuration file, which is the same as the example application mentioned above.
@@ -52,11 +52,11 @@ sink {
 
 ```
 
-More information about config please check [config concept](../../concept/config.md)
+More information can be found in [Config Concept](../../concept/config.md)
 
 ## Step 3: Run SeaTunnel Application
 
-You could start the application by the following commands
+You could start the application by the following commands:
 
 :::tip
 
@@ -70,10 +70,10 @@ cd "apache-seatunnel-${version}"
 
 ```
 
-**See The Output**: When you run the command, you could see its output in your console. You can think this
-is a sign that the command ran successfully or not.
+**See The Output**: When you run the command, you can see its output in your console. This
+is a sign to determine whether the command ran successfully or not.
 
-The SeaTunnel console will prints some logs as below:
+The SeaTunnel console will print some logs as below:
 
 ```shell
 2022-12-19 11:01:45,417 INFO  org.apache.seatunnel.connectors.seatunnel.console.sink.ConsoleSinkWriter - output rowType: name<STRING>, age<INT>
@@ -97,5 +97,5 @@ The SeaTunnel console will prints some logs as below:
 
 ## What's More
 
-For now, you are already take a quick look about SeaTunnel, you could see [connector](../../connector-v2/source/FakeSource.md) to find all
-source and sink SeaTunnel supported. Or see [SeaTunnel Engine(Zeta)](../../seatunnel-engine/about.md) if you want to know more about SeaTunnel Engine. Here you will learn how to deploy SeaTunnel Engine in cluster mode and how to use it in cluster mode.
+For now, you have taken a quick look about SeaTunnel, and you can see [connector](../../connector-v2/source/FakeSource.md) to find all
+sources and sinks SeaTunnel supported. Or see [SeaTunnel Engine(Zeta)](../../seatunnel-engine/about.md) if you want to know more about SeaTunnel Engine. Here you will learn how to deploy SeaTunnel Engine and how to use it in cluster mode.
diff --git a/docs/en/start-v2/locally/quick-start-spark.md b/docs/en/start-v2/locally/quick-start-spark.md
index e057d479be2..160da9498cb 100644
--- a/docs/en/start-v2/locally/quick-start-spark.md
+++ b/docs/en/start-v2/locally/quick-start-spark.md
@@ -7,17 +7,16 @@ sidebar_position: 4
 
 ## Step 1: Deployment SeaTunnel And Connectors
 
-Before starting, make sure you have downloaded and deployed SeaTunnel as described in [deployment](deployment.md)
+Before starting, make sure you have downloaded and deployed SeaTunnel as described in [Deployment](deployment.md)
 
-## Step 2: Deployment And Config Spark
+## Step 2: Deploy And Config Spark
 
-Please [download Spark](https://spark.apache.org/downloads.html) first(**required version >= 2.4.0**). For more information you could
-see [Getting Started: standalone](https://spark.apache.org/docs/latest/spark-standalone.html#installing-spark-standalone-to-a-cluster)
+Please [Download Spark](https://spark.apache.org/downloads.html) first(**required version >= 2.4.0**). For more information you can
+see [Getting Started: Standalone](https://spark.apache.org/docs/latest/spark-standalone.html#installing-spark-standalone-to-a-cluster)
 
-**Configure SeaTunnel**: Change the setting in `config/seatunnel-env.sh`, it is base on the path your engine install at [deployment](deployment.md).
-Change `SPARK_HOME` to the Spark deployment dir.
+**Configure SeaTunnel**: Change the setting in `${SEATUNNEL_HOME}/config/seatunnel-env.sh` and set `SPARK_HOME` to the Spark deployment dir.
 
-## Step 3: Add Job Config File to define a job
+## Step 3: Add Job Config File To Define A Job
 
 Edit `config/seatunnel.streaming.conf.template`, which determines the way and logic of data input, processing, and output after seatunnel is started.
 The following is an example of the configuration file, which is the same as the example application mentioned above.
@@ -60,13 +59,13 @@ sink {
 
 ```
 
-More information about config please check [config concept](../../concept/config.md)
+More information about config please check [Config Concept](../../concept/config.md)
 
 ## Step 4: Run SeaTunnel Application
 
-You could start the application by the following commands
+You could start the application by the following commands:
 
-spark 2.4.x
+Spark 2.4.x
 
 ```bash
 cd "apache-seatunnel-${version}"
@@ -76,7 +75,7 @@ cd "apache-seatunnel-${version}"
 --config ./config/v2.streaming.conf.template
 ```
 
-spark3.x.x
+Spark3.x.x
 
 ```shell
 cd "apache-seatunnel-${version}"
@@ -86,10 +85,10 @@ cd "apache-seatunnel-${version}"
 --config ./config/v2.streaming.conf.template
 ```
 
-**See The Output**: When you run the command, you could see its output in your console. You can think this
-is a sign that the command ran successfully or not.
+**See The Output**: When you run the command, you can see its output in your console. This
+is a sign to determine whether the command ran successfully or not.
 
-The SeaTunnel console will prints some logs as below:
+The SeaTunnel console will print some logs as below:
 
 ```shell
 fields : name, age
@@ -114,7 +113,7 @@ row=16 : SGZCr, 94186144
 
 ## What's More
 
-For now, you are already take a quick look about SeaTunnel with Spark, you could see [connector](/docs/category/connector-v2) to find all
-source and sink SeaTunnel supported. Or see [SeaTunnel With Spark](../../other-engine/spark.md) if you want to know more about SeaTunnel Run With Spark.
+For now, you have taken a quick look about SeaTunnel with Spark, and you can see [Connector](/docs/category/connector-v2) to find all
+sources and sinks SeaTunnel supported. Or see [SeaTunnel With Spark](../../other-engine/spark.md) if you want to know more about SeaTunnel With Spark.
 
-SeaTunnel have an own engine named `Zeta` and `Zeta` is the default engine of SeaTunnel. You can follow [Quick Start](quick-start-seatunnel-engine.md) to configure and run a data synchronization job.
+SeaTunnel have a builtin engine named `Zeta`, and it's the default engine of SeaTunnel. You can follow [Quick Start](quick-start-seatunnel-engine.md) to configure and run a data synchronization job.
diff --git a/docs/zh/start-v2/locally/deployment.md b/docs/zh/start-v2/locally/deployment.md
index 937e3aef73c..9fa70f16040 100644
--- a/docs/zh/start-v2/locally/deployment.md
+++ b/docs/zh/start-v2/locally/deployment.md
@@ -16,9 +16,9 @@ import TabItem from '@theme/TabItem';
 
 ## 步骤 2: 下载 SeaTunnel
 
-进入[seatunnel下载页面](https://seatunnel.apache.org/download)下载最新版本的发布版安装包`seatunnel-<version>-bin.tar.gz`
+进入[SeaTunnel下载页面](https://seatunnel.apache.org/download)下载最新版本的二进制安装包`seatunnel-<version>-bin.tar.gz`
 
-或者您也可以通过终端下载
+或者您也可以通过终端下载：
 
 ```shell
 export version="2.3.6"
@@ -28,19 +28,19 @@ tar -xzvf "apache-seatunnel-${version}-bin.tar.gz"
 
 ## 步骤 3: 下载连接器插件
 
-从2.2.0-beta版本开始，二进制包不再默认提供连接器依赖，因此在第一次使用它时，您需要执行以下命令来安装连接器：(当然，您也可以从 [Apache Maven Repository](https://repo.maven.apache.org/maven2/org/apache/seatunnel/) 手动下载连接器，然后将其移动至`connectors/seatunnel`目录下)。
+从2.2.0-beta版本开始，二进制包不再默认提供连接器依赖，因此在第一次使用时，您需要执行以下命令来安装连接器：(当然，您也可以从 [Apache Maven Repository](https://repo.maven.apache.org/maven2/org/apache/seatunnel/) 手动下载连接器，然后将其移动至`connectors/seatunnel`目录下)。
 
 ```bash
-sh bin/install-plugin.sh 2.3.6
+sh bin/install-plugin.sh
 ```
 
-如果您需要指定的连接器版本，以2.3.6为例，您需要执行如下命令
+如果您需要指定的连接器版本，以2.3.6为例，您需要执行如下命令：
 
 ```bash
 sh bin/install-plugin.sh 2.3.6
 ```
 
-通常您并不需要所有的连接器插件，所以您可以通过配置`config/plugin_config`来指定您所需要的插件，例如，您只需要`connector-console`插件，那么您可以修改plugin.properties配置文件如下
+通常您并不需要所有的连接器插件，可以通过配置`config/plugin_config`来指定您所需要的插件，例如，您只需要`connector-console`插件，那么您可以修改plugin.properties配置文件如下：
 
 ```plugin_config
 --seatunnel-connectors--
@@ -48,7 +48,7 @@ connector-console
 --end--
 ```
 
-如果您希望示例应用程序能正常工作，那么您需要添加以下插件
+如果您希望示例应用程序能正常工作，那么您需要添加以下插件：
 
 ```plugin_config
 --seatunnel-connectors--
@@ -61,21 +61,8 @@ connector-console
 
 :::tip 提示
 
-如果您想通过手动下载连接器的方式来安装连接器插件，则需要特别注意以下事项
-
-连接器目录包含以下子目录，如果他们不存在，则需要手动创建它们
-
-```
-flink
-flink-sql
-seatunnel
-spark
-```
-
-如果您想手动安装V2连接器插件，您只需要下载您所需要的连接器插件即可，并将它们放在seatunnel目录下
+如果您想通过手动下载连接器的方式来安装连接器插件，则需要下载您所需要的连接器插件即可，并将它们放在`${SEATUNNEL_HOME}/connectors/`目录下。
 
 :::
 
-## 此外
-
 现在，您已经完成了SeaTunnel部署。您可以按照[快速开始](quick-start-seatunnel-engine.md)来配置并运行数据同步作业了。
diff --git a/docs/zh/start-v2/locally/quick-start-flink.md b/docs/zh/start-v2/locally/quick-start-flink.md
index 0349567d014..09189c91dce 100644
--- a/docs/zh/start-v2/locally/quick-start-flink.md
+++ b/docs/zh/start-v2/locally/quick-start-flink.md
@@ -7,18 +7,17 @@ sidebar_position: 3
 
 ## 步骤 1: 部署SeaTunnel及连接器
 
-在开始前，请确保您已经按照[部署](deployment.md)中的描述下载并部署了SeaTunnel
+在开始前，请确保您已经按照[部署](deployment.md)中的描述下载并部署了SeaTunnel。
 
 ## 步骤 2: 部署并配置Flink
 
-请先[下载Flink](https://flink.apache.org/downloads.html)(**需要版本 >= 1.12.0**)。更多信息您可以查看[入门: standalone模式](https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/resource-providers/standalone/overview/)
+请先[下载Flink](https://flink.apache.org/downloads.html)(**需要版本 >= 1.12.0**)。更多信息您可以查看[入门: Standalone模式](https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/resource-providers/standalone/overview/)
 
-**配置SeaTunnel**: 修改`config/seatunnel-env.sh`中的设置，它是基于你的引擎在[部署](deployment.md)时的安装路径。
-将`FLINK_HOME`修改为Flink的部署目录。
+**配置SeaTunnel**: 修改`config/seatunnel-env.sh`中的设置，将`FLINK_HOME`配置设置为Flink的部署目录。
 
 ## 步骤 3: 添加作业配置文件来定义作业
 
-编辑`config/v2.streaming.conf.template`，它决定了当seatunnel启动后数据输入、处理和输出的方式及逻辑。
+编辑`config/v2.streaming.conf.template`，它决定了SeaTunnel启动后数据输入、处理和输出的方式及逻辑。
 下面是配置文件的示例，它与上面提到的示例应用程序相同。
 
 ```hocon
@@ -63,7 +62,7 @@ sink {
 
 ## 步骤 4: 运行SeaTunnel应用程序
 
-您可以通过以下命令启动应用程序
+您可以通过以下命令启动应用程序：
 
 Flink版本`1.12.x`到`1.14.x`
 
@@ -106,7 +105,7 @@ row=16 : SGZCr, 94186144
 
 ## 此外
 
-现在,您已经快速浏览了SeaTunnel使用Flink引擎的方式，你可以通过在[连接器](/docs/category/connector-v2)中找到SeaTunnel所支持的所有source和sink。
+现在,您已经快速浏览了SeaTunnel使用Flink引擎的方式，可以通过在[连接器](/docs/category/connector-v2)中找到SeaTunnel所支持的所有sources和sinks。
 如果您想要了解更多关于SeaTunnel运行在Flink上的信息，请参阅[基于Flink的SeaTunnel](../../other-engine/flink.md)。
 
-SeaTunnel有自己的名为`Zeta`的引擎，同时`Zeta`是SeaTunnel的默认引擎。您可以参考[快速开始](quick-start-seatunnel-engine.md)配置和运行数据同步作业。
+SeaTunnel有内置的`Zeta`引擎，它是作为SeaTunnel的默认引擎。您可以参考[快速开始](quick-start-seatunnel-engine.md)配置和运行数据同步作业。
diff --git a/docs/zh/start-v2/locally/quick-start-seatunnel-engine.md b/docs/zh/start-v2/locally/quick-start-seatunnel-engine.md
index 0a9e68cd4cd..cd7a9e88e3e 100644
--- a/docs/zh/start-v2/locally/quick-start-seatunnel-engine.md
+++ b/docs/zh/start-v2/locally/quick-start-seatunnel-engine.md
@@ -7,7 +7,7 @@ sidebar_position: 2
 
 ## 步骤 1: 部署SeaTunnel及连接器
 
-在开始前，请确保您已经按照[部署](deployment.md)中的描述下载并部署了SeaTunnel
+在开始前，请确保您已经按照[部署](deployment.md)中的描述下载并部署了SeaTunnel。
 
 ## 步骤 2: 添加作业配置文件来定义作业
 
@@ -56,7 +56,7 @@ sink {
 
 ## 步骤 3: 运行SeaTunnel应用程序
 
-您可以通过以下命令启动应用程序
+您可以通过以下命令启动应用程序：
 
 :::tip
 
@@ -96,5 +96,5 @@ SeaTunnel控制台将会打印一些如下日志信息:
 
 ## 此外
 
-现在,您已经快速浏览了SeaTunnel，你可以通过[连接器](../../../en/connector-v2/source/FakeSource.md)来找到SeaTunnel所支持的所有source和sink。
+现在,您已经快速浏览了SeaTunnel，可以通过[连接器](../../../en/connector-v2/source/FakeSource.md)来找到SeaTunnel所支持的所有sources和sinks。
 如果您想要了解更多关于信息，请参阅[SeaTunnel引擎](../../seatunnel-engine/about.md). 在这里你将了解如何部署SeaTunnel Engine的集群模式以及如何在集群模式下使用。
diff --git a/docs/zh/start-v2/locally/quick-start-spark.md b/docs/zh/start-v2/locally/quick-start-spark.md
index 13e1bf17bb9..fbd0fa15fe5 100644
--- a/docs/zh/start-v2/locally/quick-start-spark.md
+++ b/docs/zh/start-v2/locally/quick-start-spark.md
@@ -7,18 +7,18 @@ sidebar_position: 4
 
 ## 步骤 1: 部署SeaTunnel及连接器
 
-在开始前，请确保您已经按照[部署](deployment.md)中的描述下载并部署了SeaTunnel
+在开始前，请确保您已经按照[部署](deployment.md)中的描述下载并部署了SeaTunnel。
 
 ## 步骤 2: 部署并配置Spark
 
-请先[下载Spark](https://spark.apache.org/downloads.html)(**需要版本 >= 2.4.0**)。 更多信息您可以查看[入门: standalone模式](https://spark.apache.org/docs/latest/spark-standalone.html#installing-spark-standalone-to-a-cluster)
+请先[下载Spark](https://spark.apache.org/downloads.html)(**需要版本 >= 2.4.0**)。 更多信息您可以查看[入门: Standalone模式](https://spark.apache.org/docs/latest/spark-standalone.html#installing-spark-standalone-to-a-cluster)
 
 **配置SeaTunnel**: 修改`config/seatunnel-env.sh`中的设置,它是基于你的引擎在[部署](deployment.md)时的安装路径。
 将`SPARK_HOME`修改为Spark的部署目录。
 
 ## 步骤 3: 添加作业配置文件来定义作业
 
-编辑`config/v2.streaming.conf.template`，它决定了当seatunnel启动后数据输入、处理和输出的方式及逻辑。
+编辑`config/v2.streaming.conf.template`，它决定了当SeaTunnel启动后数据输入、处理和输出的方式及逻辑。
 下面是配置文件的示例，它与上面提到的示例应用程序相同。
 
 ```hocon
@@ -63,7 +63,7 @@ sink {
 
 ## 步骤 4: 运行SeaTunnel应用程序
 
-您可以通过以下命令启动应用程序
+您可以通过以下命令启动应用程序：
 
 Spark 2.4.x
 
@@ -112,7 +112,7 @@ row=16 : SGZCr, 94186144
 
 ## 此外
 
-现在，您已经快速浏览了SeaTunnel使用Spark引擎的方式，你可以通过在[连接器](/docs/category/connector-v2)中找到SeaTunnel所支持的所有source和sink。
+现在，您已经快速浏览了SeaTunnel使用Spark引擎的方式，可以通过在[连接器](/docs/category/connector-v2)中找到SeaTunnel所支持的所有source和sink。
 如果您想要了解更多关于SeaTunnel运行在Spark上的信息，请参阅[基于Spark的SeaTunnel](../../../en/other-engine/spark.md)。
 
-SeaTunnel有自己的名为`Zeta`的引擎，同时`Zeta`是SeaTunnel的默认引擎。您可以参考[快速开始](quick-start-seatunnel-engine.md)配置和运行数据同步作业。
+SeaTunnel有内置的`Zeta`引擎，它是作为SeaTunnel的默认引擎。您可以参考[快速开始](quick-start-seatunnel-engine.md)配置和运行数据同步作业。