remaining

v-thepet · v-thepet · commit 966a2d1b19e2 · 2023-11-27T16:17:55.000-08:00
diff --git a/articles/event-grid/communication-services-voice-video-events.md b/articles/event-grid/communication-services-voice-video-events.md
@@ -275,10 +275,10 @@ This section contains an example of what that data would look like for each even
 ```
 
 ## Limitations
-Aside from `IncomingCall`, Calling events are only available for ACS VoIP users. PSTN, bots, echo bot and Teams users events are excluded.
-No calling events will be available for ACS - Teams meeting interop call.
+Aside from `IncomingCall`, Calling events are only available for Azure Communication Services VoIP users. PSTN, bots, echo bot and Teams users events are excluded.
+No calling events will be available for Azure Communication Services - Teams meeting interop call.
 
-`IncomingCall` events have support for ACS VoIP users and PSTN numbers. For more details on which scenarios can trigger `IncomingCall` events, see the following [Incoming call concepts](../communication-services/concepts/call-automation/incoming-call-notification.md) documentation. 
+`IncomingCall` events have support for Azure Communication Services VoIP users and PSTN numbers. For more details on which scenarios can trigger `IncomingCall` events, see the following [Incoming call concepts](../communication-services/concepts/call-automation/incoming-call-notification.md) documentation. 
 
 ## Next steps
 See the following tutorial: [Quickstart: Handle voice and video calling events](../communication-services/quickstarts/voice-video-calling/handle-calling-events.md).
diff --git a/articles/machine-learning/how-to-secure-rag-workflows.md b/articles/machine-learning/how-to-secure-rag-workflows.md
@@ -70,7 +70,7 @@ If you're using an **Allow only approved outbound** Managed Vnet workspace and a
 
 - If your workspace runs into network related issues where your compute is unable to create or start a compute, try adding a placeholder FQDN rule in the **Networking** tab of your workspace in the Azure portal, in order to initiate a managed network update. Then, re-create the Compute in the Azure Machine Learning workspace.
 
-- You might see an error message related to `< Resource > is not registered with Microsoft.Network resource provider.` In which case, you should **ensure the subscription which your AOAI/ACS resource is registered with a Microsoft Network resource provider**. To do so, navigate to **Subscription**, then **Resource Providers** for the same tenant as your Managed Vnet Workspace.
+- You might see an error message related to `< Resource > is not registered with Microsoft.Network resource provider.` In which case, you should **ensure the subscription which your AOAI/Azure AI Search resource is registered with a Microsoft Network resource provider**. To do so, navigate to **Subscription**, then **Resource Providers** for the same tenant as your Managed Vnet Workspace.
 
 > [!NOTE]
 > It's expected for a first-time serverless job in the workspace to be Queued an additional 10-15 minutes while Managed Network is provisioning Private Endpoints for the first time. With Compute Instance and Compute Cluster, this process happens during the compute creation.
diff --git a/articles/role-based-access-control/includes/resource-provider-operations/analytics.md b/articles/role-based-access-control/includes/resource-provider-operations/analytics.md
@@ -186,7 +186,7 @@ Azure service: [Event Hubs](../../../event-hubs/index.yml)
 > | Microsoft.EventHub/namespaces/read | Get the list of Namespace Resource Description |
 > | Microsoft.EventHub/namespaces/Delete | Delete Namespace Resource |
 > | Microsoft.EventHub/namespaces/authorizationRules/action | Updates Namespace Authorization Rule. This API is deprecated. Please use a PUT call to update the Namespace Authorization Rule instead.. This operation is not supported on API version 2017-04-01. |
-> | Microsoft.EventHub/namespaces/removeAcsNamepsace/action | Remove ACS namespace |
+> | Microsoft.EventHub/namespaces/removeAcsNamespace/action | Remove Access Control Service namespace |
 > | Microsoft.EventHub/namespaces/privateEndpointConnectionsApproval/action | Approve Private Endpoint Connection |
 > | Microsoft.EventHub/namespaces/joinPerimeter/action | Action to Join the Network Security Perimeter. This action is used to perform linked access by NSP RP. |
 > | Microsoft.EventHub/namespaces/authorizationRules/read | Get the list of Namespaces Authorization Rules description. |
diff --git a/articles/role-based-access-control/includes/resource-provider-operations/integration.md b/articles/role-based-access-control/includes/resource-provider-operations/integration.md
@@ -1111,7 +1111,7 @@ Azure service: [Azure Relay](../../../azure-relay/relay-what-is-it.md)
 > | Microsoft.Relay/namespaces/read | Get the list of Namespace Resource Description |
 > | Microsoft.Relay/namespaces/Delete | Delete Namespace Resource |
 > | Microsoft.Relay/namespaces/authorizationRules/action | Updates Namespace Authorization Rule. This API is deprecated. Please use a PUT call to update the Namespace Authorization Rule instead.. This operation is not supported on API version 2017-04-01. |
-> | Microsoft.Relay/namespaces/removeAcsNamepsace/action | Remove ACS namespace |
+> | Microsoft.Relay/namespaces/removeAcsNamespace/action | Remove Access Control Service namespace |
 > | Microsoft.Relay/namespaces/privateEndpointConnectionsApproval/action | Approve Private Endpoint Connection |
 > | Microsoft.Relay/namespaces/authorizationRules/read | Get the list of Namespaces Authorization Rules description. |
 > | Microsoft.Relay/namespaces/authorizationRules/write | Create a Namespace level Authorization Rules and update its properties. The Authorization Rules Access Rights, the Primary and Secondary Keys can be updated. |
@@ -1186,7 +1186,7 @@ Azure service: [Service Bus](../../../service-bus-messaging/index.yml)
 > | Microsoft.ServiceBus/namespaces/Delete | Delete Namespace Resource |
 > | Microsoft.ServiceBus/namespaces/authorizationRules/action | Updates Namespace Authorization Rule. This API is deprecated. Please use a PUT call to update the Namespace Authorization Rule instead.. This operation is not supported on API version 2017-04-01. |
 > | Microsoft.ServiceBus/namespaces/migrate/action | Migrate namespace operation |
-> | Microsoft.ServiceBus/namespaces/removeAcsNamepsace/action | Remove ACS namespace |
+> | Microsoft.ServiceBus/namespaces/removeAcsNamespace/action | Remove Access Control Service namespace |
 > | Microsoft.ServiceBus/namespaces/privateEndpointConnectionsApproval/action | Approve Private Endpoint Connection |
 > | Microsoft.ServiceBus/namespaces/authorizationRules/write | Create a Namespace level Authorization Rules and update its properties. The Authorization Rules Access Rights, the Primary and Secondary Keys can be updated. |
 > | Microsoft.ServiceBus/namespaces/authorizationRules/read | Get the list of Namespaces Authorization Rules description. |
diff --git a/articles/role-based-access-control/includes/resource-provider-operations/web.md b/articles/role-based-access-control/includes/resource-provider-operations/web.md
@@ -285,8 +285,8 @@ Azure service: [Media Services](/azure/media-services/)
 > | Microsoft.Media/mediaservices/read | Read any Media Services Account |
 > | Microsoft.Media/mediaservices/write | Create or Update any Media Services Account |
 > | Microsoft.Media/mediaservices/delete | Delete any Media Services Account |
-> | Microsoft.Media/mediaservices/regenerateKey/action | Regenerate a Media Services ACS key |
-> | Microsoft.Media/mediaservices/listKeys/action | List the ACS keys for the Media Services account |
+> | Microsoft.Media/mediaservices/regenerateKey/action | Regenerate a Media Services Access Control Services key |
+> | Microsoft.Media/mediaservices/listKeys/action | List the Access Control Services keys for the Media Services account |
 > | Microsoft.Media/mediaservices/syncStorageKeys/action | Synchronize the Storage Keys for an attached Azure Storage account |
 > | Microsoft.Media/mediaservices/listEdgePolicies/action | List policies for an edge device. |
 > | Microsoft.Media/mediaservices/PrivateEndpointConnectionsApproval/action | Approve Private Endpoint Connections |
diff --git a/articles/security/fundamentals/azure-domains.md b/articles/security/fundamentals/azure-domains.md
@@ -31,7 +31,7 @@ This page is a partial list of the Azure domains in use. Some of them are REST A
 |[Azure Cloud Services](../../cloud-services/cloud-services-choose-me.md) and [Azure Virtual Machines](../../virtual-machines/index.yml)|*.cloudapp.net|
 |[Azure Cloud Services](../../cloud-services/cloud-services-choose-me.md) and [Azure Virtual Machines](../../virtual-machines/index.yml)|*.cloudapp.azure.com|
 |[Azure Container Registry](https://azure.microsoft.com/services/container-registry/)|*.azurecr.io|
-|Azure Container Service (ACS) (deprecated)|*.azurecontainer.io|
+|Azure Container Service (deprecated)|*.azurecontainer.io|
 |[Azure Content Delivery Network (CDN)](https://azure.microsoft.com/services/cdn/)|*.vo.msecnd.net|
 |[Azure Cosmos DB](../../cosmos-db/index.yml)|*.cosmos.azure.com|
 |[Azure Cosmos DB](../../cosmos-db/index.yml)|*.documents.azure.com|
diff --git a/articles/spring-apps/how-to-migrate-standard-tier-to-enterprise-tier.md b/articles/spring-apps/how-to-migrate-standard-tier-to-enterprise-tier.md
@@ -135,14 +135,14 @@ The app creation steps are the same as Standard plan.
 
 ## Use Application Configuration Service for external configuration
 
-For externalized configuration in a distributed system, managed Spring Cloud Config Server (OSS) is available only in the Basic and Standard plans. In the Enterprise plan, Application Configuration Service for Tanzu (ACS) provides similar functions for your apps. The following table describes some differences in usage between the OSS config server and ACS.
+For externalized configuration in a distributed system, managed Spring Cloud Config Server (OSS) is available only in the Basic and Standard plans. In the Enterprise plan, Application Configuration Service for Tanzu provides similar functions for your apps. The following table describes some differences in usage between the OSS config server and Application Configuration Service.
 
 | Component                                   | Support plans  | Enabled           | Bind to app | Profile                                                               |
 |---------------------------------------------|----------------|-------------------|-------------|-----------------------------------------------------------------------|
 | Spring Cloud Config Server                  | Basic/Standard | Always enabled.   | Auto bound  | Configured in app's source code.                                      |
 | Application Configuration Service for Tanzu | Enterprise     | Enable on demand. | Manual bind | Provided as `config-file-pattern` in an Azure Spring Apps deployment. |
 
-Unlike the client-server mode in the OSS config server, ACS manages configuration by using the Kubernetes-native `ConfigMap`, which is populated from properties defined in backend Git repositories. ACS can't get the active profile configured in the app's source code to match the right configuration, so the explicit configuration `config-file-pattern` should be specified at the Azure Spring Apps deployment level.
+Unlike the client-server mode in the OSS config server, Application Configuration Service manages configuration by using the Kubernetes-native `ConfigMap`, which is populated from properties defined in backend Git repositories. Application Configuration Service can't get the active profile configured in the app's source code to match the right configuration, so the explicit configuration `config-file-pattern` should be specified at the Azure Spring Apps deployment level.
 
 ## Configure Application Configuration Service for Tanzu
 
diff --git a/articles/virtual-network/deploy-container-networking.md b/articles/virtual-network/deploy-container-networking.md
@@ -12,9 +12,9 @@ ms.author: allensu
 
 The Azure Virtual Network container network interface (CNI) plug-in installs in an Azure virtual machine and brings virtual network capabilities to Kubernetes Pods and Docker containers. To learn more about the plug-in, see [Enable containers to use Azure Virtual Network capabilities](container-networking-overview.md). Additionally, the plug-in can be used with the Azure Kubernetes Service (AKS) by choosing the [Advanced Networking](../aks/configure-azure-cni.md?toc=%2fazure%2fvirtual-network%2ftoc.json) option, which automatically places AKS containers in a virtual network.
 
-## Deploy plug-in for ACS-Engine Kubernetes cluster
+## Deploy plug-in for Azure Container Service-Engine Kubernetes cluster
 
-The ACS-Engine deploys a Kubernetes cluster with an Azure Resource Manager template. The cluster configuration is specified in a JSON file that is passed to the tool when generating the template. To learn more about the entire list of supported cluster settings and their descriptions, see [Microsoft Azure Container Service Engine - Cluster Definition](https://github.com/Azure/acs-engine/blob/master/docs/clusterdefinition.md). The plug-in is the default networking plug-in for clusters created using the ACS-Engine. The following network configuration settings are important when configuring the plug-in:
+The Azure Container Service-Engine deploys a Kubernetes cluster with an Azure Resource Manager template. The cluster configuration is specified in a JSON file that is passed to the tool when generating the template. To learn more about the entire list of supported cluster settings and their descriptions, see [Microsoft Azure Container Service Engine - Cluster Definition](https://github.com/Azure/acs-engine/blob/master/docs/clusterdefinition.md). The plug-in is the default networking plug-in for clusters created using the Azure Container Service-Engine. The following network configuration settings are important when configuring the plug-in:
 
   | Setting                              | Description                                                                                                           |
   |--------------------------------------|------------------------------------------------------------------------------------------------------                 |
