fixed grammar

Author: alexlzx

articles/stream-analytics/cicd-tools.md

@@ -250,7 +250,7 @@ To deploy your Stream Analytics project using ARM templates, follow these steps:
       -TemplateParameterFile $parameterFile
     ```
 
-For more details about deploying resources with ARM templates, see [Deploy with a Resource Manager template file and Azure PowerShell](https://aka.ms/armdeploytemplate).
+For more information about deploying resources with ARM templates, see [Deploy with a Resource Manager template file and Azure PowerShell](https://aka.ms/armdeploytemplate).
 
 ## Next steps
 

articles/stream-analytics/optimize-query-using-job-diagram-simulator.md

@@ -11,7 +11,7 @@ ms.date: 12/27/2022
 
 # Optimize query using job diagram simulator
 
-One way to improve the performance of an Azure Stream Analytics job is to apply parallelism in query. This article demonstrates how to use the Job Diagram Simulator in Visual Studio Code (VSCode) and evaluate the query parallelism for a Stream Analytics job. You learn to visualize a query execution with different number of streaming units and improve query parallelism based on the edit suggestions. 
+One way to improve the performance of an Azure Stream Analytics job is to apply parallelism in query. This article demonstrates how to use the Job Diagram Simulator in Visual Studio Code (VS Code) and evaluate the query parallelism for a Stream Analytics job. You learn to visualize a query execution with different number of streaming units and improve query parallelism based on the edit suggestions. 
 
 ## What is parallel query?
 
@@ -26,46 +26,46 @@ If you want to learn more about query parallelization, see [Leverage query paral
 The **Job diagram simulator** feature simulates the job running topology in Azure and provides suggestions for adjusting Streaming Units. Therefore, you must configure live inputs and outputs for your Stream Analytics job and use them in the query. 
 
 Prerequisites: 
-* ASA Tools extension for VSCode. If you haven't installed it yet, follow [this guide](quick-create-visual-studio-code.md) to install. 
+* ASA Tools extension for VS Code. If you haven't installed it yet, follow [this guide](quick-create-visual-studio-code.md) to install. 
 * Configure live input and live output for your Stream Analytics job. 
 * You must include live input and output in the query.
 
 > [!NOTE]
 > The Job diagram simulator can't simulate job running topology for local inputs and outputs. It doesn't send results to the output destination.
 
-In this tutorial, you learn to improve query performance based on edit suggestions and make it executed in parallel. As an example, we're using a non-parallel job that takes the input data from an event hub and sends the results to another event hub.
+In this tutorial, you learn to improve query performance based on edit suggestions and make it executed in parallel. As an example, we're using a nonparallel job that takes the input data from an event hub and sends the results to another event hub.
 
-1. Open the Azure Stream Analytics project in VSCode after you finish your query authoring, go to the query file **\*.asaql** and select **Simulate job** to start the job diagram simulation.
+1. Open the Azure Stream Analytics project in VS Code after you finish your query authoring, go to the query file **\*.asaql** and select **Simulate job** to start the job diagram simulation.
 
-    :::image type="content" source="./media/job-diagram-simulator/query-file-simulate-job.png" alt-text="Screenshot of the VSCode opening job diagram simulator in query file." lightbox= "./media/job-diagram-simulator/query-file-simulate-job.png" :::
+    :::image type="content" source="./media/job-diagram-simulator/query-file-simulate-job.png" alt-text="Screenshot of the VS Code opening job diagram simulator in query file." lightbox= "./media/job-diagram-simulator/query-file-simulate-job.png" :::
 
 1. Under the **Diagram** tab, you can see the topology of the Azure Stream Analytics job. It shows the number of streaming nodes allocated to the job and the number of partitions in each streaming node. The below job diagram shows this job isn't in parallel since there's data interaction between the two nodes.
 
-    :::image type="content" source="./media/job-diagram-simulator/diagram-tab.png" alt-text="Screenshot of the VSCode using job diagram simulator and showing job topology." lightbox= "./media/job-diagram-simulator/diagram-tab.png" :::
+    :::image type="content" source="./media/job-diagram-simulator/diagram-tab.png" alt-text="Screenshot of the VS Code using job diagram simulator and showing job topology." lightbox= "./media/job-diagram-simulator/diagram-tab.png" :::
 
 1. Since this query is **NOT** in parallel, you can select **Enhancements** tab and view suggestions about optimizing query parallelism.
 
-    :::image type="content" source="./media/job-diagram-simulator/edit-suggestions.png" alt-text="Screenshot of the VSCode using job diagram simulator and showing the query edit suggestions." lightbox= "./media/job-diagram-simulator/edit-suggestions.png" :::
+    :::image type="content" source="./media/job-diagram-simulator/edit-suggestions.png" alt-text="Screenshot of the VS Code using job diagram simulator and showing the query edit suggestions." lightbox= "./media/job-diagram-simulator/edit-suggestions.png" :::
 
 1. Select query step in the enhancements list, you see the corresponding lines are highlighted and you can edit the query based on the suggestions.
 
-    :::image type="content" source="./media/job-diagram-simulator/query-highlight.png" alt-text="Screenshot of the VSCode using job diagram simulator and highlighting the query step." lightbox= "./media/job-diagram-simulator/query-highlight.png" :::
+    :::image type="content" source="./media/job-diagram-simulator/query-highlight.png" alt-text="Screenshot of the VS Code using job diagram simulator and highlighting the query step." lightbox= "./media/job-diagram-simulator/query-highlight.png" :::
 
     > [!NOTE] 
     > These are edit suggestions for improving your query parallelism. However, if you are using aggregate function among all partitions, having a parallel query might not be applicable to your business scenarios. 
 
-1. For this example, you add the **PartitionId** to line#22 and save your change. Then you can use **Refresh simulation** to get the new diagram as below. 
+1. For this example, you add the **PartitionId** to line#22 and save your change. Then you can use **Refresh simulation** to get the new diagram. 
 
     :::image type="content" source="./media/job-diagram-simulator/refresh-simulation-after-update-query.png" alt-text="Screenshot that shows the refresh diagram after updating query." lightbox= "./media/job-diagram-simulator/refresh-simulation-after-update-query.png" :::
 
 
-1. You can also adjust **Streaming Units** to stimulate how streaming nodes are allocated with different SUs. It will give you an idea of how many SUs you need to maximize the query performance. 
+1. You can also adjust **Streaming Units** to stimulate how streaming nodes are allocated with different SUs. It gives you an idea of how many SUs you need to maximize the query performance. 
 
-    :::image type="content" source="./media/job-diagram-simulator/job-diagram-simulator-adjust-su.png" alt-text="Screenshot of the VSCode using SU adjuster." lightbox= "./media/job-diagram-simulator/job-diagram-simulator-adjust-su.png" :::
+    :::image type="content" source="./media/job-diagram-simulator/job-diagram-simulator-adjust-su.png" alt-text="Screenshot of the VS Code using SU adjuster." lightbox= "./media/job-diagram-simulator/job-diagram-simulator-adjust-su.png" :::
 
 ## Processor-level diagram
 
-Once you have adjusted the streaming units to simulate the topology of your job, you can expand any of the streaming nodes to observe how your data is being processed at the processor level.
+Once you've adjusted the streaming units to simulate the topology of your job, you can expand any of the streaming nodes to observe how your data is being processed at the processor level.
 
 :::image type="content" source="./media/job-diagram-simulator/processor-level-simulator.gif" alt-text="A screenshot in gif format showing the processor level diagram of the simulator." lightbox= "./media/job-diagram-simulator/processor-level-simulator.gif" :::
 
@@ -87,7 +87,7 @@ Here are the explanations for Enhancements:
 | Input partition keys not matched | All inputs must use the same partition key. |
 | Low compatibility level | Upgrade **CompatibilityLevel** on **JobConfig.json** file. |
 | Output partition key not found | You need to use specified partition key for the output. |
-| Customized partition not supported | You can only use pre-defined partition keys.  |
+| Customized partition not supported | You can only use predefined partition keys.  |
 | Query step not using partition | Your query isn't using any PARTITION BY clause. |