diff --git a/content/en/docs/cluster-administration/application-resources-monitoring.md b/content/en/docs/cluster-administration/application-resources-monitoring.md
index ed3783e17..97ca82438 100644
--- a/content/en/docs/cluster-administration/application-resources-monitoring.md
+++ b/content/en/docs/cluster-administration/application-resources-monitoring.md
@@ -11,17 +11,17 @@ In addition to monitoring data at the physical resource level, cluster administr
 
 ## Prerequisites
 
-You need an account granted a role including the authorization of **Clusters Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
+You need an account granted a role including the authorization of **Cluster Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
 
 ## Resource Usage
 
-1. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Click **Platform** in the top left corner and select **Cluster Management**.
 
     ![Platform](/images/docs/cluster-administration/cluster-status-monitoring/platform.png)
 
 2. If you have enabled the [multi-cluster feature](../../multicluster-management/) with member clusters imported, you can select a specific cluster to view its application resources. If you have not enabled the feature, refer to the next step directly.
 
-    ![Clusters Management](/images/docs/cluster-administration/cluster-status-monitoring/clusters-management.png)
+    ![Cluster Management](/images/docs/cluster-administration/cluster-status-monitoring/clusters-management.png)
 
 3. Choose **Application Resources** under **Monitoring & Alerting** to see the overview of application resource monitoring, including the summary of the usage of all resources in the cluster, as shown in the following figure.
 
diff --git a/content/en/docs/cluster-administration/cluster-settings/cluster-visibility-and-authorization.md b/content/en/docs/cluster-administration/cluster-settings/cluster-visibility-and-authorization.md
index 5a556828c..055c05fd1 100644
--- a/content/en/docs/cluster-administration/cluster-settings/cluster-visibility-and-authorization.md
+++ b/content/en/docs/cluster-administration/cluster-settings/cluster-visibility-and-authorization.md
@@ -46,7 +46,7 @@ After a workspace is created, you can allocate additional clusters to the worksp
 
 1. Log in to KubeSphere with an account that has the permission to manage clusters, such as `admin`.
 
-2. Click **Platform** in the top left corner and select **Clusters Management**. Select a cluster from the list to view cluster information.
+2. Click **Platform** in the top left corner and select **Cluster Management**. Select a cluster from the list to view cluster information.
 
 3. In **Cluster Settings** from the navigation bar, select **Cluster Visibility**.
 
diff --git a/content/en/docs/cluster-administration/cluster-settings/log-collections/add-es-as-receiver.md b/content/en/docs/cluster-administration/cluster-settings/log-collections/add-es-as-receiver.md
index a5faea787..a78f22ae0 100644
--- a/content/en/docs/cluster-administration/cluster-settings/log-collections/add-es-as-receiver.md
+++ b/content/en/docs/cluster-administration/cluster-settings/log-collections/add-es-as-receiver.md
@@ -9,13 +9,13 @@ You can use Elasticsearch, Kafka and Fluentd as log receivers in KubeSphere. Thi
 
 ## Prerequisites
 
-- You need an account granted a role including the authorization of **Clusters Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
+- You need an account granted a role including the authorization of **Cluster Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
 
 - Before adding a log receiver, you need to enable any of the `logging`, `events` or `auditing` components. For more information, see [Enable Pluggable Components](../../../../pluggable-components/). `logging` is enabled as an example in this tutorial.
 
 ## Add Elasticsearch as a Receiver
 
-1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Cluster Management**.
 
 2. If you have enabled the [multi-cluster feature](../../../../multicluster-management/), you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
 
diff --git a/content/en/docs/cluster-administration/cluster-settings/log-collections/add-fluentd-as-receiver.md b/content/en/docs/cluster-administration/cluster-settings/log-collections/add-fluentd-as-receiver.md
index b411d67ba..21a9f253f 100644
--- a/content/en/docs/cluster-administration/cluster-settings/log-collections/add-fluentd-as-receiver.md
+++ b/content/en/docs/cluster-administration/cluster-settings/log-collections/add-fluentd-as-receiver.md
@@ -13,7 +13,7 @@ You can use Elasticsearch, Kafka and Fluentd as log receivers in KubeSphere. Thi
 
 ## Prerequisites
 
-- You need an account granted a role including the authorization of **Clusters Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
+- You need an account granted a role including the authorization of **Cluster Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
 
 - Before adding a log receiver, you need to enable any of the `logging`, `events` or `auditing` components. For more information, see [Enable Pluggable Components](../../../../pluggable-components/). `logging` is enabled as an example in this tutorial.
 
@@ -122,7 +122,7 @@ EOF
 
 ## Step 2: Add Fluentd as a Log Receiver (i.e. Collector)
 
-1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Cluster Management**.
 2. If you have enabled the [multi-cluster feature](../../../../multicluster-management/), you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
 3. On the **Cluster Management** page, go to **Log Collections** in **Cluster Settings**.
 
diff --git a/content/en/docs/cluster-administration/cluster-settings/log-collections/add-kafka-as-receiver.md b/content/en/docs/cluster-administration/cluster-settings/log-collections/add-kafka-as-receiver.md
index eca2235af..e529f60c3 100644
--- a/content/en/docs/cluster-administration/cluster-settings/log-collections/add-kafka-as-receiver.md
+++ b/content/en/docs/cluster-administration/cluster-settings/log-collections/add-kafka-as-receiver.md
@@ -13,7 +13,7 @@ You can use Elasticsearch, Kafka and Fluentd as log receivers in KubeSphere. Thi
 
 ## Prerequisites
 
-- You need an account granted a role including the authorization of **Clusters Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
+- You need an account granted a role including the authorization of **Cluster Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
 - Before adding a log receiver, you need to enable any of the `logging`, `events` or `auditing` components. For more information, see [Enable Pluggable Components](../../../../pluggable-components/). `logging` is enabled as an example in this tutorial.
 
 ## Step 1: Create a Kafka Cluster and a Kafka Topic
@@ -101,7 +101,7 @@ You can use [strimzi-kafka-operator](https://github.com/strimzi/strimzi-kafka-op
 
 ## Step 2: Add Kafka as a Log Receiver
 
-1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Cluster Management**.
 
 2. If you have enabled the [multi-cluster feature](../../../../multicluster-management/), you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
 
diff --git a/content/en/docs/cluster-administration/cluster-settings/log-collections/introduction.md b/content/en/docs/cluster-administration/cluster-settings/log-collections/introduction.md
index e74784b80..5ef2c23cd 100644
--- a/content/en/docs/cluster-administration/cluster-settings/log-collections/introduction.md
+++ b/content/en/docs/cluster-administration/cluster-settings/log-collections/introduction.md
@@ -12,7 +12,7 @@ This tutorial gives a brief introduction about the general steps of adding log r
 
 ## Prerequisites
 
-- You need an account granted a role including the authorization of **Clusters Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
+- You need an account granted a role including the authorization of **Cluster Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
 
 - Before adding a log receiver, you need to enable any of the `logging`, `events` or `auditing` components. For more information, see [Enable Pluggable Components](../../../../pluggable-components/).
 
@@ -22,7 +22,7 @@ To add a log receiver:
 
 1. Log in to the web console of KubeSphere as `admin`.
 
-2. Click **Platform** in the top left corner and select **Clusters Management**.
+2. Click **Platform** in the top left corner and select **Cluster Management**.
 
 3. If you have enabled the [multi-cluster feature](../../../../multicluster-management/), you can select a specific cluster. If you have not enabled the feature, refer to the next step directly.
 
diff --git a/content/en/docs/cluster-administration/cluster-settings/mail-server.md b/content/en/docs/cluster-administration/cluster-settings/mail-server.md
index b34c916c2..b44e3552d 100644
--- a/content/en/docs/cluster-administration/cluster-settings/mail-server.md
+++ b/content/en/docs/cluster-administration/cluster-settings/mail-server.md
@@ -18,7 +18,7 @@ This guide demonstrates email notification settings (customized settings support
 ## Hands-on Lab
 
 1. Log in to the web console with one account granted the role  `platform-admin`.
-2. Click **Platform** in the top left corner and select **Clusters Management**.
+2. Click **Platform** in the top left corner and select **Cluster Management**.
 
     ![mail_server_guide](/images/docs/alerting/mail_server_guide.png)
 
diff --git a/content/en/docs/cluster-administration/cluster-status-monitoring.md b/content/en/docs/cluster-administration/cluster-status-monitoring.md
index 142a39a18..7dd678104 100644
--- a/content/en/docs/cluster-administration/cluster-status-monitoring.md
+++ b/content/en/docs/cluster-administration/cluster-status-monitoring.md
@@ -10,17 +10,17 @@ KubeSphere provides monitoring of related metrics such as CPU, memory, network,
 
 ## Prerequisites
 
-You need an account granted a role including the authorization of **Clusters Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
+You need an account granted a role including the authorization of **Cluster Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
 
 ## Cluster Status Monitoring
 
-1. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Click **Platform** in the top left corner and select **Cluster Management**.
 
     ![Platform](/images/docs/cluster-administration/cluster-status-monitoring/platform.png)
 
 2. If you have enabled the [multi-cluster feature](../../multicluster-management/) with member clusters imported, you can select a specific cluster to view its application resources. If you have not enabled the feature, refer to the next step directly.
 
-    ![Clusters Management](/images/docs/cluster-administration/cluster-status-monitoring/clusters-management.png)
+    ![Cluster Management](/images/docs/cluster-administration/cluster-status-monitoring/clusters-management.png)
 
 3. Choose **Cluster Status** under **Monitoring & Alerting** to see the overview of cluster status monitoring, including **Cluster Node Status**, **Components Status**, **Cluster Resources Usage**, **ETCD Monitoring**, and **Service Component Monitoring**, as shown in the following figure.
 
diff --git a/content/en/docs/cluster-administration/cluster-wide-alerting-and-notification/alerting-message.md b/content/en/docs/cluster-administration/cluster-wide-alerting-and-notification/alerting-message.md
index 2299c4657..e99474725 100644
--- a/content/en/docs/cluster-administration/cluster-wide-alerting-and-notification/alerting-message.md
+++ b/content/en/docs/cluster-administration/cluster-wide-alerting-and-notification/alerting-message.md
@@ -18,7 +18,7 @@ You have created a node-level alerting policy and received alert notifications o
 
 1. Log in to the console with one account granted the role `platform-admin`.
 
-2. Click **Platform** in the top left corner and select **Clusters Management**.
+2. Click **Platform** in the top left corner and select **Cluster Management**.
 
     ![alerting_message_node_level_guide](/images/docs/alerting/alerting_message_node_level_guide.png)
 
diff --git a/content/en/docs/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy.md b/content/en/docs/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy.md
index 9933d249f..57ad32f2f 100644
--- a/content/en/docs/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy.md
+++ b/content/en/docs/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy.md
@@ -21,7 +21,7 @@ KubeSphere provides alerting policies for nodes and workloads. This guide demons
 
 1. Log in to the console with one account granted the role `platform-admin`.
 
-2. Click **Platform** in the top left corner and select **Clusters Management**.
+2. Click **Platform** in the top left corner and select **Cluster Management**.
 
     ![alerting_policy_node_level_guide](/images/docs/alerting/alerting_policy_node_level_guide.png)
 
diff --git a/content/en/docs/cluster-administration/nodes.md b/content/en/docs/cluster-administration/nodes.md
index 084535040..64284e8e6 100644
--- a/content/en/docs/cluster-administration/nodes.md
+++ b/content/en/docs/cluster-administration/nodes.md
@@ -13,13 +13,13 @@ This tutorial demonstrates what a cluster administrator can view and do for node
 
 ## Prerequisites
 
-You need an account granted a role including the authorization of **Clusters Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
+You need an account granted a role including the authorization of **Cluster Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
 
 ## Node Status
 
 Cluster nodes are only accessible to cluster administrators. Some node metrics are very important to clusters. Therefore, it is the administrator's responsibility to watch over these numbers and make sure nodes are available. Follow the steps below to view node status.
 
-1. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Click **Platform** in the top left corner and select **Cluster Management**.
 
     ![clusters-management-select](/images/docs/cluster-administration/node-management/clusters-management-select.jpg)
 
diff --git a/content/en/docs/cluster-administration/persistent-volume-and-storage-class.md b/content/en/docs/cluster-administration/persistent-volume-and-storage-class.md
index ea32bb476..b5cdc9709 100644
--- a/content/en/docs/cluster-administration/persistent-volume-and-storage-class.md
+++ b/content/en/docs/cluster-administration/persistent-volume-and-storage-class.md
@@ -28,11 +28,11 @@ The table below summarizes common volume plugins for various provisioners (stora
 
 ## Prerequisites
 
-You need an account granted a role including the authorization of **Clusters Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
+You need an account granted a role including the authorization of **Cluster Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
 
 ## Manage Storage Classes
 
-1. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Click **Platform** in the top left corner and select **Cluster Management**.
    
     ![clusters-management-select](/images/docs/cluster-administration/persistent-volume-and-storage-class/clusters-management-select.jpg)
     
diff --git a/content/en/docs/devops-user-guide/how-to-use/jenkins-email.md b/content/en/docs/devops-user-guide/how-to-use/jenkins-email.md
index deb3750cb..789440e55 100644
--- a/content/en/docs/devops-user-guide/how-to-use/jenkins-email.md
+++ b/content/en/docs/devops-user-guide/how-to-use/jenkins-email.md
@@ -12,11 +12,11 @@ The built-in Jenkins cannot share the same email configuration with the platform
 ## Prerequisites
 
 - You need to enable the [KubeSphere DevOps System](../../../pluggable-components/devops/).
-- You need an account granted a role including the authorization of **Clusters Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
+- You need an account granted a role including the authorization of **Cluster Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
 
 ## Set the Email Server
 
-1. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Click **Platform** in the top left corner and select **Cluster Management**.
 
    ![clusters-management](/images/docs/devops-user-guide/using-devops/jenkins-email/clusters-management.jpg)
 
diff --git a/content/en/docs/devops-user-guide/how-to-use/jenkins-setting.md b/content/en/docs/devops-user-guide/how-to-use/jenkins-setting.md
index 51ab1feca..0421494ed 100644
--- a/content/en/docs/devops-user-guide/how-to-use/jenkins-setting.md
+++ b/content/en/docs/devops-user-guide/how-to-use/jenkins-setting.md
@@ -20,7 +20,7 @@ You have enabled [the KubeSphere DevOps System](../../../pluggable-components/de
 
 It is recommended that you configure Jenkins in KubeSphere through Configuration-as-Code (CasC). The built-in Jenkins CasC file is stored as a [ConfigMap](../../../project-user-guide/configuration/configmaps/).
 
-1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Cluster Management**.
 
    ![cluster-management](/images/docs/devops-user-guide/using-devops/jenkins-system-settings/cluster-management.jpg)
 
diff --git a/content/en/docs/devops-user-guide/how-to-use/set-ci-node.md b/content/en/docs/devops-user-guide/how-to-use/set-ci-node.md
index 86eb8c8e4..de8acc51c 100644
--- a/content/en/docs/devops-user-guide/how-to-use/set-ci-node.md
+++ b/content/en/docs/devops-user-guide/how-to-use/set-ci-node.md
@@ -12,11 +12,11 @@ This tutorial demonstrates how you set CI nodes so that KubeSphere schedules tas
 
 ## Prerequisites
 
-You need an account granted a role including the authorization of **Clusters Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
+You need an account granted a role including the authorization of **Cluster Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
 
 ## Label a CI Node
 
-1. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Click **Platform** in the top left corner and select **Cluster Management**.
 
    ![clusters-management](/images/docs/devops-user-guide/using-devops/set-ci-node-for-dependency-cache/clusters-management.jpg)
 
diff --git a/content/en/docs/faq/access-control/add-kubernetes-namespace-to-kubesphere-workspace.md b/content/en/docs/faq/access-control/add-kubernetes-namespace-to-kubesphere-workspace.md
index c5c502a66..53d18f9db 100644
--- a/content/en/docs/faq/access-control/add-kubernetes-namespace-to-kubesphere-workspace.md
+++ b/content/en/docs/faq/access-control/add-kubernetes-namespace-to-kubesphere-workspace.md
@@ -12,7 +12,7 @@ This tutorial demonstrates how to add an existing Kubernetes namespace to a Kube
 
 ## Prerequisites
 
-- You need an account granted a role including the authorization of **Clusters Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
+- You need an account granted a role including the authorization of **Cluster Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
 
 - You have an available workspace so that the namespace can be assigned to it. For more information, see [Create Workspaces, Projects, Accounts and Roles](../../../quick-start/create-workspace-and-project/).
 
diff --git a/content/en/docs/faq/installation/telemetry.md b/content/en/docs/faq/installation/telemetry.md
index a107d8f98..bb54b1694 100644
--- a/content/en/docs/faq/installation/telemetry.md
+++ b/content/en/docs/faq/installation/telemetry.md
@@ -65,7 +65,7 @@ If you install KubeSphere on Linux, see [Disable Telemetry after Installation](.
 
 1. Log in to the console as `admin` and click **Platform** in the top left corner.
 
-2. Select **Clusters Management** and navigate to **CRDs**.
+2. Select **Cluster Management** and navigate to **CRDs**.
 
     {{< notice note >}}
 If you have enabled [the multi-cluster feature](../../../multicluster-management/), you need to select a cluster first.
diff --git a/content/en/docs/installing-on-linux/persistent-storage-configurations/install-glusterfs.md b/content/en/docs/installing-on-linux/persistent-storage-configurations/install-glusterfs.md
index 28244b076..e35dd3948 100644
--- a/content/en/docs/installing-on-linux/persistent-storage-configurations/install-glusterfs.md
+++ b/content/en/docs/installing-on-linux/persistent-storage-configurations/install-glusterfs.md
@@ -284,7 +284,7 @@ glusterfs (default)   kubernetes.io/glusterfs   Delete          Immediate
 
 ### KubeSphere console
 
-1. Log in to the web console with the default account and password (`admin/P@88w0rd`) at `<NodeIP>:30880`. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Log in to the web console with the default account and password (`admin/P@88w0rd`) at `<NodeIP>:30880`. Click **Platform** in the top left corner and select **Cluster Management**.
 
 3. Go to **Volumes** under **Storage**, and you can see PVCs in use.
 
diff --git a/content/en/docs/installing-on-linux/persistent-storage-configurations/install-nfs-client.md b/content/en/docs/installing-on-linux/persistent-storage-configurations/install-nfs-client.md
index 6abbd7d29..3d91624ab 100644
--- a/content/en/docs/installing-on-linux/persistent-storage-configurations/install-nfs-client.md
+++ b/content/en/docs/installing-on-linux/persistent-storage-configurations/install-nfs-client.md
@@ -256,7 +256,7 @@ You can verify that NFS-client has been successfully installed either from the c
 
 ### KubeSphere console
 
-1. Log in to the web console as `admin` with the default account and password at `<NodeIP>:30880`. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Log in to the web console as `admin` with the default account and password at `<NodeIP>:30880`. Click **Platform** in the top left corner and select **Cluster Management**.
 
 2. Go to **Pods** in **Application Workloads** and select `kube-system` from the project drop-down list. You can see that the Pod of `nfs-client` is up and running.
 
diff --git a/content/en/docs/installing-on-linux/persistent-storage-configurations/install-qingcloud-csi.md b/content/en/docs/installing-on-linux/persistent-storage-configurations/install-qingcloud-csi.md
index a3ad82a24..82ade068b 100644
--- a/content/en/docs/installing-on-linux/persistent-storage-configurations/install-qingcloud-csi.md
+++ b/content/en/docs/installing-on-linux/persistent-storage-configurations/install-qingcloud-csi.md
@@ -261,7 +261,7 @@ You can verify that QingCloud CSI has been successfully installed either from th
 
 ### KubeSphere console
 
-1. Log in to the web console with the default account and password (`admin/P@88w0rd`) at `<NodeIP>:30880`. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Log in to the web console with the default account and password (`admin/P@88w0rd`) at `<NodeIP>:30880`. Click **Platform** in the top left corner and select **Cluster Management**.
 
 2. Go to **Pods** in **Application Workloads** and select `kube-system` from the project drop-down list. You can see that the Pods of `csi-qingcloud` are up and running.
 
diff --git a/content/en/docs/multicluster-management/enable-multicluster/agent-connection.md b/content/en/docs/multicluster-management/enable-multicluster/agent-connection.md
index f3376ce13..f7b2f5dbb 100644
--- a/content/en/docs/multicluster-management/enable-multicluster/agent-connection.md
+++ b/content/en/docs/multicluster-management/enable-multicluster/agent-connection.md
@@ -223,7 +223,7 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
 
 ## Import a Member Cluster
 
-1. Log in to the KubeSphere console as `admin` and click **Add Cluster** on the **Clusters Management** page.
+1. Log in to the KubeSphere console as `admin` and click **Add Cluster** on the **Cluster Management** page.
    
    ![add-cluster](/images/docs/multicluster-management/enable-multicluster-management-in-kubesphere/agent-connection/add-cluster.png)
 
diff --git a/content/en/docs/multicluster-management/enable-multicluster/direct-connection.md b/content/en/docs/multicluster-management/enable-multicluster/direct-connection.md
index 716105a43..acda74c39 100644
--- a/content/en/docs/multicluster-management/enable-multicluster/direct-connection.md
+++ b/content/en/docs/multicluster-management/enable-multicluster/direct-connection.md
@@ -150,7 +150,7 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
 
 ## Import a Member Cluster
 
-1. Log in to the KubeSphere console as `admin` and click **Add Cluster** on the **Clusters Management** page.
+1. Log in to the KubeSphere console as `admin` and click **Add Cluster** on the **Cluster Management** page.
    
    ![add-cluster](/images/docs/multicluster-management/enable-multicluster-management-in-kubesphere/direct-connection/add-cluster.png)
 
diff --git a/content/en/docs/multicluster-management/import-cloud-hosted-k8s/import-aliyun-ack.md b/content/en/docs/multicluster-management/import-cloud-hosted-k8s/import-aliyun-ack.md
index 2f9aab9fb..84385e797 100644
--- a/content/en/docs/multicluster-management/import-cloud-hosted-k8s/import-aliyun-ack.md
+++ b/content/en/docs/multicluster-management/import-cloud-hosted-k8s/import-aliyun-ack.md
@@ -29,7 +29,7 @@ This tutorial demonstrates how to import an Aliyun ACK cluster through the [dire
    jwtSecret: "QVguGh7qnURywHn2od9IiOX6X8f8wK8g"
    ```
 
-2. Log in to the KubeSphere console of the ACK cluster as `admin`. Click **Platform** in the upper left corner and then select **Clusters Management**.
+2. Log in to the KubeSphere console of the ACK cluster as `admin`. Click **Platform** in the upper left corner and then select **Cluster Management**.
 
 3. Go to **CRDs**, input `ClusterConfiguration` in the search bar, and then press **Enter** on your keyboard. Click **ClusterConfiguration** to go to its detail page.
 
@@ -65,7 +65,7 @@ Log in to the web console of Aliyun. Go to **Clusters** under **Container Servic
 
 ### Step 3: Import the ACK Member Cluster
 
-1. Log in to the KubeSphere console on your Host Cluster as `admin`. Click **Platform** in the upper left corner and then select **Clusters Management**. On the **Clusters Management** page, click **Add Cluster**.
+1. Log in to the KubeSphere console on your Host Cluster as `admin`. Click **Platform** in the upper left corner and then select **Cluster Management**. On the **Cluster Management** page, click **Add Cluster**.
 
    ![click-add-cluster](/images/docs/multicluster-management/import-cloud-hosted-k8s/import-ack/click-add-cluster.png)
 
diff --git a/content/en/docs/multicluster-management/import-cloud-hosted-k8s/import-aws-eks.md b/content/en/docs/multicluster-management/import-cloud-hosted-k8s/import-aws-eks.md
index 108654ef7..a18337552 100644
--- a/content/en/docs/multicluster-management/import-cloud-hosted-k8s/import-aws-eks.md
+++ b/content/en/docs/multicluster-management/import-cloud-hosted-k8s/import-aws-eks.md
@@ -33,7 +33,7 @@ You need to deploy KubeSphere on your EKS cluster first. For more information ab
    jwtSecret: "QVguGh7qnURywHn2od9IiOX6X8f8wK8g"
    ```
 
-2. Log in to the KubeSphere console of the EKS cluster as `admin`. Click **Platform** in the upper left corner and then select **Clusters Management**.
+2. Log in to the KubeSphere console of the EKS cluster as `admin`. Click **Platform** in the upper left corner and then select **Cluster Management**.
 
 3. Go to **CRDs**, input `ClusterConfiguration` in the search bar, and then press **Enter** on your keyboard. Click **ClusterConfiguration** to go to its detail page.
 
@@ -166,7 +166,7 @@ You need to deploy KubeSphere on your EKS cluster first. For more information ab
 
 ### Step 4: Import the EKS Member Cluster
 
-1. Log in to the KubeSphere console on your Host Cluster as `admin`. Click **Platform** in the upper left corner and then select **Clusters Management**. On the **Clusters Management** page, click **Add Cluster**.
+1. Log in to the KubeSphere console on your Host Cluster as `admin`. Click **Platform** in the upper left corner and then select **Cluster Management**. On the **Cluster Management** page, click **Add Cluster**.
 
    ![click-add-cluster](/images/docs/multicluster-management/import-cloud-hosted-k8s/import-gke/click-add-cluster.png)
 
diff --git a/content/en/docs/multicluster-management/import-cloud-hosted-k8s/import-gke.md b/content/en/docs/multicluster-management/import-cloud-hosted-k8s/import-gke.md
index 451cda4a5..b10ab0994 100644
--- a/content/en/docs/multicluster-management/import-cloud-hosted-k8s/import-gke.md
+++ b/content/en/docs/multicluster-management/import-cloud-hosted-k8s/import-gke.md
@@ -33,7 +33,7 @@ You need to deploy KubeSphere on your GKE cluster first. For more information ab
    jwtSecret: "QVguGh7qnURywHn2od9IiOX6X8f8wK8g"
    ```
 
-2. Log in to the KubeSphere console on GKE as `admin`. Click **Platform** in the upper left corner and then select **Clusters Management**.
+2. Log in to the KubeSphere console on GKE as `admin`. Click **Platform** in the upper left corner and then select **Cluster Management**.
 
 3. Go to **CRDs**, input `ClusterConfiguration` in the search bar, and then press **Enter** on your keyboard. Click **ClusterConfiguration** to go to its detail page.
 
@@ -111,7 +111,7 @@ You need to deploy KubeSphere on your GKE cluster first. For more information ab
 
 ### Step 4: Import the GKE Member Cluster
 
-1. Log in to the KubeSphere console on your Host Cluster as `admin`. Click **Platform** in the upper left corner and then select **Clusters Management**. On the **Clusters Management** page, click **Add Cluster**.
+1. Log in to the KubeSphere console on your Host Cluster as `admin`. Click **Platform** in the upper left corner and then select **Cluster Management**. On the **Cluster Management** page, click **Add Cluster**.
 
    ![click-add-cluster](/images/docs/multicluster-management/import-cloud-hosted-k8s/import-gke/click-add-cluster.png)
 
diff --git a/content/en/docs/multicluster-management/unbind-cluster.md b/content/en/docs/multicluster-management/unbind-cluster.md
index f8b48bd20..7a557c1e6 100644
--- a/content/en/docs/multicluster-management/unbind-cluster.md
+++ b/content/en/docs/multicluster-management/unbind-cluster.md
@@ -11,13 +11,13 @@ This tutorial demonstrates how to unbind a cluster from the central control plan
 ## Prerequisites
 
 - You have enabled multi-cluster management.
-- You need an account granted a role including the authorization of **Clusters Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
+- You need an account granted a role including the authorization of **Cluster Management**. For example, you can log in to the console as `admin` directly or create a new role with the authorization and assign it to an account.
 
 ## Unbind a Cluster
 
-1. Click **Platform** in the top left corner and select **Clusters Management**.
+1. Click **Platform** in the top left corner and select **Cluster Management**.
 
-2. On the **Clusters Management** page, click the cluster that you want to remove from the central control plane.
+2. On the **Cluster Management** page, click the cluster that you want to remove from the central control plane.
 
    ![clusters-management](/images/docs/multicluster-management/unbind-a-cluster/clusters-management.jpg)
 
diff --git a/content/en/docs/pluggable-components/alerting-notification.md b/content/en/docs/pluggable-components/alerting-notification.md
index ea5074942..10401ce5d 100644
--- a/content/en/docs/pluggable-components/alerting-notification.md
+++ b/content/en/docs/pluggable-components/alerting-notification.md
@@ -78,7 +78,7 @@ The process of installing KubeSphere on Kubernetes is same as stated in the tuto
 
 ## Enable Alerting and Notification after Installation
 
-1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
+1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
     
     ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-alerting-and-notification/clusters-management.png)
     
diff --git a/content/en/docs/pluggable-components/app-store.md b/content/en/docs/pluggable-components/app-store.md
index cb30ff689..0315bb527 100644
--- a/content/en/docs/pluggable-components/app-store.md
+++ b/content/en/docs/pluggable-components/app-store.md
@@ -72,7 +72,7 @@ The process of installing KubeSphere on Kubernetes is same as stated in the tuto
 
 ## Enable the App Store after Installation
 
-1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
+1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
    
    ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-app-store/clusters-management.png)
 
diff --git a/content/en/docs/pluggable-components/auditing-logs.md b/content/en/docs/pluggable-components/auditing-logs.md
index cccdf8247..fabe82c7c 100644
--- a/content/en/docs/pluggable-components/auditing-logs.md
+++ b/content/en/docs/pluggable-components/auditing-logs.md
@@ -100,7 +100,7 @@ By default, ks-installer will install Elasticsearch internally if Auditing is en
 
 ## Enable Auditing Logs after Installation
 
-1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
+1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
    
     ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-auditing-logs/clusters-management.png)
     
diff --git a/content/en/docs/pluggable-components/devops.md b/content/en/docs/pluggable-components/devops.md
index 064888d82..2c7393f21 100644
--- a/content/en/docs/pluggable-components/devops.md
+++ b/content/en/docs/pluggable-components/devops.md
@@ -70,7 +70,7 @@ The process of installing KubeSphere on Kubernetes is same as stated in the tuto
 
 ## Enable DevOps after Installation
 
-1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
+1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
    
    ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-devops-system/clusters-management.png)
 
diff --git a/content/en/docs/pluggable-components/events.md b/content/en/docs/pluggable-components/events.md
index f3bd55c54..482d75540 100644
--- a/content/en/docs/pluggable-components/events.md
+++ b/content/en/docs/pluggable-components/events.md
@@ -102,7 +102,7 @@ By default, ks-installer will install Elasticsearch internally if Events is enab
 
 ## Enable Events after Installation
 
-1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
+1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
    
     ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-events/clusters-management.png)
     
diff --git a/content/en/docs/pluggable-components/logging.md b/content/en/docs/pluggable-components/logging.md
index 516f8a90a..0a8ab6bd7 100644
--- a/content/en/docs/pluggable-components/logging.md
+++ b/content/en/docs/pluggable-components/logging.md
@@ -104,7 +104,7 @@ By default, ks-installer will install Elasticsearch internally if Logging is ena
 
 ## Enable Logging after Installation
 
-1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
+1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
    
    ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-logging-system/clusters-management.png)
 
diff --git a/content/en/docs/pluggable-components/metrics-server.md b/content/en/docs/pluggable-components/metrics-server.md
index fd5c37490..fef1118ec 100644
--- a/content/en/docs/pluggable-components/metrics-server.md
+++ b/content/en/docs/pluggable-components/metrics-server.md
@@ -49,7 +49,7 @@ If you install KubeSphere on some cloud hosted Kubernetes engines, it is probabl
 
 ## Enable the Metrics Server after Installation
 
-1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
+1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
    
     ![clusters-management](/images/docs/enable-pluggable-components/metrics-server/clusters-management.png)
     
diff --git a/content/en/docs/pluggable-components/network-policy.md b/content/en/docs/pluggable-components/network-policy.md
index 9117fcf8e..0d18dacdb 100644
--- a/content/en/docs/pluggable-components/network-policy.md
+++ b/content/en/docs/pluggable-components/network-policy.md
@@ -75,7 +75,7 @@ The process of installing KubeSphere on Kubernetes is same as stated in the tuto
 
 ## Enable the Network Policy after Installation
 
-1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
+1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
    
     ![clusters-management](/images/docs/enable-pluggable-components/network-policies/clusters-management.png)
     
diff --git a/content/en/docs/pluggable-components/service-mesh.md b/content/en/docs/pluggable-components/service-mesh.md
index 357c2926e..29c8cbb7d 100644
--- a/content/en/docs/pluggable-components/service-mesh.md
+++ b/content/en/docs/pluggable-components/service-mesh.md
@@ -69,7 +69,7 @@ The process of installing KubeSphere on Kubernetes is same as stated in the tuto
 
 ## Enable KubeSphere Service Mesh after Installation
 
-1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
+1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
     
     ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-service-mesh/clusters-management.png)
     
diff --git a/content/en/docs/quick-start/enable-pluggable-components.md b/content/en/docs/quick-start/enable-pluggable-components.md
index b70ce120c..c3d7bad93 100644
--- a/content/en/docs/quick-start/enable-pluggable-components.md
+++ b/content/en/docs/quick-start/enable-pluggable-components.md
@@ -83,7 +83,7 @@ Whether you install KubeSphere on Linux or on Kubernetes, you can check the stat
 
 The KubeSphere web console provides a convenient way for users to view and operate on different resources. To enable pluggable components after installation, you only need to make few adjustments on the console directly. For those who are accustomed to the Kubernetes command-line tool, kubectl, they will have no difficulty in using KubeSphere as the tool is integrated into the console.
 
-1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Clusters Management**.
+1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
 
     ![clusters-management](/images/docs/quickstart/enable-pluggable-components/clusters-management.png)