Validation error fixes

Resolves errors and made other edits

Author: vac0224

articles/communication-services/concepts/call-automation/call-automation.md

@@ -11,7 +11,7 @@ ms.author: askaur
 ---
 # Call Automation Overview
 
-Azure Communication Services Call Automation provides developers the ability to build server-based, intelligent call workflows, and call recording for voice and Public Switched Telephone Network(PSTN) channels. The SDKs, available in C#, Java, JavaScript, and Python, use an action-event model to help you build personalized customer interactions. Your communication applications can listen to real-time call events and perform control plane actions (like answer, transfer, play audio, start recording, etc.) to steer and control calls based on your business logic.
+Azure Communication Services Call Automation provides developers the ability to build server-based, intelligent call workflows, and call recording for voice and Public Switched Telephone Network (PSTN) channels. The SDKs, available in C#, Java, JavaScript, and Python, use an action-event model to help you build personalized customer interactions. Your communication applications can listen to real-time call events and perform control plane actions (such as answer, transfer, play audio, start recording, and so on) to steer and control calls based on your business logic.
 
 ## Common use cases
 
@@ -146,8 +146,8 @@ The Call Automation events are sent to the web hook callback URI specified when
 | `CallConnected` | The call successfully started (when using `Answer` or `Create` action) or your application successfully connected to an ongoing call (when using `Connect` action). |
 | `CallDisconnected` | Your application has been disconnected from the call. |
 | `ConnectFailed` | Your application failed to connect to a call (for `Connect` call action only). |
-| `CallTransferAccepted` | Transfer action successfully completed and the transferee is connected to the target participant |.
-| `CallTransferFailed ` | The transfer action failed. |
+| `CallTransferAccepted` | Transfer action successfully completed and the transferee is connected to the target participant. |
+| `CallTransferFailed` | The transfer action failed. |
 | `AddParticipantSucceeded` | Your application successfully added a participant to the call. |
 | `AddParticipantFailed` | Your application was unable to add a participant to the call (due to an error or the participant didn't accept the invite) |
 | `CancelAddParticipantSucceeded` | Your application canceled an `AddParticipant` request successfully (the participant wasn't added to the call). |
@@ -160,7 +160,7 @@ The Call Automation events are sent to the web hook callback URI specified when
 | `PlayCanceled` | The requested play action has been canceled. |
 | `RecognizeCompleted` | Recognition of user input successfully completed. |
 | `RecognizeCanceled` | The requested `Recognize` action has been canceled. |
-| `RecognizeFailed` | Recognition of user input was unsuccessful. <br/>*For more information about recognize action events, see the how-to guide for [gathering user input](../../how-tos/call-automation/recognize-action.md).*|
+| `RecognizeFailed` | Recognition of user input was unsuccessful. <br/>*For more information about recognize action events, see the how-to guide for [gathering user input](../../how-tos/call-automation/recognize-action.md).* |
 | `RecordingStateChanged` | Status of recording action has changed from active to inactive or vice versa. |
 | `ContinuousDtmfRecognitionToneReceived` | `StartContinuousDtmfRecognition` completed successfully and a DTMF tone was received from the participant. |
 | `ContinuousDtmfRecognitionToneFailed` | `StartContinuousDtmfRecognition` completed but an error occurred while handling a DTMF tone from the participant. |
@@ -176,7 +176,7 @@ To learn how to secure the callback event delivery, see [How to secure webhook e
 
 ### Operation Callback URI
 
-Operation Callback URI is an optional parameter in some mid-call APIs that use events as their async responses. By default, all events are sent to the default callback URI set by `CreateCall` / `AnswerCall` API events when the user establishes a call. Using the Operation Callback URI, the operation sends corresponding events for this individual (one-time only) request to the new URI.
+Operation Callback URI is an optional parameter in some mid-call APIs that use events as their async responses. By default, all events are sent to the default callback URI set by `CreateCall` / `AnswerCall` API events when the user establishes a call. Using the Operation Callback URI, the API sends corresponding events for this individual (one-time only) request to the new URI.
 
 | Supported API             | Corresponding event |
 | ----------------- | ------------ |

articles/communication-services/how-tos/call-automation/includes/recognize-action-quickstart-csharp.md

@@ -1,6 +1,6 @@
 ---
 title: include file
-description: C# recognize action quickstart
+description: C# Recognize action quickstart
 services: azure-communication-services
 author: Kunaal
 ms.service: azure-communication-services
@@ -16,7 +16,7 @@ ms.author: kpunjabi
 - Azure Communication Services resource. See [Create an Azure Communication Services resource](../../../quickstarts/create-communication-resource.md?tabs=windows&pivots=platform-azp). Note the connection string for this resource. 
 - Create a new web service application using the [Call Automation SDK](../../../quickstarts/call-automation/callflows-for-customer-interactions.md).
 - The latest [.NET library](https://dotnet.microsoft.com/download/dotnet-core) for your operating system.
-- Obtain the latest [NuGet package](https://www.nuget.org/packages/Azure.Communication.CallAutomation/).
+- The latest [NuGet package](https://www.nuget.org/packages/Azure.Communication.CallAutomation/).
 
 ### For AI features 
 - Create and connect [Azure AI services to your Azure Communication Services resource](../../../concepts/call-automation/azure-communication-services-azure-cognitive-services-integration.md).
@@ -27,26 +27,26 @@ ms.author: kpunjabi
 
 The following parameters are available to customize the Recognize function:
 
-| Parameter | Type|Default (if not specified) | Description | Required or Optional |
-| ------- |--| ------------------------ | --------- | ------------------ |
-| Prompt <br/><br/> *(For details, see [Customize voice prompts to users with Play action](../play-ai-action.md))* | FileSource, TextSource | Not set |This is the message you wish to play before recognizing input. | Optional |
-| InterToneTimeout | TimeSpan | 2 seconds <br/><br/>**Min:** 1 second <br/>**Max:** 60 seconds | Limit in seconds that Azure Communication Services waits for the caller to press another digit (inter-digit timeout). | Optional |
-| InitialSegmentationSilenceTimeoutInSeconds | Integer | 0.5 second | How long recognize action waits for input before considering it a timeout. [Read more here](../../../../../articles/cognitive-services/Speech-Service/how-to-recognize-speech.md). | Optional |
-| RecognizeInputsType | Enum | dtmf | Type of input that is recognized. Options are `dtmf`, `choices`, `speech`, and `speechordtmf`. | Required |
-| InitialSilenceTimeout | TimeSpan | 5 seconds<br/><br/>**Min:** 0 seconds <br/>**Max:** 300 seconds (DTMF) <br/>**Max:** 20 seconds (Choices) <br/>**Max:** 20 seconds (Speech)| Initial silence timeout adjusts how much nonspeech audio is allowed before a phrase before the recognition attempt ends in a "no match" result. [Read more here](../../../../../articles/cognitive-services/Speech-Service/how-to-recognize-speech.md). | Optional |
-| MaxTonesToCollect | Integer | No default<br/><br/>**Min:** 1|Number of digits a developer expects as input from the participant.| Required |
-| StopTones |IEnumeration\<DtmfTone\> | Not set | The digit participants can press to escape out of a batch DTMF event. | Optional |
-| InterruptPrompt | Bool | True | If the participant has the ability to interrupt the playMessage by pressing a digit. | Optional |
-| InterruptCallMediaOperation | Bool | True | If this flag is set it interrupts the current call media operation. For example if any audio is being played it interrupts that operation and initiates recognize. | Optional |
-| OperationContext | String | Not set | String that developers can pass mid action, useful for allowing developers to store context about the events they receive. | Optional |
-| Phrases | String | Not set | List of phrases that associate to the label, if any of these are heard it's considered a successful recognition. | Required | 
-| Tone | String | Not set | The tone to recognize if user decides to press a number instead of using speech. | Optional |
-| Label | String | Not set | The key value for recognition. | Required |
-| Language | String | En-us | The language that is used for recognizing speech. | Optional |
-| EndSilenceTimeout| TimeSpan | 0.5 second | The final pause of the speaker used to detect the final result that gets generated as speech. | Optional |
+| Parameter | Type | Default (if not specified) | Description | Required or Optional |
+| ------- | --- | ------------------------ | --------- | ------------------ |
+| `Prompt` <br/><br/> *(For details, see [Customize voice prompts to users with Play action](../play-ai-action.md))* | FileSource, TextSource | Not set | The message to play before recognizing input. | Optional |
+| `InterToneTimeout` | TimeSpan | 2 seconds <br/><br/>**Min:** 1 second <br/>**Max:** 60 seconds | Limit in seconds that Azure Communication Services waits for the caller to press another digit (inter-digit timeout). | Optional |
+| `InitialSegmentationSilenceTimeoutInSeconds` | Integer | 0.5 second | How long recognize action waits for input before considering it a timeout. See [How to recognize speech](/azure/ai-services/speech-service/how-to-recognize-speech). | Optional |
+| `RecognizeInputsType` | Enum | dtmf | Type of input that is recognized. Options are `dtmf`, `choices`, `speech`, and `speechordtmf`. | Required |
+| `InitialSilenceTimeout` | TimeSpan | 5 seconds<br/><br/>**Min:** 0 seconds <br/>**Max:** 300 seconds (DTMF) <br/>**Max:** 20 seconds (Choices) <br/>**Max:** 20 seconds (Speech)| Initial silence timeout adjusts how much nonspeech audio is allowed before a phrase before the recognition attempt ends in a "no match" result. See [How to recognize speech](/azure/ai-services/speech-service/how-to-recognize-speech). | Optional |
+| `MaxTonesToCollect` | Integer | No default<br/><br/>**Min:** 1|Number of digits a developer expects as input from the participant.| Required |
+| `StopTones` | IEnumeration\<DtmfTone\> | Not set | The digit participants can press to escape out of a batch DTMF event. | Optional |
+|    `InterruptPrompt` | Bool | True | If the participant has the ability to interrupt the playMessage by pressing a digit. | Optional |
+| `InterruptCallMediaOperation` | Bool | True | If this flag is set, it interrupts the current call media operation. For example if any audio is being played it interrupts that operation and initiates recognize. | Optional |
+| `OperationContext` | String | Not set | String that developers can pass mid action, useful for allowing developers to store context about the events they receive. | Optional |
+| `Phrases` | String | Not set | List of phrases that associate to the label. Hearing any of these phrases results in a successful recognition. | Required | 
+| `Tone` | String | Not set | The tone to recognize if user decides to press a number instead of using speech. | Optional |
+| `Label` | String | Not set | The key value for recognition. | Required |
+| `Language` | String | En-us | The language that is used for recognizing speech. | Optional |
+| `EndSilenceTimeout` | TimeSpan | 0.5 second | The final pause of the speaker used to detect the final result that gets generated as speech. | Optional |
 
 >[!NOTE] 
->In situations where both dtmf and speech are in the recognizeInputsType, the recognize action will act on the first input type received, i.e. if the user presses a keypad number first then the recognize action will consider it a dtmf event and continue listening for dtmf tones. If the user speaks first then the recognize action will consider it a speech recognition and listen for voice input. 
+>In situations where both DTMF and speech are in the `recognizeInputsType`, the recognize action acts on the first input type received. For example, if the user presses a keypad number first then the recognize action considers it a DTMF event and continues listening for DTMF tones. If the user speaks first then the recognize action considers it a speech recognition event and listens for voice input.  
 
 
 ## Create a new C# application
@@ -59,11 +59,11 @@ dotnet new web -n MyApplication
 
 ## Install the NuGet package
 
-The NuGet package can be obtained from [here](https://www.nuget.org/packages/Azure.Communication.CallAutomation/), if you haven't already done so. 
+Get the NuGet package from [NuGet Gallery | Azure.Communication.CallAutomation](https://www.nuget.org/packages/Azure.Communication.CallAutomation/). Follow the instructions to install the package.
 
 ## Establish a call
 
-By this point you should be familiar with starting calls, if you need to learn more about making a call, follow our [quickstart](../../../quickstarts/call-automation/quickstart-make-an-outbound-call.md). You can also use the code snippet provided here to understand how to answer a call.
+By this point you should be familiar with starting calls. For more information about making a call, see [Quickstart: Make and outbound call](../../../quickstarts/call-automation/quickstart-make-an-outbound-call.md). You can also use the code snippet provided here to understand how to answer a call.
 
 ``` csharp
 var callAutomationClient = new CallAutomationClient("<Azure Communication Services connection string>");
@@ -99,7 +99,7 @@ var recognizeResult = await callAutomationClient.GetCallConnection(callConnectio
   .StartRecognizingAsync(recognizeOptions);
 ```
 
-For speech-to-text flows, Call Automation Recognize action also supports the use of [custom speech models](/azure/machine-learning/tutorial-train-model.md?view=azureml-api-2). Features like custom speech models can be useful when you're building an application that needs to listen for complex words that the default speech-to-text models may not understand. One example is when you're building an application for the telemedical industry and your virtual agent needs to be able to recognize medical terms. You can learn more in [Create a custom speech project](../../../../ai-services/speech-service/how-to-custom-speech-create-project.md).
+For speech-to-text flows, the Call Automation Recognize action also supports the use of [custom speech models](/azure/machine-learning/tutorial-train-model). Features like custom speech models can be useful when you're building an application that needs to listen for complex words that the default speech-to-text models may not understand. One example is when you're building an application for the telemedical industry and your virtual agent needs to be able to recognize medical terms. You can learn more in [Create a custom speech project](/azure/ai-services/speech-service/speech-services-quotas-and-limits).
 
 ### Speech-to-Text Choices 
 ``` csharp
@@ -177,7 +177,7 @@ var recognizeResult = await callAutomationClient.GetCallConnection(callConnectio
 
 ## Receiving recognize event updates
 
-Developers can subscribe to the *RecognizeCompleted* and *RecognizeFailed* events on the webhook callback they registered for the call to create business logic in their application for determining next steps when one of the previously mentioned events occurs. 
+Developers can subscribe to `RecognizeCompleted` and `RecognizeFailed` events on the registered webhook callback. Use this callback with business logic in your application to determine next steps when one of the events occurs. 
 
 ### Example of how you can deserialize the *RecognizeCompleted* event:
 ``` csharp