Merge pull request #214570 from v-ksreedevan/14Oct-NWchanges

Network watcher updates

Author: Court72

articles/network-watcher/connection-monitor.md

@@ -75,7 +75,7 @@ Complete the steps in [Create the first VM](#create-the-first-vm) again, with th
 
 |Step|Setting|Value|
 |---|---|---|
-| 1 | Select a version of the **Ubuntu Server** |                                                                     |
+| 1 | Select a version of **Ubuntu Server** |                                                                     |
 | 3 | Name                                  | myVm2                                                                   |
 | 3 | Authentication type                   | Paste your SSH public key or select **Password** and enter a password. |
 | 3 | Resource group                        | Select **Use existing** and select **myResourceGroup**.                 |
@@ -128,7 +128,7 @@ Create a connection monitor to monitor communication over TCP port 22 from *myVm
 
 Alerts are created by alert rules in Azure Monitor and can automatically run saved queries or custom log searches at regular intervals. A generated alert can automatically run one or more actions, such as to notify someone or start another process. When setting an alert rule, the resource that you target determines the list of available metrics that you can use to generate alerts.
 
-1. In the Azure portal, select the **Monitor** service, and then select **Alerts** > **New alert rule**.
+1. In Azure portal, select the **Monitor** service, and then select **Alerts** > **New alert rule**.
 2. Click **Select target**, and then select the resources that you want to target. Select the **Subscription**, and set the **Resource type** to filter down to the Connection Monitor that you want to use.
 
     ![alert screen with target selected](./media/connection-monitor/set-alert-rule.png)

articles/network-watcher/diagnose-vm-network-routing-problem.md

@@ -102,7 +102,7 @@ Azure automatically creates routes to default destinations. You may create custo
 
     When you ran the test using 13.107.21.200 in [Use next hop](#use-next-hop), the route with the address prefix 0.0.0.0/0 was used to route traffic to the address since no other route includes the address. By default, all addresses not specified within the address prefix of another route are routed to the internet.
 
-    When you ran the test using 172.31.0.100, however, the result informed you that there was no next hop type. As you can see in the previous picture, though there is a default route to the 172.16.0.0/12 prefix, which includes the 172.31.0.100 address, the **NEXT HOP TYPE** is **None**. Azure creates a default route to 172.16.0.0/12 but doesn't specify a next hop type until there is a reason to. If, for example, you added the 172.16.0.0/12 address range to the address space of the virtual network, Azure changes the **NEXT HOP TYPE** to **Virtual network** for the route. A check would then show the **Virtual network** as the **NEXT HOP TYPE**.
+    However, when you ran the test using 172.31.0.100, the result informed you that there was no next hop type. As you can see in the previous picture, though there is a default route to the 172.16.0.0/12 prefix, which includes the 172.31.0.100 address, the **NEXT HOP TYPE** is **None**. Azure creates a default route to 172.16.0.0/12 but doesn't specify a next hop type until there is a reason to. If, for example, you added the 172.16.0.0/12 address range to the address space of the virtual network, Azure changes the **NEXT HOP TYPE** to **Virtual network** for the route. A check would then show **Virtual network** as the **NEXT HOP TYPE**.
 
 ## Clean up resources
 

articles/network-watcher/quickstart-configure-network-security-group-flow-logs-from-arm-template.md

@@ -70,7 +70,7 @@ If there were issues with the deployment, see [Troubleshoot common Azure deploym
 
 ## Clean up resources
 
-You can delete Azure resources by using complete deployment mode. To delete a flow logs resource, specify a deployment in the complete mode without including the resource you want to delete. Read more about [complete deployment mode](../azure-resource-manager/templates/deployment-modes.md#complete-mode).
+You can delete Azure resources by using complete deployment mode. To delete a flow logs resource, specify a deployment in complete mode without including the resource you want to delete. Read more about [complete deployment mode](../azure-resource-manager/templates/deployment-modes.md#complete-mode).
 
 You also can disable an NSG flow log in the Azure portal:
 

articles/network-watcher/quickstart-configure-network-security-group-flow-logs-from-bicep.md

@@ -79,7 +79,7 @@ If there were issues with the deployment, see [Troubleshoot common Azure deploym
 
 ## Clean up resources
 
-You can delete Azure resources by using complete deployment mode. To delete a flow logs resource, specify a deployment in the complete mode without including the resource you want to delete. Read more about [complete deployment mode](../azure-resource-manager/templates/deployment-modes.md#complete-mode).
+You can delete Azure resources by using complete deployment mode. To delete a flow logs resource, specify a deployment in complete mode without including the resource you want to delete. Read more about [complete deployment mode](../azure-resource-manager/templates/deployment-modes.md#complete-mode).
 
 You also can disable an NSG flow log in the Azure portal:
 

includes/resource-manager-quickstart-bicep-introduction.md

@@ -6,4 +6,4 @@ ms.date: 09/27/2021
 ms.author: jgao
 ---
 
-[Bicep](../articles/azure-resource-manager/bicep/overview.md) is a domain-specific language (DSL) that uses a declarative syntax to deploy Azure resources. It provides concise syntax, reliable type safety, and support for code reuse. Bicep offers the best authoring experience for your infrastructure-as-code solutions in Azure.
+[Bicep](../articles/azure-resource-manager/bicep/overview.md) is a domain-specific language (DSL) that uses declarative syntax to deploy Azure resources. It provides concise syntax, reliable type safety, and support for code reuse. Bicep offers the best authoring experience for your infrastructure-as-code solutions in Azure.