Update New-MigrationBatch.md

chrisda · web-flow · commit bf575850e471 · 2019-11-21T13:59:43.000-08:00
diff --git a/exchange/exchange-ps/exchange/move-and-migration/New-MigrationBatch.md b/exchange/exchange-ps/exchange/move-and-migration/New-MigrationBatch.md
@@ -595,7 +595,7 @@ The BadItemLimit parameter specifies the maximum number of bad items that are al
 
 Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again.
 
-This parameter is in the process of being deprecated in the cloud-based service. In the future, if neither BadItemLimit nor LargeItemLimit is specified then the migration will use Skipped Item approval semantics instead of BadItemLimit semantics.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if neither the BadItemLimit or LargeItemLimit parameters are specified, the migration will use Skipped Item approval semantics instead of BadItemLimit semantics.
 
 ```yaml
 Type: Unlimited
