updates

windows/configuration/shell-launcher/browser-support.md

@@ -4,10 +4,7 @@ author: TerryWarwick
 ms.author: twarwick
 ms.date: 03/30/2023
 ms.topic: article
-ms.service: windows-iot
-ms.subservice: iot
 description: Learn about browser support in Kiosk Mode
-keywords: Lockdown, Kiosks, Kiosk Mode, Browser
 ---
 
 # Browser Support
@@ -38,7 +35,7 @@ In anticipation of that, you can use [Internet Explorer (IE) mode](/deployedge/e
 
 ## Supported Versions
 
-| Browser | ![Internet Explorer 11](./media/IE11.png) | ![Microsoft Edge Legacy](./media/Microsoft-Edge-Legacy.png) | ![New Microsoft Edge](./media/Microsoft-Edge-New.png) |
+| Browser | Internet Explorer 11 | Microsoft Edge Legacy | Microsoft Edge |
 |--|--|--|--|
 | OS Release | [IE11 App](/internet-explorer/internet-explorer) | [Edge Browser - Legacy](/deployedge/microsoft-edge-kiosk-mode-transition-plan) | [New Edge Browser](/deployedge/microsoft-edge-configure-kiosk-mode) |
 | Windows 10 IoT Enterprise LTSC 2019 | [Follows OS Release Support Lifecycle](/lifecycle/products/windows-10-iot-enterprise-ltsc-2019) | No browser security updates after March, 9, 2021 (removed where applicable). In-box engine supported until OS EOL | Edge and WebView2 Runtime not in-box (requires app migration from EdgeHTML) |

windows/configuration/shell-launcher/index.md

@@ -23,7 +23,7 @@ There are a few exceptions to the applications and executables you can use as a
 
 - You can't use the following executable as a custom shell: `C:\\Windows\\System32\\Eshell.exe`. Using Eshell.exe as the default shell will result in a blank screen after user signs in.
 - You can't use a Universal Windows app as a custom shell.
-- You can't use a custom shell to launch Universal Windows apps, for example, the Settings app.  
+- You can't use a custom shell to launch Universal Windows apps, for example, the Settings app.
 - You can't use an application that launches a different process and exits as a custom shell. For example, you can't specify **write.exe** in Shell Launcher. Shell Launcher launches a custom shell and monitors the process to identify when the custom shell exits. **Write.exe** creates a 32-bit wordpad.exe process and exits. Because Shell Launcher isn't aware of the newly created wordpad.exe process, Shell Launcher takes action based on the exit code of **Write.exe**, and restart the custom shell.
 - You can't prevent the system from shutting down. For Shell Launcher V1 and V2, you can't block the session ending by returning FALSE upon receiving the [WM_QUERYENDSESSION](/windows/win32/shutdown/wm-queryendsession) message in a graphical application or returning FALSE in the [handler routine](/windows/console/handlerroutine) that is added through the [SetConsoleCtrlHandler](/windows/console/setconsolectrlhandler) function in a console application.
 
@@ -32,7 +32,7 @@ There are a few exceptions to the applications and executables you can use as a
 >
 > Use **Shell Launcher V2**, you can specify a Universal Windows app as a custom shell.  Check [Use Shell Launcher to create a Windows 10 kiosk](/windows/configuration/kiosk-shelllauncher) for the differences between Shell Launcher v1 and Shell Launcher V2.
 
-Shell Launcher processes the **Run** and **RunOnce** registry keys before starting the custom shell, so your custom shell doesn’t need to handle the automatic startup of other applications and services.
+Shell Launcher processes the **Run** and **RunOnce** registry keys before starting the custom shell, so your custom shell doesn't need to handle the automatic startup of other applications and services.
 
 Shell Launcher also handles the behavior of the system when your custom shell exits. You can configure the shell exit behavior if the default behavior doesn't meet your needs.
 
@@ -52,7 +52,7 @@ In addition to allowing you to use a UWP app for your replacement shell, Shell L
 
 - You can use a custom Windows desktop application that can then launch UWP apps, such as Settings and Touch Keyboard.
 - From a custom UWP shell, you can launch secondary views and run on multiple monitors.
-- The custom shell app runs in full screen, and can run other apps in full screen on user’s demand.
+- The custom shell app runs in full screen, and can run other apps in full screen on user's demand.
 For sample XML configurations for the different app combinations, see [Samples for Shell Launcher v2](https://github.com/microsoft/Windows-IoT-Samples/tree/master/samples/ShellLauncher/ShellLauncherV2).
 
 ## Requirements
@@ -253,7 +253,7 @@ $NAMESPACE = "root\standardcimv2\embedded"
 try {
     $ShellLauncherClass = [wmiclass]"\\$COMPUTER\${NAMESPACE}:WESL_UserSetting"
     } catch [Exception] {
-    write-host $_.Exception.Message; 
+    write-host $_.Exception.Message;
     write-host "Make sure Shell Launcher feature is enabled"
     exit
     }
@@ -286,7 +286,7 @@ $do_nothing = 3
 
 # Examples. You can change these examples to use the program that you want to use as the shell.
 
-# This example sets the command prompt as the default shell, and restarts the device if the command prompt is closed. 
+# This example sets the command prompt as the default shell, and restarts the device if the command prompt is closed.
 
 $ShellLauncherClass.SetDefaultShell("cmd.exe", $restart_device)
 
@@ -344,8 +344,8 @@ A custom shell is launched with the same level of user rights as the account tha
 
 ## Related articles
 
-- [Unbranded Boot](unbranded-boot.md)
-- [Custom Logon](custom-logon.md)
+- [Unbranded Boot](../unbranded-boot/index.md)
+- [Custom Logon](../custom-logon/index.md)
 - [Use Shell Launcher to create a Windows 10 Kiosk](/windows/configuration/kiosk-shelllauncher)
 - [Launch different shells for different user accounts](/windows-hardware/customize/enterprise/shell-launcher#launch-different-shells-for-different-user-accounts)
 - [Perform an action when the shell exits](/windows-hardware/customize/enterprise/shell-launcher#perform-an-action-when-the-shell-exits)

windows/configuration/shell-launcher/multi-app-kiosk.md

@@ -15,13 +15,13 @@ keywords: Lockdown, Multi-App, Kiosk
 An assigned access multi-app kiosk runs one or more apps from the desktop. People using the kiosk see a customized Start that shows only the tiles for the apps that are allowed. With this approach, you can configure a locked-down experience for different account types. A multi-app kiosk is appropriate for devices that are shared by multiple people. Here's a [guide](/windows/configuration/lock-down-windows-10-to-specific-apps) on how to set up a multi-app kiosk.
 
 > [!NOTE]
-> Multi-app kiosk mode is not available for Windows 11 IoT Enterprise, version 21H2 or 22H2.  Please refer to [What's new for subsequent releases](../whats-new/Release-History.md#windows-11-iot-enterprise) for information about its return.
+> Multi-app kiosk mode is not available for Windows 11 IoT Enterprise, version 21H2 or 22H2.  Please refer to [What's new for subsequent releases](/windows/iot/iot-enterprise/whats-new/release-history#windows-11-iot-enterprise) for information about its return.
 >
 > **Update** - [Multi-app kiosk mode is now available in Windows 11](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/multi-app-kiosk-mode-now-available-in-windows-11/ba-p/3845558)., version 22H2 as part of the Windows continuous innovation releases.  To learn how you can take advantage of features introduced via Windows continuous innovation, see more about how you can access this feature in Windows 11 IoT Enterprise, version 22H2, see [Delivering continuous innovation in Windows 11](https://support.microsoft.com/windows/delivering-continuous-innovation-in-windows-11-b0aa0a27-ea9a-4365-9224-cb155e517f12).
 
 ## Benefits of using a multi-app kiosk
 
-The benefit of a kiosk that runs multiple specified apps is to provide an easy-to-understand experience for individuals by showing them only the things they need to use, and removing the things they don’t need to access.
+The benefit of a kiosk that runs multiple specified apps is to provide an easy-to-understand experience for individuals by showing them only the things they need to use, and removing the things they don't need to access.
 
 A multi-app kiosk is appropriate for devices that are shared by multiple people. Each user can authenticate with the device and receive a customized lockdown experience based on the configuration.
 

windows/configuration/shell-launcher/wesl-usersettingsetenabled.md

@@ -36,7 +36,7 @@ Returns an HRESULT value that indicates [WMI status](/windows/win32/wmisdk/wmi-n
 
 ## Remarks
 
-This method enables or disables Shell Launcher by modifying the **Shell** value in the registry key **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon**. If Unified Write Filter (UWF) is enabled, you may need to disable UWF or commit this registry key by using [UWF_RegistryFilter.CommitRegistry](uwf-registryfiltercommitregistry.md) in order to enable or disable Shell Launcher.
+This method enables or disables Shell Launcher by modifying the **Shell** value in the registry key `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon`. If Unified Write Filter (UWF) is enabled, you may need to disable UWF or commit this registry key by using [UWF_RegistryFilter.CommitRegistry](uwf-registryfiltercommitregistry.md) in order to enable or disable Shell Launcher.
 
 Enabling or disabling Shell Launcher does not take effect until a user signs in.