From 36cd8d74cea6171224adfa551e0082d1f7e558ec Mon Sep 17 00:00:00 2001
From: Sherlock113 <sherlockxu@yunify.com>
Date: Tue, 18 May 2021 14:00:34 +0800
Subject: [PATCH] Fix code format

Signed-off-by: Sherlock113 <sherlockxu@yunify.com>
---
 .../en/docs/pluggable-components/alerting.md  |  6 +++---
 .../en/docs/pluggable-components/app-store.md |  6 +++---
 .../pluggable-components/auditing-logs.md     |  6 +++---
 .../en/docs/pluggable-components/devops.md    |  6 +++---
 .../en/docs/pluggable-components/events.md    |  6 +++---
 .../en/docs/pluggable-components/logging.md   |  6 +++---
 .../pluggable-components/metrics-server.md    |  6 +++---
 .../pluggable-components/network-policy.md    | 21 +++++++++++--------
 .../docs/pluggable-components/pod-ip-pools.md |  6 +++---
 .../docs/pluggable-components/service-mesh.md |  6 +++---
 .../zh/docs/pluggable-components/alerting.md  |  6 +++---
 .../zh/docs/pluggable-components/app-store.md | 15 +++++++------
 .../pluggable-components/auditing-logs.md     |  6 +++---
 .../zh/docs/pluggable-components/devops.md    | 12 +++++------
 .../zh/docs/pluggable-components/events.md    |  6 +++---
 .../zh/docs/pluggable-components/logging.md   |  6 +++---
 .../pluggable-components/metrics-server.md    |  6 +++---
 .../pluggable-components/network-policy.md    | 21 +++++++++++--------
 .../docs/pluggable-components/service-mesh.md |  6 +++---
 19 files changed, 84 insertions(+), 75 deletions(-)

diff --git a/content/en/docs/pluggable-components/alerting.md b/content/en/docs/pluggable-components/alerting.md
index 6ffca5ac5..0f0c7f156 100644
--- a/content/en/docs/pluggable-components/alerting.md
+++ b/content/en/docs/pluggable-components/alerting.md
@@ -30,7 +30,7 @@ If you adopt [All-in-One Installation](../../quick-start/all-in-one-on-linux/),
 
     ```yaml
     alerting:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
     
 3. Create a cluster using the configuration file:
@@ -53,7 +53,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
 
     ```yaml
     alerting:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
     
 3. Execute the following commands to start installation:
@@ -80,7 +80,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
 
     ```yaml
     alerting:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
     
 5. You can use the web kubectl to check the installation process by executing the following command:
diff --git a/content/en/docs/pluggable-components/app-store.md b/content/en/docs/pluggable-components/app-store.md
index 7c3c439ed..cf61e74bf 100644
--- a/content/en/docs/pluggable-components/app-store.md
+++ b/content/en/docs/pluggable-components/app-store.md
@@ -37,7 +37,7 @@ If you adopt [All-in-One Installation](../../quick-start/all-in-one-on-linux/),
     ```yaml
     openpitrix:
       store:
-        enabled: true # Change "false" to "true"
+        enabled: true # Change "false" to "true".
     ```
 
 3. Create a cluster using the configuration file:
@@ -61,7 +61,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
     ```yaml
     openpitrix:
       store:
-        enabled: true # Change "false" to "true"
+        enabled: true # Change "false" to "true".
     ```
 
 3. Execute the following commands to start installation:
@@ -95,7 +95,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
     ```yaml
     openpitrix:
       store:
-        enabled: true # Change "false" to "true"
+        enabled: true # Change "false" to "true".
     ```
 
 5. You can use the web kubectl to check the installation process by executing the following command:
diff --git a/content/en/docs/pluggable-components/auditing-logs.md b/content/en/docs/pluggable-components/auditing-logs.md
index 3f1eb1d42..775dc3f34 100644
--- a/content/en/docs/pluggable-components/auditing-logs.md
+++ b/content/en/docs/pluggable-components/auditing-logs.md
@@ -32,7 +32,7 @@ If you adopt [All-in-One Installation](../../quick-start/all-in-one-on-linux/),
 
     ```yaml
     auditing:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
     {{< notice note >}}
@@ -71,7 +71,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
 
     ```yaml
     auditing:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
     {{< notice note >}}
@@ -118,7 +118,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
 
     ```yaml
     auditing:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
     {{< notice note >}}
diff --git a/content/en/docs/pluggable-components/devops.md b/content/en/docs/pluggable-components/devops.md
index 0f866889f..a50670902 100644
--- a/content/en/docs/pluggable-components/devops.md
+++ b/content/en/docs/pluggable-components/devops.md
@@ -34,7 +34,7 @@ If you adopt [All-in-One Installation](../../quick-start/all-in-one-on-linux/),
 
     ```yaml
     devops:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
 3. Create a cluster using the configuration file:
@@ -57,7 +57,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
 
     ```yaml
     devops:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
 3. Execute the following commands to start installation:
@@ -89,7 +89,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
 
     ```yaml
     devops:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
 5. You can use the web kubectl to check the installation process by executing the following command:
diff --git a/content/en/docs/pluggable-components/events.md b/content/en/docs/pluggable-components/events.md
index 68f4e6f15..152d70b7a 100644
--- a/content/en/docs/pluggable-components/events.md
+++ b/content/en/docs/pluggable-components/events.md
@@ -34,7 +34,7 @@ If you adopt [All-in-One Installation](../../quick-start/all-in-one-on-linux/),
 
     ```yaml
     events:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
     {{< notice note >}}
@@ -73,7 +73,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
 
     ```yaml
     events:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
     {{< notice note >}}
@@ -122,7 +122,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
 
     ```yaml
     events:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
     {{< notice note >}}
diff --git a/content/en/docs/pluggable-components/logging.md b/content/en/docs/pluggable-components/logging.md
index 2deddfcf0..6609bb28f 100644
--- a/content/en/docs/pluggable-components/logging.md
+++ b/content/en/docs/pluggable-components/logging.md
@@ -36,7 +36,7 @@ When you install KubeSphere on Linux, you need to create a configuration file, w
 
     ```yaml
     logging:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
     {{< notice note >}}
@@ -75,7 +75,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
 
     ```yaml
     logging:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
     {{< notice note >}}
@@ -124,7 +124,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
 
     ```yaml
     logging:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
     {{< notice note >}}By default, Elasticsearch will be installed internally if Logging is enabled. For a production environment, it is highly recommended that you set the following values in this yaml file if you want to enable Logging, especially `externalElasticsearchUrl` and `externalElasticsearchPort`. Once you provide the following information, KubeSphere will integrate your external Elasticsearch directly instead of installing an internal one.
diff --git a/content/en/docs/pluggable-components/metrics-server.md b/content/en/docs/pluggable-components/metrics-server.md
index 9c689b302..06632cafd 100644
--- a/content/en/docs/pluggable-components/metrics-server.md
+++ b/content/en/docs/pluggable-components/metrics-server.md
@@ -30,7 +30,7 @@ When you implement multi-node installation of KubeSphere on Linux, you need to c
 
    ```yaml
    metrics_server:
-     enabled: true # Change "false" to "true"
+     enabled: true # Change "false" to "true".
    ```
 
 3. Create a cluster using the configuration file:
@@ -53,7 +53,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
 
     ```yaml
     metrics_server:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
 3. Execute the following commands to start installation:
@@ -90,7 +90,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
 
     ```yaml
     metrics_server:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
 5. You can use the web kubectl to check the installation process by executing the following command:
diff --git a/content/en/docs/pluggable-components/network-policy.md b/content/en/docs/pluggable-components/network-policy.md
index a77a954ba..372767351 100644
--- a/content/en/docs/pluggable-components/network-policy.md
+++ b/content/en/docs/pluggable-components/network-policy.md
@@ -35,11 +35,12 @@ When you implement multi-node installation of KubeSphere on Linux, you need to c
 If you adopt [All-in-One Installation](../../quick-start/all-in-one-on-linux/), you do not need to create a `config-sample.yaml` file as you can create a cluster directly. Generally, the all-in-one mode is for users who are new to KubeSphere and look to get familiar with the system. If you want to enable the Network Policy in this mode (e.g. for testing purposes), refer to [the following section](#enable-network-policy-after-installation) to see how the Network Policy can be installed after installation.
     {{</ notice >}}
 
-2. In this file, navigate to `networkpolicy` and change `false` to `true` for `enabled`. Save the file after you finish.
+2. In this file, navigate to `network.networkpolicy` and change `false` to `true` for `enabled`. Save the file after you finish.
 
     ```yaml
-    networkpolicy:
-      enabled: true # Change "false" to "true"
+    network:
+      networkpolicy:
+        enabled: true # Change "false" to "true".
     ```
 
 3. Create a cluster using the configuration file:
@@ -58,11 +59,12 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
     vi cluster-configuration.yaml
     ```
 
-2. In this local `cluster-configuration.yaml` file, navigate to `networkpolicy` and enable it by changing `false` to `true` for `enabled`. Save the file after you finish.
+2. In this local `cluster-configuration.yaml` file, navigate to `network.networkpolicy` and enable it by changing `false` to `true` for `enabled`. Save the file after you finish.
 
     ```yaml
-    networkpolicy:
-      enabled: true # Change "false" to "true"
+    network:
+      networkpolicy:
+        enabled: true # Change "false" to "true".
     ```
 
 3. Execute the following commands to start installation:
@@ -89,11 +91,12 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
 
     ![edit-yaml](/images/docs/enable-pluggable-components/network-policies/edit-yaml.png)
 
-4. In this yaml file, navigate to `networkpolicy` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration.
+4. In this yaml file, navigate to `network.networkpolicy` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration.
 
     ```yaml
-    networkpolicy:
-      enabled: true # Change "false" to "true"
+    network:
+      networkpolicy:
+        enabled: true # Change "false" to "true".
     ```
 
 5. You can use the web kubectl to check the installation process by executing the following command:
diff --git a/content/en/docs/pluggable-components/pod-ip-pools.md b/content/en/docs/pluggable-components/pod-ip-pools.md
index 221df6315..233687421 100644
--- a/content/en/docs/pluggable-components/pod-ip-pools.md
+++ b/content/en/docs/pluggable-components/pod-ip-pools.md
@@ -31,7 +31,7 @@ When you implement multi-node installation of KubeSphere on Linux, you need to c
    ```yaml
    network:
      ippool:
-       type: calico # Change "none" to "calico"
+       type: calico # Change "none" to "calico".
    ```
 
 3. Create a cluster using the configuration file:
@@ -55,7 +55,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
     ```yaml
     network:
       ippool:
-        type: calico # Change "none" to "calico"
+        type: calico # Change "none" to "calico".
     ```
 
 3. Execute the following commands to start installation:
@@ -83,7 +83,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
     ```yaml
     network:
       ippool:
-        type: calico # Change "none" to "calico"
+        type: calico # Change "none" to "calico".
     ```
 
 5. You can use the web kubectl to check the installation process by executing the following command:
diff --git a/content/en/docs/pluggable-components/service-mesh.md b/content/en/docs/pluggable-components/service-mesh.md
index b92c5ff5c..18ad02e56 100644
--- a/content/en/docs/pluggable-components/service-mesh.md
+++ b/content/en/docs/pluggable-components/service-mesh.md
@@ -32,7 +32,7 @@ If you adopt [All-in-One Installation](../../quick-start/all-in-one-on-linux/),
 
     ```yaml
     servicemesh:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
 3. Create a cluster using the configuration file:
@@ -55,7 +55,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
 
     ```yaml
     servicemesh:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
 3. Execute the following commands to start installation:
@@ -85,7 +85,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
 
     ```yaml
     servicemesh:
-      enabled: true # Change "false" to "true"
+      enabled: true # Change "false" to "true".
     ```
 
 5. You can use the web kubectl to check the installation process by executing the following command:
diff --git a/content/zh/docs/pluggable-components/alerting.md b/content/zh/docs/pluggable-components/alerting.md
index 35827e2a4..4584ae115 100644
--- a/content/zh/docs/pluggable-components/alerting.md
+++ b/content/zh/docs/pluggable-components/alerting.md
@@ -30,7 +30,7 @@ weight: 6600
 
     ```yaml
     alerting:
-        enabled: true # 将“false”更改为“true”。
+      enabled: true # 将“false”更改为“true”。
     ```
     
 3. 使用该配置文件创建集群：
@@ -53,7 +53,7 @@ weight: 6600
 
     ```yaml
     alerting:
-        enabled: true # 将“false”更改为“true”。
+      enabled: true # 将“false”更改为“true”。
     ```
     
 3. 执行以下命令开始安装：
@@ -84,7 +84,7 @@ weight: 6600
 
     ```yaml
     alerting:
-        enabled: true # 将“false”更改为“true”。
+      enabled: true # 将“false”更改为“true”。
     ```
     
 5. 您可以使用 Web Kubectl 工具执行以下命令来检查安装过程：
diff --git a/content/zh/docs/pluggable-components/app-store.md b/content/zh/docs/pluggable-components/app-store.md
index 27699c145..a28d7ad5b 100644
--- a/content/zh/docs/pluggable-components/app-store.md
+++ b/content/zh/docs/pluggable-components/app-store.md
@@ -35,9 +35,10 @@ weight: 6200
 
 2. 在该文件中，搜寻到 `openpitrix`，并将 `enabled` 的 `false` 改为 `true`，完成后保存文件。
 
-    ```bash
+    ```yaml
     openpitrix:
-        enabled: true # Change "false" to "true"
+      store:
+        enabled: true # 将“false”更改为“true”。
     ```
 
 3. 使用该配置文件创建集群：
@@ -58,9 +59,10 @@ weight: 6200
 
 2. 在该本地 `cluster-configuration.yaml` 文件中，搜寻到 `openpitrix`，并将 `enabled` 的 `false` 改为 `true`，以启用应用商店。完成后保存文件。
 
-    ```bash
+    ```yaml
     openpitrix:
-        enabled: true # Change "false" to "true"
+      store:
+        enabled: true # 将“false”更改为“true”。
     ```
 
 3. 执行以下命令开始安装：
@@ -89,9 +91,10 @@ weight: 6200
 
 4. 在该 YAML 文件中，搜寻到 `openpitrix`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。
 
-    ```bash
+    ```yaml
     openpitrix:
-        enabled: true # Change "false" to "true"
+      store:
+        enabled: true # 将“false”更改为“true”。
     ```
 
 5. 您可以使用 Web Kubectl 工具执行以下命令来检查安装过程：
diff --git a/content/zh/docs/pluggable-components/auditing-logs.md b/content/zh/docs/pluggable-components/auditing-logs.md
index 5f66f175d..e699ecc5a 100644
--- a/content/zh/docs/pluggable-components/auditing-logs.md
+++ b/content/zh/docs/pluggable-components/auditing-logs.md
@@ -32,7 +32,7 @@ KubeSphere 审计日志系统提供了一套与安全相关并按时间顺序排
 
     ```yaml
     auditing:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
     {{< notice note >}}
@@ -71,7 +71,7 @@ KubeSphere 审计日志系统提供了一套与安全相关并按时间顺序排
 
     ```yaml
     auditing:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
     {{< notice note >}}
@@ -118,7 +118,7 @@ KubeSphere 审计日志系统提供了一套与安全相关并按时间顺序排
 
     ```yaml
     auditing:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
     {{< notice note >}}
diff --git a/content/zh/docs/pluggable-components/devops.md b/content/zh/docs/pluggable-components/devops.md
index 75ae2fd7a..47d73ddeb 100644
--- a/content/zh/docs/pluggable-components/devops.md
+++ b/content/zh/docs/pluggable-components/devops.md
@@ -33,9 +33,9 @@ DevOps 系统为用户提供了一个自动化的环境，应用可以自动发
 
 2. 在该文件中，搜寻到 `devops`，并将 `enabled` 的 `false `改为 `true`，完成后保存文件。
 
-    ```bash
+    ```yaml
     devops:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
 3. 使用该配置文件创建集群：
@@ -56,9 +56,9 @@ DevOps 系统为用户提供了一个自动化的环境，应用可以自动发
 
 2. 在该本地 `cluster-configuration.yaml` 文件中，搜寻到 `devops`，并将 `enabled` 的 `false` 改为 `true`，完成后保存文件。
 
-    ```bash
+    ```yaml
     devops:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
 3. 执行以下命令开始安装：
@@ -87,9 +87,9 @@ DevOps 系统为用户提供了一个自动化的环境，应用可以自动发
 
 4. 在该 YAML 文件中，搜寻到 `devops`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。
 
-    ```bash
+    ```yaml
     devops:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
 5. 您可以使用 Web Kubectl 工具执行以下命令来检查安装过程：
diff --git a/content/zh/docs/pluggable-components/events.md b/content/zh/docs/pluggable-components/events.md
index 06140aa07..80caa8452 100644
--- a/content/zh/docs/pluggable-components/events.md
+++ b/content/zh/docs/pluggable-components/events.md
@@ -34,7 +34,7 @@ KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如
 
     ```yaml
     events:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
     {{< notice note >}}
@@ -73,7 +73,7 @@ KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如
 
     ```yaml
     events:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
     {{< notice note >}}
@@ -122,7 +122,7 @@ KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如
 
     ```yaml
     events:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
     {{< notice note >}}
diff --git a/content/zh/docs/pluggable-components/logging.md b/content/zh/docs/pluggable-components/logging.md
index 17839f5ce..5c8e5a4a5 100644
--- a/content/zh/docs/pluggable-components/logging.md
+++ b/content/zh/docs/pluggable-components/logging.md
@@ -36,7 +36,7 @@ KubeSphere 为日志收集、查询和管理提供了一个强大的、全面的
 
     ```yaml
     logging:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
     {{< notice note >}}
@@ -75,7 +75,7 @@ KubeSphere 为日志收集、查询和管理提供了一个强大的、全面的
 
     ```yaml
     logging:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
     {{< notice note >}}
@@ -124,7 +124,7 @@ KubeSphere 为日志收集、查询和管理提供了一个强大的、全面的
 
     ```yaml
     logging:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
     {{< notice note >}}默认情况下，如果启用了日志系统，将会安装内置 Elasticsearch。对于生产环境，如果您想启用日志系统，强烈建议在该 YAML 文件中设置以下值，尤其是 `externalElasticsearchUrl` 和 `externalElasticsearchPort`。在文件中提供以下信息后，KubeSphere 将直接对接您的外部 Elasticsearch，不再安装内置 Elasticsearch。
diff --git a/content/zh/docs/pluggable-components/metrics-server.md b/content/zh/docs/pluggable-components/metrics-server.md
index c621b16e6..fff1d23e1 100644
--- a/content/zh/docs/pluggable-components/metrics-server.md
+++ b/content/zh/docs/pluggable-components/metrics-server.md
@@ -30,7 +30,7 @@ KubeSphere 支持用于[部署](../../project-user-guide/application-workloads/d
 
    ```yaml
    metrics_server:
-     enabled: true # Change "false" to "true"
+     enabled: true # 将“false”更改为“true”。
    ```
 
 3. 使用该配置文件创建集群：
@@ -53,7 +53,7 @@ KubeSphere 支持用于[部署](../../project-user-guide/application-workloads/d
 
     ```yaml
     metrics_server:
-      enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
 3. 执行以下命令以开始安装：
@@ -91,7 +91,7 @@ KubeSphere 支持用于[部署](../../project-user-guide/application-workloads/d
 
     ```yaml
     metrics_server:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
 5. 您可以通过执行以下命令，使用 kubectl 来检查安装过程：
diff --git a/content/zh/docs/pluggable-components/network-policy.md b/content/zh/docs/pluggable-components/network-policy.md
index 6c9b21a82..8984ad606 100644
--- a/content/zh/docs/pluggable-components/network-policy.md
+++ b/content/zh/docs/pluggable-components/network-policy.md
@@ -35,11 +35,12 @@ weight: 6900
 如果您采用 [All-in-One 安装](../../quick-start/all-in-one-on-linux/)，则不需要创建 `config-sample.yaml` 文件，因为可以直接创建集群。一般来说，All-in-One 模式是为那些刚接触 KubeSphere 并希望熟悉系统的用户而准备的。如果您想在该模式下启用网络策略（例如用于测试），可以参考[下面的部分](#在安装后启用网络策略)，查看如何在安装后启用网络策略。
     {{</ notice >}}
 
-2. 在该文件中，搜寻到 `networkpolicy`，并将 `enabled` 的 `false` 改为 `true`。完成后保存文件。
+2. 在该文件中，搜寻到 `network.networkpolicy`，并将 `enabled` 的 `false` 改为 `true`。完成后保存文件。
 
     ```yaml
-    networkpolicy:
-        enabled: true # Change "false" to "true"
+    network:
+      networkpolicy:
+        enabled: true # 将“false”更改为“true”。
     ```
 
 3. 使用配置文件创建一个集群：
@@ -58,11 +59,12 @@ weight: 6900
     vi cluster-configuration.yaml
     ```
 
-2. 在该本地 `cluster-configuration.yaml` 文件中，搜寻到 `networkpolicy`，并将  `enabled` 的 `false` 改为 `true`，启用该功能。完成后保存文件。
+2. 在该本地 `cluster-configuration.yaml` 文件中，搜寻到 `network.networkpolicy`，并将 `enabled` 的 `false` 改为 `true`，启用该功能。完成后保存文件。
 
     ```yaml
-    networkpolicy:
-        enabled: true # Change "false" to "true"
+    network:
+      networkpolicy:
+        enabled: true # 将“false”更改为“true”。
     ```
 
 3. 执行以下命令开始安装：
@@ -89,11 +91,12 @@ weight: 6900
 
     ![编辑 YAML](/images/docs/zh-cn/enable-pluggable-components/network-policies/edit-yaml.PNG)
 
-4. 在该 YAML 文件中，搜寻到 `networkpolicy`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。
+4. 在该 YAML 文件中，搜寻到 `network.networkpolicy`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。
 
     ```yaml
-    networkpolicy:
-        enabled: true # Change "false" to "true"
+    network:
+      networkpolicy:
+        enabled: true # 将“false”更改为“true”。
     ```
 
 5. 您可以执行以下命令，使用 Web Kubectl 工具来检查安装过程：
diff --git a/content/zh/docs/pluggable-components/service-mesh.md b/content/zh/docs/pluggable-components/service-mesh.md
index 85eda5932..0f5292b04 100644
--- a/content/zh/docs/pluggable-components/service-mesh.md
+++ b/content/zh/docs/pluggable-components/service-mesh.md
@@ -33,7 +33,7 @@ KubeSphere 服务网格基于 [Istio](https://istio.io/)，将微服务治理和
 
     ```yaml
     servicemesh:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
 3. 使用该配置文件创建集群：
@@ -56,7 +56,7 @@ KubeSphere 服务网格基于 [Istio](https://istio.io/)，将微服务治理和
 
     ```yaml
     servicemesh:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
 3. 执行以下命令开始安装：
@@ -86,7 +86,7 @@ KubeSphere 服务网格基于 [Istio](https://istio.io/)，将微服务治理和
 
     ```yaml
     servicemesh:
-        enabled: true # Change "false" to "true"
+      enabled: true # 将“false”更改为“true”。
     ```
 
 5. 您可以执行以下命令，使用 Web Kubectl 工具来检查安装过程：