Merge pull request #49445 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)

Author: huypub

articles/azure-resource-manager/resource-manager-quickstart-create-templates-use-visual-studio-code.md

@@ -126,7 +126,7 @@ There are many methods for deploying templates.  In this quickstart, you use the
 
     From the screenshot output, the storage account name is *3tqebj3slyfyestandardsa*. 
 
-7. Run the following PowerShell command to list the newly created storage account:
+7. Run the following CLI command to list the newly created storage account:
 
     ```cli
     az storage account show --resource-group <ResourceGroupName> --name <StorageAccountName>

articles/hdinsight/hdinsight-component-versioning.md

@@ -46,7 +46,7 @@ The component versions associated with HDInsight cluster versions are listed in
 | Apache Phoenix |4.7.0 |4.7.0 |4.4.0 |4.4.0 |4.2.0 |4.0.0.2.1.7.0-2162 |-|
 | Apache Spark |2.3.0, 2.2.0, 2.1.0 |1.6.2, 2.0 |1.6.0 |1.5.2 |1.3.1 (Windows only) |-|-|
 | Apache Livy |0.4 |0.3 |0.3 |0.2 |-|-|-|
-| Apache Kafka | 1.0, 0.10.1 | 0.10.0 | 0.9.0 |-|-|-|-|
+| Apache Kafka | 1.1, 1.0, 0.10.1 | 0.10.0 | 0.9.0 |-|-|-|-|
 | Apache Ambari | 2.6.0 | 2.4.0 | 2.2.1 | 2.1.0 |-|-|-|
 | Apache Zeppelin | 0.7.0 |-|-|-|-|-|-|
 | Mono |4.2.1 |4.2.1 |3.2.8 |-|-|-|

articles/iot-edge/quickstart-linux.md

@@ -287,7 +287,8 @@ Delete the containers that were created on your device by the IoT Edge runtime.
 Remove the container runtime.
 
    ```bash
-   sudo apt-get remove --purge moby
+   sudo apt-get remove --purge moby-cli
+   sudo apt-get remove --purge moby-engine
    ```
 
 ## Next steps

articles/monitoring-and-diagnostics/monitor-alerts-unified-log.md

@@ -81,7 +81,7 @@ Then alert would run the query every 5 minutes, with 30 minutes of data - to loo
 #### Example
 Consider a scenario where you wanted an alert if any computer exceeded processor utilization of 90% three times over 30 minutes.  You would create an alert rule with the following details:  
 
-- **Query:** Perf | where ObjectName == "Processor" and CounterName == "% Processor Time" | summarize AggregatedValue = avg(CounterValue) by bin(TimeGenerated, 5 m), Computer<br>
+- **Query:** Perf | where ObjectName == "Processor" and CounterName == "% Processor Time" | summarize AggregatedValue = avg(CounterValue) by bin(TimeGenerated, 5m), Computer<br>
 - **Time period:** 30 minutes<br>
 - **Alert frequency:** five minutes<br>
 - **Aggregate value:** Greater than 90<br>

articles/sql-database/sql-database-managed-instance-vnet-configuration.md

@@ -33,7 +33,7 @@ Plan how you deploy a Managed Instance in virtual network using your answers to
 
 ## Requirements
 
-For Managed Instance creation you need dedicate subnet inside the VNet that conforms to the following requirements:
+For Managed Instance creation you need to dedicate a subnet inside the VNet that conforms to the following requirements:
 - **Be empty**: The subnet must not contain any other cloud service associated to it, and it must not be Gateway subnet. You won’t be able to create Managed Instance in subnet that contains resources other than managed instance or add other resources inside the subnet later.
 - **No NSG**: The subnet must not have a Network Security Group associated with it.
 - **Have specific route table**: The subnet must have a User Route Table (UDR) with 0.0.0.0/0 Next Hop Internet as the only route assigned to it. For more information, see [Create the required route table and associate it](#create-the-required-route-table-and-associate-it)

includes/app-service-mobile-android-run-app.md

@@ -1,8 +1,8 @@
 
-1. Visit the [Azure Portal]. Click **Browse All** > **Mobile Apps** > the backend that you just created. In the mobile app settings, click **Quickstart** > **Android)**. Under **Configure your client application**, click **Download**. This downloads a complete Android project for an app pre-configured to connect to your backend. 
+1. Visit the [Azure Portal]. Click **Browse All** > **Mobile Apps** > the backend that you just created. In the mobile app settings, click **Quickstart** > **Android**. Under **Configure your client application**, click **Download**. This downloads a complete Android project for an app pre-configured to connect to your backend. 
 2. Open the project using **Android Studio**, using **Import project (Eclipse ADT, Gradle, etc.)**. Make sure you make this import selection to avoid any JDK errors.
 3. Press the **Run 'app'** button to build the project and start the app in the Android simulator.
-4. In the app, type meaningful text, such as *Complete the tutorial* and then click the 'Add' button. This sends a POST request to the Azure backend you deployed earlier. The backend inserts data from the request is into the TodoItem SQL table, and returns information about the newly stored items back to the mobile app. The mobile app displays this data in the list. 
+4. In the app, type meaningful text, such as *Complete the tutorial* and then click the 'Add' button. This sends a POST request to the Azure backend you deployed earlier. The backend inserts data from the request into the TodoItem SQL table, and returns information about the newly stored items back to the mobile app. The mobile app displays this data in the list. 
 
     ![](./media/app-service-mobile-android-quickstart/mobile-quickstart-startup-android.png)