check wording issue

alex-lin-msft · alex-lin-msft · commit 62a7e8a9afc5 · 2022-12-28T15:53:18.000+08:00
diff --git a/articles/stream-analytics/cicd-tools.md b/articles/stream-analytics/cicd-tools.md
@@ -21,7 +21,7 @@ You can [download the package](https://www.npmjs.com/package/azure-streamanalyti
 
 The **asa-streamanalytics-cicd** npm package provides the tools to generate Azure Resource Manager templates of Stream Analytics [Visual Studio Code projects](./quick-create-visual-studio-code.md) or [Visual Studio projects](stream-analytics-quick-create-vs.md). You can also use the npm package on Windows, macOS, and Linux without installing Visual Studio Code or Visual Studio.
 
-Once you have installed the package, use the following command to build your Stream Analytics projects.
+Once you've installed the package, use the following command to build your Stream Analytics projects.
 
 ```powershell
 azure-streamanalytics-cicd build -project <projectFullPath> [-outputPath <outputPath>]
@@ -32,7 +32,7 @@ The *build* command does a keyword syntax check and outputs the Azure Resource M
 | Parameter | Description |
 |---|---|
 | `-project` | The absolute path of the **asaproj.json** file for your Visual Studio Code project or **[Your project name].asaproj** for Visual Studio project. |
-| `-outputPath` | The path of the output folder for Azure Resource Manager Templates. If it is not specified, the templates will be placed in the current directory. |
+| `-outputPath` | The path of the output folder for Azure Resource Manager Templates. If it isn't specified, the templates will be placed in the current directory. |
 
 #### [Visual Studio Code](#tab/visual-studio-code)
 
@@ -60,7 +60,7 @@ When a Stream Analytics project builds successfully, it generates the following
 
 The default parameters in the parameters.json file are from the settings in your Visual Studio Code or Visual Studio project. If you want to deploy to another environment, replace the parameters accordingly.
 
-The default values for all credentials are **null**. You are required to set the values before you deploy to Azure.
+The default values for all credentials are **null**. You're required to set the values before you deploy to Azure.
 
 ```json
 "Input_EntryStream_sharedAccessPolicyKey": {
@@ -81,8 +81,8 @@ azure-streamanalytics-cicd localrun -project <projectFullPath> [-outputPath <out
 | Parameter | Description |
 |---|---|
 | `-project` | The path of the **asaproj.json** file for your Visual Studio Code project or **[Your project name].asaproj** for Visual Studio project. |
-| `-outputPath` | The path of the output folder. If it is not specified, the output result files will be placed in the current directory. |
-| `-customCodeZipFilePath` | The path of the zip file for C# custom code, such as a UDF or deserializer, if they are used. Package the DLLs into a zip file and specify this path. |
+| `-outputPath` | The path of the output folder. If it isn't specified, the output result files will be placed in the current directory. |
+| `-customCodeZipFilePath` | The path of the zip file for C# custom code, such as a UDF or deserializer, if they're used. Package the DLLs into a zip file and specify this path. |
 
 #### [Visual Studio Code](#tab/visual-studio-code)
 
@@ -116,7 +116,7 @@ azure-streamanalytics-cicd addtestcase -project <projectFullPath> [-testConfigPa
 | Parameter | Description |
 |---|---|
 | `-project` | The path of the **asaproj.json** file for your Visual Studio Code project or **[Your project name].asaproj** for Visual Studio project. |
-| `-testConfigPath` | The path of the test configuration file. If it is not specified, the file will be searched in **\test** under the current directory of the **asaproj.json** file, with default file name **testConfig.json**. A new file will be created if not existed. |
+| `-testConfigPath` | The path of the test configuration file. If it isn't specified, the file will be searched in **\test** under the current directory of the **asaproj.json** file, with default file name **testConfig.json**. A new file will be created if not existed. |
 
 > [!NOTE]
 > The `Script` value in the generated **testConfig.json** file is only for providing the context; It's not used in the testing logic. 
@@ -249,9 +249,9 @@ azure-streamanalytics-cicd test -project <projectFullPath> [-testConfigPath <tes
 | Parameter | Description |
 |---|---|
 | `-project` | The path of the **asaproj.json** file for your Visual Studio Code project or **[Your project name].asaproj** for Visual Studio project. |
-| `-testConfigPath` | The path to the test configuration file. If it is not specified, the file will be searched in **\test** under the current directory of the **asaproj.json** file, with default file name **testConfig.json**.
-| `-outputPath` | The path of the test result output folder. If it is not specified, the output result files will be placed in the current directory. |
-| `-customCodeZipFilePath` | The path of the zip file for custom code such as a UDF or deserializer, if they are used. |
+| `-testConfigPath` | The path to the test configuration file. If it isn't specified, the file will be searched in **\test** under the current directory of the **asaproj.json** file, with default file name **testConfig.json**.
+| `-outputPath` | The path of the test result output folder. If it isn't specified, the output result files will be placed in the current directory. |
+| `-customCodeZipFilePath` | The path of the zip file for custom code such as a UDF or deserializer, if they're used. |
 
 As an example, in a PowerShell enabled terminal, if all test assets are located in a `test` subfolder of the project folder. With each test run output stored in a new timestamped subfolder of a `testResults` subfolder:
 
diff --git a/articles/stream-analytics/develop-locally.md b/articles/stream-analytics/develop-locally.md
@@ -10,7 +10,7 @@ ms.service: stream-analytics
 
 # Develop and debug Azure Stream Analytics jobs locally
 
-Apart from creating and developing an Azure Stream Analytics job in the Azure portal, you can set up a Stream Analytics job using a developer tool on your computer. Azure Stream Analytics (ASA) allows you to use your favorite code editor e.g. Visual Studio Code to build and test query locally with live data streams from Azure Event Hub, IoT Hub, Blob Storage and other Azure resources. The ASA developer tool creates a fully functional node in local runtime to run your Stream Analytics job. You can also submit your local Stream Analytics jobs to Azure and change the job running status. This's a convenient way to build, test and manage your Stream Analytics jobs.
+Apart from creating and developing an Azure Stream Analytics job in the Azure portal, you can set up a Stream Analytics job using a developer tool on your computer. Azure Stream Analytics (ASA) allows you to use your favorite code editor, e.g.,  Visual Studio Code to build and test query locally with live data streams from Azure Event Hubs, IoT Hub, Blob Storage and other Azure resources. The ASA developer tool creates a fully functional node in local runtime to run your Stream Analytics job. You can also submit your local Stream Analytics jobs to Azure and change the job running status. Using the ASA developer tool is a convenient way to build, test and manage your Stream Analytics jobs.
 
 ## Local development environments
 
@@ -20,7 +20,7 @@ The environments in the following table support local development:
 
 |Environment                              |Description    |
 |-----------------------------------------|------------|
-|[Visual Studio Code](visual-studio-code-explore-jobs.md)| The [Azure Stream Analytics Tools extension](https://marketplace.visualstudio.com/items?itemName=ms-bigdatatools.vscode-asa) for Visual Studio Code allows you to author, manage, test your Stream analytics job both locally and in the cloud with rich IntelliSense and native source control. Supports development on Linux, MacOS and Windows. To learn more, see [Create an Azure Stream Analytics job in Visual Studio Code](quick-create-visual-studio-code.md). The extension also supports [Visual Studio Codespaces](https://visualstudio.microsoft.com/services/visual-studio-codespaces/) which is a cloud-hosted dev environment.|
+|[Visual Studio Code](visual-studio-code-explore-jobs.md)| The [Azure Stream Analytics Tools extension](https://marketplace.visualstudio.com/items?itemName=ms-bigdatatools.vscode-asa) for Visual Studio Code allows you to author, manage, test your Stream analytics job both locally and in the cloud with rich IntelliSense and native source control. Supports development on Linux, macOS and Windows. To learn more, see [Create an Azure Stream Analytics job in Visual Studio Code](quick-create-visual-studio-code.md). The extension also supports [Visual Studio Codespaces](https://visualstudio.microsoft.com/services/visual-studio-codespaces/), which is a cloud-hosted dev environment.|
 |[Command prompt or terminal](stream-analytics-tools-for-visual-studio-cicd.md)|The Azure Stream Analytics CI/CD NuGet package provides tools for Visual studio project build, local testing on an arbitrary machine. The Azure Stream Analytics CI/CD npm package provides tools for Visual Studio Code project builds (which generates an Azure Resource Manager template) on an arbitrary machine.|
 
 ## Next steps
diff --git a/articles/stream-analytics/set-up-cicd-pipeline.md b/articles/stream-analytics/set-up-cicd-pipeline.md
@@ -85,7 +85,7 @@ Use following steps if you need to use hosted-Linux agent:
    azure-streamanalytics-cicd build -project $(projectRootPath)/asaproj.json -outputpath $(projectRootPath)/$(outputPath)/$(deployPath)
    ```
 
-   The image below uses a Stream Analytics Visual Studio Code project as an example.
+   The image uses a Stream Analytics Visual Studio Code project as an example.
 
    :::image type="content" source="media/set-up-cicd-pipeline/command-line-config-build.png" alt-text="Enter configurations for command-line task visual studio code":::
 
@@ -138,7 +138,7 @@ You need to add a copy file task to copy the test summary file and Azure Resourc
 
 ## Save and run
 
-Once you have finished adding the npm package, command line, copy files, and publish build artifacts tasks, select **Save & queue**. When you are prompted, enter a save comment and select **Save and run**. You can download the testing results from **Summary** page of the pipeline.
+Once you have finished adding the npm package, command line, copy files, and publish build artifacts tasks, select **Save & queue**. When you're prompted, enter a save comment and select **Save and run**. You can download the testing results from **Summary** page of the pipeline.
 
 ## Check the build and test results
 
diff --git a/articles/stream-analytics/visual-studio-code-local-run.md b/articles/stream-analytics/visual-studio-code-local-run.md
@@ -10,7 +10,7 @@ ms.topic: how-to
 
 # Test Stream Analytics queries locally with sample data using Visual Studio Code
 
-You can use Azure Stream Analytics tools for Visual Studio Code to test your Stream Analytics jobs locally with sample data. You output results can be found as JSON files in the **LocalRunOutputs** folder of your project.
+You can use Azure Stream Analytics tools for Visual Studio Code to test your Stream Analytics jobs locally with sample data. The output results can be found as JSON files in the **LocalRunOutputs** folder of your project.
 
 For more information, see [Overview of local Stream Analytics runs in Visual Studio Code with ASA Tools](visual-studio-code-local-run-all.md).
 
@@ -26,13 +26,13 @@ You need to prepare sample input data files first. If you already have some samp
 
 1. Click **Preview data** in your input configuration file from the top line. Some input data will be fetched from IoT Hub and shown in the preview window.
 
-2. Once the data is shown, click **Save as** to save the data to a local file.
+2. Once the data is shown, select **Save as** to save the data to a local file.
 
  ![Preview live input](./media/quick-create-visual-studio-code/preview-live-input.png)
 
 ## Define a local input
 
-1. Click **input.json** under Inputs folder in your Stream Analytics project. Then select **Add local input** from the top line.
+1. Select **input.json** under Inputs folder in your Stream Analytics project. Then select **Add local input** from the top line.
 
     ![Add local input from project](./media/quick-create-visual-studio-code/add-input-from-project.png)
 
@@ -56,7 +56,7 @@ You need to prepare sample input data files first. If you already have some samp
 
     ![Enter local file path in Visual Studio](./media/vscode-local-run/local-file-path.png)
 
-6. Select **Preview Data** to preview the input data. The serialization type for your data is automatically detected if its JSON or CSV. Use the selector to view your data in **Table** or **Raw** format. The following table is an example of data in the **Table format**:
+6. Select **Preview Data** to preview the input data. The serialization type (JSON or CSV) for your data is automatically detected. Use the selector to view your data in **Table** or **Raw** format. The following table is an example of data in the **Table format**:
 
      ![Preview local data in table format](./media/vscode-local-run/local-file-preview-table.png)
 
@@ -72,7 +72,7 @@ Return to your query editor, and select **Run locally**. Then select **Use local
 
 ![Use local input](./media/vscode-local-run/run-locally-use-local-input.png)
 
-The result is shown in the right window. You can click **Run** to test again. You can also select **Open in folder** to see the result files in file explorer and further open them with other tools. The result files are only available in JSON format.
+The result is shown in the right window. You can select **Run** to test again. You can also select **Open in folder** to see the result files in file explorer and further open them with other tools. The result files are only available in JSON format.
 
 ![View local run result](./media/vscode-local-run/run-locally-result.png)
 
