Update call-diagnostics.md

Author: amagginetti

articles/communication-services/concepts/voice-video-calling/call-diagnostics.md

@@ -25,12 +25,14 @@ Just like a real conversation, many things happen simultaneously in a call that
 
 ## Enable Call Diagnostics
 
-Azure Communication Services generates call data in the form of metrics and events as you make calls. You must store these data in a Log Analytics workspace that is in the same resource group as your calling resource in order to Call Diagnostics to work. For Call Diagnostics to analyze new call data, you must enable a diagnostic setting in Azure Monitor that directs these call data to be stored in your Log Analytics workspace as they are created. These call data are not retroactively available from Azure Communication Services, but once you setup your diagnostic setting you control the data retention periods for your Log Analytics resource.  
+Azure Communication Services generates call data in the form of metrics and events as you make calls. You must store these data in a Log Analytics workspace that is in the same resource group as your calling resource in order for Call Diagnostics to work. To store these data, you must enable a diagnostic setting in Azure Monitor that directs these call data to be stored in a Log Analytics workspace as they're created. These call data aren't retroactively available from Azure Communication Services, but once you set up your diagnostic setting you control the data retention periods for your Log Analytics resource.  
 
 > [!IMPORTANT]
-> To enable Call Diagnostics in your calling resource you must collect log data for Call Diagnostics to display. Call Diagnostics can only query data sent to a Log Analytics workspace. Diagnostic settings begin collecting data by a single Azure Communications Services resource ID after you enable the diagnostic setting. 
+> To enable Call Diagnostics in your calling resource see: [**How do I set up Call Diagnostics?**](#how-do-i-set-up-call-diagnostics) 
+>
+>You need to start collecting the log data for Call Diagnostics to visualize. Call Diagnostics can only query data sent to a Log Analytics workspace that is located in the same resource group as your calling resource. Keep in mind, call data isn't stored anywhere until you set up a Diagnostic Setting to store it in a Log Analytics workspace. You need to enable a Diagonstic Setting for each Azure Communications Services resource ID you want to monitor. 
 
-Because Call Diagnostics is an application layer on top of data for your Azure Communications Services resource, you can query the call data and [build workbook reports on top of your data](/azure/azure-monitor/logs/data-platform-logs#built-in-insights-and-custom-dashboards-workbooks-and-reports).
+Since Call Diagnostics is an application layer on top of data for your Azure Communications Services resource, you can query the call data and [build workbook reports on top of your data](/azure/azure-monitor/logs/data-platform-logs#built-in-insights-and-custom-dashboards-workbooks-and-reports).
 
 You can access Call Diagnostics from any Azure Communication Services resource in the Azure portal. After you open your Azure Communications Services resource, look for the **Monitoring** section on the service menu and select **Call Diagnostics**.
 
@@ -88,13 +90,13 @@ AI can help app developers across every step of the development lifecycle: desig
 
 ### How do I set up Call Diagnostics?
 
-Follow instructions to add diagnostic settings for your resource in [Enable logs via Diagnostic Settings in Azure Monitor](../analytics/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 diagnostic setting, you're prompted to [select logs](../analytics/enable-logging.md#adding-a-diagnostic-setting). To collect all logs, select **allLogs**.
+Follow instructions to add diagnostic settings for your resource in [Enable logs via Diagnostic Settings in Azure Monitor](../analytics/enable-logging.md). We recommend that you **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 a Diagnostic Setting, you will be prompted to [select logs](../analytics/enable-logging.md#adding-a-diagnostic-setting). To collect **all logs**, select **allLogs**.
 
 Your data volume, retention, and Call Diagnostics query 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. Then you can query call details for participants within their respective resource IDs.
 
-Participants who join from other Azure Communication Services resources have limited information in Call Diagnostics. The participants who belong to the resource when you open Call Diagnostics have all available insights shown.
+Participants who join from other Azure Communication Services resources will show limited information in your view of Call Diagnostics. The participants who belong to your resource when you open Call Diagnostics have all available insights shown.
 
 ### What are the common call problems  and how to fix them?
 
@@ -139,7 +141,7 @@ To view the `DiagnosticOptions` columns in Call Diagnostics, you need to enable
 
 :::image type="content" source="./media/ui-hint-edit-columns-button.png" alt-text="Screenshot of the Call Diagnostics search view with a red rectangle around the Edit Columns icon."  lightbox="./media/ui-hint-edit-columns-button.png":::
 
-After clicking the **Edit Columns** button, choose the **DiagnosticOptions** option and click **Done**:
+After clicking the **Edit Columns** button, choose the **DiagnosticOptions** option and select **Done**:
 
 :::image type="content" source="./media/ui-hint-choose-columns-sidepane.png" alt-text="Screenshot of the Call Diagnostics search view with the column editor opened on the right side. There are red rectangles around the DiagnosticOptions option and the Done button."  lightbox="./media/ui-hint-choose-columns-sidepane.png":::