Merge pull request #259604 from v-thepet/acs1

American-Dipper · web-flow · commit ca9804345b94 · 2023-12-04T16:08:08.000-08:00
[BULK] Spell out ACS acronym #1
diff --git a/articles/communication-services/concepts/analytics/logs/voice-and-video-logs.md b/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
diff --git a/articles/communication-services/concepts/known-issues.md b/articles/communication-services/concepts/known-issues.md
@@ -25,7 +25,7 @@ The following sections provide information about known issues associated with th
 
 ### Chrome M115 - regression 
 
-Chrome version 115 for Android introduced a regression when making video calls - the result of this bug is a user making a call on Azure Communication Services with this version of Chrome will have no outgoing video in Group and ACS-MS Teams calls.
+Chrome version 115 for Android introduced a regression when making video calls - the result of this bug is a user making a call on Azure Communication Services with this version of Chrome will have no outgoing video in Group and Azure Communication Services-Microsoft Teams calls.
 - This is a known regression introduced on [Chromium](https://bugs.chromium.org/p/chromium/issues/detail?id=1469318)
 - As a short term mitigation please instruct users to use Microsoft Edge or Firefox on Android, or avoid using Google Chrome 115/116 on Android
 
diff --git a/articles/communication-services/concepts/telephony/monitoring-troubleshooting-telephony/troubleshoot-outbound-calls.md b/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.
diff --git a/articles/communication-services/concepts/voice-video-calling/manage-call-quality.md b/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/) -->
 
 
diff --git a/articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-js.md b/articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-js.md
@@ -149,7 +149,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" }; 
diff --git a/articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-python.md b/articles/communication-services/how-tos/call-automation/includes/play-audio-how-to-python.md
@@ -203,7 +203,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>")
diff --git a/articles/communication-services/how-tos/call-automation/includes/play-audio-quickstart-csharp.md b/articles/communication-services/how-tos/call-automation/includes/play-audio-quickstart-csharp.md
@@ -162,7 +162,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 }; 
diff --git a/articles/communication-services/how-tos/call-automation/includes/play-audio-quickstart-java.md b/articles/communication-services/how-tos/call-automation/includes/play-audio-quickstart-java.md
@@ -190,7 +190,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); 
diff --git a/articles/communication-services/how-tos/calling-sdk/includes/manage-calls/manage-calls-web.md b/articles/communication-services/how-tos/calling-sdk/includes/manage-calls/manage-calls-web.md
@@ -288,7 +288,7 @@ Get the local participant Id:
 ```js
 const participantId: string = call.info.participantId;
 ```
-*Note: An ACS identity can use the web calling sdk in many endpoints, and each endpoint will have its own unique `participantId`. `participantId` is different from the ACS identity raw Id.*
+*Note: An Azure Communication Services identity can use the web calling sdk in many endpoints, and each endpoint will have its own unique `participantId`. `participantId` is different from the Azure Communication Services identity raw Id.*
 
 Retrieve the thread ID if joining a Teams meeting:
 > [!NOTE]
diff --git a/articles/communication-services/how-tos/managed-identity.md b/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.
diff --git a/articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-csharp.md b/articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-csharp.md
@@ -64,7 +64,7 @@ var cognitiveServiceEndpoint = "<COGNITIVE_SERVICE_ENDPOINT>";
 
 ## Make an outbound call
 
-To make the outbound call from ACS, this sample uses the `targetPhonenumber` you defined earlier in the application to create the call using the `CreateCallAsync` API. This code will make an outbound call using the target phone number.
+To make the outbound call from Azure Communication Services, this sample uses the `targetPhonenumber` you defined earlier in the application to create the call using the `CreateCallAsync` API. This code will make an outbound call using the target phone number.
 
 ```csharp
 PhoneNumberIdentifier target = new PhoneNumberIdentifier(targetPhonenumber);
diff --git a/articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-java.md b/articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-java.md
@@ -59,7 +59,7 @@ acs:
 
 ## Make an outbound call and play media
 
-To make the outbound call from ACS, this sample uses the `targetphonenumber` you defined in the `application.yml` file to create the call using the `createCallWithResponse` API.
+To make the outbound call from Azure Communication Services, this sample uses the `targetphonenumber` you defined in the `application.yml` file to create the call using the `createCallWithResponse` API.
 
 ```java
 PhoneNumberIdentifier caller = new PhoneNumberIdentifier(appConfig.getCallerphonenumber());
diff --git a/articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-node.md b/articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-node.md
@@ -66,7 +66,7 @@ COGNITIVE_SERVICES_ENDPOINT="<COGNITIVE_SERVICEs_ENDPOINT>"
 
 ## Make an outbound call and play media
 
-To make the outbound call from ACS, you use the phone number you provided to the environment. Ensure that the phone number is in the [E164](https://en.wikipedia.org/wiki/E.164) phone number format (e.g +18881234567)
+To make the outbound call from Azure Communication Services, you use the phone number you provided to the environment. Ensure that the phone number is in the [E164](https://en.wikipedia.org/wiki/E.164) phone number format (e.g +18881234567)
 
 The code makes an outbound call using the target_phone_number you've provided and place an outbound call to that number: 
 
diff --git a/articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-python.md b/articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-python.md
@@ -75,7 +75,7 @@ COGNITIVE_SERVICES_ENDPOINT = "<COGNITIVE_SERVICES_ENDPOINT>"
 
 ## Make an outbound call
 
-To make the outbound call from ACS, first you provide the phone number you want to receive the call. To make it simple, you can update the `target_phone_number` with a phone number in the [E164](https://en.wikipedia.org/wiki/E.164) phone number format (e.g +18881234567)
+To make the outbound call from Azure Communication Services, first you provide the phone number you want to receive the call. To make it simple, you can update the `target_phone_number` with a phone number in the [E164](https://en.wikipedia.org/wiki/E.164) phone number format (e.g +18881234567)
 
 Make an outbound call using the target_phone_number you've provided: 
 
diff --git a/articles/communication-services/whats-new.md b/articles/communication-services/whats-new.md
@@ -23,7 +23,7 @@ Get detailed information on the latest Azure Communication Services feature laun
 ### Managed identities in public preview
 :::image type="content" source="./media/whats-new-images/10-23/managed-id.png" alt-text="A graphic showing Azure logos for security and the Azure Communication Services logo.":::
 
-We're thrilled to announce the support for Azure Managed Identities for Azure Communication Services in public preview This is an Azure Enterprise Promise that enhances security for customers, and simplifies workflows to manage identities in their ACS resources.
+We're thrilled to announce the support for Azure Managed Identities for Azure Communication Services in public preview This is an Azure Enterprise Promise that enhances security for customers, and simplifies workflows to manage identities in their Azure Communication Services resources.
 
 
 [Read the documentation](./how-tos/managed-identity.md)
