Merge pull request #33729 from MicrosoftDocs/MashaMSFT-patch-2

Update log-replay-service-migrate.md

Author: prmerger-automator[bot]

azure-sql/managed-instance/log-replay-service-migrate.md

@@ -624,7 +624,7 @@ Consider the following limitations when migrating with LRS:
 - You must place backup files for different databases in separate folders on the Blob Storage account in a flat-file structure. Nesting folders inside database folders isn't supported.
 - If you're using autocomplete mode, the entire backup chain needs to be available in advance on the Blob Storage account. It isn't possible to add new backup files in autocomplete mode. Use continuous mode if you need to add new backup files while migration is in progress.
 - You must start LRS separately for each database that points to the full URI path that contains an individual database folder. 
-- The backup URI path, container name, or folder names should not contain `backup` or `backups` as these are reserved keywords.
+- The backup URI path, container name, or folder names can't contain `backup` or `Backup` as these are reserved keywords.
 - When starting multiple Log Replay restores in parallel, targeting the same storage container, ensure that the same valid SAS token is provided for every restore operation.
 - LRS can support up to 100 simultaneous restore processes per single managed instance.
 - A single LRS job can run for a maximum of 30 days, after which it will be automatically canceled.