Merge pull request #259441 from rcdun/make_easy_clarity_fixes

Make easy clarity fixes

Author: prmerger-automator[bot]

articles/communications-gateway/configure-test-customer-teams-direct-routing.md

@@ -23,13 +23,13 @@ Testing Microsoft Teams Direct Routing requires some test numbers in a Microsoft
 
 You must have a Microsoft 365 tenant that you can use as a test customer. You must have at least one number that you can allocate to this test customer.
 
-You must have completed the following procedures.
+You must complete the following procedures.
 
 - [Prepare to deploy Azure Communications Gateway](prepare-to-deploy.md)
 - [Deploy Azure Communications Gateway](deploy.md)
 - [Connect Azure Communications Gateway to Microsoft Teams Direct Routing](connect-teams-direct-routing.md)
 
-Your organization must have integrated with Azure Communications Gateway's Provisioning API. Someone in your organization must be able to make requests using the Provisioning API during this procedure.
+Your organization must [integrate with Azure Communications Gateway's Provisioning API](integrate-with-provisioning-api.md). Someone in your organization must be able to make requests using the Provisioning API during this procedure.
 
 You must be able to sign in to the Microsoft 365 admin center for your test customer tenant as a Global Administrator.
 

articles/communications-gateway/configure-test-numbers-teams-direct-routing.md

@@ -21,15 +21,14 @@ To test Microsoft Teams Direct Routing with Azure Communications Gateway, you ne
 
 You must have at least one number that you can allocate to your test tenant.
 
-You must have completed the following procedures.
+You must complete the following procedures.
 
 - [Prepare to deploy Azure Communications Gateway](prepare-to-deploy.md)
 - [Deploy Azure Communications Gateway](deploy.md)
 - [Connect Azure Communications Gateway to Microsoft Teams Direct Routing](connect-teams-direct-routing.md)
 - [Configure a test customer for Microsoft Teams Direct Routing](configure-test-customer-teams-direct-routing.md)
 
-Your organization must have integrated with Azure Communications Gateway's Provisioning API. Someone in your organization must be able to make requests using the Provisioning API during this procedure.
-
+Your organization must [integrate with Azure Communications Gateway's Provisioning API](integrate-with-provisioning-api.md). Someone in your organization must be able to make requests using the Provisioning API during this procedure.
 You must be able to sign in to the Microsoft 365 admin center for your test customer tenant as a Global Administrator.
 
 ## Configure the test numbers on Azure Communications Gateway with the Provisioning API

articles/communications-gateway/configure-test-numbers-zoom.md

@@ -20,13 +20,13 @@ You must have [chosen test numbers](deploy.md#prerequisites). You need two types
 - Integration testing by your staff.
 - Service verification (continuous call testing) by your chosen communication services.
 
-You must have completed the following procedures.
+You must complete the following procedures.
 
 - [Prepare to deploy Azure Communications Gateway](prepare-to-deploy.md)
 - [Deploy Azure Communications Gateway](deploy.md)
 - [Connect Azure Communications Gateway to Zoom Phone Cloud Peering](connect-zoom.md)
 
-Your organization must have integrated with Azure Communications Gateway's Provisioning API. Someone in your organization must be able to make requests using the Provisioning API during this procedure.
+Your organization must [integrate with Azure Communications Gateway's Provisioning API](integrate-with-provisioning-api.md). Someone in your organization must be able to make requests using the Provisioning API during this procedure.
 
 You must be an owner or admin of a Zoom account that you want to use for testing.
 
@@ -39,7 +39,7 @@ You must provision Azure Communications Gateway with the details of the test num
 > [!IMPORTANT]
 > Do not provision the service verification numbers for Zoom. Azure Communications Gateway routes calls involving those numbers automatically. Any provisioning you do for those numbers has no effect.
 
-This step requires Azure Communications Gateway's Provisioning API. The API allows you to indicate to Azure Communications Gateway which service(s) you are supporting for each number, using _account_ and _number_ resources.
+This step requires Azure Communications Gateway's Provisioning API. The API allows you to indicate to Azure Communications Gateway which service(s) you're supporting for each number, using _account_ and _number_ resources.
 - Account resources are descriptions of your customers (typically, an enterprise), and per-customer settings for service provisioning.
 - Number resources belong to an account. They describe numbers, the services (for example, Zoom) that the numbers make use of, and any extra per-number configuration.
 
@@ -50,9 +50,9 @@ Use the Provisioning API for Azure Communications Gateway to:
 
 ## Configure users in Zoom with the test numbers for integration testing
 
-Upload the numbers for integration testing to Zoom. When you do this, you can optionally configure Zoom to add a header with custom contents to SIP INVITEs. You can use this header to identify the Zoom account for the number or indicate that these are test numbers. For more information on this header, see Zoom's _Zoom Phone Provider Exchange Solution Reference Guide_.
+Upload the numbers for integration testing to Zoom. When you upload numbers, you can optionally configure Zoom to add a header containing custom contents to SIP INVITEs. You can use this header to identify the Zoom account for the number or indicate that these numbers are test numbers. For more information on this header, see Zoom's _Zoom Phone Provider Exchange Solution Reference Guide_.
 
-Use [https://support.zoom.us/hc/en-us/articles/360020808292-Managing-phone-numbers](https://support.zoom.us/hc/en-us/articles/360020808292-Managing-phone-numbers) to assign the numbers for integration testing to the user accounts that you will use for testing.
+Use [https://support.zoom.us/hc/en-us/articles/360020808292-Managing-phone-numbers](https://support.zoom.us/hc/en-us/articles/360020808292-Managing-phone-numbers) to assign the numbers for integration testing to the user accounts that you need to use for integration testing. Integration testing is part of preparing for live traffic.
 
 > [!IMPORTANT]
 > Do not assign the service verification numbers to Zoom user accounts. In the next step, you will ask your Zoom representative to configure the service verification numbers for you.

articles/communications-gateway/connect-operator-connect.md

@@ -214,7 +214,7 @@ To add the Application IDs:
 
 ## Register your deployment's domain name in Microsoft Entra
 
-Microsoft Teams only sends traffic to domains that you've confirmed that you own. Your Azure Communications Gateway deployment automatically receives an autogenerated fully qualified domain name (FQDN). You need to add this domain name to your Microsoft Entra tenant as a custom domain name, share the details with your onboarding team and then verify the domain name. This process confirms that you own the domain.
+Microsoft Teams only sends traffic to domains that you confirm that you own. Your Azure Communications Gateway deployment automatically receives an autogenerated fully qualified domain name (FQDN). You need to add this domain name to your Microsoft Entra tenant as a custom domain name, share the details with your onboarding team and then verify the domain name. This process confirms that you own the domain.
 
 1. Navigate to the **Overview** of your Azure Communications Gateway resource and select **Properties**. Find the field named **Domain**. This name is your deployment's domain name.
 1. Complete the following procedure: [Add your custom domain name to Microsoft Entra ID](../active-directory/fundamentals/add-custom-domain.md#add-your-custom-domain-name).

articles/communications-gateway/connect-teams-direct-routing.md

@@ -45,7 +45,7 @@ You must be able to sign in to the Microsoft 365 admin center for your tenant as
 
 Before starting this step, check that the **Provisioning Status** field for your resource is "Complete".
 
-Microsoft Teams only sends traffic to domains that you've confirmed that you own. Your Azure Communications Gateway deployment automatically receives an autogenerated fully qualified domain name (FQDN) and regional subdomains of this domain.
+Microsoft Teams only sends traffic to domains that you confirm that you own. Your Azure Communications Gateway deployment automatically receives an autogenerated fully qualified domain name (FQDN) and regional subdomains of this domain.
 
 1. Sign in to the [Azure portal](https://azure.microsoft.com/).
 1. In the search bar at the top of the page, search for your Communications Gateway resource.
@@ -72,7 +72,7 @@ If Microsoft 365 prompts you to verify the domain name:
 1. Select **Next**, and note the TXT value that Microsoft 365 provides.
 1. Provide the TXT value to your onboarding team as part of [Provide additional information to your onboarding team](#provide-additional-information-to-your-onboarding-team).
 
-Don't try to finish verifying the domain name until your onboarding team has confirmed that DNS records with the TXT value have been set up.
+Don't try to finish verifying the domain name until your onboarding team confirms that DNS records with the TXT value have been set up.
 
 ## Provide additional information to your onboarding team
 
@@ -88,7 +88,7 @@ If you don't already have an onboarding team, contact azcog-enablement@microsoft
 > [!NOTE]
 > If Microsoft 365 did not prompt you to verify the domain in [Register the base domain name for Azure Communications Gateway in your tenant](#register-the-base-domain-name-for-azure-communications-gateway-in-your-tenant), skip this step.
 
-After your onboarding team confirm the DNS records have been set up, finish verifying the base domain name in the Microsoft 365 admin center.
+After your onboarding team confirms that the DNS records have been set up, finish verifying the base domain name in the Microsoft 365 admin center.
 
 1. Sign into the Microsoft 365 admin center as a Global Administrator.
 1. Select **Settings** > **Domains**.

articles/communications-gateway/includes/communications-gateway-general-restrictions.md

@@ -10,4 +10,4 @@ The following restrictions apply to all Azure Communications Gateways:
 
 * All traffic must use IPv4.
 * All traffic must use TLS 1.2 or greater. Earlier versions aren't supported.
-* The number of active calls is limited to 15% of the number of Users assigned to the Azure Communications Gateway as defined in [Plan and manage costs for Azure Communications Gateway](/azure/communications-gateway/plan-and-manage-costs).
+* The number of active calls is limited to 15% of the number of users assigned to Azure Communications Gateway. For the definition of users, see [Plan and manage costs for Azure Communications Gateway](/azure/communications-gateway/plan-and-manage-costs).

articles/communications-gateway/includes/communications-gateway-sip-behavior-restrictions.md

@@ -6,7 +6,7 @@ ms.topic: include
 ms.date: 01/10/2022
 ---
 
-Some endpoints might add parameters in the following headers to an in-dialog message when those parameters weren't present in the dialog-creating message. In that case, Azure Communications Gateway will strip them, because this behavior isn't permitted by RFC 3261.
+Some endpoints might add parameters in the following headers to an in-dialog message when those parameters weren't present in the dialog-creating message. In that case, Azure Communications Gateway strips the parameters, because RFC 3261 doesn't permit this behavior.
 
 * Request URI
 * To header

articles/communications-gateway/index.yml

@@ -1,7 +1,7 @@
 ### YamlMime:Landing
 
 title: Azure Communications Gateway documentation
-summary: Learn about Azure Communications Gateway for telecommunications operators and service providers. Azure Communications Gateway allows you to provide your customers with Operator Connect, Teams Phone Mobile, Microsoft Teams Direct Routing and Zoom Phone Cloud Peering service. Launching Operator Connect, Teams Phone Mobile or Zoom Phone Cloud Peering requires additional agreements.
+summary: Learn about Azure Communications Gateway for telecommunications operators and service providers. Azure Communications Gateway allows you to provide your customers with Operator Connect, Teams Phone Mobile, Microsoft Teams Direct Routing and Zoom Phone Cloud Peering service. Using Azure Communications Gateway for Operator Connect, Teams Phone Mobile or Zoom Phone Cloud Peering requires separate acceptance into the relevant program.
 metadata:
   title: Azure Communications Gateway documentation
   description: Learn about Azure Communications Gateway. Azure Communications Gateway enables telecommunications operators to provide Operator Connect, Teams Phone Mobile, Microsoft Teams Direct Routing and Zoom Phone Cloud Peering services.

articles/communications-gateway/prepare-for-live-traffic-operator-connect.md

@@ -28,7 +28,7 @@ In this article, you learn about the steps that you and your onboarding team mus
 - You must [deploy Azure Communications Gateway](deploy.md) using the Microsoft Azure portal and [connect it to Operator Connect or Teams Phone Mobile](connect-operator-connect.md).
 - You must know the test numbers to use for integration testing and for service verification (continuous call testing). These numbers can't be the same. You chose them as part of [deploying Azure Communications Gateway](deploy.md#prerequisites) or [connecting it to Operator Connect or Teams Phone Mobile](connect-operator-connect.md#prerequisites).
     - Integration testing allows you to confirm that Azure Communications Gateway and Microsoft Phone System are interoperating correctly with your network.
-    - Service verification is set up by the Operator Connect and Teams Phone Mobile programs and ensures that your deployment is able to handle calls from Microsoft Phone System throughout the lifetime of your deployment.
+    - Service verification is set up by the Operator Connect and Teams Phone Mobile programs. It ensures that your deployment is able to handle calls from Microsoft Phone System throughout the lifetime of your deployment.
 - You must have a tenant you can use for integration testing (representing an enterprise customer), and some users in that tenant to whom you can assign the numbers for integration testing.
     - If you don't already have a suitable test tenant, you can use the [Microsoft 365 Developer Program](https://developer.microsoft.com/microsoft-365/dev-program), which provides E5 licenses.
     - The test users must be licensed for Teams Phone System and in Teams Only mode.
@@ -61,7 +61,7 @@ Integration testing requires setting up your test tenant for Operator Connect or
 > [!IMPORTANT]
 > Do not assign the service verification numbers to test users. Your onboarding team arranges configuration of your service verification numbers.
 
-1. Ask your onboarding team for the name of the Calling Profile that you must use for these test numbers. The name typically has the suffix `commsgw`. This Calling Profile has been created for you during the Azure Communications Gateway deployment process.
+1. Ask your onboarding team for the name of the Calling Profile that you must use for these test numbers. The name typically has the suffix `commsgw`. This Calling Profile was created for you during the Azure Communications Gateway deployment process.
 1. In your test tenant, request service from your company.
     1. Sign in to the [Teams Admin Center](https://admin.teams.microsoft.com/) for your test tenant.
     1. Select **Voice** > **Operators**.
@@ -111,7 +111,7 @@ Your network must route calls for service verification testing and for integrati
 
 Network integration includes identifying SIP interoperability requirements and configuring devices to meet these requirements. For example, this process often includes interworking header formats and/or the signaling & media flows used for call hold and session refresh.
 
-You must test typical call flows for your network. Your onboarding team will provide an example test plan that we recommend you follow. Your test plan should include call flow, failover, and connectivity testing.
+You must test typical call flows for your network. We recommend that you follow the example test plan from your onboarding team. Your test plan should include call flow, failover, and connectivity testing.
 
 - If you decide that you need changes to Azure Communications Gateway, ask your onboarding team. Microsoft will make the changes for you.
 - If you need changes to the configuration of devices in your core network, you must make those changes.
@@ -170,7 +170,7 @@ If you have the Number Management Portal, your onboarding team can obtain proof
 
 # [Without the Number Management Portal](#tab/no-number-management-portal)
 
-If you don't have the Number Management Portal, you must provide your onboarding team with proof that you have made successful API calls for:
+If you don't have the Number Management Portal, you must provide your onboarding team with proof of successful API calls for:
 
 - Partner consent
 - TN Upload to Account
@@ -187,7 +187,7 @@ After launch, synthetic traffic will be sent through your deployment using your
 
 ## Schedule launch
 
-Your launch date is the date that you'll appear to enterprises in the Teams Admin Center. Your onboarding team must arrange this date by making a request to Microsoft Teams.
+Your launch date is the date that you appear to enterprises in the Teams Admin Center. Your onboarding team must arrange this date by making a request to Microsoft Teams.
 
 Your service can be launched on specific dates each month. Your onboarding team must submit the request at least two weeks before your preferred launch date.