Merge pull request #268592 from rcdun/fixtypo

Fix typo, add more detail to DNS SRV lookups, and update style

Author: prmerger-automator[bot]

articles/communications-gateway/reliability-communications-gateway.md

@@ -1,6 +1,6 @@
 ---
 title: Reliability in Azure Communications Gateway
-description: Find out about reliability in Azure Communications Gateway
+description: Find out about reliability in Azure Communications Gateway.
 author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
@@ -61,7 +61,7 @@ Each site in your network must:
 > [!div class="checklist"]
 > - Send traffic to its local Azure Communications Gateway service region by default.
 > - Locate Azure Communications Gateway peers within a region using DNS SRV, as outlined in RFC 3263.
->     - Make a DNS SRV lookup on the domain name for the service region's connection to your network, for example `pstn-region1.<deployment-id>.commsgw.azure.com` (where `<deployment-id>` is autogenerated and unique to the deployment). You can find these domain names from the **Hostname** fields on the ***Overview** of your resource in the Azure portal.
+>     - Make a DNS SRV lookup on the domain name for the service region's connection to your network, using `_sip._tls.<regional-FQDN-from-portal>`. Replace `<regional-FQDN-from-portal>` with the per-region FQDNs from the **Hostname** fields on the **Overview** page for your resource in the Azure portal. For example, if your deployment uses `commsgw.azure.com` domain names, look up  `_sip._tls.pstn-region1.<deployment-id>.commsgw.azure.com` for the first region.
 >     - If the SRV lookup returns multiple targets, use the weight and priority of each target to select a single target.
 > - Send new calls to available Azure Communications Gateway peers.
 
@@ -82,7 +82,7 @@ The details of this routing behavior are specific to your network. You must agre
 
 ## Management regions
 
-Management regions contain the infrastructure used for the ordering, monitoring and billing of Azure Communications Gateway. All infrastructure within these regions is deployed in a zonally redundant manner, meaning that all data is automatically replicated across each Availability Zone within the region. All critical configuration data is also replicated to each of the Service Regions to ensure the proper functioning of the service during an Azure region failure.
+Management regions contain the infrastructure used for the ordering, monitoring, and billing of Azure Communications Gateway. All infrastructure within these regions is deployed in a zonally redundant manner, meaning that all data is automatically replicated across each Availability Zone within the region. All critical configuration data is also replicated to each of the Service Regions to ensure the proper functioning of the service during an Azure region failure.
 
 ## Availability zone support