Apply suggestions from code review

Author: ttorble

articles/network-watcher/azure-monitor-agent-with-connection-monitor.md

@@ -38,7 +38,7 @@ Connection Monitor relies on lightweight executable files to run connectivity ch
 
 ### Agents for Azure virtual machines and scale sets
 
-To install agents for Azure virtual machines and Virtual Machine Scale sets, see the "Agents for Azure virtual machines and Virtual Machine Scale sets" section of [Monitor network connectivity by using Connection Monitor](connection-monitor-overview.md#agents-for-azure-virtual-machines-and-virtual-machine-scale-sets).
+To install agents for Azure virtual machines and Virtual Machine Scale Sets, see the "Agents for Azure virtual machines and Virtual Machine Scale Sets" section of [Monitor network connectivity by using Connection Monitor](connection-monitor-overview.md#agents-for-azure-virtual-machines-and-virtual-machine-scale-sets).
 
 ### Agents for on-premises machines
 

articles/network-watcher/connection-monitor-create-using-portal.md

@@ -22,11 +22,11 @@ This article describes how to create a monitor in Connection Monitor by using th
 > To minimize service disruption to your current workloads, [migrate your tests from Network Performance Monitor ](migrate-to-connection-monitor-from-network-performance-monitor.md) or  [migrate from Connection Monitor (classic)](migrate-to-connection-monitor-from-connection-monitor-classic.md) to the new connection monitor in Azure Network Watcher before February 19, 2024.
 
 > [!IMPORTANT]
-> Connection Monitor supports end-to-end connectivity checks from and to Azure Virtual Machine Scale sets. These checks enable faster performance monitoring and network troubleshooting across scale sets. 
+> Connection Monitor supports end-to-end connectivity checks from and to Azure Virtual Machine Scale Sets. These checks enable faster performance monitoring and network troubleshooting across scale sets. 
 
 ## Before you begin 
 
-In monitors that you create by using Connection Monitor, you can add on-premises machines, Azure virtual machines (VMs), and Azure Virtual Machine Scale sets as sources. These connection monitors can also monitor connectivity to endpoints. The endpoints can be on Azure or on any other URL or IP.
+In monitors that you create by using Connection Monitor, you can add on-premises machines, Azure virtual machines (VMs), and Azure Virtual Machine Scale Sets as sources. These connection monitors can also monitor connectivity to endpoints. The endpoints can be on Azure or on any other URL or IP.
 
 Here are some definitions to get you started:
 
@@ -111,7 +111,7 @@ In the Azure portal, to create a test group in a connection monitor, specify val
 
 * **Test group Name**: Enter the name of your test group.
 * **Sources**: Select **Add sources** to specify both Azure VMs and on-premises machines as sources if agents are installed on them. To learn about installing an agent for your source, see [Install monitoring agents](./connection-monitor-overview.md#install-monitoring-agents).
-   * To choose Azure agents, select the **Azure endpoints** tab. Here you see only VMs or Virtual Machine Scale sets that are bound to the region that you specified when you created the connection monitor. By default, VMs and Virtual Machine Scale sets are grouped into the subscription that they belong to. These groups are collapsed. 
+   * To choose Azure agents, select the **Azure endpoints** tab. Here you see only VMs or Virtual Machine Scale Sets that are bound to the region that you specified when you created the connection monitor. By default, VMs and Virtual Machine Scale sets are grouped into the subscription that they belong to. These groups are collapsed. 
 
        You can drill down to further levels in the hierarchy from the **Subscription** level:
 
@@ -121,7 +121,7 @@ In the Azure portal, to create a test group in a connection monitor, specify val
 
       When you select a virtual network, subnet, a single VM, or a virtual machine scale set, the corresponding resource ID is set as the endpoint. By default, all VMs in the selected virtual network or subnet participate in monitoring. To reduce the scope, either select specific subnets or agents or change the value of the scope property. 
 
-      :::image type="content" source="./media/connection-monitor-2-preview/add-sources-1.png" alt-text="Screenshot that shows the 'Add Sources' pane and the Azure endpoints, including the 'Virtual Machine Scale sets' tab in Connection Monitor.":::
+      :::image type="content" source="./media/connection-monitor-2-preview/add-sources-1.png" alt-text="Screenshot that shows the 'Add Sources' pane and the Azure endpoints, including the 'Virtual Machine Scale Sets' tab in Connection Monitor.":::
 
    * To choose on-premises agents, select the **Non–Azure endpoints** tab. Select from a list of on-premises hosts with a Log Analytics agent installed. Select **Arc Endpoint** as the **Type**, and select the subscriptions from the **Subscription** dropdown list. The list of hosts that have the [Azure Arc endpoint](azure-monitor-agent-with-connection-monitor.md) extension and the [Azure Monitor Agent extension](connection-monitor-install-azure-monitor-agent.md) enabled are displayed.
 
@@ -184,9 +184,9 @@ In the Azure portal, to create a test group in a connection monitor, specify val
    :::image type="content" source="./media/connection-monitor-2-preview/add-test-config.png" alt-text="Screenshot that shows where to set up a test configuration in Connection Monitor.":::
 
 * **Test Groups**: You can add one or more test groups to a connection monitor. These test groups can consist of multiple Azure or non-Azure endpoints.
-    * For selected Azure VMs or Azure Virtual Machine Scale sets and non-Azure endpoints without monitoring extensions, the extension for Azure VMs and the npm solution for non-Azure endpoints will be auto enabled after the creation of the connection monitor begins.
+    * For selected Azure VMs or Azure Virtual Machine Scale Sets and non-Azure endpoints without monitoring extensions, the extension for Azure VMs and the npm solution for non-Azure endpoints will be auto enabled after the creation of the connection monitor begins.
     * If the selected virtual machine scale set is set for a manual upgrade, you'll have to upgrade the scale set after Network Watcher extension installation to continue setting up the connection monitor with virtual machine scale set as endpoints. If the virtual machine scale set is set to auto upgrade, you don't need to worry about any upgrading after the Network Watcher extension is installed.
-    * In the previously mentioned scenario, you can consent to an auto upgrade of a virtual machine scale set with auto enabling of the Network Watcher extension during the creation of the connection monitor for Virtual Machine Scale sets with manual upgrading. This would eliminate your having to manually upgrade the virtual machine scale set after you install the Network Watcher extension.   
+    * In the previously mentioned scenario, you can consent to an auto upgrade of a virtual machine scale set with auto enabling of the Network Watcher extension during the creation of the connection monitor for Virtual Machine Scale Sets with manual upgrading. This would eliminate your having to manually upgrade the virtual machine scale set after you install the Network Watcher extension.   
 
    :::image type="content" source="./media/connection-monitor-2-preview/consent-vmss-auto-upgrade.png" alt-text="Screenshot that shows where to set up test groups and consent for auto-upgrading of a virtual machine scale set in the connection monitor.":::
 * **Disable test group**: You can select this checkbox to disable monitoring for all sources and destinations that the test group specifies. This checkbox is cleared by default.

articles/network-watcher/connection-monitor-virtual-machine-scale-set.md

@@ -1,6 +1,6 @@
 ---
-title: Tutorial - Monitor network communication between two Virtual Machine Scale sets by using the Azure portal 
-description: In this tutorial, you'll learn how to monitor network communication between two Virtual Machine Scale sets by using the Azure Network Watcher connection monitor capability.
+title: Tutorial - Monitor network communication between two Virtual Machine Scale Sets by using the Azure portal 
+description: In this tutorial, you'll learn how to monitor network communication between two Virtual Machine Scale Sets by using the Azure Network Watcher connection monitor capability.
 services: network-watcher
 documentationcenter: na
 author: Medha1507
@@ -16,7 +16,7 @@ ms.author: mjha
 ms.custom: mvc, engagement-fy23
 ---
 
-# Tutorial: Monitor network communication between two Virtual Machine Scale sets by using the Azure portal
+# Tutorial: Monitor network communication between two Virtual Machine Scale Sets by using the Azure portal
 
 Successful communication between a virtual machine scale set and an endpoint, such as another virtual machine (VM), can be critical for your organization. Sometimes, the introduction of configuration changes can break communication. In this tutorial, you learn how to:
 
@@ -73,8 +73,8 @@ First, create a public standard load balancer by using the Azure portal. The nam
 
 You can deploy a scale set with a Windows Server image or Linux images such as RHEL, CentOS, Ubuntu, or SLES.
 
-1. Type **Scale set** in the search box. In the results, under **Marketplace**, select **Virtual Machine Scale sets**. 
-1. On the **Virtual Machine Scale sets** pane, select **Create**.
+1. Type **Scale set** in the search box. In the results, under **Marketplace**, select **Virtual Machine Scale Sets**. 
+1. On the **Virtual Machine Scale Sets** pane, select **Create**.
 
    The **Create a virtual machine scale set** page opens. 
 1. On the **Basics** pane, under **Project details**, ensure that the correct subscription is selected, and then select **myVMSSResourceGroup** in the resource group list. 
@@ -184,7 +184,7 @@ In the Azure portal, to create a test group in a connection monitor, do the foll
 1. **Name**: Name your test group.
 1. **Sources**: You can specify both Azure VMs and on-premises machines as sources if agents are installed on them. To learn about installing an agent for your source, see [Install monitoring agents](./connection-monitor-overview.md#install-monitoring-agents).
 
-   * To choose Azure agents, select the **Azure endpoints** tab. Here you see only VMs or Virtual Machine Scale sets that are bound to the region that you specified when you created the connection monitor. By default, VMs and Virtual Machine Scale sets are grouped into the subscription that they belong to. These groups are collapsed. 
+   * To choose Azure agents, select the **Azure endpoints** tab. Here you see only VMs or Virtual Machine Scale Sets that are bound to the region that you specified when you created the connection monitor. By default, VMs and Virtual Machine Scale Sets are grouped into the subscription that they belong to. These groups are collapsed. 
 
      You can drill down from the **Subscription** level to other levels in the hierarchy:
 
@@ -261,9 +261,9 @@ In the Azure portal, to create a test group in a connection monitor, do the foll
 
 1. **Test Groups**: You can add one or more Test Groups to a Connection Monitor. These test groups can consist of multiple Azure or non-Azure endpoints.
 
-   For selected Azure VMs or Azure Virtual Machine Scale sets and non-Azure endpoints without monitoring extensions, the extension for Azure VMs and the Network Performance Monitor solution for non-Azure endpoints will be auto-enabled after the creation of Connection Monitor begins.
+   For selected Azure VMs or Azure Virtual Machine Scale Sets and non-Azure endpoints without monitoring extensions, the extension for Azure VMs and the Network Performance Monitor solution for non-Azure endpoints will be auto-enabled after the creation of Connection Monitor begins.
 
-   If the selected Virtual Machine Scale set is set for manual upgrade, you'll have to upgrade the scale set after the Network Watcher extension installation. Doing so lets you continue setting up the Connection Monitor with Virtual Machine Scale sets as endpoints. If the virtual machine scale set is set to auto-upgrade, you don't need to worry about upgrading after the installation of the Network Watcher extension.
+   If the selected Virtual Machine Scale Set is set for manual upgrade, you'll have to upgrade the scale set after the Network Watcher extension installation. Doing so lets you continue setting up the Connection Monitor with Virtual Machine Scale Sets as endpoints. If the virtual machine scale set is set to auto-upgrade, you don't need to worry about upgrading after the installation of the Network Watcher extension.
 
    In the previously mentioned scenario, you can consent to an auto-upgrade of Virtual Machine Scale sets with auto-enabling of the Network Watcher extension during the creation of Connection Monitor for Virtual Machine Scale sets with manual upgrading. This approach eliminates the need to manually upgrade the virtual machine scale set after you install the Network Watcher extension. 
 

articles/network-watcher/network-insights-overview.md

@@ -57,7 +57,7 @@ The Resource view helps you visualize how a resource is configured. The Resource
 
 ![Sreenshot that shows Application Gateway view in Azure Monitor Network Insights.](media/network-insights-overview/application-gateway.png)
 
-The resource view for Application Gateway provides a simplified view of how the front-end IPs are connected to the listeners, rules, and backend pool. The connecting lines are color coded and provide additional details based on the backend pool health. The view also provides a detailed view of Application Gateway metrics and metrics for all related backend pools, like Virtual Machine Scale sets and VM instances.
+The resource view for Application Gateway provides a simplified view of how the front-end IPs are connected to the listeners, rules, and backend pool. The connecting lines are color coded and provide additional details based on the backend pool health. The view also provides a detailed view of Application Gateway metrics and metrics for all related backend pools, like Virtual Machine Scale Sets and VM instances.
 
 [![Screenshot that shows dependency view in Azure Monitor Network Insights.](media/network-insights-overview/dependency-view.png)](media/network-insights-overview/dependency-view.png#lightbox)