Merge branch 'comm-services-samples-tutorials' of https://github.com/paulth1/azure-docs-pr into comm-services-samples-tutorials

Author: paulth1

articles/communication-services/how-tos/call-automation/control-mid-call-media-actions.md

@@ -19,7 +19,7 @@ Call Automation uses a REST API interface to receive requests for actions and pr
 Call Automation supports other actions to manage calls and recordings that aren't included in this article.
 
 > [!NOTE]
-> Call Automation currently doesn't interoperate with Microsoft Teams. Actions like making or redirecting a call to a Teams user or playing audio to a Teams user by using Call Automation isn't supported.
+> Call Automation currently doesn't interoperate with Microsoft Teams. Actions like making or redirecting a call to a Teams user or playing audio to a Teams user by using Call Automation aren't supported.
 
 ## Prerequisites
 

articles/communication-services/how-tos/call-automation/custom-context.md

@@ -16,7 +16,7 @@ services: azure-communication-services
 
 Call Automation allows developers to pass along custom contextual information when routing calls. Developers can pass metadata about the call, caller, or any other information that's relevant to their application or business logic. Businesses can then manage and route calls across networks without having to worry about losing context.
 
-Passing context is supported by specifying custom headers. This optional list of key-value pairs is included as part of `AddParticipant` or `Transfer` actions. The context is retrieved later as part of the `IncomingCall` event payload.
+Passing context is supported by specifying custom headers. This optional list of key/value pairs is included as part of `AddParticipant` or `Transfer` actions. The context is retrieved later as part of the `IncomingCall` event payload.
 
 Custom call context is also forwarded to the Session Initiation Protocol (SIP), which includes both the freeform custom headers and the standard user-to-user information (UUI) SIP header. When an inbound call from your telephony network is routed, the data set from your Session Border Controller (SBC) in the custom headers and UUI is similarly included in the `IncomingCall` event payload.
 
@@ -27,7 +27,7 @@ The following samples show how to get started by using custom context headers in
 ## Prerequisites
 
 - Read the Call Automation [concepts article](../../concepts/call-automation/call-automation.md#call-actions) that describes the action-event programming model and event callbacks.
-- Learn about the [user identifiers](../../concepts/identifiers.md#the-communicationidentifier-type) like `CommunicationUserIdentifier`` and PhoneNumberIdentifier` that are used in this article.
+- Learn about the [user identifiers](../../concepts/identifiers.md#the-communicationidentifier-type) like `CommunicationUserIdentifier` and PhoneNumberIdentifier` that are used in this article.
 
 For all the code samples, `client` is the `CallAutomationClient` object that you can create, and `callConnection` is the `CallConnection` object that you obtain from an `Answer` or `CreateCall` response. You can also obtain it from callback events that your application receives.
 

articles/communication-services/how-tos/call-automation/includes/secure-websocket-csharp.md

@@ -1,5 +1,5 @@
 ---
-title: include file
+title: Include file
 description: .NET websocket callback security
 services: azure-communication-services
 author: Kunaal Punjabi

articles/communication-services/how-tos/call-automation/secure-webhook-endpoint.md

@@ -17,7 +17,7 @@ zone_pivot_groups: acs-js-csharp-java-python
 
 # Secure webhook endpoints and WebSocket connections
 
-Securing the delivery of messages from end to end is crucial for ensuring the confidentiality, integrity, and trustworthiness of sensitive information transmitted between systems. Your ability and willingness to trust information received from a remote system relies on the sender providing their identity. Call Automation has two ways of communicating events that can be secured: the shared `IncomingCall` event sent by Azure Event Grid and all other mid-call events sent by the Call Automation platform via webhook.
+Securing the delivery of messages from end to end is crucial for ensuring the confidentiality, integrity, and trustworthiness of sensitive information transmitted between systems. Your ability and willingness to trust information received from a remote system rely on the sender providing their identity. Call Automation has two ways of communicating events that can be secured: the shared `IncomingCall` event sent by Azure Event Grid and all other mid-call events sent by the Call Automation platform via webhook.
 
 ## Incoming call event
 

articles/communication-services/samples/includes/call-automation-azure-openai-js.md

@@ -20,7 +20,7 @@ This server-side application helps you create a virtual assistant that can handl
 
 ## Prerequisites
 
-- An Azure account with an active subscription. For more information, see [Create an account for free](https://azure.microsoft.com/free/)
+- An Azure account with an active subscription. For more information, see [Create an account for free](https://azure.microsoft.com/free/).
 - [Visual Studio Code](https://code.visualstudio.com/download) installed.
 - [Node.js](https://nodejs.org/en/download) installed.
 - An Azure Communication Services resource. For more information, see [Create an Azure Communication Services resource](../../quickstarts/create-communication-resource.md?tabs=windows&pivots=platform-azp). You need to record your resource *connection string* for this sample.
@@ -34,7 +34,7 @@ This server-side application helps you create a virtual assistant that can handl
 ## Before you run the sample for the first time
 
 1. Open an instance of PowerShell, a Windows terminal, a command prompt, or the equivalent, and go to the directory where you want to clone the sample.
-1. Use the command `git clone` `https://github.com/Azure-Samples/communication-services-javascript-quickstarts.git`.
+1. Use the command `git clone https://github.com/Azure-Samples/communication-services-javascript-quickstarts.git`.
 1. Use the command `cd` to access the `callautomation-az-openai-voice` folder.
 1. From the root of the folder, and with a node installed, run `npm install`.
 
@@ -66,9 +66,9 @@ Open the `.env` file to configure the following settings:
 1. The browser opens with a page. If it doesn't, go to `http://localhost:8080/`.
 1. Register an Azure Event Grid webhook for the `IncomingCall` event that points to your 8080 port URI. For more information, see [Incoming call concepts](/azure/communication-services/concepts/call-automation/incoming-call-notification). For example:
 
-``` code
- https://<devtunelurl>/api/incomingCall
-```
+   ``` code
+    https://<devtunelurl>/api/incomingCall
+   ```
 
 Now you have a running application. The best way to test this sample is to place a call to your Azure Communication Services phone number and talk to your intelligent agent.
 

articles/communication-services/samples/integrate-azure-communication-services-with-copilot-studio.md

@@ -239,6 +239,6 @@ Now you can make a call and talk to your agent.
 
 To optimize for voice, we recommend that you update topics where you're using the `Message` type of text to speech, because it optimizes the agent's responses for speech scenarios.
 
-### Handle system topics
+### System topics
 
 Your agent has system topics built in by default. You can choose to disable these topics. If you want to continue using them, your application should build logic to handle these topics. For example, you need to build agent transfer into your application to escalate the call from this Copilot agent to a human representative.