more

Author: v-thepet

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

@@ -83,7 +83,7 @@ The call summary log contains data to help you identify key properties of all ca
 |     `sdkVersion`                |     The version string for the Communication Services Calling SDK version that each relevant endpoint uses (for example, `"1.1.00.20212500"`).                                               |
 |     `osVersion`                 |     A string that represents the operating system and version of each endpoint device.                                                                        |
 |     `participantTenantId`               |    The ID of the Microsoft tenant associated with the identity of the participant. The tenant can either be the Azure tenant that owns the Azure Communication Services resource or the Microsoft tenant of an M365 identity. This field is used to guide cross-tenant redaction.
-|`participantType` | 	Description of the participant as a combination of its client (Azure Communication Services (ACS) or Teams), and its identity, (ACS or Microsoft 365). Possible values include: Azure Communication Services (ACS identity and Azure Communication Services SDK), Teams (Teams identity and Teams client), Azure Communication Services as Teams external user (ACS identity and Azure Communication Services SDK in Teams call or meeting), and Azure Communication Services as Microsoft 365 user (M365 identity and Azure Communication Services client).
+|`participantType` | 	Description of the participant as a combination of its client (Azure Communication Services or Teams), and its identity, (Azure Communication Services or Microsoft 365). Possible values include: Azure Communication Services (Azure Communication Services identity and Azure Communication Services SDK), Teams (Teams identity and Teams client), Azure Communication Services as Teams external user (Azure Communication Services identity and Azure Communication Services SDK in Teams call or meeting), and Azure Communication Services as Microsoft 365 user (M365 identity and Azure Communication Services client).
 | `pstnPartcipantCallType `|It represents the type and direction of PSTN participants including Emergency calling, direct routing, transfer, forwarding, etc.| 
 
 ### Call diagnostic log schema

articles/communication-services/concepts/telephony/monitoring-troubleshooting-telephony/troubleshoot-outbound-calls.md

@@ -12,7 +12,7 @@ ms.service: azure-communication-services
 
 # Issues that affect outbound direct routing calls
 
-You might experience various issues when you use direct routing to make outbound calls from an app built on Azure Communication Services (ACS) Software Development Kit (SDK) to a Session Border Controller (SBC). These issues include:
+You might experience various issues when you use direct routing to make outbound calls from an app built on Azure Communication Services Software Development Kit (SDK) to a Session Border Controller (SBC). These issues include:
 
 - An incorrect or anonymous caller ID is displayed to the call recipient.
 - A connection to the SBC isn't established.

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

@@ -104,7 +104,7 @@ The Network Diagnostic Tool provides a hosted experience for
 
 
 - For more information, please see: [Network Diagnostics Tool](../developer-tools/network-diagnostic.md).
-  <!-- - <span class="mark">Visual</span> - [ACS Network Diagnostic
+  <!-- - <span class="mark">Visual</span> - [Azure Communication Services Network Diagnostic
     Tool](https://azurecommdiagnostics.net/) -->
 
 

articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-js.md

@@ -143,7 +143,7 @@ await callAutomationClient.getCallConnection(callConnectionId)
 
 If you're playing the same audio file multiple times, your application can provide Azure Communication Services with the sourceID for the audio file. Azure Communication Services caches this audio file for 1 hour. 
 > [!Note]
-> Caching audio files isn't suitable for dynamic prompts. If you change the URL provided to ACS, it does not update the cached URL straight away. The update will occur after the existing cache expires.
+> Caching audio files isn't suitable for dynamic prompts. If you change the URL provided to Azure Communication Services, it does not update the cached URL straight away. The update will occur after the existing cache expires.
 
 ``` javascript
 const playSource: FileSource = { url: audioUri, playsourcacheid: "<playSourceId>", kind: "fileSource" }; 

articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-python.md

@@ -204,7 +204,7 @@ call_automation_client.get_call_connection(call_connection_id).play_media(
 
 If you're playing the same audio file multiple times, your application can provide Azure Communication Services with the sourceID for the audio file. Azure Communication Services caches this audio file for 1 hour. 
 > [!Note]
-> Caching audio files isn't suitable for dynamic prompts. If you change the URL provided to ACS, it does not update the cached URL straight away. The update will occur after the existing cache expires.
+> Caching audio files isn't suitable for dynamic prompts. If you change the URL provided to Azure Communication Services, it does not update the cached URL straight away. The update will occur after the existing cache expires.
 
 ``` python
 play_source = FileSource(url=audioUri, play_source_cache_id="<playSourceId>")

articles/communication-services/how-tos/call-automation/includes/play-audio-quickstart-csharp.md

@@ -163,7 +163,7 @@ var playResult = await callAutomationClient.GetCallConnection(callConnectionId)
 
 If you're playing the same audio file multiple times, your application can provide Azure Communication Services with the sourceID for the audio file. Azure Communication Services caches this audio file for 1 hour.
 > [!Note] 
-> Caching audio files isn't suitable for dynamic prompts. If you change the URL provided to ACS, it does not update the cached URL straight away. The update will occur after the existing cache expires.
+> Caching audio files isn't suitable for dynamic prompts. If you change the URL provided to Azure Communication Services, it does not update the cached URL straight away. The update will occur after the existing cache expires.
 
 ``` csharp
 var playTo = new List<CommunicationIdentifier> { targetParticipant }; 

articles/communication-services/how-tos/call-automation/includes/play-audio-quickstart-java.md

@@ -194,7 +194,7 @@ var playResponse = callAutomationClient.getCallConnectionAsync(callConnectionId)
 
 If you're playing the same audio file multiple times, your application can provide Azure Communication Services with the sourceID for the audio file. Azure Communication Services caches this audio file for 1 hour.
 > [!Note]
-> Caching audio files isn't suitable for dynamic prompts. If you change the URL provided to ACS, it does not update the cached URL straight away. The update will occur after the existing cache expires.
+> Caching audio files isn't suitable for dynamic prompts. If you change the URL provided to Azure Communication Services, it does not update the cached URL straight away. The update will occur after the existing cache expires.
 
 ``` java
 var playTo = Arrays.asList(targetParticipant); 

articles/communication-services/how-tos/managed-identity.md

@@ -23,7 +23,7 @@ Your Azure Communication Services resource can be assigned two types of identity
    Your resource can only have one system-assigned identity.
 2. A **User Assigned Identity** which is an Azure resource that can be assigned to your Azure Communication Services resource. This identity isn't deleted when your resource is deleted. Your resource can have multiple user-assigned identities.
 
-To use Managed Identity with ACS, follow these steps:
+To use Managed Identity with Azure Communication Services, follow these steps:
 
 1. Grant your Managed Identity access to the Communication Services resource. This assignment can be through the Azure portal, Azure CLI and the Azure Communication Management SDKs.
 2. Use the Managed Identity to authenticate with Azure Communication Services. Authentication can be done through the Azure SDKs or REST APIs that support Managed Identity.