edit pass: comm-services-samples-tutorials

Author: paulth1

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

@@ -23,7 +23,7 @@ Call Automation supports other actions to manage call media and recording that h
 - 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.
 
-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 your application receives.
+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.
 
 ## [csharp](#tab/csharp)
 

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

@@ -1,5 +1,5 @@
 ---
-title: Azure Communication Services Call Automation how-to for securing webhook endpoint 
+title: Azure Communication Services Call Automation How-to for Securing Webhook Endpoint 
 titleSuffix: An Azure Communication Services how-to document
 description: The article shows how to secure the delivery of incoming calls and callback events.
 author: fanche
@@ -49,11 +49,10 @@ A common way that you can improve this security is by implementing an API key me
 
 ### Authentication token in a WebSocket header
 
-Each WebSocket connection request made by Call Automation now includes a signed JWT in the Authentication header. This token is validated by using standard OIDC JWT validation methods:
+Each WebSocket connection request made by Call Automation now includes a signed JWT in the authentication header. This token is validated by using standard OIDC JWT validation methods:
 
   - The JWT has a lifetime of 24 hours.
   - A new token is generated for each connection request to your WebSocket server.
-  - More information is available in the official documentation: Secure webhook endpoint – Azure Communication Services.
 
  ::: zone pivot="programming-language-csharp"
 [!INCLUDE [Secure websocket with .NET](./includes/secure-websocket-csharp.md)]
@@ -69,7 +68,7 @@ Each WebSocket connection request made by Call Automation now includes a signed
 
 ## IP range
 
-Another way that you can secure your WebSocket connections is by allowing only Microsoft connections from certain IP ranges.
+Another way that you can secure your WebSocket connections is to allow only Microsoft connections from certain IP ranges.
 
 | Category | IP ranges or FQDN | Ports |
 | :-- | :-- | :-- |