Update known-issues-azure-sql-migration-azure-data-studio.md

error 2060 - correcting the T-sql - v2

Author: abhims14

articles/dms/known-issues-azure-sql-migration-azure-data-studio.md

@@ -269,13 +269,13 @@ This article provides a list of known issues and troubleshooting steps associate
 
   1. Add 'sysadmin' role to the account, which grants the admin permission.
 
-  1. If customers can't use admin account or can't grant admin permission to the account, then minimum permission on source SQL Server required is "db_owner"and they can create a user in master and grant **##MS_DatabaseManager##**,**##MS_DatabaseConnector##**, **##MS_DefinitionReader##** and **##MS_LoginManager##**  fixed server roles to the user. For example,
+  1. If customers can't use sysadmin account or can't grant sysadmin permission to the account, then minimum permission on source SQL Server required is "db_owner" and on target Azure SQL DB create a user in master and grant **##MS_DatabaseManager##**,**##MS_DatabaseConnector##**, **##MS_DefinitionReader##** and **##MS_LoginManager##** fixed server roles to the user. For example,
 
      ```sql
      -- Run the script in the master
      -- Please run the script on Master database
-      CREATE LOGIN testuser with Password = '*********';
-      ALTER SERVER ROLE ##MS_DefinitionReader## ADD MEMBER [testuser]; 
+     CREATE LOGIN testuser with Password = '*********';
+     ALTER SERVER ROLE ##MS_DefinitionReader## ADD MEMBER [testuser]; 
       GO
      ALTER SERVER ROLE ##MS_DatabaseConnector## ADD MEMBER [testuser]; 
       GO