diff --git a/docs/userguide/scheduling/resource-propagating.md b/docs/userguide/scheduling/resource-propagating.md
index 0b602f99..753ddc84 100644
--- a/docs/userguide/scheduling/resource-propagating.md
+++ b/docs/userguide/scheduling/resource-propagating.md
@@ -45,27 +45,21 @@ kubectl create deployment nginx --image nginx
 > Note: The resource exists only as a template in karmada. After being propagated to a member cluster, the behavior of the resource is the same as that of a single kubernetes cluster.
 
 > Note: Resources and PropagationPolicy are created in no sequence.
-  
 3. Display information of the deployment:
 ```shell
 karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
-   
 4. List the pods created by the deployment:
 ```shell
 karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +91,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -117,15 +107,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/userguide/scheduling/resource-propagating.md b/i18n/zh/docusaurus-plugin-content-docs/current/userguide/scheduling/resource-propagating.md
index 4f78004e..2d9b4d9d 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/current/userguide/scheduling/resource-propagating.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/current/userguide/scheduling/resource-propagating.md
@@ -52,8 +52,6 @@ karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
@@ -64,8 +62,6 @@ karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +93,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -117,15 +109,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/userguide/scheduling/resource-propagating.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/userguide/scheduling/resource-propagating.md
index 0e6730b0..e35706c8 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/userguide/scheduling/resource-propagating.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.3/userguide/scheduling/resource-propagating.md
@@ -45,27 +45,21 @@ kubectl create deployment nginx --image nginx
 > Note: The resource exists only as a template in karmada. After being propagated to a member cluster, the behavior of the resource is the same as that of a single kubernetes cluster.
 
 > Note: Resources and PropagationPolicy are created in no sequence.
-   
 3. Display information of the deployment:
 ```shell
 karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
-   
 4. List the pods created by the deployment:
 ```shell
 karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +91,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -118,15 +108,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.4/userguide/scheduling/resource-propagating.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.4/userguide/scheduling/resource-propagating.md
index c4cc1603..5238f238 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.4/userguide/scheduling/resource-propagating.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.4/userguide/scheduling/resource-propagating.md
@@ -45,27 +45,21 @@ kubectl create deployment nginx --image nginx
 > Note: The resource exists only as a template in karmada. After being propagated to a member cluster, the behavior of the resource is the same as that of a single kubernetes cluster.
 
 > Note: Resources and PropagationPolicy are created in no sequence.
-   
 3. Display information of the deployment:
 ```shell
 karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
-   
 4. List the pods created by the deployment:
 ```shell
 karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +91,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -117,15 +107,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.5/userguide/scheduling/resource-propagating.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.5/userguide/scheduling/resource-propagating.md
index 4f78004e..2d9b4d9d 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.5/userguide/scheduling/resource-propagating.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.5/userguide/scheduling/resource-propagating.md
@@ -52,8 +52,6 @@ karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
@@ -64,8 +62,6 @@ karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +93,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -117,15 +109,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.6/userguide/scheduling/resource-propagating.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.6/userguide/scheduling/resource-propagating.md
index 4f78004e..2d9b4d9d 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.6/userguide/scheduling/resource-propagating.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.6/userguide/scheduling/resource-propagating.md
@@ -52,8 +52,6 @@ karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
@@ -64,8 +62,6 @@ karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +93,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -117,15 +109,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.7/userguide/scheduling/resource-propagating.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.7/userguide/scheduling/resource-propagating.md
index 4f78004e..2d9b4d9d 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.7/userguide/scheduling/resource-propagating.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.7/userguide/scheduling/resource-propagating.md
@@ -52,8 +52,6 @@ karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
@@ -64,8 +62,6 @@ karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +93,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -117,15 +109,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-v1.8/userguide/scheduling/resource-propagating.md b/i18n/zh/docusaurus-plugin-content-docs/version-v1.8/userguide/scheduling/resource-propagating.md
index 4f78004e..2d9b4d9d 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-v1.8/userguide/scheduling/resource-propagating.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-v1.8/userguide/scheduling/resource-propagating.md
@@ -52,8 +52,6 @@ karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
@@ -64,8 +62,6 @@ karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +93,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -117,15 +109,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/versioned_docs/version-v1.3/userguide/scheduling/resource-propagating.md b/versioned_docs/version-v1.3/userguide/scheduling/resource-propagating.md
index 0e6730b0..e35706c8 100644
--- a/versioned_docs/version-v1.3/userguide/scheduling/resource-propagating.md
+++ b/versioned_docs/version-v1.3/userguide/scheduling/resource-propagating.md
@@ -45,27 +45,21 @@ kubectl create deployment nginx --image nginx
 > Note: The resource exists only as a template in karmada. After being propagated to a member cluster, the behavior of the resource is the same as that of a single kubernetes cluster.
 
 > Note: Resources and PropagationPolicy are created in no sequence.
-   
 3. Display information of the deployment:
 ```shell
 karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
-   
 4. List the pods created by the deployment:
 ```shell
 karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +91,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -118,15 +108,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/versioned_docs/version-v1.4/userguide/scheduling/resource-propagating.md b/versioned_docs/version-v1.4/userguide/scheduling/resource-propagating.md
index d67c9b4f..5238f238 100644
--- a/versioned_docs/version-v1.4/userguide/scheduling/resource-propagating.md
+++ b/versioned_docs/version-v1.4/userguide/scheduling/resource-propagating.md
@@ -45,27 +45,21 @@ kubectl create deployment nginx --image nginx
 > Note: The resource exists only as a template in karmada. After being propagated to a member cluster, the behavior of the resource is the same as that of a single kubernetes cluster.
 
 > Note: Resources and PropagationPolicy are created in no sequence.
-  
 3. Display information of the deployment:
 ```shell
 karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
-   
 4. List the pods created by the deployment:
 ```shell
 karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +91,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -117,15 +107,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/versioned_docs/version-v1.5/userguide/scheduling/resource-propagating.md b/versioned_docs/version-v1.5/userguide/scheduling/resource-propagating.md
index 0b602f99..753ddc84 100644
--- a/versioned_docs/version-v1.5/userguide/scheduling/resource-propagating.md
+++ b/versioned_docs/version-v1.5/userguide/scheduling/resource-propagating.md
@@ -45,27 +45,21 @@ kubectl create deployment nginx --image nginx
 > Note: The resource exists only as a template in karmada. After being propagated to a member cluster, the behavior of the resource is the same as that of a single kubernetes cluster.
 
 > Note: Resources and PropagationPolicy are created in no sequence.
-  
 3. Display information of the deployment:
 ```shell
 karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
-   
 4. List the pods created by the deployment:
 ```shell
 karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +91,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -117,15 +107,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/versioned_docs/version-v1.6/userguide/scheduling/resource-propagating.md b/versioned_docs/version-v1.6/userguide/scheduling/resource-propagating.md
index 0b602f99..753ddc84 100644
--- a/versioned_docs/version-v1.6/userguide/scheduling/resource-propagating.md
+++ b/versioned_docs/version-v1.6/userguide/scheduling/resource-propagating.md
@@ -45,27 +45,21 @@ kubectl create deployment nginx --image nginx
 > Note: The resource exists only as a template in karmada. After being propagated to a member cluster, the behavior of the resource is the same as that of a single kubernetes cluster.
 
 > Note: Resources and PropagationPolicy are created in no sequence.
-  
 3. Display information of the deployment:
 ```shell
 karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
-   
 4. List the pods created by the deployment:
 ```shell
 karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +91,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -117,15 +107,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/versioned_docs/version-v1.7/userguide/scheduling/resource-propagating.md b/versioned_docs/version-v1.7/userguide/scheduling/resource-propagating.md
index 0b602f99..753ddc84 100644
--- a/versioned_docs/version-v1.7/userguide/scheduling/resource-propagating.md
+++ b/versioned_docs/version-v1.7/userguide/scheduling/resource-propagating.md
@@ -45,27 +45,21 @@ kubectl create deployment nginx --image nginx
 > Note: The resource exists only as a template in karmada. After being propagated to a member cluster, the behavior of the resource is the same as that of a single kubernetes cluster.
 
 > Note: Resources and PropagationPolicy are created in no sequence.
-  
 3. Display information of the deployment:
 ```shell
 karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
-   
 4. List the pods created by the deployment:
 ```shell
 karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +91,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -117,15 +107,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s
diff --git a/versioned_docs/version-v1.8/userguide/scheduling/resource-propagating.md b/versioned_docs/version-v1.8/userguide/scheduling/resource-propagating.md
index 0b602f99..753ddc84 100644
--- a/versioned_docs/version-v1.8/userguide/scheduling/resource-propagating.md
+++ b/versioned_docs/version-v1.8/userguide/scheduling/resource-propagating.md
@@ -45,27 +45,21 @@ kubectl create deployment nginx --image nginx
 > Note: The resource exists only as a template in karmada. After being propagated to a member cluster, the behavior of the resource is the same as that of a single kubernetes cluster.
 
 > Note: Resources and PropagationPolicy are created in no sequence.
-  
 3. Display information of the deployment:
 ```shell
 karmadactl get deployment
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member1   1/1     1            1           52s   Y
 ```
-   
 4. List the pods created by the deployment:
 ```shell
 karmadactl get pod -l app=nginx
 ```
 The output is similar to this:
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-s7vv9   member1   1/1     Running   0          52s
 ```
@@ -97,15 +91,11 @@ kubectl apply -f propagationpolicy-update.yaml
 ```
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE   ADOPTION
 nginx   member2   1/1     1            1           5s    Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          17s
 ```
@@ -117,15 +107,11 @@ You can update the deployment template. The changes will be automatically synchr
 1. Update deployment replicas to 2
 2. Display information of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME    CLUSTER   READY   UP-TO-DATE   AVAILABLE   AGE     ADOPTION
 nginx   member2   2/2     2            2           7m59s   Y
 ```
 3. List the pods of the deployment (the output is similar to this):
 ```shell
-The karmadactl get command now only supports the push mode. [ member3 ] is not running in push mode.
-
 NAME                     CLUSTER   READY   STATUS    RESTARTS   AGE
 nginx-6799fc88d8-8t8cc   member2   1/1     Running   0          8m12s
 nginx-6799fc88d8-zpl4j   member2   1/1     Running   0          17s