minor updates

Author: Michael Bender

articles/virtual-network-manager/concept-user-defined-route.md

@@ -107,17 +107,18 @@ Here are the common routing scenarios that you can simplify and automate by usin
 
 When you add other virtual networks to a network group, the routing configuration is automatically applied to the new virtual network. Your network manager automatically detects the new virtual network and applies the routing configuration to it. When you remove a virtual network from the network group, the applied routing configuration is automatically removed as well.
 
-Newly created or deleted subnets have their route table updated with eventual consistency. The processing time may vary based on the volume of subnet creation and deletion.
+Newly created or deleted subnets have their route table updated with eventual consistency. The processing time can vary based on the volume of subnet creation and deletion.
 
-> [!NOTE]
-> The following are behaviors of UDR management with Azure Virtual Network Manager:r:
+## Behaviors of UDR management
 
-> - When conflicting routing rules exist (rules with same destination but different next hops), they aren't supported within or across rule collections that target the same virtual network or subnet.
-> - When you create a route rule with the same destination as an existing route in the route table, the routing rule is ignored.
-> - When a virtual network manager-created UDR is manually modified in the route table, the route isn't up when an empty commit is performed. Also, any update to the rule isn't reflected in the route with the same destination.
-> - Existing Azure services in the Hub virtual network maintain their existing limitations with respect to Route Table and UDRs.
-> - Azure Virtual Network Manager requires a managed resource group to store the route table. If you need to delete the resource group, deletion must happen before any new deployments are attempted for resources in the same subscription.
-> - UDR Management supports creating 1000 UDRs within a route table. This means that you can create a routing configuration with a maximum of 1,000 routing rules.
+The following are behaviors of UDR management with Azure Virtual Network Manager:
+
+- When conflicting routing rules exist (rules with same destination but different next hops), they aren't supported within or across rule collections that target the same virtual network or subnet.
+- When you create a route rule with the same destination as an existing route in the route table, the routing rule is ignored.
+- When a virtual network manager-created UDR is manually modified in the route table, the route isn't up when an empty commit is performed. Also, any update to the rule isn't reflected in the route with the same destination.
+- Existing Azure services in the Hub virtual network maintain their existing limitations with respect to Route Table and UDRs.
+- Azure Virtual Network Manager requires a managed resource group to store the route table. If you need to delete the resource group, deletion must happen before any new deployments are attempted for resources in the same subscription.
+- UDR Management supports creating 1000 UDRs within a route table. This means that you can create a routing configuration with a maximum of 1,000 routing rules.
 
 ## Next step
 

articles/virtual-network-manager/how-to-create-user-defined-route.md

@@ -221,7 +221,7 @@ In this step, you deploy the routing configuration to create the UDRs for the ne
 1. Select **Next** and then **Deploy** to deploy the routing configuration.
 
 > [!NOTE]
-> When you create and deploy a routing configuration, you need to be aware of the impact of existing routing rules. For more information, see [limitations for UDR management](./concept-user-defined-route.md#limitations-of-udr-management).
+> When you create and deploy a routing configuration, you need to be aware of the impact of existing routing rules. For more information, see [Behaviors for UDR management](./concept-user-defined-route.md#behaviors-of-udr-management).
 
 ## Next steps