From 10afec4a8501bc49a2399daec8776630bf95418b Mon Sep 17 00:00:00 2001
From: "Chris J. Lin" <36452239+chrisjlin@users.noreply.github.com>
Date: Thu, 21 Nov 2024 16:17:17 -0800
Subject: [PATCH] Update mcc-ent-deploy-to-windows.md

Corrected "environment variable" to "PowerShell variable"
---
 windows/deployment/do/mcc-ent-deploy-to-windows.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/windows/deployment/do/mcc-ent-deploy-to-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md
index e1ff1c2af4..0c3eb345fb 100644
--- a/windows/deployment/do/mcc-ent-deploy-to-windows.md
+++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md
@@ -33,9 +33,9 @@ Before deploying Connected Cache to a Windows host machine, ensure that the host
 
 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package.
 1. Set the Execution Policy to *Unrestricted* to allow the provisioning scripts to run.
-1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account. 
+1. Create a `$User` PowerShell variable containing the username of the account you intend to designate as the Connected Cache runtime account.
 
-    For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`.
+    For gMSAs, the `$User` PowerShell variable should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` PowerShell variable should be formatted as `"LocalMachineName\Username"`.
 
    If you're using a Local User account as the Connected Cache runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`.