edit pass: comm-services-samples-tutorials

Author: paulth1

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

@@ -11,18 +11,18 @@ ms.topic: include file
 ms.author: richardcho
 ---
 
-## Improving Call Automation webhook callback security
+## Improve Call Automation webhook callback security
 
-Each mid-call webhook callback sent by Call Automation uses a signed JSON Web Token (JWT) in the Authentication header of the inbound HTTPS request. You can use standard Open ID Connect (OIDC) JWT validation techniques to ensure the integrity of the token as follows. The lifetime of the JWT is five (5) minutes and a new token is created for every event sent to the callback URI.
+Each mid-call webhook callback sent by Call Automation uses a signed JSON Web Token (JWT) in the Authentication header of the inbound HTTPS request. You can use standard OpenID Connect (OIDC) JWT validation techniques to ensure the integrity of the token. The lifetime of the JWT is five minutes, and a new token is created for every event sent to the callback URI.
 
-1. Obtain the Open ID configuration URL: <https://acscallautomation.communication.azure.com/calling/.well-known/acsopenidconfiguration>
-2. Install the [Microsoft.AspNetCore.Authentication.JwtBearer NuGet](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.JwtBearer) package.
-3. Configure your application to validate the JWT using the NuGet package and the configuration of your Azure Communication Services resource. You need the `audience` values as it is present in the JWT payload.
-4. Validate the issuer, audience and the JWT.
-   - The audience is your Azure Communication Services resource ID you used to set up your Call Automation client. Refer [here](../../../quickstarts/voice-video-calling/get-resource-id.md) about how to get it.
-   - The JSON Web Key Set (JWKS) endpoint in the OpenId configuration contains the keys used to validate the JWT. When the signature is valid and the token hasn't expired (within 5 minutes of generation), the client can use the token for authorization.
+1. Obtain the OpenID configuration URL: <https://acscallautomation.communication.azure.com/calling/.well-known/acsopenidconfiguration>
+1. Install the [Microsoft.AspNetCore.Authentication.JwtBearer NuGet](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.JwtBearer) package.
+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.
 
-This sample code demonstrates how to use `Microsoft.IdentityModel.Protocols.OpenIdConnect` to validate webhook payload
+This sample code demonstrates how to use `Microsoft.IdentityModel.Protocols.OpenIdConnect` to validate the webhook payload:
 
 ```csharp
 using Microsoft.AspNetCore.Authentication.JwtBearer;

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

@@ -11,13 +11,13 @@ ms.topic: include file
 ms.author: richardcho
 ---
 
-## Improving Call Automation webhook callback security
+## Improve Call Automation webhook callback security
 
-Each mid-call webhook callback sent by Call Automation uses a signed JSON Web Token (JWT) in the Authentication header of the inbound HTTPS request. You can use standard Open ID Connect (OIDC) JWT validation techniques to ensure the integrity of the token as follows. The lifetime of the JWT is five (5) minutes and a new token is created for every event sent to the callback URI.
+Each mid-call webhook callback sent by Call Automation uses a signed JSON Web Token (JWT) in the Authentication header of the inbound HTTPS request. You can use standard OpenID Connect (OIDC) JWT validation techniques to ensure the integrity of the token. The lifetime of the JWT is five minutes, and a new token is created for every event sent to the callback URI.
 
-1. Obtain the Open ID configuration URL: <https://acscallautomation.communication.azure.com/calling/.well-known/acsopenidconfiguration>
-2. The following sample uses Spring framework, created using [spring initializr](https://start.spring.io/) with Maven as project build tool.
-3. Add the following dependencies in your `pom.xml`:
+1. Obtain the OpenID configuration URL: <https://acscallautomation.communication.azure.com/calling/.well-known/acsopenidconfiguration>
+1. The following sample uses the Spring framework, which is created by using [spring initializr](https://start.spring.io/) with Maven as the project build tool.
+1. Add the following dependencies in your `pom.xml`:
 
 ```
   <dependency>
@@ -34,12 +34,12 @@ Each mid-call webhook callback sent by Call Automation uses a signed JSON Web To
   </dependency>
 ```
 
-4. Configure your application to validate the JWT and the configuration of your Azure Communication Services resource. You need the `audience` values as it is present in the JWT payload.
-5. Validate the issuer, audience and the JWT.
-   - The audience is your Azure Communication Services resource ID you used to set up your Call Automation client. Refer [here](../../../quickstarts/voice-video-calling/get-resource-id.md) about how to get it.
-   - The JSON Web Key Set (JWKS) endpoint in the OpenId configuration contains the keys used to validate the JWT. When the signature is valid and the token hasn't expired (within 5 minutes of generation), the client can use the token for authorization.
+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.
 
-This sample code demonstrates how to configure OIDC client to validate webhook payload using JWT
+This sample code demonstrates how to configure the OIDC client to validate a webhook payload by using JWT:
 
 ```java
 package callautomation.example.security;

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

@@ -11,12 +11,12 @@ ms.topic: include file
 ms.author: richardcho
 ---
 
-## Improving Call Automation webhook callback security
+## Improve Call Automation webhook callback security
 
-Each mid-call webhook callback sent by Call Automation uses a signed JSON Web Token (JWT) in the Authentication header of the inbound HTTPS request. You can use standard Open ID Connect (OIDC) JWT validation techniques to ensure the integrity of the token as follows. The lifetime of the JWT is five (5) minutes and a new token is created for every event sent to the callback URI.
+Each mid-call webhook callback sent by Call Automation uses a signed JSON Web Token (JWT) in the Authentication header of the inbound HTTPS request. You can use standard OpenID Connect (OIDC) JWT validation techniques to ensure the integrity of the token. The lifetime of the JWT is five minutes, and a new token is created for every event sent to the callback URI.
 
-1. Obtain the Open ID configuration URL: <https://acscallautomation.communication.azure.com/calling/.well-known/acsopenidconfiguration>
-2. Install the following packages:
+1. Obtain the OpenID configuration URL: <https://acscallautomation.communication.azure.com/calling/.well-known/acsopenidconfiguration>
+1. Install the following packages:
     - [express npm](https://www.npmjs.com/package/express)
     - [jwks-rsa npm](https://www.npmjs.com/package/jwks-rsa)
     - [jsonwebtoken npm](https://www.npmjs.com/package/jsonwebtoken)
@@ -25,12 +25,12 @@ Each mid-call webhook callback sent by Call Automation uses a signed JSON Web To
 npm install express jwks-rsa jsonwebtoken
 ```
 
-3. Configure your application to validate the JWT and the configuration of your Azure Communication Services resource. You need the `audience` values as it is present in the JWT payload.
-4. Validate the issuer, audience and the JWT.
-   - The audience is your Azure Communication Services resource ID you used to set up your Call Automation client. Refer [here](../../../quickstarts/voice-video-calling/get-resource-id.md) about how to get it.
-   - The JSON Web Key Set (JWKS) endpoint in the OpenId configuration contains the keys used to validate the JWT. When the signature is valid and the token hasn't expired (within 5 minutes of generation), the client can use the token for authorization.
+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.
 
-This sample code demonstrates how to configure OIDC client to validate webhook payload using JWT
+This sample code demonstrates how to configure the OIDC client to validate a webhook payload by using JWT:
 
 ```JavaScript
 import express from "express";

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

@@ -11,25 +11,25 @@ ms.topic: include file
 ms.author: richardcho
 ---
 
-## Improving Call Automation webhook callback security
+## Improve Call Automation webhook callback security
 
-Each mid-call webhook callback sent by Call Automation uses a signed JSON Web Token (JWT) in the Authentication header of the inbound HTTPS request. You can use standard Open ID Connect (OIDC) JWT validation techniques to ensure the integrity of the token as follows. The lifetime of the JWT is five (5) minutes and a new token is created for every event sent to the callback URI.
+Each mid-call webhook callback sent by Call Automation uses a signed JSON Web Token (JWT) in the Authentication header of the inbound HTTPS request. You can use standard OpenID Connect (OIDC) JWT validation techniques to ensure the integrity of the token. The lifetime of the JWT is five minutes, and a new token is created for every event sent to the callback URI.
 
-1. Obtain the Open ID configuration URL: <https://acscallautomation.communication.azure.com/calling/.well-known/acsopenidconfiguration>
-2. Install the following packages:
+1. Obtain the OpenID configuration URL: <https://acscallautomation.communication.azure.com/calling/.well-known/acsopenidconfiguration>
+1. Install the following packages:
     - [flask pypi](https://pypi.org/project/Flask/)
     - [PyJWT pypi](https://pypi.org/project/PyJWT/)
 
 ```console
 pip install flask pyjwt
 ```
 
-3. Configure your application to validate the JWT and the configuration of your Azure Communication Services resource. You need the `audience` values as it is present in the JWT payload.
-4. Validate the issuer, audience and the JWT.
-   - The audience is your Azure Communication Services resource ID you used to set up your Call Automation client. Refer [here](../../../quickstarts/voice-video-calling/get-resource-id.md) about how to get it.
-   - The JSON Web Key Set (JWKS) endpoint in the OpenId configuration contains the keys used to validate the JWT. When the signature is valid and the token hasn't expired (within 5 minutes of generation), the client can use the token for authorization.
+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.
 
-This sample code demonstrates how to configure OIDC client to validate webhook payload using JWT
+This sample code demonstrates how to configure the OIDC client to validate a webhook payload by using JWT:
 
 ```Python
 from flask import Flask, jsonify, abort, request

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

@@ -11,9 +11,9 @@ ms.topic: include file
 ms.author: kpunjabi
 ---
 
-## Websocket code sample
+## WebSocket code sample
 
-This sample code demonstrates how to authenticate WebSocket connection requests using JSON Web Token (JWT) tokens.
+This sample code demonstrates how to authenticate WebSocket connection requests by using JWT tokens.
 
 ```csharp
 // 1. Load OpenID Connect metadata

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

@@ -11,9 +11,9 @@ ms.topic: include file
 ms.author: kpunjabi
 ---
 
-## Websocket code sample
+## WebSocket code sample
 
-This sample demonstrates how to configure an OpenID Connect (OIDC) client to validate WebSocket connection requests using a JSON Web Token (JWT).
+This sample demonstrates how to configure an OIDC client to validate WebSocket connection requests by using a JWT.
 
 ```JavaScript
 const audience = "ACS resource ID";

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

@@ -11,9 +11,9 @@ ms.topic: include file
 ms.author: kpunjabi
 ---
 
-## Websocket code sample
+## WebSocket code sample
 
-This sample demonstrates how to configure an OIDC-compliant client to validate WebSocket connection requests using JWT.
+This sample demonstrates how to configure an OIDC-compliant client to validate WebSocket connection requests by using a JWT.
 
 Make sure to install the required package:
 `pip install cryptography`