Merge pull request #172761 from joesarabia/patch-7

Update vmware-hcx-mon-guidance.md

Author: ShannonLeavitt

articles/azure-vmware/vmware-hcx-mon-guidance.md

@@ -24,7 +24,7 @@ In this article, you'll learn about the Azure VMware Solution-specific use cases
 In this scenario, VM1 is migrated to the cloud using the NE, which provides optimal VM to VM latency. As a result, VM1 needs low latency to VM3 on the local Azure VMware Solution segment. We migrate the VM1 gateway from on-premises to Azure VMware Solution (cloud) to ensure an optimal path for traffic (blue line). If the gateway remains on-premises (red line), a tromboning effect and higher latency are observed. 
 
 >[!NOTE]
->When you enable MON without migrating the VM gateway to the cloud side, it doesn't ensure an optimal path for traffic flow.  It also doesn't allow the evaluation of policy-based routes.
+>When you enable MON without migrating the VM gateway to the cloud side, it doesn't ensure an optimal path for traffic flow.  It also doesn't allow the evaluation of policy routes.
 
 :::image type="content" source="media/tutorial-vmware-hcx/hcx-mon-user-case-diagram-1.png" alt-text="Diagram showing the optimization for VM to VM L2 communication when using stretched networks." border="false":::
 
@@ -39,19 +39,17 @@ In this scenario, we assume a VM from on-premises has been migrated to Azure VMw
 
 By default and without using MON, a VM in Azure VMware Solution on a stretched network without MON can communicate back to on-premises using the ExpressRoute preferred path. Ideally, and based on customers use case one should evaluate how a VM on an Azure VMware Solution stretched segment enabled with MON should be traversing back to on-premises either over the NE or the T0 gateway via the ExpressRoute, but keeping traffic flows symmetric.
 
-If choosing the NE path for example, the MON policy-based routes have to specifically address the subnet on the on-premises side; otherwise, the 0.0/0 route is used. Policy-based routes can be found under the NE segment, selecting advanced. By default, all RFC1918 routes are included in the MON policy-based routes defined. 
+If choosing the NE path for example, the MON policy routes have to specifically address the subnet on the on-premises side; otherwise, the 0.0/0 route is used. Policy routes can be found under the NE segment, selecting advanced. By default, all RFC1918 IP addresses are included in the MON policy routes definition. 
 
-:::image type="content" source="media/tutorial-vmware-hcx/default-hcx-mon-policy-based-routes.png" alt-text="Screenshot showing the default policy-based routes.":::
-
-Policy-based routes are evaluated only if the VM gateway is migrated to the cloud. The effect of this configuration is that any matching subnets for the destination get tunneled over the NE appliance.  If not matched, they get routed through the T0 gateway.
+Policy routes are evaluated only if the VM gateway is migrated to the cloud. The effect of this configuration is that any matching subnets for the destination get tunneled over the NE appliance.  If not matched, they get routed through the T0 gateway.
 
 >[!NOTE]
 >Special consideration for using MON in Azure VMware Solution is to give the /32 routes advertised over BGP to its peers; this includes on-premises and Azure over the ExpressRoute connection. For example, a VM in Azure learns the path to an Azure VMware Solution VM on an Azure VMware Solution MON enabled segment. Once the return traffic is sent back to the T0 as expected, if the return subnet is an RFC1918 match, traffic is forced over the NE instead of the T0.  Then egresses over the ExpressRoute back to Azure on the on-premises side.  This can cause confusion for stateful firewalls in the middle and asymmetric routing behavior. It's also a good idea to determine how VMs on NE MON segments will need to access the internet, either via the T0 in Azure VMware Solution or only through the NE back to on-premises.
 
 :::image type="content" source="media/tutorial-vmware-hcx/hcx-mon-user-case-diagram-3.png" alt-text="Diagram showing the RFC1918 egress and egress traffic flow." border="false":::
 
-As outlined in the above diagram, the importance is to match a policy-based route to each required subnet. Otherwise, the traffic gets routed over the T0 and not the NE.
+As outlined in the above diagram, the importance is to match a policy route to each required subnet. Otherwise, the traffic gets routed over the T0 and not the NE.
 
 
-To learn more about policy-based routes, see [Mobility Optimized Networking Policy Routes](https://docs.vmware.com/en/VMware-HCX/4.1/hcx-user-guide/GUID-F45B1DB5-C640-4A75-AEC5-45C58B1C9D63.html).
+To learn more about policy routes, see [Mobility Optimized Networking Policy Routes](https://docs.vmware.com/en/VMware-HCX/4.1/hcx-user-guide/GUID-F45B1DB5-C640-4A75-AEC5-45C58B1C9D63.html).