edits to langauge and factoring feedback from acrolinx

Author: ovishesh

articles/communication-services/concepts/voice-video-calling/call-automation.md

@@ -79,11 +79,11 @@ Web hooks – Calling Automation SDKs use standard web hook HTTP/S callbacks for
 
 These actions are performed before the destination endpoint listed in the IncomingCall event notification is connected. Web hook callback events only communicate the “answer” pre-call action, not for reject or redirect actions.  
 
-**Answer** – Using the IncomingCall event from Event Grid and Call Automation SDK, a call can be answered by your application. This action allows for IVR scenarios where an inbound PSTN call can be answered programmatically by your application. Other scenarios include answering a call on behalf of a user, or answering an outbound call to a phone number in the same Azure Communication Services resource.
+**Answer** – Using the IncomingCall event from Event Grid and Call Automation SDK, a call can be answered by your application. This action allows for IVR scenarios where an inbound PSTN call can be answered programmatically by your application. Other scenarios include answering a call on behalf of a user.
 
 **Reject** – To reject a call means your application can receive the IncomingCall event and prevent the call from being connected to the destination endpoint.
 
-**Redirect** – Using the IncomingCall event from Event Grid, a call can be redirected to one or more endpoints creating a single or simultaneous ringing (sim-ring) scenario. Redirect means it isn't answered by your application, it's simply ‘redirected’ to another destination endpoint to be answered.
+**Redirect** – Using the IncomingCall event from Event Grid, a call can be redirected to one or more endpoints creating a single or simultaneous ringing (sim-ring) scenario. This means the call isn't answered by your application, it's simply ‘redirected’ to another destination endpoint to be answered.
 
 **Make Call** - Make Call action can be used to place outbound calls to phone numbers and to other communication users. Use cases include your application placing outbound calls to proactively inform users about an outage or notify about an order update.
 
@@ -93,7 +93,7 @@ These actions can be performed on the calls that are answered or placed using Ca
 
 **Add/Remove participant(s)** – One or more participants can be added in a single request with each participant being a variation of supported destination endpoints. A web hook callback is sent for every participant successfully added to the call.
 
-**Play** - When your application answers a call or places an outbound call, you can play an audio prompt for the caller. The audio prompt can be looped for scenarios like playing hold music. To learn more, view our [quickstart](../../quickstarts/voice-video-calling/Play-Action.md).
+**Play** - When your application answers a call or places an outbound call, you can play an audio prompt for the caller. This audio can be looped if needed in scenarios like playing hold music. To learn more, view our [quickstart](../../quickstarts/voice-video-calling/play-action.md)
 
 **Transfer** – When your application answers a call or places an outbound call to an endpoint, that endpoint can be transferred to another destination endpoint. Transferring a 1:1 call will remove your application's ability to control the call using the Call Automation SDKs.
 

articles/communication-services/concepts/voice-video-calling/play-action.md

@@ -25,33 +25,28 @@ The Play action allows you to provide access to a pre-recorded audio file of WAV
 The play action can be used in many ways, below are some examples of how developers may wish to use the play action in their applications. 
 
 ### Announcements
-Your application might want to play some sort of announcement when a participant joins or leaves the call, to notify other users:
-- Someone has entered the meeting, so they're aware of a new participant.
-- Someone has left the meeting, so they're aware that a participant may have disconnected. 
+Your application might want to play some sort of announcement when a participant joins or leaves the call, to notify other users.
 
 ### Self-serve customers
 
-In scenarios with IVRs and virtual assistants, you can use your application or bots to play audio prompts to callers, this prompt can be in the form of a menu to guide the caller through their interaction. 
+In scenarios with IVRs and virtual assistants, you can use your application or bots to play audio prompts to callers, this prompt can be in the form of a menu to guide the caller through their interaction.
 
 ### Hold music
-
-The play action can also be used to play hold music for callers. You can configure the audio to be played in a loop so that the music keeps playing until an agent is available to assist the caller. 
+The play action can also be used to play hold music for callers. This action can be set up in a loop so that the music keeps playing untill an agent is available to assist the caller.
 
 ### Playing compliance messages
-
-As part of compliance requirements in various industries, vendors are expected to play legal or compliance messages to callers, for example “This call will be recorded for quality purposes”. 
+As part of compliance requirements in various industries, vendors are expected to play legal or compliance messages to callers, for example, “This call will be recorded for quality purposes”.
 
 ## How the play action workflow looks
 
 ![Screenshot of flow for play action.](./play-action-flow.png)
 
 ## Known Issues/Limitations
 - Play action isn't enabled to work with Teams Interoperability.
-- Play doesn't support loop for targeted playing. 
+- Play won't support loop for targeted playing.
 
 ## What's coming up next for Play action
-
-As we invest more into this functionality, we recommend developers sign up to our TAP program that allows you to get early access to the newest feature releases. Over the coming months the play action will add in new capabilities that use our integration with Azure Cognitive Services to provide AI capabilities such as Text-to-Speech and fine tuning Text-to-Speech with SSML. With these, you can improve customer interactions and create more personalized messages. 
+As we invest more into this functionality, we recommend developers sign up to our TAP program that allows you to get early access to the newest feature releases. Over the coming months the play action will add new capabilities that use our integration with Azure Cognitive Services to provide AI capabilities such as Text-to-Speech and fine tuning Text-to-Speech with SSML. With these capabilities you can improve customer interactions to create more personalized messages.
 
 ## Next Steps
 Check out the [Play action quickstart](../../quickstarts/voice-video-calling/Play-Action.md) to learn more.

articles/communication-services/quickstarts/telephony/includes/call-automation/redirect-pstn-call-csharp.md

@@ -42,7 +42,8 @@ Call Automation uses Event Grid to deliver the `IncomingCall` event to a subscri
     ngrok http https://localhost:<your_web_service_port>
     ```
     This command will produce a public URI you can use to receive the events from the Event Grid subscription.
-5. Optional: Determine an API route path for the incoming call event together with your NGROK URI, which will be used in the armclient command-line statement below, for example: `https://ff2f-75-155-253-232.ngrok.io/api/incomingcall`.
+5. Optional: Determine an API route path for the incoming call event together with your NGROK URI that will be used in the armclient command-line statement below, for example: `https://ff2f-75-155-253-232.ngrok.io/api/incomingcall`.
+
 6. Event Grid web hooks require a valid reachable endpoint before they can be created. As such, start your web service application and run the commands below.
 7. Since the `IncomingCall` event isn't yet published in the portal, you must run the following command-line statements to configure your subscription:
 

articles/communication-services/quickstarts/telephony/includes/call-automation/redirect-pstn-call-java.md

@@ -73,7 +73,7 @@ Azure Event Grid SDK package: [com.azure : azure-messaging-eventgrid](https://se
 
 **spark-core**
 
-Spark framework: com.sparkjava : spark-core. We’ll use this micro-framework to create a webhook (web api endpoint) to handle Event Grid events. Note that you can use any framework to create a web api.
+Spark framework: com.sparkjava : spark-core. We’ll use this micro-framework to create a webhook (web api endpoint) to handle Event Grid events. You can use any framework to create a web api.
 ```xml
 <dependency>
   <groupId>com.sparkjava</groupId>
@@ -152,7 +152,7 @@ Azure Communication Services use Event Grid to deliver the `IncomingCall` event.
     ```
 
     This command will create a public URI like `https://ff2f-75-155-253-232.ngrok.io/`.
-4. Since the IncomingCall event isn't yet published in the Azure portal, you need run the following Azure CLI command to configure an event subscription (please replace with your identifiers and ngrok URI).
+4. Since the IncomingCall event isn't yet published in the Azure portal, you need run the following Azure CLI command to configure an event subscription (replace with your identifiers and ngrok URI).
     ```console
     az eventgrid event-subscription create --name <eventSubscriptionName> \
     --endpoint-type webhook \

articles/communication-services/quickstarts/voice-video-calling/callflows-for-customer-interactions.md

@@ -19,10 +19,11 @@ zone_pivot_groups: acs-csharp-java
 > Functionality described on this document is currently in private preview. Private preview includes access to SDKs and documentation for testing purposes that are not yet available publicly.
 > Apply to become an early adopter by filling out the form for [preview access to Azure Communication Services](https://aka.ms/ACS-EarlyAdopter).
 
-In this tutorial, you'll learn how to build applications that use Azure Communication Services Call Automation SDKs to handle common customer support scenarios. You'll learn how your application can build a call flow, which involves: 
-- receiving notifications for incoming calls to a phone number using Event Grid,
-- answer the call and play audio file using Call Automation SDK, 
-- add a Communication User to the call using Call Automation SDK. This user can be a customer service agent who uses a web application built using Calling SDKs to connect to Azure Communication Services.  
+In this tutorial, you'll learn how to build applications that use Azure Communication Services Call Automation to handle common customer support scenarios, such as:
+- receiving notifications for incoming calls to a phone number using Event Grid
+- answering the call and play audio file using Call Automation SDK
+- adding a communication user to the call using Call Automation SDK. This user can be a customer service agent who uses a web application built using Calling SDKs to connect to Azure Communication Services
+
 
 ::: zone pivot="programming-language-csharp"
 [!INCLUDE [Call flows for customer interactions with .NET](./includes/call-automation/Callflow-for-customer-interactions-csharp.md)]

articles/communication-services/quickstarts/voice-video-calling/includes/call-automation-media/play-audio-quickstart-csharp.md

@@ -47,7 +47,7 @@ By this point you should be familiar with starting calls, if you need to learn m
 
 ## Play audio
 
-Once the call has been established, there are multiple options for how you may wish to play the audio. The first scenario is if you want to play it to the participant that has joined the call, while the second scenario is when you wish to play audio to all the participants in the call. 
+Once the call has been established, there are multiple options for how you may wish to play the audio. You can play audio to the participant that has just joined the call or play audio to all the participants in the call.
 
 ## Play audio - Specific participant
 
@@ -132,7 +132,7 @@ To learn more about other supported events, visit the [Call Automation overview
 
 ## Cancel play action
 
-Cancel all media operations, all pending media operations will be canceled. This will also cancel other queued up play actions.
+Cancel all media operations, all pending media operations will be canceled. This action will also cancel other queued play actions.
 
 ```csharp
 var callMedia = callAutomationClient.GetCallConnection(<callConnectionId>).GetCallMedia();

articles/communication-services/quickstarts/voice-video-calling/includes/call-automation-media/play-audio-quickstart-java.md

@@ -77,7 +77,7 @@ By this point you should be familiar with starting calls, if you need to learn m
 
 ## Play audio
 
-Once the call has been established, there are multiple options for how you may wish to play the audio. The first scenario is if you want to play it to the participant that has joined the call, while the second scenario is when you wish to play audio to all the participants in the call.
+Once the call has been established, there are multiple options for how you may wish to play the audio. You can play audio to the participant that has just joined the call or play audio to all the participants in the call.
 
 ## Play audio - Specific participant
 
@@ -171,7 +171,7 @@ To learn more about other supported events, visit the [Call Automation overview
 
 ## Cancel play action
 
-Cancel all media operations, all pending media operations will be canceled. This will also cancel other queued up play actions. 
+Cancel all media operations, all pending media operations will be canceled. This action will also cancel other queued play actions.
 
 ```console
 var callConnection = callAutomationAsyncClient.getCallConnectionAsync(<callConnectionId>);

articles/communication-services/quickstarts/voice-video-calling/includes/call-automation/callflow-for-customer-interactions-csharp.md

@@ -25,7 +25,7 @@ ms.author: askaur
 
 ## Configure an Event Grid subscription
 
-The Call Automation platform uses Event Grid to deliver the IncomingCall event to a subscription of your choice. For this guide, we will use a web hook subscription pointing to your NGROK application proxy address.
+The Call Automation platform uses Event Grid to deliver the IncomingCall event to a subscription of your choice. For this guide, we'll use a web hook subscription pointing to your NGROK application proxy address.
 
 1. Locate and copy the following to be used in the armclient command-line statement below:
     - Azure subscription ID
@@ -43,11 +43,11 @@ The Call Automation platform uses Event Grid to deliver the IncomingCall event t
     ngrok http <https://localhost:<your_web_service_port>>
     ```
 
-    This will produce a public URI you can use to receive the events from the Event Grid subscription.
+    This command will produce a public URI you can use to receive the events from the Event Grid subscription.
 
-5. Optional: Determine an API route path for the incoming call event together with your NGROK URI which will be used in the armclient command-line statement below, for example: `https://ff2f-75-155-253-232.ngrok.io/api/incomingcall`.
+5. Optional: Determine an API route path for the incoming call event together with your NGROK URI that will be used in the armclient command-line statement below, for example: `https://ff2f-75-155-253-232.ngrok.io/api/incomingcall`.
 6. Event Grid web hooks require a valid reachable endpoint before they can be created. As such, start your web service application and run the commands below.
-7. Since the `IncomingCall` event is not yet published in the portal, you must run the following command-line statements to configure your subscription:
+7. Since the `IncomingCall` event isn't yet published in the portal, you must run the following command-line statements to configure your subscription:
 
     ``` console
     armclient login
@@ -65,7 +65,7 @@ dotnet new web -n MyApplication
 
 ## Install the NuGet package
 
-During the preview phase the NuGet package can be obtained by configuring your package manager to use the Azure SDK Dev Feed from [here](https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md#nuget-package-dev-feed)
+During the preview phase, the NuGet package can be obtained by configuring your package manager to use the Azure SDK Dev Feed from [here](https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md#nuget-package-dev-feed)
 
 ## Obtain your connection string
 
@@ -155,5 +155,5 @@ app.Run();
 1. Place a call to the number you acquired in the Azure portal (see prerequisites above).
 2. Your Event Grid subscription to the `IncomingCall` should execute and call your web server.
 3. The call will be answered, and an asynchronous web hook callback will be sent to the NGROK callback URI.
-4. When the call is connected, a `CallConnected` event will be sent to your web server, wrapped in a `CloudEvent` schema and can be easily deserialized using the Call Automation SDK parser. At this point the application will request audio to be played in a loop to all participants on the call.
-5. When the audio file has played, a `PlayCompleted` event is received and the web server will make a request to add a participant to the call.
+4. When the call is connected, a `CallConnected` event will be sent to your web server, wrapped in a `CloudEvent` schema and can be easily deserialized using the Call Automation SDK parser. At this point, the application will request audio to be played in a loop to all participants on the call.
+5. When the audio file has played, a `PlayCompleted` event is received, and the web server will make a request to add a participant to the call.