Update faq.yml

Update-3

Author: abhims14

articles/dms/faq.yml

@@ -64,10 +64,13 @@ sections:
         answer: |
           a)	For Azure SQL VM and Azure SQL MI targets: 
               DMS uses physical migration i.e. using Backup and restore. Data consistency between source and target is ensured as explained below depending on the migration mode chosen-
-              **Offline migration**: During offline migration to Azure SQL VM and Azure SQL MI targets, application downtime starts when the migration starts, DMS will ensure that all the backup files get restored to the Target provided the last backup file/s from source is copied to SMB network storage or to blob container (as per the migration configuration).
+              
+              * Offline migration: During offline migration to Azure SQL VM and Azure SQL MI targets, application downtime starts when the migration starts, DMS will ensure that all the backup files get restored to the Target provided the last backup file/s from source is copied to SMB network storage or to blob container (as per the migration configuration).
               You can verify the last backup file name from source with the last applied backup file applied on target shown on DMS migration monitoring page.
-              **Online migration**: During online migration to Azure SQL VM and Azure SQL MI targets once you initiate the migration cutover and followed by stopping the application, DMS will ensure that all the backup files get restored to the Target provided the last backup file/s from source is copied to SMB network storage or to blob container (as per the migration configuration). It also shows the count for pending backup file/s which are yet to be applied on target, before you complete the migration cutover.
+              
+              * Online migration: During online migration to Azure SQL VM and Azure SQL MI targets once you initiate the migration cutover and followed by stopping the application, DMS will ensure that all the backup files get restored to the Target provided the last backup file/s from source is copied to SMB network storage or to blob container (as per the migration configuration). It also shows the count for pending backup file/s which are yet to be applied on target, before you complete the migration cutover.
               You can verify the last backup file name from source with the last applied backup file applied on target shown on DMS migration monitoring page.
+              
           b)	For Azure SQL DB targets-
               DMS does logical migration in case of Azure SQL DB i.e. it copies the data from source SQL database’s tables and write it to the Target Azure SQL DB’s tables. As DMS only support offline migration to Azure SQL DB, application downtime starts when the migration starts, you can monitor and validate the number of rows read (from source database table) and copied (written to target Azure SQL DB table) from the migration monitoring page.