more updates

Author: Juliako

articles/azure-video-indexer/logic-apps-connector-arm-accounts.md

@@ -44,7 +44,7 @@ The following image shows the first flow:
 
 ![File upload flow](./media/logic-apps-connector-arm-accounts/first-flow-high-level.png)
 
-1. Create the [Logic App](https://ms.portal.azure.com/#create/Microsoft.LogicApp). We create a Logic App in the same region as the Azure Video  Indexer region (recommended). We call the logic app `UploadIndexVideosApp`.
+1. Create the [Logic App](https://ms.portal.azure.com/#create/Microsoft.LogicApp). We create a Logic App in the same region as the Azure Video  Indexer region (recommended but not required). We call the logic app `UploadIndexVideosApp`.
 
     1. Select **Consumption** for **Plan type**.
     1. Press **Review + Create** -> **Create**.
@@ -146,30 +146,28 @@ The following image shows the first flow:
         1. Press **Review + assign**.
 1. Back in your Logic App, create an **Upload video and index** action.
 
-    1. Select **Video Indexer(V2).
+    1. Select **Video Indexer(V2)**.
     1. From Video Indexer(V2) chose **Upload Video and index**.
     1. Set the connection to the Video Indexer account.
 
-    |Key| Value|
-    |----|----|
-    | Connection name| *Enter name for connection*, in this case `aviconnection`.|
-    | API key| This is your personal API key, which is available under **Profile** in the [developer portal](https://api-portal.videoindexer.ai/profile)|
-
-    Select **Create**.
-
-    ![api-key](./media/logic-apps-connector-arm-accounts/profile.png)
+        |Key| Value|
+        |----|----|
+        | Connection name| *Enter name for connection*, in this case `aviconnection`.|
+        | API key| This is your personal API key, which is available under **Profile** in the [developer portal](https://api-portal.videoindexer.ai/profile)|
+    
+        Select **Create**.
     1. Fill **Upload video and index** action parameters.
-
-    |Key| Value|
-    |----|----|
-    |Location| Location of the associated the Azure Video Indexer account.|	
-    | Account ID| Account ID of the associated Azure Video Indexer account. You can find the **Account ID** in the **Overview** page of your account, in the Azure portal. Or, the **Account settings** tab, left of the [Azure Video Indexer website](https://www.videoindexer.ai/).|
-    |Access Token| Select **accessToken** from the **dynamic content** of the **Parse JSON** action.|
-    | Video Name| Select **List of Files Name** from the dynamic content of **When a blob is added or modified** action. |
-    |Video URL|Select **Web Url** from the dynamic content of **Create SAS URI by path** action.|
-    | Body| Can be left as default.|
 
-    ![upload-video](./media/logic-apps-connector-arm-accounts/uplaod-and-index.png)
+        |Key| Value|
+        |----|----|
+        |Location| Location of the associated the Azure Video Indexer account.|	
+        | Account ID| Account ID of the associated Azure Video Indexer account. You can find the **Account ID** in the **Overview** page of your account, in the Azure portal. Or, the **Account settings** tab, left of the [Azure Video Indexer website](https://www.videoindexer.ai/).|
+        |Access Token| Select **accessToken** from the **dynamic content** of the **Parse JSON** action.|
+        | Video Name| Select **List of Files Name** from the dynamic content of **When a blob is added or modified** action. |
+        |Video URL|Select **Web Url** from the dynamic content of **Create SAS URI by path** action.|
+        | Body| Can be left as default.|
+        
+        ![upload-video](./media/logic-apps-connector-arm-accounts/uplaod-and-index.png)
 
 The completion of the uploading and indexing from the first flow will send an HTTP request with the correct callback URL to trigger the second flow. Then, it will retrieve the insights generated by Azure Video Indexer. In this example, it will store the output of your indexing job in your Azure Storage. However, it's up to you what you do with the output.
 
@@ -189,7 +187,7 @@ Create the second flow, Logic Apps of type consumption. The second flow is t
 
     > [!TIP]
     > We will come back to the URL created in this step. 
-1. Generate an access token 
+1. Generate an access token.
 
     Follow all the steps from: