Merge branch 'avinewimages1' of https://github.com/Juliako/azure-docs-pr into avinewimages1

Author: Juliako

articles/azure-video-indexer/connect-classic-account-to-arm.md

@@ -38,7 +38,7 @@ However, this can be resolved by assigning the right role-assignment to these us
 Only the account owner, who performed the connect action, is automatically assigned as the owner on the connected account. When [Azure policies][docs-governance-policy] are enforced, they override the settings on the account.
 
 If users are not added through Azure RBAC to the account after 30 days, they will lose access through API as well as Azure Video Indexer portal.  
-After the transition state ends, users will only be able to generate a valid access token through through ARM, making Azure RBAC the exclusive way to manage role-based access control on the account.
+After the transition state ends, users will only be able to generate a valid access token through ARM, making Azure RBAC the exclusive way to manage role-based access control on the account.
 
 > [!NOTE]
 > If there are invited users you wish to remove access from, do it before connecting the account to ARM. 
@@ -62,9 +62,11 @@ Before the end of the 30 days of transition state, you can remove access from us
 1. The Azure Video Indexer create blade will open.
 1. In the **Create Azure Video Indexer account** section enter required values.
 
-    * If you followed the steps the fields should be auto-populated, make sure to validate the eligible values.
+    If you followed the steps the fields should be auto-populated, make sure to validate the eligible values.
 
     ![connect-to-arm](media/connect-classic-account-to-arm/connect-blade.png)
+    
+    Here are the descriptions for the resource fields: 
 
     | Name | Description |
     | ---|---|