acrolinx

Author: greg-lindsay

articles/traffic-manager/traffic-manager-subnet-override-cli.md

@@ -1,6 +1,6 @@
 ---
 title: Azure Traffic Manager subnet override using Azure CLI
-description: This article will help you understand how Traffic Manager subnet override can be used to override the routing method of a Traffic Manager profile to direct traffic to an endpoint based upon the end-user IP address via predefined IP range to endpoint mappings.
+description: This article helps you understand Traffic Manager subnet override. This feature can be used to override the routing method of a Traffic Manager profile to direct traffic to an endpoint based upon the end-user IP address via predefined IP range to endpoint mappings.
 services: traffic-manager
 author: greg-lindsay
 ms.topic: how-to
@@ -12,18 +12,18 @@ ms.custom: template-how-to, devx-track-azurecli
 
 # Traffic Manager subnet override using Azure CLI
 
-Traffic Manager subnet override allows you to alter the routing method of a profile.  The addition of an override will direct traffic based upon the end user's IP address with a predefined IP range to endpoint mapping. 
+Traffic Manager subnet override allows you to alter the routing method of a profile.  The addition of an override directs traffic based upon the end user's IP address with a predefined IP range to endpoint mapping. 
 
 ## How subnet override works
 
-When subnet overrides are added to a traffic manager profile, Traffic Manager will first check if there's a subnet override for the end user’s IP address. If one is found, the user’s DNS query will be directed to the corresponding endpoint.  If a mapping is not found, Traffic Manager will fall back to the profile’s original routing method. 
+When subnet overrides are added to a traffic manager profile, Traffic Manager first checks if there's a subnet override for the end user’s IP address. If one is found, the user’s DNS query ix directed to the corresponding endpoint.  If a mapping is not found, Traffic Manager falls back to the profile’s original routing method. 
 
-The IP address ranges can be specified as either CIDR ranges (for example, 1.2.3.0/24) or as address ranges (for example, 1.2.3.4-5.6.7.8). The IP ranges associated with each endpoint must be unique to that endpoint. Any overlap of IP ranges among different endpoints will cause the profile to be rejected by Traffic Manager.
+The IP address ranges can be specified as either CIDR ranges (for example, 1.2.3.0/24) or as address ranges (for example, 1.2.3.4-5.6.7.8). The IP ranges associated with each endpoint must be unique to that endpoint. Any overlap of IP ranges among different endpoints cause the profile to be rejected by Traffic Manager.
 
 There are two types of routing profiles that support subnet overrides:
 
-* **Geographic** - If Traffic Manager finds a subnet override for the DNS query's IP address, it will route the query to the endpoint whatever the health of the endpoint is.
-* **Performance** - If Traffic Manager finds a subnet override for the DNS query's IP address, it will only route the traffic to the endpoint if it's healthy.  Traffic Manager will fall back to the performance routing heuristic if the subnet override endpoint isn't healthy.
+* **Geographic** - If Traffic Manager finds a subnet override for the DNS query's IP address, it routes the query to the endpoint whatever the health of the endpoint is.
+* **Performance** - If Traffic Manager finds a subnet override for the DNS query's IP address, it only routes the traffic to the endpoint if it's healthy.  Traffic Manager falls back to the performance routing heuristic if the subnet override endpoint isn't healthy.
 
 > [!NOTE]
 > Azure Traffic Manager supports IPv6 addresses in subnet overrides for subnet profiles. This capability enables more granular control over traffic routing based on the source IP address of DNS queries, including both IPv4 and IPv6 addresses. 

articles/traffic-manager/traffic-manager-subnet-override-powershell.md

@@ -1,6 +1,6 @@
 ---
 title: Azure Traffic Manager subnet override using Azure PowerShell
-description: This article will help you understand how Traffic Manager subnet override is used to override the routing method of a Traffic Manager profile to direct traffic to an endpoint based upon the end-user IP address via predefined IP range to endpoint mappings using Azure PowerShell.
+description: This article helps you understand the Traffic Manager subnet override feature. This feature is used to override the routing method of a Traffic Manager profile to direct traffic to an endpoint based upon the end-user IP address via predefined IP range to endpoint mappings using Azure PowerShell.
 services: traffic-manager
 author: greg-lindsay
 ms.topic: how-to
@@ -12,26 +12,26 @@ ms.custom: template-how-to, devx-track-azurepowershell
 
 # Traffic Manager subnet override using Azure PowerShell
 
-Traffic Manager subnet override allows you to alter the routing method of a profile.  The addition of an override will direct traffic based upon the end user's IP address with a predefined IP range to endpoint mapping. 
+Traffic Manager subnet override allows you to alter the routing method of a profile.  The addition of an override directs traffic based upon the end user's IP address with a predefined IP range to endpoint mapping. 
 
 ## How subnet override works
 
-When subnet overrides are added to a traffic manager profile, Traffic Manager will first check if there's a subnet override for the end user’s IP address. If one is found, the user’s DNS query will be directed to the corresponding endpoint.  If a mapping isn't found, Traffic Manager will fall back to the profile’s original routing method. 
+When subnet overrides are added to a traffic manager profile, Traffic Manager first checks if there's a subnet override for the end user’s IP address. If one is found, the user’s DNS query is directed to the corresponding endpoint.  If a mapping isn't found, Traffic Manager falls back to the profile’s original routing method. 
 
-The IP address ranges can be specified as either CIDR ranges (for example, 1.2.3.0/24) or as address ranges (for example, 1.2.3.4-5.6.7.8). The IP ranges associated with each endpoint must be unique to that endpoint. Any overlap of IP ranges among different endpoints will cause the profile to be rejected by Traffic Manager.
+The IP address ranges can be specified as either CIDR ranges (for example, 1.2.3.0/24) or as address ranges (for example, 1.2.3.4-5.6.7.8). The IP ranges associated with each endpoint must be unique to that endpoint. Any overlap of IP ranges among different endpoints causes the profile to be rejected by Traffic Manager.
 
 There are two types of routing profiles that support subnet overrides:
 
-* **Geographic** - If Traffic Manager finds a subnet override for the DNS query's IP address, it will route the query to the endpoint whatever the health of the endpoint is.
-* **Performance** - If Traffic Manager finds a subnet override for the DNS query's IP address, it will only route the traffic to the endpoint if it's healthy.  Traffic Manager will fall back to the performance routing heuristic if the subnet override endpoint isn't healthy.
+* **Geographic** - If Traffic Manager finds a subnet override for the DNS query's IP address, it routes the query to the endpoint whatever the health of the endpoint is.
+* **Performance** - If Traffic Manager finds a subnet override for the DNS query's IP address, it only routes the traffic to the endpoint if it's healthy.  Traffic Manager falls back to the performance routing heuristic if the subnet override endpoint isn't healthy.
 
 > [!NOTE]
 > Azure Traffic Manager supports IPv6 addresses in subnet overrides for subnet profiles. This capability enables more granular control over traffic routing based on the source IP address of DNS queries, including both IPv4 and IPv6 addresses. 
 
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
-- For this guide you will need an App Service and a Traffic Manager profile. To learn more, see [Create a Traffic Manager profile](./quickstart-create-traffic-manager-profile.md).
+- For this guide you need an App Service and a Traffic Manager profile. To learn more, see [Create a Traffic Manager profile](./quickstart-create-traffic-manager-profile.md).
 
 [!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
 
@@ -47,7 +47,7 @@ To create a Traffic Manager subnet override, you can use Azure PowerShell to add
 
     To enable the subnet override, retrieve the endpoint you wish to add the override to and store it in a variable using [Get-AzTrafficManagerEndpoint](/powershell/module/az.trafficmanager/get-aztrafficmanagerendpoint).
 
-    Replace the Name, ProfileName, and ResourceGroupName with the values of the endpoint that you're changing. In this example we will use the endpoint name *myAppServicePlan* and the profile name *myTrafficManagerProfile*. 
+    Replace the Name, ProfileName, and ResourceGroupName with the values of the endpoint that you're changing. In this example we use the endpoint name *myAppServicePlan* and the profile name *myTrafficManagerProfile*. 
 
     ```powershell