Update New-MoveRequest.md to clarify when to check status

Fixing use of incorrect verb (restore vs move) and timing of checking DCS.

Author: wesmimsft

exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md

@@ -559,7 +559,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is deprecated in the cloud-based service. [Data Consistency Score](https://learn.microsoft.com/exchange/mailbox-migration/track-prevent-data-loss-dcs) is used instead. Admins must review the DataConsistencyScore and any skipped items after the restore completes.
+**Note**: This parameter is deprecated in the cloud-based service. [Data Consistency Score](https://learn.microsoft.com/exchange/mailbox-migration/track-prevent-data-loss-dcs) is used instead. Admins must review the DataConsistencyScore and any skipped items before the move completes.
 
 ```yaml
 Type: Unlimited
@@ -840,7 +840,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is deprecated in the cloud-based service. [Data Consistency Score](https://learn.microsoft.com/exchange/mailbox-migration/track-prevent-data-loss-dcs). Admins must review the DataConsistencyScore and any skipped items after the restore completes.
+**Note**: This parameter is deprecated in the cloud-based service. [Data Consistency Score](https://learn.microsoft.com/exchange/mailbox-migration/track-prevent-data-loss-dcs). Admins must review the DataConsistencyScore and any skipped items before the move completes.
 
 ```yaml
 Type: Unlimited