Apply suggestions from code review

Co-authored-by: Rachel Dunstan <[email protected]>

Author: nslack

articles/communications-gateway/connectivity.md

@@ -99,11 +99,11 @@ Azure Communications Gateway uses the following local port ranges which must be
 | 5060 | SIP | UDP/TCP |
 | 5061 | SIP over TLS | TCP |
 
-All Azure Communications Gateway IP addresses can be used for both signaling (SIP) and media (RTP/RTCP). When connecting to multiple networks, additional SIP local ports are used, please refer to your Azure Communications Gateway resource in the Azure portal for details.
+All Azure Communications Gateway IP addresses can be used for both signaling (SIP) and media (RTP/RTCP). When connecting to multiple networks, additional SIP local ports are used. For details, see your Azure Communications Gateway resource in the Azure portal.
 
 ## VNet injection for Azure Communications Gateway (preview)
 
-VNet injection for Azure Communications Gateway (preview) allows the network interfaces on your Azure Communications Gateway which connect to your network to be deployed into virtual networks in your subscription. This allows you to control the traffic flowing between your network and your Azure Communications Gateway instance using private subnets, and lets you use private connectivity to your premises such as ExpressRoute Private Peering and Virtual Private Networks.
+VNet injection for Azure Communications Gateway (preview) allows the network interfaces on your Azure Communications Gateway that connect to your network to be deployed into virtual networks in your subscription. This allows you to control the traffic flowing between your network and your Azure Communications Gateway instance using private subnets, and lets you use private connectivity to your premises such as ExpressRoute Private Peering and Virtual Private Networks.
 
 If you use VNet injection (preview) with Operator Connect or Teams Phone Mobile, your network must still meet the redundancy and resiliency requirements described in the _Network Connectivity Specification_ provided to you by your onboarding team. This mandates that your network is connected to Azure by at least 2 ExpressRoute circuits, each deployed with local redundancy and configured so that each region can use both circuits in the case of failure as described in the diagram below:
 

articles/communications-gateway/prepare-for-vnet-injection.md

@@ -18,15 +18,15 @@ The following diagram shows an overview of Azure Communications Gateway deployed
 
 ## Prerequisites
 - Your Azure subscription is [enabled for Azure Communications Gateway](prepare-to-deploy.md#get-access-to-azure-communications-gateway-for-your-azure-subscription).
-- Your onboarding team are aware that you intend to use your own virtual network.
-- An Azure virtual network and subnet in each of the Azure regions to be used as the Azure Communications Gateway [service regions](reliability-communications-gateway.md#service-regions). Learn how to create a [virtual network](/azure/virtual-network/manage-virtual-network) and [subnet](/azure/virtual-network/virtual-network-manage-subnet).
+- Your onboarding team is aware that you intend to use your own virtual network.
+- You  have an Azure virtual network and subnet in each of the Azure regions to be used as the Azure Communications Gateway [service regions](reliability-communications-gateway.md#service-regions). Learn how to create a [virtual network](/azure/virtual-network/manage-virtual-network) and [subnet](/azure/virtual-network/virtual-network-manage-subnet).
 - Each subnet has at least 16 free IP addresses which can be used by Azure Communications Gateway. 
 - Your chosen connectivity solution (for example ExpressRoute) is deployed into your Azure subscription and ready to use.
 
 > [!TIP]
 > Lab deployments only have one service region, so you only need to set up a single region during this procedure.
 
-## 1. Provide permissions to the Azure Communications Gateway Service Principal
+## Provide permissions to the Azure Communications Gateway Service Principal
 
 To give Azure Communications Gateway permission to deploy network interfaces into your subnets:
 
@@ -38,7 +38,7 @@ To give Azure Communications Gateway permission to deploy network interfaces int
 1. Assign the **Network Contributor** role.
 1. Repeat these steps for the virtual network to use in the other service region.
 
-## 2. Delegate the virtual network subnets
+## Delegate the virtual network subnets
 
 To use your virtual network with Azure Communications Gateway, you need to [delegate the subnets](/azure/virtual-network/subnet-delegation-overview) to Azure Communications Gateway. Subnet delegation gives explicit permissions to Azure Communications Gateway to create service-specific resources, such as network interfaces (NICs), in the subnets.
 
@@ -56,7 +56,7 @@ Follow these steps to delegate your subnets for use with your Azure Communicatio
 1. Verify that *Microsoft.AzureCommunicationsGateway/networkSettings* appears in the **Delegated to** column for your subnet.
 1. Repeat the above steps for the virtual network and subnet in the other Azure Communications Gateway service region.
 
-## 3. Configure network security groups.
+## Configure network security groups
 
 When you connect your Azure Communications Gateway to virtual networks, you need to configure a network security group (NSG) to allow traffic from your network to reach the Azure Communications Gateway. An NSG contains access control rules that allow or deny traffic based on traffic direction, protocol, source address and port, and destination address and port.
 
@@ -80,15 +80,14 @@ Your network security group configuration should allow traffic to the necessary
 
 ### Associate the subnet with the network security group
 
-Go to your network security group, and select **Subnets**.
-
+1. Go to your network security group, and select **Subnets**.
 1. Select **+ Associate** from the top menu bar.
 1. For **Virtual network**, select your virtual network.
 1. For **Subnet**, select your virtual network subnet.
 1. Select **OK** to associate the virtual network subnet with the network security group.
 1. Repeat these steps for the other service region.
 
-## Next Steps
+## Next step
 
 > [!div class="nextstepaction"]
 > [Prepare to deploy Azure Communications Gateway](prepare-to-deploy.md)

articles/communications-gateway/prepare-to-deploy.md

@@ -50,7 +50,7 @@ Access to Azure Communications Gateway is restricted. When you've completed the
 
 ## Create a network design
 
-Decide how Azure Communications Gateway should connect to your network. We recommend Microsoft Azure Peering Service Voice (sometimes called MAPS Voice). For more information about your options, see [Connectivity for Azure Communications Gateway](connectivity.md). If you are planning to use Azure Communications Gateway with VNet injection (preview), complete the [prerequisites for deploying Azure Communications Gateway with VNet injection](prepare-for-vnet-injection.md).
+Decide how Azure Communications Gateway should connect to your network. We recommend Microsoft Azure Peering Service Voice (sometimes called MAPS Voice). For more information about your options, see [Connectivity for Azure Communications Gateway](connectivity.md). If you're planning to use Azure Communications Gateway with VNet injection (preview), complete the [prerequisites for deploying Azure Communications Gateway with VNet injection](prepare-for-vnet-injection.md).
 
 For Teams Phone Mobile and Azure Operator Call Protection Preview, you must decide how your network should determine whether a call involves a relevant subscriber and therefore route the call correctly. You can: