diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml
index d5071f8114..38e5eeab4c 100644
--- a/windows/deployment/windows-autopatch/TOC.yml
+++ b/windows/deployment/windows-autopatch/TOC.yml
@@ -58,10 +58,10 @@
               href: operate/windows-autopatch-teams.md
         - name: Deregister a device
           href: operate/windows-autopatch-deregister-devices.md
-        - name: Un-enroll your tenant
-          href: operate/windows-autopatch-unenroll-tenant.md
         - name: Submit a support request
           href: operate/windows-autopatch-support-request.md
+        - name: Un-enroll your tenant
+          href: operate/windows-autopatch-unenroll-tenant.md
     - name: Reference
       href:
       items:
diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
index f6dc54cf8d..5a53ee749f 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -125,7 +125,7 @@ Registering your devices in Windows Autopatch does the following:
 Once devices or Azure AD groups containing devices are added to the **Windows Autopatch Device Registration** group, Windows Autopatch discovers these devices and runs software-based prerequisite checks to try to register them with its service.
 
 > [!IMPORTANT]
-> It might take up to an hour for a device to change its status from **Ready for User** to **Active** in the Ready tab during the public preview.
+> It might take up to an hour for a device to change its status from **Ready for User** to **Active** in the Ready tab.
 
 ## Device management lifecycle scenarios