Implemented PM reviews

Author: rao-shwe

modules/install/pages/migration.adoc

@@ -31,7 +31,7 @@ Follow these steps to migrate your data to a new bucket during unidirectional re
 . Stop application traffic coming into Cluster 1 (Bucket A).
 +
 NOTE: Allow enough time for the replication queues to drain.
-Confirm by reviewing the XDCR Total Outbound Mutations statistic.
+Confirm by reviewing the XDCR Total Outbound Mutations statistic derived from `xdcr_changes_left_total`.
 For more information, see xref:manage:monitor/monitor-intro.html#monitoring-with-the-ui[].
 
 . Stop and delete the replication stream to Cluster 2 (Bucket A’).
@@ -50,8 +50,11 @@ For instructions, see
 xref:manage:manage-buckets/create-bucket.adoc[Create a Bucket].
 
 . Run the `cbbackupmgr` tool on Cluster 1 to restore data to Bucket B.
-Turn off the Conflict Resolution setting on the destination cluster and then use the `--force-updates` option to restore data from backup.
-Do this because the source and destination clusters have different conflict resolution types.
+Use the xref:backup-restore/ccbackupmgr-restore.adoc[`cbbackupmgr restore`] command with the option `--force-updates` to restore data from the backup.
+This option turns off conflict resolution during the restore,
+and it's needed because the bucket you're restoring to has a different conflict resolution type than the bucket the backup is from.
++
+NOTE: The `--force-updates` option also updates the CAS of the restored documents.
 
 . After the data restore operation is complete on Cluster 1, delete Bucket A’ from Cluster 2.
 
@@ -67,7 +70,7 @@ Follow these steps to migrate your data to a new bucket during bidirectional rep
 . Stop application traffic coming into Cluster 1 (Bucket A) and Cluster 2 (Bucket A’).
 +
 NOTE: Allow enough time for the replication queues to drain.
-Confirm by reviewing the XDCR Total Outbound Mutations statistic.
+Confirm by reviewing the XDCR Total Outbound Mutations statistic derived from `xdcr_changes_left_total`.
 For more information, see xref:manage:monitor/monitor-intro.html#monitoring-with-the-ui[].
 
 . Stop and delete the replication streams to both clusters.
@@ -88,6 +91,11 @@ For instructions, see xref:manage:manage-buckets/create-bucket.adoc[Create a Buc
 . Run the `cbbackupmgr` tool to restore data.
 Turn off the Conflict Resolution setting on the destination cluster and then use the `--force-updates` option to restore data from backup.
 Do this because the source and destination clusters have different conflict resolution types.
+Use the xref:backup-restore/ccbackupmgr-restore.adoc[`cbbackupmgr restore`] command with the option `--force-updates` to restore data from the backup.
+This option turns off conflict resolution during the restore,
+and it's needed because the bucket you're restoring to has a different conflict resolution type than the bucket the backup is from.
++
+NOTE: The `--force-updates` option also updates the CAS of the restored documents.
 
 . After the restore operation is complete on both clusters, create replication streams both ways between Cluster 1 and Cluster 2.
 For more information, see xref:manage:manage-xdcr/xdcr-management-overview.adoc[XDCR Management Overview].