review comment

Author: gitName

articles/api-management/integrate-vnet-outbound.md

@@ -63,8 +63,6 @@ The subnet needs to be delegated to the **Microsoft.Web/serverFarms** service.
 
 For more information about configuring subnet delegation, see [Add or remove a subnet delegation](../virtual-network/manage-subnet-delegation.md).
 
-[!INCLUDE [api-management-virtual-network-address-prefix](../../includes/api-management-virtual-network-address-prefix.md)]
-
 ### Permissions
 
 You must have at least the following role-based access control permissions on the subnet or at a higher level to configure virtual network integration:

includes/api-management-virtual-network-address-prefix.md

@@ -8,13 +8,15 @@ ms.author: danlep
 
 ### addressPrefix property
 
-Networking in the Premium v2 tier requires that the `addressPrefix` subnet property is set to a valid CIDR block. 
+Virtual network injection in the Premium v2 tier requires that the `addressPrefix` subnet property is set to a valid CIDR block. 
 
 If you configure the subnet using the Azure portal, the subnet sets an `addressPrefixes` (plural) property consisting of a list of address prefixes. However, API Management requires a single CIDR block as the value of the `addressPrefix` property. 
 
 To create or update a subnet with `addressPrefix`, use a tool such as Azure PowerShell, an Azure Resource Manager template, or the [REST API](/rest/api/virtualnetwork/subnets/create-or-update). For example, update a subnet using the [Set-AzVirtualNetworkSubnetConfig](/powershell/module/az.network/set-azvirtualnetworksubnetconfig) Azure PowerShell cmdlet:
 
 ```powershell
+# Set values for the variables that are appropriate for your environment.
+
 $resourceGroupName = "MyResourceGroup"
 $virtualNetworkName = "MyVirtualNetwork"
 $subnetName = "ApimSubnet"