Update voice-and-video-insights.md

Author: amagginetti

articles/communication-services/concepts/analytics/insights/voice-and-video-insights.md

@@ -36,9 +36,9 @@ We recommend using Copilot in the **Voice and Video Insights** dashboards to sta
 any quality investigations, and use Copilot in [Call Diagnostics](../../voice-video-calling/call-diagnostics.md) as needed to explore individual calls when you need granular detail. 
 
 **Voice and Video Insights** consists of four main sections. 
-- **[Volume](#volume):** Provides general statistics.
-- **[Reliability](#reliability):** Aggregates all API functionality and error codes to focus your analysis.
-- **[User Facing Diagnostics (UFD)](#user-facing-diagnostics-ufd):** Highlights trends that can impact users call experiences.
+- **[Volume](#volume):** Provides general usage numbers.
+- **[Reliability](#reliability):** Aggregates all API functionality and error codes.
+- **[User Facing Diagnostics (UFD)](#user-facing-diagnostics-ufd):** Summarizes events that can affect user call experiences.
 - **[Quality](#quality):** Provides key media stream measurements.
 
 
@@ -76,24 +76,24 @@ The **Volume** tab contains a **Grouping** parameter, which helps visualize the
 :::image type="content" source="..\media\workbooks\voice-and-video-volume-grouping.png" alt-text="Screenshot of voice and video volume grouping."::: -->
 
 ## Reliability
-The **Reliability** tab summarizes the performance of key calling SDK APIs to help you focus on the lowest performing areas. The default view shows a trend of all the APIs. You need to select a single API scenario to focus on then the dashboard visuals will change and show you a detailed breakdown of that API. You can then ask Copilot for help understanding individual error codes and possible solutions to improve performance. 
+The **Reliability** tab summarizes the performance of key calling SDK APIs to help you focus on the lowest performing areas. The default view shows a trend of all the APIs to give you an overview of your reliability. You can get more details by selecting a single API scenario to focus on. When you choose a single API scenario the dashboard visuals update to show a detailed breakdown of that API and highlight where you can chat with Copilot to learn about individual error codes and possible solutions to improve performance. 
 
 ## User Facing Diagnostics (UFD)
 
-The User Facing Diagnostic (UFD) tab opens with a summary of the top UFD events and highlights the recovery rate of each UFD for you to focus on. Like the Reliability tab, you’ll see an overview of all the UFDs first. Then you can interact with Copilot and select an individual UFD for further drill-down insights. 
+The User Facing Diagnostic (UFD) tab opens with a summary of the top UFD events and highlights the recovery rate of each UFD for you to focus on. Like the Reliability tab, you see an overview of all the UFDs first. Then you can interact with Copilot and select an individual UFD for further drill-down insights. 
 
-We recommend prioritizing improvements on a UFD that has a low recovery rate and a high volume, which can indicate the best opportunity to improve your user's call experiences. For example, the calling SDK will try to re-attempt or mitigate some in call events, finding the poorest performing areas can help identify root causes. 
+We recommend prioritizing improvements on a UFD that has a low recovery rate and a high volume, which can indicate the best opportunity to improve your user's call experiences. For example, the calling SDK might recover from some in call events and the user might not perceive an issue. By focusing on the poorest performing areas you can help identify root causes. 
 
 ### How do you interpret UFDs?
 
-During calls, the calling SDK may trigger events called User Facing Diagnostics (UFDs), these UFD events can indicate a user had a poor call experience for various reasons. For example, their video freezes and their network quality drops in the middle of a call. Since UFDs are symptomatic by nature and are triggered based on broader quantitative criteria, there can be various root causes that trigger a UFD event. Additionally, a UFD can be triggered but the user may not have perceived an issue during a call. In contrast the reliability tab attempts to provide more concrete error code and subcode information for your analysis. 
+During calls, the calling SDK might trigger events called User Facing Diagnostics (UFDs), these UFD events indicate a user may have perceived a poor call experience for various reasons. For example, their video freezes and their network quality drops in the middle of a call. Since UFDs are symptomatic by nature and are triggered based on broad quantitative criteria, there can be various root causes that trigger a UFD event. Additionally, a UFD can be triggered but the user might not perceive an issue during a call because the calling SDK was able to mitigate any potential issue. In contrast, the reliability tab attempts to provide more concrete error code and subcode information for your analysis. 
 
 
 ## Quality
 
 The **Quality** tab under **Voice and video** allows users to inspect the quality distribution of calls, where quality is defined at three levels for this dashboard:
 
-- The proportion of poor-quality media streams (**Stream quality** plot), where a stream’s quality is classified as Poor when it has at least one unhealthy telemetry value, where unhealthy ranges are defined as:
+- The proportion of poor-quality media streams (**Stream quality** plot), where a stream’s quality is classified as Poor when it has at least one unhealthy value, unhealthy ranges are defined as:
   - Jitter > 30 milliseconds
   - Packet loss rate > 10%
   - Round trip time > 500 milliseconds
@@ -104,11 +104,11 @@ The **Quality** tab under **Voice and video** allows users to inspect the qualit
 
 <!-- :::image type="content" source="..\media\workbooks\voice-and-video-quality.png" alt-text="Screenshot of voice and video quality."::: -->
 
-Quality can also be filtered by the types of media streams (**Media Type** parameter) used in the call, e.g. to only get the impacted calls in terms of video stream quality:
+Quality can also be filtered by the types of media streams (**Media Type** parameter) used in the call, for example, to only get the impacted calls in terms of video stream quality:
 
 <!-- :::image type="content" source="..\media\workbooks\voice-and-video-quality-params.png" alt-text="Screenshot voice and video quality media type parameter."::: -->
 
-And can also be filtered by endpoint types (**Endpoint Type** parameter), e.g. getting the participant end reasons for PSTN participants. These filters allow for multiple selections:
+And can also be filtered by endpoint types (**Endpoint Type** parameter), for example, getting the participant end reasons for PSTN participants. These filters allow for multiple selections:
 
 <!-- :::image type="content" source="..\media\workbooks\voice-and-video-params-2.png" alt-text="Screenshot voice and video quality endpoint type parameter."::: -->
 
@@ -132,19 +132,19 @@ For an in-depth description of workbooks, refer to the [Azure Monitor Workbooks]
 ## Frequently asked questions
 
 ### How do I set up Voice and Video Insights?
-Since the Voice and Video insights dashboard is integrated with [Copilot in Azure](/azure/copilot/overview) and powered by [Azure Monitor Workbooks](/azure/azure-monitor/visualize/workbooks-overview) you need to store call logs for it to visualize and confirm you've enabled [Copilot in Azure](/azure/copilot/overview). The following sections explain these two requirements.
+Since the Voice and Video insights dashboard is integrated with [Copilot in Azure](/azure/copilot/overview) and powered by [Azure Monitor Workbooks](/azure/azure-monitor/visualize/workbooks-overview), you need to store call logs for it to visualize anything. Also you must enable [Copilot in Azure](/azure/copilot/overview). The following sections explain these two requirements.
 
 #### Collect Call Logs
 
-The Insights Dashboards uses [Azure Monitor Workbooks](/azure/azure-monitor/visualize/workbooks-overview) which displays call log data from Azure Communication Services. These call logs aren't stored in your Azure account by default so you need to begin storing them for the dashboard to work. To collect these call logs you need to enable a diagnostic setting that sends call data to a Log Analytics workspace in the same resource group as your calling resource. 
+The Insights Dashboards uses [Azure Monitor Workbooks](/azure/azure-monitor/visualize/workbooks-overview) which displays call log data from Azure Communication Services. These call logs aren't stored in your Azure account by default so you need to begin storing them for the dashboard to work. To collect these call logs, you need to enable a diagnostic setting that sends call data to a Log Analytics workspace in the same resource group as your calling resource. 
 
 Data isn’t stored retroactively, so you begin capturing call logs only after configuring the diagnostic setting.
 
 Follow instructions to add diagnostic settings for your resource in [Enable logs via Diagnostic Settings in Azure Monitor](../enable-logging.md). We recommend that you initially collect all logs. After you understand the capabilities in Azure Monitor, determine which logs you want to retain and for how long. When you add your diagnostic setting, you're prompted to [select logs](../enable-logging.md#adding-a-diagnostic-setting). To collect **all logs**, select **allLogs**.
 
 Your data volume, retention, and usage in Log Analytics within Azure Monitor is billed through existing Azure data meters. We recommend that you monitor your data usage and retention policies for cost considerations as needed. For more information, see [Controlling costs](/azure/azure-monitor/essentials/diagnostic-settings#controlling-costs).
 
-If you have multiple Azure Communications Services resource IDs, you must enable these settings for each resource ID. When you view Voice and Video Insights it shows you details for the resourceID you're viewing. 
+If you have multiple Azure Communications Services resource IDs, you must enable these settings for each resource ID. When you view Voice and Video Insights, it shows you details for the resourceID you're viewing. 
 
 #### Enable Copilot in Azure
 Your organization manages access to [Copilot in Azure](/azure/copilot/overview). After your organization has access to Copilot in Azure, the Voice and Video Insights sections will display multiple Copilot icons you can interact with.