diff --git a/windows/configuration/assigned-access/quickstart-kiosk.md b/windows/configuration/assigned-access/quickstart-kiosk.md
index 25d10bffc6..ba0216d025 100644
--- a/windows/configuration/assigned-access/quickstart-kiosk.md
+++ b/windows/configuration/assigned-access/quickstart-kiosk.md
@@ -61,8 +61,6 @@ Here are the steps to configure a kiosk using the Settings app:
 
 [!INCLUDE [quickstart-kiosk-intune](includes/quickstart-kiosk-intune.md)]
 
-[!INCLUDE [intune-custom-settings-2](../../../includes/configure/intune-custom-settings-2.md)]
-
 Alternatively, you can configure devices using a [custom policy][MEM-1] with the [AssignedAccess CSP][WIN-3].
 
 - **Setting:** `./Vendor/MSFT/AssignedAccess/Configuration`
@@ -70,6 +68,8 @@ Alternatively, you can configure devices using a [custom policy][MEM-1] with the
 
 [!INCLUDE [quickstart-kiosk-xml](includes/quickstart-kiosk-xml.md)]
 
+Assign the policy to a group that contains as members the devices that you want to configure.
+
 #### [:::image type="icon" source="../images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
 
 [!INCLUDE [provisioning-package-1](../../../includes/configure/provisioning-package-1.md)]
@@ -102,7 +102,7 @@ After the settings are applied, reboot the device. A local user account is autom
 >
 > [Assigned Access overview](overview.md)
 
-<!--links-->
+
 
 [WIN-3]: /windows/client-management/mdm/assignedaccess-csp
 [MEM-1]: /mem/intune/configuration/custom-settings-windows-10
diff --git a/windows/configuration/assigned-access/shell-launcher/index.md b/windows/configuration/assigned-access/shell-launcher/index.md
index 64f6dcb122..ee76caf41d 100644
--- a/windows/configuration/assigned-access/shell-launcher/index.md
+++ b/windows/configuration/assigned-access/shell-launcher/index.md
@@ -53,6 +53,8 @@ You can configure devices using a [custom policy][MEM-1] with the [AssignedAcces
 - **Setting:** `./Vendor/MSFT/AssignedAccess/ShellLauncher`
 - **Value:** content of the XML configuration file
 
+Assign the policy to a group that contains as members the devices that you want to configure.
+
 #### [:::image type="icon" source="../../images/icons/provisioning-package.svg"::: **PPKG**](#tab/ppkg)
 
 [!INCLUDE [provisioning-package-1](../../../../includes/configure/provisioning-package-1.md)]
@@ -93,6 +95,10 @@ Depending on your configuration, you can have a user to automatically sign in to
 ## Next steps
 
 > [!div class="nextstepaction"]
-> To learn how to configure the Shell Launcher XML file:
+> Learn how to configure the Shell Launcher XML file:
 >
 > [Create a Shell Launcher configuration file](configuration-file.md)
+
+<!--links-->
+
+[MEM-1]: /mem/intune/configuration/custom-settings-windows-10
\ No newline at end of file
diff --git a/windows/configuration/assigned-access/shell-launcher/quickstart-kiosk.md b/windows/configuration/assigned-access/shell-launcher/quickstart-kiosk.md
index 6eda3d5b51..0fd185766c 100644
--- a/windows/configuration/assigned-access/shell-launcher/quickstart-kiosk.md
+++ b/windows/configuration/assigned-access/shell-launcher/quickstart-kiosk.md
@@ -35,7 +35,7 @@ The examples can be modified to fit your specific requirements. For example, you
 
 [!INCLUDE [quickstart-intune](includes/quickstart-intune.md)]
 
-[!INCLUDE [intune-custom-settings-2](../../../../includes/configure/intune-custom-settings-2.md)]
+Assign the policy to a group that contains as members the devices that you want to configure.
 
 Alternatively, you can configure devices using a [custom policy][MEM-1] with the [AssignedAccess CSP][WIN-3].