From 214b137d8efa31bcb07b751962e46cfb549c37ff Mon Sep 17 00:00:00 2001
From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com>
Date: Fri, 28 Feb 2025 13:49:43 -0500
Subject: [PATCH] updates

---
 windows/configuration/assigned-access/toc.yml  | 4 ++--
 windows/configuration/shell-launcher/enable.md | 6 +++---
 windows/configuration/shell-launcher/toc.yml   | 2 +-
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/windows/configuration/assigned-access/toc.yml b/windows/configuration/assigned-access/toc.yml
index 96833cfc9a..658f482baf 100644
--- a/windows/configuration/assigned-access/toc.yml
+++ b/windows/configuration/assigned-access/toc.yml
@@ -9,6 +9,8 @@ items:
   href: configure-multi-app-kiosk.md
 - name: 🔴 Multi-app kiosk (merged ↖️)
   href: multi-app-kiosk.md
+- name: Recommendations
+  href: recommendations.md
 - name: Create a configuration file
   href: configuration-file.md
 - name: Quickstarts
@@ -17,8 +19,6 @@ items:
       href: quickstart-kiosk.md
     - name: Configure a multi-app kiosk
       href: quickstart-restricted-user-experience.md
-- name: Recommendations
-  href: recommendations.md
 - name: Reference
   items:
     - name: Assigned Access XSD
diff --git a/windows/configuration/shell-launcher/enable.md b/windows/configuration/shell-launcher/enable.md
index be6e4b76c8..ffeae5ffc9 100644
--- a/windows/configuration/shell-launcher/enable.md
+++ b/windows/configuration/shell-launcher/enable.md
@@ -8,9 +8,9 @@ ms.topic: how-to
 # Enable Shell Launcher
 
 > [!NOTE]
-> Configuring Shell Launcher using Assigned Access CSP, automatically enables Shell Launcher on the device, if the device supports it. There's no need to enable Shell Launcher separately if you configure it using Assigned Access CSP.
+> When you configure Shell Launcher with the Assigned Access Configuration Service Provider (CSP), Shell Launcher is automatically enabled, if the device supports it. There's no need to enable Shell Launcher separately when you configure it using Assigned Access CSP.
 
-Shell Launcher is an optional component and isn't turned on by default in Windows. It must be turned on prior to configuring. You can turn on and configure Shell Launcher in a customized Windows 10 image (.wim) if Microsoft Windows hasn't been installed. If Windows has already been installed, you must turn on Shell Launcher before applying a provisioning package to configure Shell Launcher.
+Shell Launcher is an optional component and isn't turned on by default in Windows. It must be turned on before configuring it. You can turn on and configure Shell Launcher in a customized Windows image, or you must turn on Shell Launcher before applying a provisioning package to configure Shell Launcher.
 
 ## Enable Shell Launcher using Control Panel
 
@@ -21,7 +21,7 @@ Shell Launcher is an optional component and isn't turned on by default in Window
 1. Select **Close** to close the **Windows Features** window.
 
 > [!NOTE]
-> Turning on Shell Launcher does not require a device restart.
+> Turning on Shell Launcher doesn't require a device restart.
 
 ## Enable Shell Launcher by calling WESL_UserSetting
 
diff --git a/windows/configuration/shell-launcher/toc.yml b/windows/configuration/shell-launcher/toc.yml
index 06459f5360..27a0e8b2c7 100644
--- a/windows/configuration/shell-launcher/toc.yml
+++ b/windows/configuration/shell-launcher/toc.yml
@@ -13,7 +13,7 @@ items:
   items:
     - name: Shell Launcher XSD
       href: xsd.md
-    - name: Enable Shell Launcher
+    - name: 🟡 Enable Shell Launcher
       href: enable.md
     - name: WMI Provider
       items: