Merge pull request #313991 from joasa123/patch-8

Update blackout window note for clarity

Author: prmerger-automator[bot]

articles/migrate/concepts-vmware-agentless-migration.md

@@ -230,10 +230,11 @@ You can also increase and decrease replication bandwidth based on a schedule by
 Azure Migrate provides a configuration-based mechanism that you can use to specify the time interval during which you don't want any replications to proceed. This interval is called the *blackout window*. The need for a blackout window can arise in multiple scenarios, such as when the source environment is resource constrained or when you want replication to happen only outside business hours.
 
 > [!NOTE]
-> The existing replication cycles at the start of the blackout window finish before the replication pauses.
+> The existing replication cycles before the start of the blackout window will complete before the replication pauses.
 >
 > For any migration that you initiate during the blackout window, the final replication doesn't run. The migration fails.
 
+
 You can specify a blackout window for the appliance by creating or updating the `GatewayDataWorker.json` file in `C:\ProgramData\Microsoft Azure\Config`. A typical file has this form:
 
 ```