From 1f81616e963183697e0303bafd0434dc88db75cd Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Wed, 18 Dec 2019 16:57:52 -0800 Subject: [PATCH] Acrolinx spelling: Changed "lockscreen" to "lock screen" --- windows/deployment/windows-autopilot/windows-autopilot-reset.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/windows-autopilot-reset.md b/windows/deployment/windows-autopilot/windows-autopilot-reset.md index e2679d47f7..e114e9f5ec 100644 --- a/windows/deployment/windows-autopilot/windows-autopilot-reset.md +++ b/windows/deployment/windows-autopilot/windows-autopilot-reset.md @@ -87,7 +87,7 @@ Performing a local Windows Autopilot Reset is a two-step process: trigger it and 1. From the Windows device lock screen, enter the keystroke: **CTRL + ![Windows key](images/windows_glyph.png) + R**. - ![Enter CTRL+Windows key+R on the Windows lockscreen](images/autopilot-reset-lockscreen.png) + ![Enter CTRL+Windows key+R on the Windows lock screen](images/autopilot-reset-lockscreen.png) This will open up a custom login screen for the local Autopilot Reset. The screen serves two purposes: 1. Confirm/verify that the end user has the right to trigger Local Autopilot Reset