edit pass: comm-services-samples-tutorials

Author: paulth1

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

@@ -436,7 +436,7 @@ call_invite = CallInvite(
 -----
 No events are published for redirect. If the target is an Azure Communication Services user or a phone number that your resource owns, it generates a new `IncomingCall` event with the `to` field set to the target that you specify.
 
-## Transfer a participant in call
+## Transfer a participant in a call
 
 When your application answers a call or places an outbound call to an endpoint, your app can transfer the endpoint to another destination endpoint. Transferring a 1:1 call removes your application from the call and removes its ability to control the call by using Call Automation. The call invite to the target shows the caller ID of the endpoint being transferred. Providing a custom caller ID isn't supported.
 

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

@@ -25,7 +25,7 @@ Call Automation supports other actions to manage calls and recordings that aren'
 
 - 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 more about [how to control and steer calls with Call Automation](./actions-for-call-control.md), which teaches you about dealing with the basics of dealing with a call.
+- Learn more about how to [control and steer calls with Call Automation](./actions-for-call-control.md), which teaches you about the basics of dealing with a call.
 
 For all the code samples, `client` is the `CallAutomationClient` object that you can create, as shown, and `callConnection` is the `CallConnection` object that you obtain from the `Answer` or `CreateCall` response. You can also obtain it from callback events that your application receives.
 

articles/communication-services/how-tos/call-automation/handle-events-with-event-processor.md

@@ -71,8 +71,7 @@ CallConnected returnedEvent = eventResult.SuccessResult;
 
 With the event processor, you can easily wait for the `CallConnected` event until the call is established. If the call was never established (that is, the caller never picked up the phone), it throws a timeout exception. If the creation of the call otherwise fails, you receive `CallDisconnected` and `CreateCallFailed` events with error codes for further troubleshooting. For more information on Call Automation error codes, see [Troubleshooting call end response codes](./../../resources/troubleshooting/voice-video-calling/troubleshooting-codes.md).
 
-> [!NOTE]
-> If a specific timeout wasn't given when you waited on the event processor, it waits until its default timeout happens. The default timeout is four minutes.
+If a specific timeout wasn't given when you waited on the event processor, it waits until its default timeout happens. The default timeout is four minutes.
 
 ## Use the play request's response to wait for Play events
 
@@ -119,8 +118,7 @@ eventProcessor.AttachOngoingEventProcessor<ParticipantsUpdated>(callConnectionId
 
 With this specific ongoing event processor, you can now print the number of participants or the participants on the call whenever people join or leave the call.
 
-> [!TIP]
-> You can attach an ongoing handler to any event type. This capability opens the possibility to build your application with a callback design pattern.
+You can attach an ongoing handler to any event type. This capability opens the possibility to build your application with a callback design pattern.
 
 ## Advanced: Use a predicate to wait for a specific event
 

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

@@ -1,5 +1,5 @@
 ---
-title: include file
+title: Include file
 description: C# webhook callback security
 services: azure-communication-services
 author: Richard Cho
@@ -20,7 +20,7 @@ Each mid-call webhook callback sent by Call Automation uses a signed JSON Web To
 1. Configure your application to validate the JWT by using the NuGet package and the configuration of your Azure Communication Services resource. You need the `audience` value as it appears in the JWT payload.
 1. Validate the issuer, the audience, and the JWT:
    - The audience is your Azure Communication Services resource ID that you used to set up your Call Automation client. For information about how to get it, see [Get your Azure resource ID](../../../quickstarts/voice-video-calling/get-resource-id.md).
-   - The JSON Web Key Set (JWKS) endpoint in the OpenId configuration contains the keys that are used to validate the JWT. When the signature is valid and the token hasn't expired (within five minutes of generation), the client can use the token for authorization.
+   - The JSON Web Key Set endpoint in the OpenId configuration contains the keys that are used to validate the JWT. When the signature is valid and the token hasn't expired (within five minutes of generation), the client can use the token for authorization.
 
 This sample code demonstrates how to use `Microsoft.IdentityModel.Protocols.OpenIdConnect` to validate the webhook payload:
 

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

@@ -1,5 +1,5 @@
 ---
-title: include file
+title: Include file
 description: Java webhook callback security
 services: azure-communication-services
 author: Richard Cho
@@ -37,7 +37,7 @@ Each mid-call webhook callback sent by Call Automation uses a signed JSON Web To
 1. Configure your application to validate the JWT and the configuration of your Azure Communication Services resource. You need the `audience` value as it appears in the JWT payload.
 1. Validate the issuer, the audience, and the JWT:
    - The audience is your Azure Communication Services resource ID that you used to set up your Call Automation client. For information about how to get it, see [Get your Azure resource ID](../../../quickstarts/voice-video-calling/get-resource-id.md).
-   - The JSON Web Key Set (JWKS) endpoint in the OpenId configuration contains the keys that are used to validate the JWT. When the signature is valid and the token hasn't expired (within five minutes of generation), the client can use the token for authorization.
+   - The JSON Web Key Set endpoint in the OpenID configuration contains the keys that are used to validate the JWT. When the signature is valid and the token hasn't expired (within five minutes of generation), the client can use the token for authorization.
 
 This sample code demonstrates how to configure the OIDC client to validate a webhook payload by using JWT:
 

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

@@ -1,5 +1,5 @@
 ---
-title: include file
+title: Include file
 description: JavaScript webhook callback security
 services: azure-communication-services
 author: Richard Cho
@@ -28,7 +28,7 @@ npm install express jwks-rsa jsonwebtoken
 1. Configure your application to validate the JWT and the configuration of your Azure Communication Services resource. You need the `audience` value as it appears in the JWT payload.
 1. Validate the issuer, the audience, and the JWT:
    - The audience is your Azure Communication Services resource ID that you used to set up your Call Automation client. For information about how to get it, see [Get your Azure resource ID](../../../quickstarts/voice-video-calling/get-resource-id.md).
-   - The JSON Web Key Set (JWKS) endpoint in the OpenId configuration contains the keys that are used to validate the JWT. When the signature is valid and the token hasn't expired (within five minutes of generation), the client can use the token for authorization.
+   - The JSON Web Key Set endpoint in the OpenID configuration contains the keys that are used to validate the JWT. When the signature is valid and the token hasn't expired (within five minutes of generation), the client can use the token for authorization.
 
 This sample code demonstrates how to configure the OIDC client to validate a webhook payload by using JWT:
 

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

@@ -1,5 +1,5 @@
 ---
-title: include file
+title: Include file
 description: Python webhook callback security
 services: azure-communication-services
 author: Richard Cho
@@ -27,7 +27,7 @@ pip install flask pyjwt
 1. Configure your application to validate the JWT and the configuration of your Azure Communication Services resource. You need the `audience` value as it appears in the JWT payload.
 1. Validate the issuer, the audience, and the JWT:
    - The audience is your Azure Communication Services resource ID that you used to set up your Call Automation client. For information about how to get it, see [Get your Azure resource ID](../../../quickstarts/voice-video-calling/get-resource-id.md).
-   - The JSON Web Key Set (JWKS) endpoint in the OpenId configuration contains the keys that are used to validate the JWT. When the signature is valid and the token hasn't expired (within five minutes of generation), the client can use the token for authorization.
+   - The JSON Web Key Set endpoint in the OpenId configuration contains the keys that are used to validate the JWT. When the signature is valid and the token hasn't expired (within five minutes of generation), the client can use the token for authorization.
 
 This sample code demonstrates how to configure the OIDC client to validate a webhook payload by using JWT:
 

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

@@ -1,6 +1,6 @@
 ---
-title: include file
-description: JavaScript websocket callback security
+title: Include file
+description: JavaScript WebSocket callback security
 services: azure-communication-services
 author: Kunaal Punjabi
 ms.service: azure-communication-services

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

@@ -1,6 +1,6 @@
 ---
-title: include file
-description: Python websocket callback security
+title: Include file
+description: Python WebSocket callback security
 services: azure-communication-services
 author: Kunaal Punjabi
 ms.service: azure-communication-services

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

@@ -19,7 +19,7 @@ zone_pivot_groups: acs-js-csharp-java-python
 
 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.
 
-## Incoming Call Event
+## Incoming call event
 
 Azure Communication Services relies on Azure Event Grid subscriptions to deliver the [IncomingCall event](../../concepts/call-automation/incoming-call-notification.md). For more information, see [Deliver events to Microsoft Entra protected endpoints](../../../event-grid/secure-webhook-delivery.md).