more self markup

nslack · nslack · commit 6b4835efd05c · 2024-04-26T17:05:05.000+01:00
diff --git a/articles/communications-gateway/connectivity.md b/articles/communications-gateway/connectivity.md
@@ -26,7 +26,7 @@ Azure Communications Gateway supports multiple types of connection to your netwo
 - We strongly recommend using Microsoft Azure Peering Service Voice (also called MAPS Voice or MAPSV).
 - If you can't use MAPS Voice, we recommend ExpressRoute Microsoft Peering.
 
-Azure Communications Gateway is normally deployed with public IP addresses on all interfaces. This means that you can use connectivity methods supporting public IP addresses to connect your network to Azure Communications Gateway such as MAPS Voice, ExpressRoute Microsoft Peering and the public internet. If you want to control and manage the traffic between your network and Azure Communications Gateway you can use VNet injection (preview) to deploy Azure Communications Gateway into your own subnet.
+Azure Communications Gateway is normally deployed with public IP addresses on all interfaces. This means that you can use connectivity methods supporting public IP addresses to connect your network to Azure Communications Gateway such as MAPS Voice, ExpressRoute Microsoft Peering and the public internet. If you want to control and manage the traffic between your network and Azure Communications Gateway you can use VNet injection for Azure Communications Gateway (preview) to deploy the interfaces which connect to your network into your own subnet.
 
 The following table lists all the available connection types and whether they're supported for each communications service. The connection types are in the order that we recommend (with recommended types first).
 
@@ -94,6 +94,7 @@ Azure Communications Gateway provides multiple FQDNs:
 Azure Communications Gateway uses the following local port ranges which must be accessible from your network, depending on the connectivity type chosen: 
 
 | Port Range | Protocol | Transport |
+|---------|---------|---------|
 | 16384-23983| RTP/RTCP <br> SRTP/SRTCP | UDP |
 | 5060 | SIP | UDP/TCP |
 | 5061 | SIP over TLS | TCP |
diff --git a/articles/communications-gateway/plan-and-manage-costs.md b/articles/communications-gateway/plan-and-manage-costs.md
@@ -69,8 +69,8 @@ If your Azure subscription has a spending limit, Azure prevents you from spendin
 
 You must pay for Azure networking costs, because these costs aren't included in the Azure Communications Gateway meters.
 
-- If you're connecting to the public internet with Microsoft Azure Peering Service for Voice (MAPS Voice), you might need to pay a third party for the cross-connect at the exchange location.
-- If you're connecting to Azure with ExpressRoute or Virtual Private Networks, you must purchase ExpressRoute circuits with a specified bandwidth and data billing model.
+- If you're connecting to the public internet with Microsoft Azure Peering Service for Voice (MAPS Voice), bandwidth costs are included in Azure Communications Gateway but you might need to pay a third party for the cross-connect at the exchange location.
+- If you're connecting to Azure with ExpressRoute, you must purchase ExpressRoute circuits with a specified bandwidth and data billing model.
 - If you're connecting into Azure as a next hop, you might need to pay virtual network peering costs.
 
 You must also pay for any costs charged by the communications services to which you're connecting. These costs don't appear on your Azure bill, and you need to pay them to the communications service yourself.
diff --git a/articles/communications-gateway/prepare-for-vnet-injection.md b/articles/communications-gateway/prepare-for-vnet-injection.md
@@ -26,15 +26,15 @@ The following diagram shows an overview of Azure Communications Gateway deployed
 > [!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
+## 1. Provide permissions to the Azure Communications Gateway Service Principal
 
 To give Azure Communications Gateway permission to deploy network interfaces into your subnets:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. Go to your [virtual networks](https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.Network%2FvirtualNetworks) and select the virtual network to use in the first service region for Azure Communications Gateway. 
 1. Select **Access control (IAM)**.
 1. Select **Add role assignment**.
-1. Search for and select **AzureCommunicationsGateway** in the search bar.
+1. Search for and select the **AzureCommunicationsGateway** Service Principal in the search bar.
 1. Assign the **Network Contributor** role.
 1. Repeat these steps for the virtual network to use in the other service region.
 
diff --git a/articles/communications-gateway/whats-new.md b/articles/communications-gateway/whats-new.md
@@ -16,7 +16,7 @@ This article covers new features and improvements for Azure Communications Gatew
 
 ### VNet injection for Azure Communications Gateway (preview)
 
-From April 2024, you can set up private networking between your on-premises environment and Azure Communications Gateway. 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.
+From April 2024, you can set up private networking between your on-premises environment and Azure Communications Gateway. 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.
 
 For more information about private networking, see [Connecting to Azure Communications Gateway](./connectivity.md). For deployment instructions, see [Prepare to connect Azure Communications Gateway to your own virtual network](./prepare-for-vnet-injection.md).
 
