edit pass: five-communication-services-articles

paulth1 · paulth1 · commit 8d3e9bd0a33a · 2023-07-06T13:56:22.000-07:00
diff --git a/articles/communication-services/concepts/analytics/chat-metrics.md b/articles/communication-services/concepts/analytics/chat-metrics.md
@@ -13,26 +13,31 @@ ms.subservice: data
 ---
 # Chat metrics overview
 
-Azure Communication Services currently provides metrics for all ACS primitives. [Azure Metrics Explorer](../../../azure-monitor\essentials\metrics-getting-started.md) can be used to plot your own charts, investigate abnormalities in your metric values, and understand your API traffic by using the metrics data that Chat requests emit.
+Azure Communication Services currently provides metrics for all Communication Services primitives. You can use [Azure Metrics Explorer](../../../azure-monitor\essentials\metrics-getting-started.md) to:
+
+- Plot your own charts.
+- Investigate abnormalities in your metric values.
+- Understand your API traffic by using the metrics data that Chat requests emit.
+
 ## Where to find metrics
 
-Primitives in Azure Communication Services emit metrics for API requests. These metrics can be found in the Metrics tab under your Communication Services resource. You can also create permanent dashboards using the workbooks tab under your Communication Services resource.
+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.
 
 ## Metric definitions
 
-All API request metrics contain three dimensions that you can use to filter your metrics data. These dimensions can be aggregated together using the `Count` aggregation type and support all standard Azure Aggregation time series including `Sum`, `Average`, `Min`, and `Max`.
+All API request metrics contain three dimensions that you can use to filter your metrics data. These dimensions can be aggregated together by using the `Count` aggregation type. They support all standard Azure Aggregation time series, including `Sum`, `Average`, `Min`, and `Max`.
 
-More information on supported aggregation types and time series aggregations can be found [Advanced features of Azure Metrics Explorer](../../../azure-monitor/essentials/metrics-charts.md#aggregation).
+For more information on supported aggregation types and time series aggregations, see [Advanced features of Azure Metrics Explorer](../../../azure-monitor/essentials/metrics-charts.md#aggregation).
 
-- **Operation** - All operations or routes that can be called on the Azure Communication Services Chat gateway.
-- **Status Code** - The status code response sent after the request.
-- **StatusSubClass** - The status code series sent after the response. 
+- **Operation**: All operations or routes that can be called on the Communication Services Chat gateway.
+- **Status Code**: The status code response sent after the request.
+- **StatusSubClass**: The status code series sent after the response.
 
 ### Chat API request metric operations
 
-The following operations are available on Chat API request metrics:
+The following operations are available on Chat API request metrics.
 
-| Operation / Route    | Description                                                                                    |
+| Operation/Route    | Description                                                                                    |
 | -------------------- | ---------------------------------------------------------------------------------------------- |
 | GetChatMessage       | Gets a message by message ID. |
 | ListChatMessages     | Gets a list of chat messages from a thread. |
@@ -45,13 +50,14 @@ The following operations are available on Chat API request metrics:
 | CreateChatThread     | Creates a chat thread. |
 | DeleteChatThread     | Deletes a thread. |
 | GetReadReceipts      | Gets read receipts for a thread. |
-| SendReadReceipt      | Sends a read receipt event to a thread, on behalf of a user. |
-| SendTypingIndicator           | Posts a typing event to a thread, on behalf of a user. |
+| SendReadReceipt      | Sends a read receipt event to a thread for a user. |
+| SendTypingIndicator           | Posts a typing event to a thread for a user. |
 | ListChatThreadParticipants    | Gets the members of a thread. |
 | AddChatThreadParticipants     | Adds thread members to a thread. If members already exist, no change occurs. |
-| RemoveChatThreadParticipant   | Remove a member from a thread. |
+| 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.
+
 ## Next steps
 
-- Learn more about [Data Platform Metrics](../../../azure-monitor/essentials/data-platform-metrics.md).
+Learn more about [Data Platform Metrics](../../../azure-monitor/essentials/data-platform-metrics.md).
diff --git a/articles/communication-services/concepts/analytics/logs/call-automation-metrics.md b/articles/communication-services/concepts/analytics/logs/call-automation-metrics.md
@@ -13,46 +13,46 @@ ms.subservice: data
 ---
 # Call automation metrics overview
 
+Azure Communication Services currently provides metrics for all Communication Services primitives.
+
 ## Where to find metrics
 
-Primitives in Azure Communication Services emit metrics for API requests. These metrics can be found in the Metrics tab under your Communication Services resource. You can also create permanent dashboards using the workbooks tab under your Communication Services resource.
+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.
 
 ## Metric definitions
 
-All API request metrics contain three dimensions that you can use to filter your metrics data. These dimensions can be aggregated together using the `Count` aggregation type and support all standard Azure Aggregation time series including `Sum`, `Average`, `Min`, and `Max`.
+All API request metrics contain three dimensions that you can use to filter your metrics data. These dimensions can be aggregated together by using the `Count` aggregation type. They support all standard Azure Aggregation time series, including `Sum`, `Average`, `Min`, and `Max`.
 
-More information on supported aggregation types and time series aggregations can be found [Advanced features of Azure Metrics Explorer](../../../../azure-monitor/essentials/metrics-charts.md#aggregation).
+For more information on supported aggregation types and time series aggregations, see [Advanced features of Azure Metrics Explorer](../../../../azure-monitor/essentials/metrics-charts.md#aggregation).
 
-- **Operation** - All operations or routes that can be called on the Azure Communication Services Chat gateway.
-- **Status Code** - The status code response sent after the request.
-- **StatusSubClass** - The status code series sent after the response. 
+- **Operation**: All operations or routes that can be called on the Communication Services Chat gateway.
+- **Status Code**: The status code response sent after the request.
+- **StatusSubClass**: The status code series sent after the response.
 
 ### Call Automation API requests
 
-The following operations are available on Call Automation API request metrics:
+The following operations are available on Call Automation API request metrics.
 
-| Operation / Route  | Description                                                                                    |
+| Operation/Route  | Description                                                                                    |
 | -------------------- | ---------------------------------------------------------------------------------------------- |
-| Create Call           | Create an outbound call to user. 
+| Create Call           | Create an outbound call to user.
 | Answer Call           | Answer an inbound call. |
 | Redirect Call         | Redirect an inbound call to another user. |
 | Reject Call           | Reject an inbound call. |
 | Transfer Call To Participant   |  Transfer 1:1 call to another user.   |
 | Play                  | Play audio to call participants.  |
 | PlayPrompt            | Play a prompt to users as part of the Recognize action. |
 | Recognize             | Recognize user input from call participants. |
-| Add Participants      |  Add a participant to a call.    |
+| Add Participants      | Add a participant to a call.    |
 | Remove Participants   | Remove a participant from a call.   |
-| HangUp Call           | Hang up your call leg. | 
-| Terminate Call        | End the call for all participants.  | 
+| HangUp Call           | Hang up your call leg. |
+| Terminate Call        | End the call for all participants.  |
 | Get Call              | Get details about a call.     |
-| Get Participant       |  Get details on a call participant.   |
-| Get Participants      |  Get all participants in a call.   |
-| Delete Call           |  Delete a call.    |
-| Cancel All Media Operations | Cancel all ongoing or queued media operations in a call. | 
-
-
+| Get Participant       | Get details on a call participant.   |
+| Get Participants      | Get all participants in a call.   |
+| Delete Call           | Delete a call.    |
+| Cancel All Media Operations | Cancel all ongoing or queued media operations in a call. |
 
 ## Next steps
 
-- Learn more about [Data Platform Metrics](../../../../azure-monitor/essentials/data-platform-metrics.md).
+Learn more about [Data Platform Metrics](../../../../azure-monitor/essentials/data-platform-metrics.md).
diff --git a/articles/communication-services/concepts/analytics/rooms-metrics.md b/articles/communication-services/concepts/analytics/rooms-metrics.md
@@ -13,40 +13,44 @@ ms.subservice: data
 ---
 # Rooms metrics overview
 
-Azure Communication Services currently provides metrics for all ACS primitives. [Azure Metrics Explorer](../../../azure-monitor\essentials\metrics-getting-started.md) can be used to plot your own charts, investigate abnormalities in your metric values, and understand your API traffic by using the metrics data that rooms requests emit.
+Azure Communication Services currently provides metrics for all Communication Services primitives. You can use [Azure Metrics Explorer](../../../azure-monitor\essentials\metrics-getting-started.md) to:
+
+- Plot your own charts.
+- Investigate abnormalities in your metric values.
+- Understand your API traffic by using the metrics data that Chat requests emit.
 
 ## Where to find metrics
 
-Primitives in Azure Communication Services emit metrics for API requests. These metrics can be found in the Metrics tab under your Communication Services resource. You can also create permanent dashboards using the workbooks tab under your Communication Services resource.
+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.
 
 ## Metric definitions
 
-All API request metrics contain three dimensions that you can use to filter your metrics data. These dimensions can be aggregated together using the `Count` aggregation type and support all standard Azure Aggregation time series including `Sum`, `Average`, `Min`, and `Max`.
+All API request metrics contain three dimensions that you can use to filter your metrics data. These dimensions can be aggregated together by using the `Count` aggregation type. They support all standard Azure Aggregation time series, including `Sum`, `Average`, `Min`, and `Max`.
 
-More information on supported aggregation types and time series aggregations can be found [Advanced features of Azure Metrics Explorer](../../../azure-monitor/essentials/metrics-charts.md#aggregation).
+For more information on supported aggregation types and time series aggregations, see [Advanced features of Azure Metrics Explorer](../../../azure-monitor/essentials/metrics-charts.md#aggregation).
 
-- **Operation** - All operations or routes that can be called on the Azure Communication Services Chat gateway.
-- **Status Code** - The status code response sent after the request.
-- **StatusSubClass** - The status code series sent after the response. 
+- **Operation**: All operations or routes that can be called on the Communication Services Chat gateway.
+- **Status Code**: The status code response sent after the request.
+- **StatusSubClass**: The status code series sent after the response.
 
 ### Rooms API requests
 
-The following operations are available on Rooms API request metrics:
+The following operations are available on Rooms API request metrics.
 
-| Operation / Route             | Description                                                                                    |
+| Operation/Route             | Description                                                                                    |
 | ----------------------------- | ---------------------------------------------------------------------------------------------- |
 | CreateRoom                    | Creates a Room. |
 | DeleteRoom                    | Deletes a Room. |
 | GetRoom                       | Gets a Room by Room ID. |
 | PatchRoom                     | Updates a Room by Room ID. |
-| ListRooms                     | Lists all the Rooms for an ACS Resource. |
+| ListRooms                     | Lists all the Rooms for a Communication Services resource. |
 | AddParticipants               | Adds participants to a Room.|
 | RemoveParticipants            | Removes participants from a Room. |
-| GetParticipants               | Gets list of participants for a Room. |
-| UpdateParticipants            | Updates list of participants for a Room. |
+| GetParticipants               | Gets a list of participants for a Room. |
+| UpdateParticipants            | Updates a list of participants for a Room. |
 
-:::image type="content" source="../media/rooms/rooms-metrics.png" alt-text="Screenshot showing Rooms Request Metrics.":::
+:::image type="content" source="../media/rooms/rooms-metrics.png" alt-text="Screenshot that shows Rooms Request Metrics.":::
 
 ## Next steps
 
-- Learn more about [Data Platform Metrics](../../../azure-monitor/essentials/data-platform-metrics.md)
+Learn more about [Data Platform Metrics](../../../azure-monitor/essentials/data-platform-metrics.md).
diff --git a/articles/communication-services/concepts/analytics/sms-metrics.md b/articles/communication-services/concepts/analytics/sms-metrics.md
@@ -13,29 +13,32 @@ ms.subservice: data
 ---
 # SMS metrics overview
 
-Azure Communication Services currently provides metrics for all ACS primitives. [Azure Metrics Explorer](../../../azure-monitor\essentials\metrics-getting-started.md) can be used to plot your own charts, investigate abnormalities in your metric values, and understand your API traffic by using the metrics data that SMS requests emit.
+Azure Communication Services currently provides metrics for all Communication Services primitives. You can use [Azure Metrics Explorer](../../../azure-monitor\essentials\metrics-getting-started.md) to:
+
+- Plot your own charts.
+- Investigate abnormalities in your metric values.
+- Understand your API traffic by using the metrics data that Chat requests emit.
+
 ## Where to find metrics
 
-Primitives in Azure Communication Services emit metrics for API requests. These metrics can be found in the Metrics tab under your Communication Services resource. You can also create permanent dashboards using the workbooks tab under your Communication Services resource.
+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.
 
 ## Metric definitions
 
-All API request metrics contain three dimensions that you can use to filter your metrics data. These dimensions can be aggregated together using the `Count` aggregation type and support all standard Azure Aggregation time series including `Sum`, `Average`, `Min`, and `Max`.
+All API request metrics contain three dimensions that you can use to filter your metrics data. These dimensions can be aggregated together by using the `Count` aggregation type. They support all standard Azure Aggregation time series, including `Sum`, `Average`, `Min`, and `Max`.
+
+For more information on supported aggregation types and time series aggregations, see [Advanced features of Azure Metrics Explorer](../../../azure-monitor/essentials/metrics-charts.md#aggregation).
 
-More information on supported aggregation types and time series aggregations can be found [Advanced features of Azure Metrics Explorer](../../../azure-monitor/essentials/metrics-charts.md#aggregation).
+- **Operation**: All operations or routes that can be called on the Azure Communication Services Chat gateway.
+- **Status Code**: The status code response sent after the request.
+- **StatusSubClass**: The status code series sent after the response.
 
-- **Operation** - All operations or routes that can be called on the Azure Communication Services Chat gateway.
-- **Status Code** - The status code response sent after the request.
-- **StatusSubClass** - The status code series sent after the response. 
-  
 ### SMS API requests
 
-The following operations are available on SMS API request metrics:
+The following operations are available on SMS API request metrics.
 
-| Operation / Route    | Description                                                                                    |
+| Operation/Route    | Description                                                                                    |
 | -------------------- | ---------------------------------------------------------------------------------------------- |
 | SMSMessageSent       | Sends an SMS message. |
 | SMSDeliveryReportsReceived     | Gets SMS Delivery Reports |
 | SMSMessagesReceived      | Gets SMS messages. |
-
-
diff --git a/articles/communication-services/concepts/analytics/turn-metrics.md b/articles/communication-services/concepts/analytics/turn-metrics.md
