From ae04245d42a3dac666d15033168eea77c4006f92 Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Tue, 12 May 2020 15:27:38 -0700 Subject: [PATCH] Corrected "Powershell" --- .../ue-v/uev-upgrade-uev-from-previous-releases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/configuration/ue-v/uev-upgrade-uev-from-previous-releases.md b/windows/configuration/ue-v/uev-upgrade-uev-from-previous-releases.md index fe1b881f81..d726744568 100644 --- a/windows/configuration/ue-v/uev-upgrade-uev-from-previous-releases.md +++ b/windows/configuration/ue-v/uev-upgrade-uev-from-previous-releases.md @@ -39,7 +39,7 @@ Performing an in-place upgrade on user devices automatically installs the UE-V s ## Verify that UE-V settings were migrated correctly -After upgrading a user device to Windows 10, version 1607, it’s important to verify that UE-V settings and template registrations were migrated correctly during the upgrade. You can verify UE-V settings using Windows Powershell or the device’s registry. +After upgrading a user device to Windows 10, version 1607, it’s important to verify that UE-V settings and template registrations were migrated correctly during the upgrade. You can verify UE-V settings using Windows PowerShell or the device’s registry. **To verify UE-V settings using Windows PowerShell**