Merge pull request #264783 from rcdun/fix_connectivity_typos

Fix typos in Communications Gateway connectivity article

Author: prmerger-automator[bot]

articles/communications-gateway/connectivity.md

@@ -12,7 +12,7 @@ ms.date: 11/20/2023
 
 # Connectivity for Azure Communications Gateway
 
-Each Azure region in your deployment connects to your core network. You need to choose the type of connection (for example, MAPS Voice or Express Route) and route traffic between your network and Azure Communications Gateway with specific IP addresses and domain names.
+Each Azure region in your deployment connects to your core network. You must choose the type of connection (for example, Microsoft Azure Peering Service Voice). You must use specific IP addresses and domain names to route traffic between your network and Azure Communications Gateway.
 
 This article describes:
 
@@ -26,11 +26,11 @@ 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.
 
-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 services first).
+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).
 
 |Connection type  | Operator Connect / Teams Phone Mobile  | Microsoft Teams Direct Routing  | Zoom Phone Cloud Peering | Notes |
 |---------|---------|---------|---------|---------|
-| MAPS Voice |✅ |✅|✅|- Best media quality because of prioritization with Microsoft network<br>- No extra costs<br>- See [Azure Internet peering for Communications Services walkthrough](../internet-peering/walkthrough-communications-services-partner.md)|
+| MAPS Voice |✅ |✅|✅|- Best media quality because of prioritization with Microsoft network<br>- No extra costs<br>- See [Internet peering for Peering Service Voice walkthrough](../internet-peering/walkthrough-communications-services-partner.md)|
 |ExpressRoute Microsoft Peering |✅|✅|✅|- Easy to deploy<br>- Extra cost<br>- Consult with your onboarding team and ensure that it's available in your region<br>- See [Using ExpressRoute for Microsoft PSTN services](/azure/expressroute/using-expressroute-for-microsoft-pstn)|
 |Public internet |❌|✅|✅|- No extra setup<br>- Not recommended for production|
 
@@ -83,7 +83,7 @@ Azure Communications Gateway provides multiple FQDNs:
 
 You must decide whether you want these FQDNs to be `*.commsgw.azure.com` domain names or subdomains of a domain you already own, using [domain delegation with Azure DNS](../dns/dns-domain-delegation.md).
 
-Domain delegation provides topology hiding and might increase customer trust, but requires giving us full control over the subdomain that you delegate. For Microsoft Teams Direct Routing, choose domain delegation if you don't want customers to see an `*.commsgw.azure.com` in their Microsoft 365 admin centers.
+Domain delegation provides topology hiding and might increase customer trust, but requires giving us full control over the subdomain that you delegate. For Microsoft Teams Direct Routing, choose domain delegation if you don't want customers to see a `*.commsgw.azure.com` address in their Microsoft 365 admin centers.
 
 ## Related content
 

articles/communications-gateway/deploy.md

@@ -197,7 +197,7 @@ When your resource has been provisioned, you can connect Azure Communications Ga
             </ApplicationServer>
         </InitialFilterCriteria>
         ```
-1. Configure your routers and peering connection to ensure all traffic to Azure Communications Gateway is through Azure Internet Peering for Communications Services (also known as Microsoft Azure Peering Service for Voice and MAPS Voice) or ExpressRoute Microsoft Peering.
+1. Configure your routers and peering connection to ensure all traffic to Azure Communications Gateway is through Microsoft Azure Peering Service Voice (also known as MAPS Voice) or ExpressRoute Microsoft Peering.
 1. Enable Bidirectional Forwarding Detection (BFD) on your on-premises edge routers to speed up link failure detection.
     - The interval must be 150 ms (or 300 ms if you can't use 150 ms).
     - With MAPS Voice, BFD must bring up the BGP peer for each Private Network Interface (PNI).

articles/communications-gateway/get-started.md

@@ -19,7 +19,7 @@ This article summarizes the steps and documentation that you need.
 > [!IMPORTANT]
 > You must fully understand the onboarding process for your chosen communications service and any dependencies introduced by the onboarding process. For advice, ask your onboarding team.
 >
-> Some steps in the deployment and integration process can require days or weeks to complete. For example, you might need to arrange Microsoft Azure Peering Service for Voice (MAPS Voice) connectivity before you can deploy, wait for onboarding, or wait for a specific date to launch your service. We recommend that you read through any documentation from your onboarding team and the procedures in [Deploy Azure Communications Gateway](#deploy-azure-communications-gateway) and [Integrate with your chosen communications services](#integrate-with-your-chosen-communications-services) before you start deploying.
+> Some steps in the deployment and integration process can require days or weeks to complete. For example, you might need to arrange Microsoft Azure Peering Service Voice (MAPS Voice) connectivity before you can deploy, wait for onboarding, or wait for a specific date to launch your service. We recommend that you read through any documentation from your onboarding team and the procedures in [Deploy Azure Communications Gateway](#deploy-azure-communications-gateway) and [Integrate with your chosen communications services](#integrate-with-your-chosen-communications-services) before you start deploying.
 
 ## Learn about and plan for Azure Communications Gateway
 

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

@@ -46,7 +46,7 @@ Wait for confirmation that Azure Communications Gateway is enabled before moving
 
 Decide how Azure Communications Gateway should connect to your network. You must choose:
 
-- The type of connection you want to use (for example, MAPS Voice (recommended) or ExpressRoute).
+- The type of connection you want to use: for example, Microsoft Azure Peering Service Voice (recommended; sometimes called MAPS Voice).
 - The form of domain names Azure Communications Gateway uses towards your network: an autogenerated `*.commsgw.azure.com` domain name or a subdomain of a domain you already own (using [domain delegation with Azure DNS](../dns/dns-domain-delegation.md)).
 
 For more information about your options, see [Connectivity for Azure Communications Gateway](connectivity.md).
@@ -65,11 +65,11 @@ If you plan to route emergency calls through Azure Communications Gateway, read
 - [Operator Connect and Teams Phone Mobile](emergency-calls-operator-connect.md)
 - [Zoom Phone Cloud Peering](emergency-calls-zoom.md)
 
-## Configure MAPS Voice or ExpressRoute
+## Configure Microsoft Azure Peering Service Voice or ExpressRoute
 
 Connect your network to Azure:
 
-- To configure MAPS Voice, follow the instructions in [Azure Internet peering for Communications Services walkthrough](../internet-peering/walkthrough-communications-services-partner.md).
+- To configure Microsoft Azure Peering Service Voice (sometimes called MAPS Voice), follow the instructions in [Internet peering for Peering Service Voice walkthrough](../internet-peering/walkthrough-communications-services-partner.md).
 - To configure ExpressRoute Microsoft Peering, follow the instructions in [Tutorial: Configure peering for ExpressRoute circuit](../../articles/expressroute/expressroute-howto-routing-portal-resource-manager.md).
 
 ## Next step