Merge pull request #178913 from MikeRayMSFT/20211105-log-replay

Remove unexpected characters.

Author: MikeRayMSFT

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

@@ -410,9 +410,9 @@ Functional limitations of LRS are:
 After you start LRS, use the monitoring cmdlet (`get-azsqlinstancedatabaselogreplay` or `az_sql_midb_log_replay_show`) to see the status of the operation. If LRS fails to start after some time and you get an error, check for the most common issues:
 
 - Does an existing database on SQL Managed Instance have the same name as the one you're trying to migrate from SQL Server? Resolve this conflict by renaming one of databases.
-- Was the database backup on SQL Server made via the `CHECKSUM` option?
-- Are the permissions on the SAS token only read and list for LRS?
-- Did you copy the SAS token for LRS after the question mark (`?`), with content starting like this: `sv=2020-02-10...`? 
+- Was the database backup on SQL Server made via the `CHECKSUM` option?
+- Are the permissions on the SAS token only read and list for LRS?
+- Did you copy the SAS token for LRS after the question mark (`?`), with content starting like this: `sv=2020-02-10...`? 
 - Is the SAS token validity time applicable for the time window of starting and completing the migration? There might be mismatches due to the different time zones used for SQL Managed Instance and the SAS token. Try regenerating the SAS token and extending the token validity of the time window before and after the current date.
 - Are the database name, resource group name, and managed instance name spelled correctly?
 - If you started LRS in autocomplete mode, was a valid filename for the last backup file specified?