Fixed "Pre-Call" to "pre-call" unless starting a sentence

vac0224 · vac0224 · commit f6db75bb113f · 2024-11-11T14:49:58.000-06:00
Per editor, "pre-call" is not a branded term. Also referred to pre-call as a feature as it is in the reference articles, and fixed some link text.
diff --git a/articles/communication-services/concepts/voice-video-calling/includes/media-stats/media-stats-web.md b/articles/communication-services/concepts/voice-video-calling/includes/media-stats/media-stats-web.md
@@ -80,7 +80,7 @@ If you set the following values:
 - `aggregatinInterval` = 60
 - `dataPointsPerAggregation` = 1
 
-The `summaryReported` event is raised every 60 seconds and contains 1 unique unit for each statistic recorded.
+The `summaryReported` event is raised every 60 seconds and contains one (1) unique unit for each statistic recorded.
 
 ## Best practices
 
@@ -232,6 +232,7 @@ In earlier versions, `rttInMs` existed as `pairRttInMs` in the stats for audio,
 ## What are changed in SDK version 1.20.1 (GA)
 
 We now support MediaStats feature API in 1.20.1 (GA).
+
 Compared to the previous beta versions, we also made some minor changes to the API interface in this GA version.
 
 In the previous beta versions, `pairRttInMs`, `availableBitrate` were included in audio, video, and screenShare statistics. Now these metrics are separated into transport metrics.
@@ -240,4 +241,4 @@ We introduced `packets` and `packetsLost` metric fields in audio, video, screenS
 
 The `frameRateOutput` in video and screenShare statistics is removed. You can use `frameRateDecoded` instead.
 
-The metric field `jitterBufferInMs` has been renamed to `jitterBufferDelayInMs` to provide a clearer description, because this metric indicates the duration of a packet stay in the jitter buffer.
+The metric field `jitterBufferInMs` is renamed to `jitterBufferDelayInMs` to provide a clearer description, because this metric indicates the duration of a packet stay in the jitter buffer.
diff --git a/articles/communication-services/concepts/voice-video-calling/pre-call-diagnostics.md b/articles/communication-services/concepts/voice-video-calling/pre-call-diagnostics.md
@@ -1,7 +1,7 @@
 ---
-title: Azure Communication Services Pre-Call diagnostics
+title: Azure Communication Services pre-call diagnostics
 titleSuffix: An Azure Communication Services concept document
-description: Overview of Pre-Call Diagnostic APIs
+description: Overview of the pre-call diagnostic API feature.
 author: tophpalmer
 manager: chpalm
 services: azure-communication-services
@@ -11,11 +11,11 @@ ms.topic: conceptual
 ms.service: azure-communication-services
 ---
 
-# Pre-Call diagnostic
+# Pre-call diagnostic
 
 [!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include.md)]
 
-The Pre-Call API enables developers to programmatically validate a client’s readiness to join an Azure Communication Services Call. You can only access Pre-Call APIs through the Calling SDK. They provide multiple diagnostics including device, connection, and call quality. Pre-Call APIs are available only for Web (JavaScript). We'll be enabling these capabilities across platforms in the future. Provide us with [feedback](../../support.md) on which platforms you want to see Pre-Call APIs enabled.
+The pre-call API feature enables developers to programmatically validate a client’s readiness to join an Azure Communication Services call. You can only access pre-call features using the Calling SDK. The pre-call diagnostic feature provides multiple diagnostics including device, connection, and call quality. The pre-call diagnotic feature is available only for Web (JavaScript). We plan to enable these capabilities across platforms in the future. Provide us with [feedback](../../support.md) about which platforms you want to see pre-call diagnostics enabled.
 
 ## Prerequisites
 
@@ -30,12 +30,12 @@ The Pre-Call API enables developers to programmatically validate a client’s re
 
   For more information, see [Use Azure CLI to Create and Manage Access Tokens](../../quickstarts/identity/access-tokens.md?pivots=platform-azcli).
 
-## Accessing Pre-Call APIs
+## Accessing pre-call diagnostics
 
 >[!IMPORTANT]
->Pre-call diagnostics are available starting on the version [1.9.1-beta.1](https://www.npmjs.com/package/@azure/communication-calling/v/1.9.1-beta.1) of the Calling SDK. Make sure to use that version when following these instructions.
+>Pre-call diagnostics are available starting with version [1.9.1-beta.1](https://www.npmjs.com/package/@azure/communication-calling/v/1.9.1-beta.1) of the Calling SDK. Make sure to use that version or higher when following these instructions.
 
-To Access the Pre-Call API, you need to initialize a `callClient`, and provision an Azure Communication Services access token. There you can access the `PreCallDiagnostics` feature and the `startTest` method.
+To Access pre-call diagnostics, you need to initialize a `callClient`, and provision an Azure Communication Services access token. There you can access the `PreCallDiagnostics` feature and the `startTest` method.
 
 ```javascript
 import { CallClient, Features} from "@azure/communication-calling";
@@ -51,7 +51,7 @@ Once it finishes running, developers can access the result object.
 
 ## Diagnostic results
 
-The Pre-Call API returns a full diagnostic of the device including details like device permissions, availability and compatibility, call quality stats and in-call diagnostics. The results are returned as a `PreCallDiagnosticsResult` object. 
+Pre-call diagnostics returns a full diagnostic of the device including details like device permissions, availability and compatibility, call quality statistics, and in-call diagnostics. The results are returned as a `PreCallDiagnosticsResult` object. 
 
 ```javascript
 
@@ -66,11 +66,11 @@ export declare type PreCallDiagnosticsResult  = {
 
 ```
 
-Individual result objects can be accessed as such using the `preCallDiagnosticsResult` constant. Results for individual tests be returned as they're completed with many of the test results being available immediately. If you use the `inCallDiagnostics` test, the results might take up to 1 minute as the test validates quality of the video and audio.
+You can access individual result objects using the `preCallDiagnosticsResult` type. Results for individual tests are returned as they're completed with many of the test results being available immediately. If you use the `inCallDiagnostics` test, the results might take up to 1 minute as the test validates the quality of the video and audio.
 
 ### Browser support
 
-Browser compatibility check. Checks for `Browser` and `OS` compatibility and provides a `Supported` or `NotSupported` value back. 
+Browser compatibility check. Checks for `Browser` and `OS` compatibility and returns a `Supported` or `NotSupported` value. 
 
 ```javascript
 
@@ -82,14 +82,14 @@ const browserSupport =  await preCallDiagnosticsResult.browserSupport;
 
 ```
 
-In the case that the test fails and the browser being used by the user is `NotSupported`, the easiest way to fix that is by asking the user to switch to a supported browser. Refer to the supported browsers in our [documentation](./calling-sdk-features.md#javascript-calling-sdk-support-by-os-and-browser).
+If the test fails and the browser being used by the user is `NotSupported`, the easiest way to fix that is by asking the user to switch to a supported browser. Refer to the supported browsers in [Calling SDK overview > JavaScript Calling SDK support by OS and browser](./calling-sdk-features.md#javascript-calling-sdk-support-by-os-and-browser).
 
 >[!NOTE]
 >Known issue: `browser support` test returning `Unknown` in cases where it should be returning a correct value.
 
 ### Device access
 
-Permission check. Checks whether video and audio devices are available from a permissions perspective. Provides `boolean` value for `audio` and `video` devices. 
+The permission check determines whether video and audio devices are available from a permissions perspective. Provides `boolean` value for `audio` and `video` devices. 
 
 ```javascript
 
@@ -101,11 +101,11 @@ Permission check. Checks whether video and audio devices are available from a pe
 
 ```
 
-In the case that the test fails and the permissions are false for audio and video, the user shouldn't continue into joining a call. Rather you need to prompt the user to enable the permissions. To do it, the best way is provided the specific instruction on how to access permission access based on the OS, version, and browser they are on. For more information on permissions, check out our [recommendations](https://techcommunity.microsoft.com/t5/azure-communication-services/checklist-for-advanced-calling-experiences-in-mobile-web/ba-p/3266312).
+If the test fails and the permissions are false for audio and video, the user shouldn't continue into joining a call. Rather, prompt the user to enable the permissions. The best way to do this is by providing the specific instruction on how to access permissions based on the OS, version, and browser they're using. For more information about permissions, see the [Checklist for advanced calling experiences in web browsers](https://techcommunity.microsoft.com/t5/azure-communication-services/checklist-for-advanced-calling-experiences-in-mobile-web/ba-p/3266312).
 
 ### Device enumeration
 
-Device availability. Checks whether microphone, camera, and speaker devices are detected in the system and ready to use. Provides an `Available` or `NotAvailable` value back.
+Device availability. Checks whether microphone, camera, and speaker devices are detected in the system and ready to use. Returns an `Available` or `NotAvailable` value.
 
 ```javascript
 
@@ -118,13 +118,15 @@ Device availability. Checks whether microphone, camera, and speaker devices are
 
 ```
 
-In the case that devices aren't available, the user shouldn't continue into joining a call. Rather the user should be prompted to check device connections to ensure any headsets, cameras or speakers are properly connected. For more information on device management, check out our [documentation](../../how-tos/calling-sdk/manage-video.md?pivots=platform-web#device-management)
+If devices aren't available, the user shouldn't continue into joining a call. Rather, prompt the user to check device connections to ensure any headsets, cameras, or speakers are properly connected. For more information about device management, see [Manage video during calls](../../how-tos/calling-sdk/manage-video.md?pivots=platform-web#device-management).
 
 ### InCall diagnostics
 
-Performs a quick call to check in-call metrics for audio and video and provides results back. Includes connectivity (`connected`, boolean), bandwidth quality (`bandWidth`, `'Bad' | 'Average' | 'Good'`) and call diagnostics for audio and video (`diagnostics`). Diagnostic are provided `jitter`, `packetLoss`, and `rtt` and results are generated using a simple quality grade (`'Bad' | 'Average' | 'Good'`).
+Performs a quick call to check in-call metrics for audio and video and provides results back. Includes connectivity (`connected`, boolean), bandwidth quality (`bandWidth`, `'Bad' | 'Average' | 'Good'`) and call diagnostics for audio and video (`diagnostics`). Provided diagnostic categories include `jitter`, `packetLoss`, and `rtt` and results are generated using a simple quality grade (`'Bad' | 'Average' | 'Good'`).
 
-InCall diagnostics uses [media quality stats](./media-quality-sdk.md) to calculate quality scores and diagnose issues. During the pre-call diagnostic, the full set of media quality stats are available for consumption. These stats include raw values across video and audio metrics that can be used programatically. The InCall diagnostic provides a convenience layer on top of media quality stats to consume the results without the need to process all the raw data. See section on media stats for instructions to access.
+InCall diagnostics uses [Media quality statistics](./media-quality-sdk.md) to calculate quality scores and diagnose issues. During the pre-call diagnostic, the full set of media quality statistics are available for consumption. These statistics include raw values across video and audio metrics that you can use programatically.
+
+The InCall diagnostic provides a convenience layer on top of media quality statistics to consume the results without the need to process all the raw data. For more information including instructions to access, see [Media quality statistics for an ongoing call](./media-quality-sdk.md#media-quality-statistics-for-an-ongoing-call).
 
 
 ```javascript
@@ -139,53 +141,10 @@ InCall diagnostics uses [media quality stats](./media-quality-sdk.md) to calcula
 
 ```
 
-At this step, there are multiple failure points to watch out for. The values provided by the API are based on the threshold values required by the service. Those raw thresholds can be found in our [media quality stats documentation](./media-quality-sdk.md#best-practices).
-
-- If connection fails, the user should be prompted to recheck their network connectivity. Connection failures can also be attributed to network conditions like DNS, proxies, or firewalls. For more information on recommended network setting, check out our [documentation](network-requirements.md).
-- If bandwidth is `Bad`, the user should be prompted to try out a different network or verify the bandwidth availability on their current one. Ensure no other high bandwidth activities might be taking place.
-
-### Media stats
-
-For granular stats on quality metrics like jitter, packet loss, rtt, and so on. We provide `callMediaStatistics` as part of the `preCallDiagnosticsResult` feature. For the full list and descriptions of available metrics, see [Media quality statistics](./media-quality-sdk.md). You can subscribe to the call media stats to get the full collection. This stat is the raw metrics used to calculate InCall diagnostic results which can be consumed granularly for further analysis.
-
-Media quality statistics is an extended feature of the core `Call` API. You first need to obtain the `mediaStatsFeature` API object:
-
-```js
-const mediaStatsFeature = call.feature(Features.MediaStats);
-```
-
-To receive the media statistics data, you can subscribe to the `sampleReported` event or the `summaryReported` event.
-
-The `sampleReported` event triggers every second. It's suitable as a data source for UI display or your own data pipeline.
-
-The `summaryReported` event contains the aggregated values of the data over intervals, which is useful when you just need a summary.
-
-If you want control over the interval of the `summaryReported` event, you need to define `mediaStatsCollectorOptions` of type `MediaStatsCollectorOptions`. Otherwise, the SDK uses default values.
-
-```js
-const mediaStatsCollectorOptions: SDK.MediaStatsCollectorOptions = {
-    aggregationInterval: 10,
-    dataPointsPerAggregation: 6
-};
-
-const mediaStatsCollector = mediaStatsFeature.createCollector(mediaStatsSubscriptionOptions);
-
-mediaStatsCollector.on('sampleReported', (sample) => {
-    console.log('media stats sample', sample);
-});
-
-mediaStatsCollector.on('summaryReported', (summary) => {
-    console.log('media stats summary', summary);
-});
-```
-
-If you don't need to use the media statistics collector, you can call `dispose` method of `mediaStatsCollector`.
-
-```js
-mediaStatsCollector.dispose();
-```
+At this step, there are multiple possible failure points. The values provided by the API are based on the threshold values required by the service. The raw thresholds can be found in [Media quality statistics](./media-quality-sdk.md#best-practices).
 
-You don't need to call `dispose` method of `mediaStatsCollector` every time when the call ends, because the collectors are reclaimed internally when the call ends.
+- If a connection fails, prompt users to recheck their network connectivity. Connection failures can also be attributed to network conditions like DNS, proxies, or firewalls. For more information on recommended network setting, see [Network recommendations](network-requirements.md).
+- If bandwidth is `Bad`, prompt users to try a different network or verify the bandwidth availability on their current network. Ensure no other high bandwidth activities are taking place.
 
 ## Pricing
 
