From aaecd9a743a14e41b51d52700cde8ae72391ea39 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Fri, 16 Feb 2024 14:14:18 +0100 Subject: [PATCH] Fix typos and update content in kiosk configuration guides --- .../assigned-access/assigned-access-quickstart-kiosk.md | 4 ++-- .../assigned-access/shell-launcher-quickstart-kiosk.md | 6 +++++- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/windows/configuration/assigned-access/assigned-access-quickstart-kiosk.md b/windows/configuration/assigned-access/assigned-access-quickstart-kiosk.md index ec52aa99a1..d0b6552de3 100644 --- a/windows/configuration/assigned-access/assigned-access-quickstart-kiosk.md +++ b/windows/configuration/assigned-access/assigned-access-quickstart-kiosk.md @@ -7,9 +7,9 @@ ms.date: 02/05/2024 # Quickstart: Configure a kiosk with Assigned Access -When you configure Windows as a *kiok*, you assign a single application to run above the lock screen. This is useful for public-facing scenarios, such as a digital sign or a public browser. +When you configure Windows as a *kisok*, you assign a single application to run above the lock screen. This is useful for public-facing scenarios, such as a digital sign or a public browser. -This quickstart provides practical examples of how to configure a kiosk experience on Windows. The examples describe the steps using the Settings app, a mobile device management solution (MDM) like Microsoft Intune, provisioning packages (PPKG), and PowerShell. While different solutions are used, the configuration settings and results are the same. +This quickstart provides practical examples of how to configure a kiosk experience on Windows with Assigne Access. The examples describe the steps using the Settings app, a mobile device management solution (MDM) like Microsoft Intune, provisioning packages (PPKG), and PowerShell. While different solutions are used, the configuration settings and results are the same. The examples can be modified to fit your specific requirements. For example, you can change the app used, the URL specified when opening Microsoft Edge, or change the name of the user that automatically signs in to Windows. diff --git a/windows/configuration/assigned-access/shell-launcher-quickstart-kiosk.md b/windows/configuration/assigned-access/shell-launcher-quickstart-kiosk.md index 4fa5834b8a..65749ec54d 100644 --- a/windows/configuration/assigned-access/shell-launcher-quickstart-kiosk.md +++ b/windows/configuration/assigned-access/shell-launcher-quickstart-kiosk.md @@ -7,7 +7,11 @@ ms.date: 02/05/2024 # Quickstart: configure a kiosk experience with Shell Launcher -This quickstart provides the information to configure a kiosk experience with Shell Launcher, using Windows Configuration Designer, Microsoft Intune, or PowerShell. +When you configure Windows as a *kisok*, you assign a single application to run above the lock screen. This is useful for public-facing scenarios, such as a digital sign or a public browser. + +This quickstart provides practical examples of how to configure a kiosk experience on Windows with Shell Launcher. The examples describe the steps using a mobile device management solution (MDM) like Microsoft Intune, and PowerShell. While different solutions are used, the configuration settings and results are the same. + +The examples can be modified to fit your specific requirements. For example, you can change the app used, the URL specified when opening Microsoft Edge, or change the name of the user that automatically signs in to Windows. ## Prerequisites