address review comments

Author: xujxu

articles/stream-analytics/job-diagram-with-metrics.md

@@ -86,9 +86,9 @@ The processor diagram in physical job diagram visualizes the processor topology
         | --- | --- | 
         | **Input** or **Output** | This processor is used for reading input or writing output data streams. |
         | **ReferenceData** | This processor is used for fetching the reference data. |
-        | **Computing** | This processor is used for processing the stream data according to the query logic, for example, aggregating, filtering, grouping with window, etc.. To learn more about the stream data computation query functions, see [Azure Stream Analytics Query Language Reference](/stream-analytics-query/stream-analytics-query-language-reference). |
+        | **Computing** | This processor is used for processing the stream data according to the query logic, for example, aggregating, filtering, grouping with window, etc. To learn more about the stream data computation query functions, see [Azure Stream Analytics Query Language Reference](/stream-analytics-query/stream-analytics-query-language-reference). |
         | **MarshallerUpstream** and **MarshallerDownstream** | When there's stream data interaction among streaming nodes, there will be two marshaller processors: 1). **MarshallerUpstream** for sending the data in the upstream streaming node and 2). **MarshallerDownstream** for receiving the data in the downstream streaming node. |
-        | **Merger** | This processor is to receive the crossing-partition stream data, which were outputted from several upstream streaming nodes. The best practice to optimize job performance is to update query to remove the merger processor to make the job become parallel since the merger processor is the bottleneck of the job. The job diagram simulator feature within VSCode ASA extension can help you simulating your query locally when you optimizing your job query. To learn more, see [Optimize query using job diagram simulator (preview)](./optimize-query-using-job-diagram-simulator.md). |
+        | **Merger** | This processor is to receive the crossing-partition stream data, which were outputted from several upstream streaming nodes. The best practice to optimize job performance is to update query to remove the merger processor to make the job become parallel since the merger processor is the bottleneck of the job. The job diagram simulator feature within Visual Studio Code ASA extension can help you simulating your query locally when you optimizing your job query. To learn more, see [Optimize query using job diagram simulator (preview)](./optimize-query-using-job-diagram-simulator.md). |
         |
 
 

articles/stream-analytics/media/no-code-build-power-bi-dashboard/no-code-pbi-configuration.png

@@ -48,7 +48,7 @@ This article describes how you can use the no code editor to easily create a Str
     - **Dataset**: it's the Power BI destination where the Azure Stream Analytics job output data is written into.
     - **Table**: it's the table name in the Dataset where the output data goes to.
 
-    :::image type="content" source="./media/no-code-build-power-bi-dashboard/nocode.pbi.configuration.png" alt-text="Screenshot that shows the Power BI output configuration." lightbox="./media/no-code-build-power-bi-dashboard/nocode.pbi.configuration.png" :::
+    :::image type="content" source="./media/no-code-build-power-bi-dashboard/no-code-pbi-configuration.png" alt-text="Screenshot that shows the Power BI output configuration." lightbox="./media/no-code-build-power-bi-dashboard/no-code-pbi-configuration.png" :::
 
 1. Optionally, select **Get static preview/Refresh static preview** to see the data preview that will be ingested in event hub.  
     :::image type="content" source="./media/no-code-build-power-bi-dashboard/no-code-output-static-preview.png" alt-text="Screenshot showing the Get static preview/Refresh static preview option." lightbox="./media/no-code-build-power-bi-dashboard/no-code-output-static-preview.png" :::

articles/stream-analytics/media/no-code-build-power-bi-dashboard/nocode.pbi.configuration.png

@@ -237,11 +237,11 @@ Managed identities eliminate the limitations of user-based authentication method
 
 **Exactly once delivery (preview)** is supported in the ADLS Gen2 as no code editor output. You can enable it in the **Write mode** section in ADLS Gen2 configuration. For more information about this feature, see [Exactly once delivery (preview) in Azure Data Lake Gen2](./blob-storage-azure-data-lake-gen2-output.md#exactly-once-delivery-public-preview)
 
-:::image type="content" source="./media/no-code-stream-processing/exactly-once-delivery-adls-gen2.png" alt-text="Screenshot that shows the exactly once configuration in ADLS Gen2 output." lightbox="./media/no-code-stream-processing/exactly-once-delivery-adls-gen2.png" :::
+:::image type="content" source="./media/no-code-stream-processing/exactly-once-delivery-adls.png" alt-text="Screenshot that shows the exactly once configuration in ADLS Gen2 output." lightbox="./media/no-code-stream-processing/exactly-once-delivery-adls.png" :::
 
 **Write to Delta Lake table (preview)** is supported in the ADLS Gen2 as no code editor output. You can access this option in section **Serialization** in ADLS Gen2 configuration. For more information about this feature, see [Write to Delta Lake table (Public Preview)](./write-to-delta-lake.md).
 
-:::image type="content" source="./media/no-code-stream-processing/delta-lake-format-output-in-adls-gen2.png" alt-text="Screenshot that shows the delta lake configuration in ADLS Gen2 output." lightbox="./media/no-code-stream-processing/delta-lake-format-output-in-adls-gen2.png" :::
+:::image type="content" source="./media/no-code-stream-processing/delta-lake-format-output-in-adls.png" alt-text="Screenshot that shows the delta lake configuration in ADLS Gen2 output." lightbox="./media/no-code-stream-processing/delta-lake-format-output-in-adls.png" :::
 
 ### Azure Synapse Analytics