diff --git a/docs/tutorials/resource-migration.md b/docs/tutorials/resource-migration.md
index 2a7a5cbd..fd87c38d 100644
--- a/docs/tutorials/resource-migration.md
+++ b/docs/tutorials/resource-migration.md
@@ -180,11 +180,13 @@ which means the existing resources in `member1` cluster has been taken over by K
 
 So far, you have finished the migration, isn't it so easy?
 
-### Apply higher priority PropagationPolicy
+
+
+### Apply Higher Priority PropagationPolicy
 
 #### Step 5: Write the code
 
-Create new file `/tmp/pp-for-nginx-app.yaml` and copy text below to it:
+Create a new file `/tmp/pp-for-nginx-app.yaml` and copy the text below into it:
 
 ```yaml
 apiVersion: policy.karmada.io/v1alpha1
@@ -212,24 +214,48 @@ spec:
 
 #### Step 6: Run the command
 
-Apply this higher priority PropagationPolicy to Karmada control plane. 
+Apply this higher priority `PropagationPolicy` to the Karmada control plane:
 
 ```shell
-$ kubectl --context karmada-apiserver apply -f /tmp/pp-for-nginx-app.yaml
+kubectl --context karmada-apiserver apply -f /tmp/pp-for-nginx-app.yaml
 propagationpolicy.policy.karmada.io/nginx-pp created
 ```
 
 #### Step 7: Verification
 
 ```shell
-$ kubectl --context member2 get deploy -o wide 
-NAME           READY   UP-TO-DATE   AVAILABLE   AGE     CONTAINERS   IMAGES         SELECTOR
-nginx-deploy   2/2     2            2           5m24s   nginx        nginx:latest   app=nginx
-$ kubectl --context member2 get svc -o wide   
-NAME         TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE   SELECTOR
-nginx-svc    NodePort    10.13.161.255   <none>        80:30000/TCP   54s   app=nginx
-...
+kubectl --context member1 get deploy -o wide
+kubectl --context member1 get svc -o wide
+kubectl --context member2 get deploy -o wide
+kubectl --context member2 get svc -o wide
 ```
 
-As you see, you shall find `nginx` application related resource are all propagated to `member2` cluster, 
-which means the higher priority `PropagationPolicy` does work.
\ No newline at end of file
+You should see the `nginx` application related resources originally in `member1` also propagated to `member2`, completing the migration of resources :
+
+- **member1**:
+
+  ```shell
+  kubectl --context member1 get deploy -o wide
+  NAME           READY   UP-TO-DATE   AVAILABLE   AGE     CONTAINERS   IMAGES         SELECTOR
+  nginx-deploy   2/2     2            2           5m24s   nginx        nginx:latest   app=nginx
+
+  kubectl --context member1 get svc -o wide
+  NAME         TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE   SELECTOR
+  nginx-svc    NodePort    10.13.161.255   <none>        80:30000/TCP   54s   app=nginx
+  ```
+
+- **member2**:
+
+  ```shell
+  kubectl --context member2 get deploy -o wide
+  NAME           READY   UP-TO-DATE   AVAILABLE   AGE     CONTAINERS   IMAGES         SELECTOR
+  nginx-deploy   2/2     2            2           5m24s   nginx        nginx:latest   app=nginx
+
+  kubectl --context member2 get svc -o wide
+  NAME         TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE   SELECTOR
+  nginx-svc    NodePort    10.13.161.255   <none>        80:30000/TCP   54s   app=nginx
+  ```
+
+This confirms that the higher priority `PropagationPolicy` has effectively propagated the `nginx` application resources to both `member1` and `member2` clusters, meeting the desired propagation requirements.
+
+---