Edits

Ran Acrolinx and edited.

Author: vac0224

articles/communication-services/quickstarts/voice-video-calling/includes/call-recording-samples/call-recording-csharp.md

@@ -23,8 +23,10 @@ Call Recording APIs use exclusively the `serverCallId`to initiate recording. The
 ### Call Automation scenarios
 
 When using [Call Automation](../../../call-automation/callflows-for-customer-interactions.md), you have two options to get the `serverCallId`:
-    1) Once a call is created, it returns a `serverCallId` as a property of the `CallConnected` event after a call is established. Learn how to [Get CallConnected event](../../../call-automation/callflows-for-customer-interactions.md?pivots=programming-language-csharp#update-programcs) from Call Automation SDK.
-    2) Once you answer the call or a call is created, it returns the `serverCallId` as a property of the `AnswerCallResult` or `CreateCallResult` API responses respectively.
+
+1. When you establish a call, it returns a `serverCallId` as a property of the `CallConnected` event after a call is established. Learn how to [Get CallConnected event](../../../call-automation/callflows-for-customer-interactions.md?pivots=programming-language-csharp#update-programcs) from Call Automation SDK.
+
+2. When you answer the call or a call is created, it returns the `serverCallId` as a property of the `AnswerCallResult` or `CreateCallResult` API responses respectively.
 
 ### Calling SDK scenarios
 
@@ -46,9 +48,9 @@ CallAutomationClient callAutomationClient = new CallAutomationClient("<ACSConnec
 ## 2. Start recording session with StartRecordingOptions using 'StartAsync' API
 
 Use the `serverCallId` received during initiation of the call.
-- RecordingContent is used to pass the recording content type. Use audio
-- RecordingChannel is used to pass the recording channel type. Use mixed or unmixed.
-- RecordingFormat is used to pass the format of the recording. Use wav.
+- Use `RecordingContent` to pass the recording content type. Use `audio`.
+- Use `RecordingChannel` to pass the recording channel type. Use `mixed` or `unmixed`.
+- Use `RecordingFormat` to pass the format of the recording. Use `wav`.
 
 ```csharp
 StartRecordingOptions recordingOptions = new StartRecordingOptions(new ServerCallLocator("<ServerCallId>")) 
@@ -62,7 +64,8 @@ Response<RecordingStateResult> response = await callAutomationClient.GetCallReco
 .StartAsync(recordingOptions);
 ```
 ### 2.1. Start Recording  - Bring Your Own Azure Blob Store
-Start Recording with your own Azure Blob Storage defined to store the recording file once recording is complete.
+
+To store the recording file when recording is complete, start recording with your own Azure Blob Storage defined.
 
 ```csharp
 StartRecordingOptions recordingOptions = new StartRecordingOptions(new ServerCallLocator("<ServerCallId>"))
@@ -123,35 +126,36 @@ StartRecordingOptions recordingOptions = new StartRecordingOptions(new ServerCal
 };
 Response<RecordingStateResult> response = await callAutomationClient.GetCallRecording().StartAsync(recordingOptions);
 ```
+
 The `StartAsync` API response contains the `recordingId` of the recording session.
 
-## 3.	Stop recording session using 'StopAsync' API
+## 3. Stop recording session using `StopAsync` API
 
 Use the `recordingId` received in response of `StartAsync`.
 
 ```csharp
 var stopRecording = await callAutomationClient.GetCallRecording().StopAsync(recordingId);
 ```
 
-## 4.	Pause recording session using 'PauseAsync' API
+## 4. Pause recording session using `PauseAsync` API
 
 Use the `recordingId` received in response of `StartAsync`.
 
 ```csharp
 var pauseRecording = await callAutomationClient.GetCallRecording ().PauseAsync(recordingId);
 ```
 
-## 5.	Resume recording session using 'ResumeAsync' API
+## 5. Resume recording session using `ResumeAsync` API
 
 Use the `recordingId` received in response of `StartAsync`.
 
 ```csharp
 var resumeRecording = await callAutomationClient.GetCallRecording().ResumeAsync(recordingId);
 ```
 
-## 6.	Download recording File using 'DownloadToAsync' API
+## 6.	Download recording File using `DownloadToAsync` API
 
-Use an [Azure Event Grid](../../../../../event-grid/event-schema-communication-services.md) web hook or other triggered action should be used to notify your services when the recorded media is ready for download.
+Use an [Azure Event Grid](../../../../../event-grid/event-schema-communication-services.md) web hook or other triggered action to notify your services when the recorded media is ready for download.
 
 An Event Grid notification `Microsoft.Communication.RecordingFileStatusUpdated` is published when a recording is ready for retrieval, typically a few minutes after the recording finishes processing (such as when meeting ends or a recording stops). Recording event notifications include `contentLocation` and `metadataLocation`, which you can use to retrieve both recorded media and a recording metadata file.
 
@@ -186,17 +190,18 @@ Example of the event schema:
 }
 ```
 
-Use `DownloadToAsync` API for downloading the recorded media.
+Use `DownloadToAsync` API to download the recorded media.
 
 ```csharp
 var recordingDownloadUri = new Uri(contentLocation);
 var response = await callAutomationClient.GetCallRecording().DownloadToAsync(recordingDownloadUri, fileName);
 ```
-The `downloadLocation` for the recording can be fetched from the `contentLocation` attribute of the `recordingChunk`. `DownloadToAsync` method downloads the content into provided filename.
 
-## 7. Delete recording content using 'DeleteAsync' API
+Fetch the `downloadLocation` for the recording from the `contentLocation` attribute of the `recordingChunk`. `DownloadToAsync` method downloads the content into provided filename.
+
+## 7. Delete recording content using `DeleteAsync` API
 
-Use `DeleteAsync` API for deleting the recording content (for example, recorded media, metadata)
+Use `DeleteAsync` API to delete the recording content (such as recorded media and metadata)
 
 ```csharp
 var recordingDeleteUri = new Uri(deleteLocation);

articles/communication-services/quickstarts/voice-video-calling/includes/call-recording-samples/call-recording-java.md

@@ -24,8 +24,10 @@ Call Recording APIs exclusively use the `serverCallId` to initiate recording. Th
 ### Call Automation scenarios
 
 When using [Call Automation](../../../call-automation/callflows-for-customer-interactions.md), you have two options to get the `serverCallId`:
-    1) Once a call is created, a `serverCallId` is returned as a property of the `CallConnected` event after a call has been established. Learn how to [Get CallConnected event](../../../call-automation/callflows-for-customer-interactions.md?pivots=programming-language-java#update-programcs) from Call Automation SDK.
-    2) Once you answer the call or a call is created the `serverCallId` is returned as a property of the `AnswerCallResult` or `CreateCallResult` API responses respectively.
+
+1. Once a call is created, a `serverCallId` is returned as a property of the `CallConnected` event after a call is established. Learn how to [Get CallConnected event](../../../call-automation/callflows-for-customer-interactions.md?pivots=programming-language-java#update-programcs) from Call Automation SDK.
+
+2.  Once you answer the call or a call is created the `serverCallId` is returned as a property of the `AnswerCallResult` or `CreateCallResult` API responses respectively.
 
 ### Calling SDK scenarios
 
@@ -37,21 +39,22 @@ Let's get started with a few simple steps.
 
 ## 1. Create a Call Automation client
 
-Call Recording APIs are part of the Azure Communication Services [Call Automation](../../../../concepts/call-automation/call-automation.md) libraries. Thus, it's necessary to create a Call Automation client. 
-To create a call automation client, you'll use your Communication Services connection string and pass it to `CallAutomationClient` object.
+Call Recording APIs are part of the Azure Communication Services [Call Automation](../../../../concepts/call-automation/call-automation.md) libraries. So you need to create a Call Automation client.
+
+To create a call automation client, use your Communication Services connection string and pass it to `CallAutomationClient` object.
 
 ```java
 CallAutomationClient callAutomationClient = new CallAutomationClientBuilder()
             .connectionString("<acsConnectionString>")
             .buildClient();
 ```
 
-## 2. Start recording session with StartRecordingOptions using 'startWithResponse' API
+## 2. Start recording session with StartRecordingOptions using `startWithResponse` API
 
 Use the `serverCallId` received during initiation of the call.
-- RecordingContent is used to pass the recording content type. Use AUDIO
-- RecordingChannel is used to pass the recording channel type. Use MIXED or UNMIXED.
-- RecordingFormat is used to pass the format of the recording. Use WAV.
+- Use `RecordingContent` to pass the recording content type. Use `AUDIO`.
+- Use `RecordingChannel` to pass the recording channel type. Use `MIXED` or `UNMIXED`.
+- Use `RecordingFormat` to pass the format of the recording. Use `WAV`.
 
 ```java
 StartRecordingOptions recordingOptions = new StartRecordingOptions(new ServerCallLocator("<serverCallId>"))
@@ -66,7 +69,8 @@ Response<RecordingStateResult> response = callAutomationClient.getCallRecording(
 ```
 
 ### 2.1. Start Recording  - Bring Your Own Azure Blob Store
-Start Recording session with your own Azure Blob Storage to store the recording file once recording is complete.
+
+To store the recording file when recording is complete, start the recording session with your own Azure Blob Storage.
 
 ```java
         StartRecordingOptions recordingOptions = new StartRecordingOptions(callLocator)
@@ -80,9 +84,11 @@ Start Recording session with your own Azure Blob Storage to store the recording
        RecordingStateResult result = callRecording.start(recordingOptions);
 ```
 
-### 2.2. Start recording session with Pause mode enabled using 'StartAsync' API
+### 2.2. Start recording session with Pause mode enabled using `StartAsync` API
+
 > [!NOTE]
-> **Recordings will need to be resumed for recording file to be generated.**
+> **Recordings must be resumed for recording file to be generated.**
+
 ```java
 StartRecordingOptions recordingOptions = new StartRecordingOptions(new ServerCallLocator("<serverCallId>"))
                     .setRecordingChannel(RecordingChannel.UNMIXED)
@@ -98,7 +104,8 @@ Response<RecordingStateResult> response = callAutomationClient.getCallRecording(
 ```
 
 ### 2.3. Only for Unmixed - Specify a user on channel 0
-To produce unmixed audio recording files, you can use the `AudioChannelParticipantOrdering` functionality to specify which user you want to record on channel 0. The rest of the participants will be assigned to a channel as they speak. If you use `RecordingChannel.Unmixed` but don't use `AudioChannelParticipantOrdering`, Call Recording will assign channel 0 to the first participant speaking. 
+
+To produce unmixed audio recording files, you can use the `AudioChannelParticipantOrdering` functionality to specify which user you want to record on channel 0. The rest of the participants are assigned to a channel as they speak. If you use `RecordingChannel.Unmixed` but don't use `AudioChannelParticipantOrdering`, Call Recording assigns channel 0 to the first participant speaking. 
 
 ```java
 StartRecordingOptions recordingOptions = new StartRecordingOptions(new ServerCallLocator("<serverCallId>"))
@@ -114,6 +121,7 @@ Response<RecordingStateResult> response = callAutomationClient.getCallRecording(
 ```
 
 ### 2.4. Only for Unmixed - Specify channel affinity
+
 ```java
 ChannelAffinity channelAffinity = new ChannelAffinity()
 .setParticipant(new PhoneNumberIdentifier("RECORDING_ID"))
@@ -131,39 +139,40 @@ Response<RecordingStateResult> response = callAutomationClient.getCallRecording(
 ```
 The `startWithResponse` API response contains the `recordingId` of the recording session.
 
-## 3.	Stop recording session using 'stopWithResponse' API
+## 3. Stop recording session using `stopWithResponse` API
 
-Use the `recordingId` received in response of `startWithResponse`.
+Use the `recordingId` received in response to `startWithResponse`.
 
 ```java
 Response<Void> response = callAutomationClient.getCallRecording()
                .stopWithResponse(response.getValue().getRecordingId(), null);
 ```
 
-## 4.	Pause recording session using 'pauseWithResponse' API
+## 4. Pause recording session using `pauseWithResponse` API
+
+Use the `recordingId` received in response to `startWithResponse`.
 
-Use the `recordingId` received in response of `startWithResponse`.
 ```java
 Response<Void> response = callAutomationClient.getCallRecording()
               .pauseWithResponse(response.getValue().getRecordingId(), null);
 ```
 
-## 5.	Resume recording session using 'resumeWithResponse' API
+## 5. Resume recording session using `resumeWithResponse` API
 
-Use the `recordingId` received in response of `startWithResponse`.
+Use the `recordingId` received in response to `startWithResponse`.
 
 ```java
 Response<Void> response = callAutomationClient.getCallRecording()
                .resumeWithResponse(response.getValue().getRecordingId(), null);
 ```
 
-## 6.	Download recording File using 'downloadToWithResponse' API
+## 6. Download recording File using `downloadToWithResponse` API
 
 Use an [Azure Event Grid](../../../../../event-grid/event-schema-communication-services.md) web hook or other triggered action should be used to notify your services when the recorded media is ready for download.
 
-An Event Grid notification `Microsoft.Communication.RecordingFileStatusUpdated` is published when a recording is ready for retrieval, typically a few minutes after the recording process has completed (for example, meeting ended, recording stopped). Recording event notifications include `contentLocation` and `metadataLocation`, which are used to retrieve both recorded media and a recording metadata file.
+An Event Grid notification `Microsoft.Communication.RecordingFileStatusUpdated` is published when a recording is ready for retrieval, typically a few minutes after the recording process completes (such as meeting ends or recording stops). Recording event notifications include `contentLocation` and `metadataLocation`, which you can use to retrieve both recorded media and a recording metadata file.
 
-Below is an example of the event schema.
+The following code is an example of the event schema.
 
 ```
 {
@@ -197,7 +206,7 @@ Below is an example of the event schema.
 Use `downloadToWithResponse` method of `CallRecording` class for downloading the recorded media. Following are the supported parameters for `downloadToWithResponse` method:
 - `contentLocation`: Azure Communication Services URL where the content is located.
 - `destinationPath` : File location.
-- `parallelDownloadOptions`: An optional ParallelDownloadOptions object to modify how the - parallel download will work.
+- `parallelDownloadOptions`: An optional `ParallelDownloadOptions` object to modify how the parallel download works.
 - `overwrite`: True to overwrite the file if it exists.
 - `context`: A Context representing the request context.
 
@@ -212,15 +221,17 @@ Path destinationPath = Paths.get(filePath);
 
 Response<Void> downloadResponse = callAutomationClient.getCallRecording().downloadToWithResponse(contentLocation, destinationPath, parallelDownloadOptions, overwrite, context);
 ```
+
 The content location and document IDs for the recording files can be fetched from the `contentLocation` and `documentId` fields respectively, for each `recordingChunk`.
 
-## 7. Delete recording content using ‘deleteWithResponse’ API.
+## 7. Delete recording content using `deleteWithResponse` API
 
-Use `deleteWithResponse` method of `CallRecording` class for deleting the recorded media. Following are the supported parameters for `deleteWithResponse` method:
+Use `deleteWithResponse` method of `CallRecording` class to delete the recorded media. Supported parameters for `deleteWithResponse` method:
 - `deleteLocation`: Azure Communication Services URL where the content to delete is located.
 - `context`: A Context representing the request context.
 
 ```
 Response<Void> deleteResponse = callAutomationClient.getCallRecording().deleteWithResponse(deleteLocation, context);
 ```
-The delete location for the recording can be fetched from the `deleteLocation` field of the Event Grid event.
+
+The delete location for the recording can be fetched from the `deleteLocation` field of the Event Grid event.