refresh update, fixed cloud admin spelling issues

Author: suzuber

articles/azure-vmware/rotate-cloudadmin-credentials.md

@@ -1,27 +1,27 @@
 ---
-title: Rotate the cloudadmin credentials for Azure VMware Solution
+title: Rotate the cloud admin credentials for Azure VMware Solution
 description: Learn how to rotate the vCenter Server credentials for your Azure VMware Solution private cloud. 
 ms.topic: how-to
 ms.service: azure-vmware
 ms.custom: devx-track-azurecli, engagement-fy23
 ms.date: 3/25/2026
-# Customer intent: As an Azure service administrator, I want to rotate my cloudadmin credentials so that the HCX Connector has the latest vCenter Server CloudAdmin credentials.
+# Customer intent: As an Azure service administrator, I want to rotate my cloud admin credentials so that the HCX Connector has the latest vCenter Server Cloud Admin credentials.
 ---
 
-# Rotate the cloudadmin credentials for Azure VMware Solution
+# Rotate the cloud admin credentials for Azure VMware Solution
 
-In this article, you learn how to rotate the cloudadmin credentials (vCenter Server and VMware NSX cloudadmin credentials) for your Azure VMware Solution private cloud. Although the password for this account doesn't expire, you can generate a new one at any time.
+In this article, you learn how to rotate the cloud admin credentials (vCenter Server and VMware NSX cloud admin credentials) for your Azure VMware Solution private cloud. Although the password for this account doesn't expire, you can generate a new one at any time.
 
 >[!CAUTION]
->If you use your cloudadmin credentials to connect services to vCenter Server or NSX in your private cloud, those connections stop working after you rotate your password. Those connections also lock out the cloudadmin account unless you stop those services before you rotate the password.
+>If you use your cloud admin credentials to connect services to vCenter Server or NSX in your private cloud, those connections stop working after you rotate your password. Those connections also lock out the cloud admin account unless you stop those services before you rotate the password.
 
 ## Prerequisites
 
-Consider and determine which services connect to vCenter Server as `[email protected]` or NSX as cloudadmin before you rotate the password. Services can include VMware services like HCX, vRealize Orchestrator, vRealize Operations Manager, VMware Horizon, or other non-Microsoft tools that are used for monitoring or provisioning.
+Consider and determine which services connect to vCenter Server as `[email protected]` or NSX as cloud admin before you rotate the password. Services can include VMware services like HCX, vRealize Orchestrator, vRealize Operations Manager, VMware Horizon, or other non-Microsoft tools that are used for monitoring or provisioning.
 
-One way to determine which services authenticate to vCenter Server with the cloudadmin user is to inspect vSphere events by using the vSphere Client for your private cloud. After you identify such services, and before you rotate the password, you must stop these services. Otherwise, the services won't work after you rotate the password. You can also experience temporary locks on your vCenter Server cloudadmin account. Locks occur because these services continuously attempt to authenticate by using a cached version of the old credentials.
+One way to determine which services authenticate to vCenter Server with the cloud admin user is to inspect vSphere events by using the vSphere Client for your private cloud. After you identify such services, and before you rotate the password, you must stop these services. Otherwise, the services won't work after you rotate the password. You can also experience temporary locks on your vCenter Server cloud admin account. Locks occur because these services continuously attempt to authenticate by using a cached version of the old credentials.
 
-Instead of using the cloudadmin user to connect services to vCenter Server or NSX, we recommend that you use individual accounts for each service. For more information about setting up separate accounts for connected services, see [Access and identity architecture](./architecture-identity.md).
+Instead of using the cloud admin user to connect services to vCenter Server or NSX, we recommend that you use individual accounts for each service. For more information about setting up separate accounts for connected services, see [Access and identity architecture](./architecture-identity.md).
 
 ## Reset your vCenter Server credentials
 
@@ -39,7 +39,7 @@ To begin using the Azure CLI:
 
 1. In your Azure VMware Solution private cloud, open an Azure Cloud Shell session.
 
-1. Update your vCenter Server cloudadmin credentials. Remember to replace `{SubscriptionID}`, `{ResourceGroup}`, and `{PrivateCloudName}` with your private cloud information.
+1. Update your vCenter Server cloud admin credentials. Remember to replace `{SubscriptionID}`, `{ResourceGroup}`, and `{PrivateCloudName}` with your private cloud information.
 
    ```azurecli-interactive
    az resource invoke-action --action rotateVcenterPassword --ids "/subscriptions/{SubscriptionID}/resourceGroups/{ResourceGroup}/providers/Microsoft.AVS/privateClouds/{PrivateCloudName}" --api-version "2020-07-17-preview"