Third commit

Most Chat articles

Author: vac0224

articles/communication-services/concepts/analytics/chat-metrics.md

@@ -1,7 +1,7 @@
 ---
 title: Chat metrics definitions for Azure Communication Service
-titleSuffix: An Azure Communication Services concept document
-description: This document covers definitions of chat metrics available in the Azure portal.
+titleSuffix: An Azure Communication Services article
+description: This article defines of chat metrics available in the Azure portal.
 author: mkhribech
 services: azure-communication-services
 ms.author: mkhribech
@@ -10,17 +10,18 @@ ms.topic: conceptual
 ms.service: azure-communication-services
 ms.subservice: data
 ---
+
 # Chat metrics overview
 
-Azure Communication Services currently provides metrics for all Communication Services primitives. You can use [Azure Metrics Explorer](/azure/azure-monitor/essentials/metrics-getting-started) to:
+Azure Communication Services currently provides metrics for all Communication Services services. You can use [Azure Metrics Explorer](/azure/azure-monitor/essentials/metrics-getting-started) to:
 
 - Plot your own charts.
 - Investigate abnormalities in your metric values.
-- Understand your API traffic by using the metrics data that Chat requests emit.
+- Understand your API traffic using the metrics data that Chat requests emit.
 
 ## Where to find metrics
 
-Primitives in Communication Services emit metrics for API requests. To find these metrics, see the **Metrics** tab under your Communication Services resource. You can also create permanent dashboards by using the workbooks tab under your Communication Services resource.
+Each service emits metrics for API requests. To find these metrics, see the **Metrics** tab under your Communication Services resource. You can also create permanent dashboards using the workbooks tab under your Communication Services resource.
 
 ## Metric definitions
 
@@ -55,7 +56,7 @@ The following operations are available on Chat API request metrics.
 | AddChatThreadParticipants     | Adds thread members to a thread. If members already exist, no change occurs. |
 | RemoveChatThreadParticipant   | Removes a member from a thread. |
 
-If a request is made to an operation that isn't recognized, you receive a "Bad Route" value response.
+If a request to an operation isn't recognized, you receive a "Bad Route" value response.
 
 ## Next steps
 

articles/communication-services/concepts/analytics/insights/chat-insights.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Communication Services Chat Insights Dashboard
-titleSuffix: An Azure Communication Services concept document
+title: Chat insights
+titleSuffix: An Azure Communication Services article
 description: Descriptions of data visualizations available for Chat Communications Services via Workbooks
 author:  mkhribech
 services: azure-communication-services
@@ -12,33 +12,34 @@ ms.service: azure-communication-services
 ms.subservice: data
 ---
 
-# Chat Insights
+# Chat insights
 
-In this document, we outline the available insights dashboard to monitor Chat logs and metrics.
+This article describes the insights dashboard you can view to monitor Chat logs and metrics.
 
-## Overview
-Within your Communications Resource, we've provided an **Insights Preview** feature that displays many  data visualizations conveying insights from the Azure Monitor logs and metrics monitored for your Communications Services. The visualizations within Insights are made possible via [Azure Monitor Workbooks](/azure/azure-monitor/visualize/workbooks-overview). In order to take advantage of Workbooks, follow the instructions outlined in [Enable Azure Monitor in Diagnostic Settings](../enable-logging.md). To enable Workbooks, you need to send your logs to a [Log Analytics workspace](/azure/azure-monitor/logs/log-analytics-overview) destination. 
+Within your Communications Resource, we provide an **Insights Preview** feature that displays many data visualizations conveying insights from the Azure Monitor logs and metrics monitored for your Communications Services.
+
+The visualizations within Insights are made possible via [Azure Monitor Workbooks](/azure/azure-monitor/visualize/workbooks-overview). In order to take advantage of Workbooks, follow the instructions outlined in [Enable Azure Monitor in Diagnostic Settings](../enable-logging.md). To enable Workbooks, you need to send your logs to a [Log Analytics workspace](/azure/azure-monitor/logs/log-analytics-overview) destination. 
 
 :::image type="content" source="..\media\workbooks\insights-overview-2.png" alt-text="Screenshot of Communication Services Insights dashboard.":::
 
 ## Prerequisites
 
-- In order to take advantage of Workbooks, follow the instructions outlined in [Enable Azure Monitor in Diagnostic Settings](../enable-logging.md). You need to enable `Operational Chat Logs`, `Operational Authentication Logs`.
+- To use Workbooks, follow the instructions in [Enable Azure Monitor in Diagnostic Settings](../enable-logging.md). You need to enable `Operational Chat Logs` and `Operational Authentication Logs`.
 - To use Workbooks, you need to send your logs to a [Log Analytics workspace](/azure/azure-monitor/logs/log-analytics-overview) destination. 
 
 ## Accessing Azure Insights for Communication Services
 
-Inside your Azure Communication Services resource, scroll down on the left nav bar to the **Monitor** category and click on the **Insights** tab:
+Inside your Azure Communication Services resource, scroll down on the left nav bar to the **Monitor** category and click the **Insights** tab:
 
 :::image type="content" source="..\media\workbooks\acs-insights-nav.png" alt-text="Screenshot of the Insights navigation blade.":::
 
-## Authentication insights
+## Authentication insights tab
 
 The **Authentication** tab shows authentication logs, which are created through operations such as issuing an access token or creating an identity. The data displayed includes the types of operations performed and the results of those operations:
 
 :::image type="content" source="..\media\workbooks\auth.png" alt-text="Screenshot that shows the authentication tab.":::
 
-## Chat insights
+## Chat insights tab
 
 The **Chat** tab displays the data for all chat-related operations and their result types:
 

articles/communication-services/concepts/analytics/logs/chat-logs.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Communication Services chat logs
-titleSuffix: An Azure Communication Services concept document
+title: Chat logs
+titleSuffix: An Azure Communication Services article
 description: Learn about logging for Azure Communication Services chat.
 author: tophpalmer
 services: azure-communication-services
@@ -11,16 +11,16 @@ ms.service: azure-communication-services
 ms.subservice: data
 ---
 
-# Azure Communication Services chat logs
+# Chat logs
 
-Azure Communication Services offers logging capabilities that you can use to monitor and debug your Communication Services solution. These capabilities can be configured through the Azure portal.
+Azure Communication Services provides logging capabilities that you can use to monitor and debug your Communication Services solution. These capabilities can be configured through the Azure portal.
 
 > [!IMPORTANT]
-> The following refers to logs enabled through [Azure Monitor](/azure/azure-monitor/overview) (see also [FAQ](/azure/azure-monitor/overview#frequently-asked-questions)). To enable these logs for your Communications Services, see: [Enable logging in Diagnostic Settings](../enable-logging.md)
+> This article refers to logs enabled through [Azure Monitor](/azure/azure-monitor/overview) (see also [FAQ](/azure/azure-monitor/overview#frequently-asked-questions)). To enable these logs for your Communications Services, see [Enable logging in Diagnostic Settings](../enable-logging.md).
 
 ## Resource log categories
 
-Communication Services offers the following types of logs that you can enable:
+Communication Services provides the following types of logs that you can enable:
 
 * **Usage logs** - provides usage data associated with each billed service offering
 * **Authentication operational logs** - provides basic information related to the Authentication service

articles/communication-services/concepts/chat/concepts.md

@@ -43,7 +43,10 @@ Azure Communication Services stores chat threads according to the [data retentio
 
 [!INCLUDE [chat-retention-policy.md](../../includes/chat-retention-policy.md)]
 
-You can choose between indefinite thread retention, automatic deletion between 30 and 90 days via the retention policy on the [Create Chat Thread API](/rest/api/communication/chat/chat/create-chat-thread), or immediate deletion using the APIs [Delete Chat Message](/rest/api/communication/chat/chat-thread/delete-chat-message) or [Delete Chat Thread](/rest/api/communication/chat/chat/delete-chat-thread). 
+You can choose between:
+- Indefinite thread retention.
+- Automatic deletion between 30 and 90 days via the retention policy on the [Create Chat Thread API](/rest/api/communication/chat/chat/create-chat-thread).
+- Immediate deletion using the APIs [Delete Chat Message](/rest/api/communication/chat/chat-thread/delete-chat-message) or [Delete Chat Thread](/rest/api/communication/chat/chat/delete-chat-thread). 
 
 Any thread created before the new retention policy isn't affected unless you specifically change the policy for that thread. If you submit a support request for a deleted chat thread more than 30 days after the retention policy deleted that thread, it can no longer be retrieved and no information about that thread is available. If needed, [open a support ticket](/azure/azure-portal/supportability/how-to-create-azure-support-request) as quickly as possible within the 30 day window after you create a thread so we can assist you.
 
@@ -110,7 +113,7 @@ The client app can subscribe to following events:
  - `chatMessageEdited` - when a message is edited in a chat thread.
  - `chatMessageDeleted` - when a message is deleted in a chat thread.
  - `typingIndicatorReceived` - when another participant sends a typing indicator to the chat thread.
- - `readReceiptReceived` - when another participant sends a read receipt for a message they have read.
+ - `readReceiptReceived` - when another participant sends a read receipt for a message they read.
  - `chatThreadCreated` - when a Communication Services user creates a chat thread.
  - `chatThreadDeleted` - when a Communication Services user deletes a chat thread.
  - `chatThreadPropertiesUpdated` - when chat thread properties are updated; currently, only updating the topic for the thread is supported.
@@ -120,7 +123,7 @@ The client app can subscribe to following events:
  - `realTimeNotificationDisconnected` -when real time notification is disconnected.
 
 > [!NOTE] 
-> Real time notifications are not to be used with server applications.
+> Do not use real-time notifications with server applications.
 
 ## Server events
 
@@ -155,6 +158,6 @@ For more information, see [Push Notifications](../notifications.md).
 
 ## Related articles
 
-- Familiarize yourself with the [Chat SDK](./sdk-features.md)
-- Access control for participants on a thread using [Identity and Tokens](../identity-model.md)
-- Build an application or a mobile app with [UI Library](../ui-library/ui-library-overview.md)
+- Familiarize yourself with the [Chat SDK](./sdk-features.md).
+- Access control for participants on a thread using [Identity and Tokens](../identity-model.md).
+- Build an application or a mobile app with [UI Library](../ui-library/ui-library-overview.md).

articles/communication-services/concepts/chat/government-cloud.md

@@ -10,6 +10,7 @@ ms.subservice: chat
 ---
 
 # Chat support for government clouds
+
 Developers can build a chat application in government cloud for real-time text communications. 
 
 [!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
@@ -18,18 +19,18 @@ Developers can build a chat application in government cloud for real-time text c
 | --- | --- | --- |
 | Public |Public| ✔️ |
 | GCC |Public | ❌ |
-| GCC-H |[US Government](../../../azure-government/documentation-government-welcome.md) | ✔️ |
+| GCC-High |[US Government](../../../azure-government/documentation-government-welcome.md) | ✔️ |
 
 ## Supported use cases
 
-The following table show supported use cases for Gov Cloud user with Azure Communication Services:
+The following table shows supported use cases for Government Community Cloud (GCC) user with Azure Communication Services:
 
 | Scenario | Supported |
 | --- | --- |
 | 1:1 Chat | ✔️ |
 | Group Chat | ✔️ |
 
-Azure Communication Chat service also allows connecting to Microsoft 365 cloud that meets government security and compliance requirements for Teams Interoperability [scenarios](../interop/guest/government-cloud.md). 
+Azure Communication Chat service also enables connecting to Microsoft 365 cloud that meets government security and compliance requirements for Teams Interoperability [scenarios](../interop/guest/government-cloud.md). 
 
 ## Next steps