Making last updates

Author: Carlos Robles

articles/dms/includes/sql-virtual-machines-limitations.md

@@ -23,5 +23,6 @@ ms.topic: include
 - There is a temporary limit of 80 databases per target Azure Virtual Machine. A workaround to break the limit (reset the counter) is to Uninstall and Reinstall SQL IaaS Agent Extension in the target Azure Virtual Machine.
 - Apart from configuring the Networking/Firewall of your Azure Storage Account to allow your VM to access backup files. You also need to configure the Networking/Firewall of your SQL Server on Azure VM to allow outbound connection to your storage account.
 - You need to keep the target SQL Server on Azure VM **power ON** while the SQL Migration is in progress. Also, when creating a new migration, failover or cancel the migration.
-- Error: `Login failed for user 'NT Service\SQLIaaSExtensionQuery`. Reason: SQL Server instance is in single-user mode. One possible reason is the target SQL Server on Azure VM is in upgrade mode. Solution: Please wait for the target SQL Server on Azure VM exit the upgrade mode and start migration again. 
-- Error: `Ext_RestoreSettingsError, message: Failed to create restore job.;Cannot create file 'F:\data\XXX.mdf' because it already exists`. Solution: Connect to the target SQL Server on Azure VM  and delete the XXX.mdf file. Then, start migration again. 
+- **Error**: `Login failed for user 'NT Service\SQLIaaSExtensionQuery`. 
+**Reason**: SQL Server instance is in single-user mode. One possible reason is the target SQL Server on Azure VM is in upgrade mode. **Solution**: Please wait for the target SQL Server on Azure VM exit the upgrade mode and start migration again. 
+- **Error**: `Ext_RestoreSettingsError, message: Failed to create restore job.;Cannot create file 'F:\data\XXX.mdf' because it already exists`. **Solution**: Connect to the target SQL Server on Azure VM  and delete the XXX.mdf file. Then, start migration again.