acrolinx

Author: halkazwini

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

@@ -18,7 +18,7 @@ With the increase of sophisticated and high-performance workloads in Azure, ther
 
 The connection troubleshoot feature of Azure Network Watcher helps reduce the amount of time to diagnose and troubleshoot network connectivity issues. The results returned can provide insights about the root cause of the connectivity problem and whether it's due to a platform or user configuration issue.
 
-Connection troubleshoot reduces the Mean Time To Resolution (MTTR) by providing a comprehensive method of performing all connection major checks to detect issues pertaining to network security groups, user-defined routes, and blocked ports and . It provides the following results with actionable insights where a step-by-step guide or corresponding documentation is provided for faster resolution:
+Connection troubleshoot reduces the Mean Time To Resolution (MTTR) by providing a comprehensive method of performing all connection major checks to detect issues pertaining to network security groups, user-defined routes, and blocked ports. It provides the following results with actionable insights where a step-by-step guide or corresponding documentation is provided for faster resolution:
 
 - Connectivity test with different destination types (VM, URI, FQDN, or IP Address).
 - Configuration issues that impact reachability.
@@ -120,4 +120,4 @@ The Connection troubleshoot feature returns fault types about the connection. Th
 ### Next steps
 
 - Learn more about [Network Watcher](network-watcher-monitoring-overview.md) 
-- Learn how to use connection troubleshoot using the [Azure Portal](network-watcher-connectivity-portal.md), [PowerShell](network-watcher-connectivity-powershell.md), the [Azure CLI](network-watcher-connectivity-cli.md), or [REST API](network-watcher-connectivity-rest.md).
+- Learn how to use connection troubleshoot using the [Azure portal](network-watcher-connectivity-portal.md), [PowerShell](network-watcher-connectivity-powershell.md), the [Azure CLI](network-watcher-connectivity-cli.md), or [REST API](network-watcher-connectivity-rest.md).

articles/network-watcher/network-watcher-connectivity-portal.md

@@ -62,7 +62,7 @@ In this section, you test connectivity between two connected virtual machines.
 
     - Network security group rules allow traffic between the two virtual machines.
     - The two virtual machines are directly connected (VM2 is the next hop of VM1).
-    - Azure default system route is used to route traffic between the two virtual machines (Route table Id: System route).
+    - Azure default system route is used to route traffic between the two virtual machines (Route table ID: System route).
     - 66 probes were successfully sent with average latency of 2 ms.
 
     :::image type="content" source="./media/network-watcher-connectivity-portal/virtual-machine-connected-test-result.png" alt-text="Screenshot of connection troubleshoot results after testing the connection between two connected virtual machines.":::
@@ -99,14 +99,14 @@ In this section, you test connectivity between two virtual machines that have co
 
 1. Select **Test connection**.
 
-    The test results show that the two virtual machines are not communicating:
+    The test results show that the two virtual machines aren't communicating:
 
-    - The two virtual machines are not connected (no probes were sent from VM1 to VM3).
-    - There is no route between the two virtual machines (Next hop type: None).
-    - Azure default system route is the route table used (Route table Id: System route).
+    - The two virtual machines aren't connected (no probes were sent from VM1 to VM3).
+    - There's no route between the two virtual machines (Next hop type: None).
+    - Azure default system route is the route table used (Route table ID: System route).
     - Network security group rules allow traffic between the two virtual machines.
 
-    :::image type="content" source="./media/network-watcher-connectivity-portal/virtual-machines-test-result.png" alt-text="Screenshot of connection troubleshoot results after testing the connection between two virtual machines that are not communicating.":::
+    :::image type="content" source="./media/network-watcher-connectivity-portal/virtual-machines-test-result.png" alt-text="Screenshot of connection troubleshoot results after testing the connection between two virtual machines that aren't communicating.":::
 
 ## Test connectivity with `www.bing.com`