Update Set-MigrationBatch.md

Author: chrisda

exchange/exchange-ps/exchange/Set-MigrationBatch.md

@@ -204,17 +204,15 @@ Accept wildcard characters: False
 ### -CompleteAfter
 This parameter is available only in the cloud-based service.
 
-The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch will start, but completion won´t start until the date/time you specify with this parameter.
+The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch will start, but completion won't start until the date/time you specify with this parameter.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format mm/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
-In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC).
+In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options:
 
-To specify a date/time value for this parameter, use either of the following options:
+- Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`.
 
-- Specify the date/time value in UTC: For example, "7/30/2020 9:00PM Z".
-
-- Specify the date/time value in your local time zone: For example, "7/30/2020 9:00PM -700" (Pacific Daylight Time). It will be converted to UTC if you don't use the -TimeZone parameter.
+- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter.
 
 ```yaml
 Type: DateTime
@@ -472,13 +470,11 @@ The StartAfter parameter specifies a delay before the data migration for the use
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format mm/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
-In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC).
-
-To specify a date/time value for this parameter, use either of the following options:
+In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options:
 
-- Specify the date/time value in UTC: For example, "7/30/2020 9:00PM Z".
+- Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`.
 
-- Specify the date/time value in your local time zone: For example, "7/30/2020 9:00PM -700" (Pacific Daylight Time). It will be converted to UTC if you don't use the -TimeZone parameter.
+- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter.
 
 ```yaml
 Type: DateTime