updated with acrolinx suggestions

Author: ovishesh

articles/communication-services/concepts/call-automation/call-automation-teams-interop.md

@@ -11,23 +11,23 @@ ms.author: visho
 ms.custom: private_preview
 ---
 
-# Deliver expedient customer service by leveraging Microsoft Teams users in Call Automation workflows
+# Deliver expedient customer service by adding Microsoft Teams users in Call Automation workflows
 
 [!INCLUDE [Private Preview Notice](../../includes/private-preview-include.md)]
 
-Businesses are looking for innovative ways to increase the efficiency of their customer service operations. Azure Communication Services Call Automation provides developers the ability to build programmable customer interactions using real-time event triggers to perform actions based on custom business logic. For example, with supp\ort for interoperability with Microsoft Teams, developers can use Call Automation to add subject matter experts, who use Microsoft Teams, into existing customer service calls to provide their expertise to resolve a customer issue.
+Businesses are looking for innovative ways to increase the efficiency of their customer service operations. Azure Communication Services Call Automation provides developers the ability to build programmable customer interactions using real-time event triggers to perform actions based on custom business logic. For example, with support for interoperability with Microsoft Teams, developers can use Call Automation APIs to add subject matter experts (SMEs). These SMEs, who use Microsoft Teams, can be added to an existing customer service call to provide to resolve a customer issue.
 
-This interoperability with Microsoft Teams over VoIP makes it easy for developers to implement per-region multi-tenant trunks that maximize value and reduce telephony infrastructure overhead. Each new tenant will be able to leverage this setup in a few minutes after Microsoft Teams admin has granted necessary permissions to the Azure Communication Services resource.
+This interoperability with Microsoft Teams over VoIP makes it easy for developers to implement per-region multi-tenant trunks that maximize value and reduce telephony infrastructure overhead. Each new tenant will be able to use this setup in a few minutes after Microsoft Teams admin has granted necessary permissions to the Azure Communication Services resource.
 
 ## Use-cases
 
-1. Expert Consultation: Businesses can invite subject expert experts into their customer service workflows for expedient issue resolution, and to improve their first call resolution rate. 
-1. Extend customer service workforce with knowledge workers: Businesses can extend their customer service operation with additional capacity during peak influx of customer service calls.
+1. Expert Consultation: Businesses can invite subject matter experts into their customer service workflows for expedient issue resolution, and to improve their first call resolution rate. 
+1. Extend customer service workforce with knowledge workers: Businesses can extend their customer service operation with more capacity during peak influx of customer service calls.
 
 ## Scenario Showcase – Expert Consultation
 A customer service agent, who is using a Contact Center Agent experience, wants to now add a subject matter expert, who is knowledge worker (regular employee) at Contoso and uses Microsoft Teams, into a support call with a customer to provide some expert advice to a resolve a customer issue. 
 
-The dataflow diagram below depicts a canonical scenario where a Teams user is added to an ongoing ACS call for expert consultation.
+The dataflow diagram depicts a canonical scenario where a Teams user is added to an ongoing ACS call for expert consultation.
 
 ![Diagram of calling flow for a customer service with Microsoft Teams and Call Automation.](./media/call-automation-teams-interop.png)
 
@@ -66,17 +66,17 @@ The following list presents the set of features that are currently available in
 | Microsoft Teams Web | ❌ |
 | Microsoft Teams iOS | ❌ |
 | Microsoft Teams Android | ❌ |
-| Azure Communications Services signed in with with M365 Identity | ❌ |
+| Azure Communications Services signed in with Microsoft 365 Identity | ❌ |
 
 ## Roadmap
 
 1. Support for Microsoft Teams Web coming soon.
-1. Support for Azure Communications Services signed in with with M365 Identity coming soon.
+1. Support for Azure Communications Services signed in with Microsoft 365 Identity coming soon.
 
 ## Next steps
 
 > [!div class="nextstepaction"]
 > [Get started with Adding a Microsoft Teams user to an ongoing call using Call Automation](./../../quickstarts/call-automation/Callflows-for-customer-interactions.md)
 
 Here are some articles of interest to you: 
-- Understand how your resource will be [charged for various calling use cases](../pricing.md) with examples. 
+- Understand how your resource is [charged for various calling use cases](../pricing.md) with examples. 

articles/communication-services/quickstarts/call-automation/teams-interop-call-automation-quickstart.md

@@ -1,7 +1,7 @@
 ---
 title: Azure Communication Services Call Automation how-to for adding Microsoft Teams User into an existing call
 titleSuffix: An Azure Communication Services how-to document
-description: Provides a how-to for adding a Microsoft Teams user to a call with Call Automation.
+description: ProvIDes a how-to for adding a Microsoft Teams user to a call with Call Automation.
 author: visho
 
 ms.service: azure-communication-services
@@ -17,9 +17,9 @@ zone_pivot_groups: acs-csharp-java
 
 [!INCLUDE [Private Preview Notice](../../includes/private-preview-include.md)]
 
-In this quickstart, we’ll use the Azure Communication Services Call Automation APIs to add, remove and transfer to a Teams user.
+In this quickstart, we use the Azure Communication Services Call Automation APIs to add, remove and transfer to a Teams user.
 
-You will need to be part of Azure Communication Services TAP program. It is likely that you’re already part of this program, and if you are not, please sign-up using https://aka.ms/acs-tap-invite. To access to the specific Teams Interop functionality for Call Automation, please submit your Teams Tenant Ids and Azure Communication Services Resource Ids by filling this form – https://aka.ms/acs-ca-teams-tap. You will need to fill the form every time you need a new tenant Id and new resource Id allow-listed.
+You need to be part of the Azure Communication Services TAP program. It's likely that you’re already part of this program, and if you aren't, sign-up using https://aka.ms/acs-tap-invite. To access to the specific Teams Interop functionality for Call Automation, submit your Teams Tenant IDs and Azure Communication Services Resource IDs by filling this form – https://aka.ms/acs-ca-teams-tap. You need to fill the form every time you need a new tenant ID and new resource ID allow-listed.
 
 ## Prerequisites
 
@@ -33,16 +33,16 @@ You will need to be part of Azure Communication Services TAP program. It is like
 
 ## Step 1: Authorization for your Azure Communication Services Resource to enable calling to Microsoft Teams users
 
-To enable ad hoc calling through Call Automation APIs, a [Microsoft Teams Administrator](~/azure/active-directory/roles/permissions-reference#teams-administrator) or [Global Administrator](~/en-us/azure/active-directory/roles/permissions-reference#global-administrator) must explicitly enable the ACS resource(s) access to their tenant to allow ad hoc calling. They can further restrict ad hoc calling at the user level, so that only designated users in the tenant can communicate with ACS users.
+To enable calling through Call Automation APIs, a [Microsoft Teams Administrator](~/azure/active-directory/roles/permissions-reference#teams-administrator) or [Global Administrator](~/en-us/azure/active-directory/roles/permissions-reference#global-administrator) must explicitly enable the ACS resource(s) access to their tenant to allow calling.
 
 [Set-CsTeamsAcsFederationConfiguration (MicrosoftTeamsPowerShell)](~/powershell/module/teams/set-csteamsacsfederationconfiguration?view=teams-ps)
-This is the tenant level setting that enables/disables federation between their tenant and specific ACS resources.
+Tenant level setting that enables/disables federation between their tenant and specific ACS resources.
 
 [Set-CsExternalAccessPolicy (SkypeForBusiness)](~/powershell/module/skype/set-csexternalaccesspolicy?view=skype-ps)
-This is a user policy that allows the admin to further control which users in their organization can participate in federated communications with ACS users.
+User policy that allows the admin to further control which users in their organization can participate in federated communications with ACS users.
 
 ## Step 2: Use the Graph API to get AAD object ID for Teams users and optionally check their presence
-A Teams user’s AAD object ID (OID) is required to add them to or transfer to them from an ACS call. This can be retrieved through 1) Office portal, 2) Azure AD portal, 3) Azure AD Connect; or 4) Graph API. The example below uses Graph API.
+A Teams user’s Azure Active Directory (AAD) object ID (OID) is required to add them to or transfer to them from an ACS call. The OID can be retrieved through 1) Office portal, 2) Azure AD portal, 3) Azure AD Connect; or 4) Graph API. The example below uses Graph API.
 
 Consent must be granted by an AAD admin before Graph can be used to search for users, learn more by following on the [Microsoft Graph Security API overview](~/graph/security-concept-overview) document. The OID can be retrieved using the list users API to search for users. The following shows a search by display name, but other properties can be searched as well:
 
@@ -76,7 +76,7 @@ Response:
 ```
 
 ## Step 3: Add a Teams user to an existing ACS call controlled by Call Automation APIs
-You will need to complete the pre-requisite step and have a web service app to control an ACS call. Using the callConnection object, add a participant to the call.
+You need to complete the prerequisite step and have a web service app to control an ACS call. Using the callConnection object, add a participant to the call.
 
 ```csharp
 CallAutomationClient client = new CallAutomationClient('<Connection_String>');
@@ -96,11 +96,11 @@ await answer.Value.CallConnection.AddParticipantAsync(
 await answer.Value.CallConnection.RemoveParticipantAsync(new MicrosoftTeamsUserIdentifier('<Teams_User_Guid>'));
 ```
 
-### Additional optional feature: Transfer to a Teams user from an existing ACS call controlled by Call Automation APIs
+### Optional feature: Transfer to a Teams user from an existing ACS call controlled by Call Automation APIs
 ```csharp
 await answer.Value.CallConnection.TransferCallToParticipantAsync(new CallInvite(new MicrosoftTeamsUserIdentifier('<Teams_User_Guid>')));
 ```
-### How to tell if your Tenant is not enabled for this preview?
+### How to tell if your Tenant isn't enabled for this preview?
 ![You will receive this error during Step 1.](./media/teams-federation-error.png)
 
 ## Clean up resources