Refactor deployment and authentication sections

windows/security/identity-protection/hello-for-business/deploy/hybrid-cloud-kerberos-trust.md

@@ -12,13 +12,13 @@ ms.topic: tutorial
 [!INCLUDE [requirements](includes/requirements.md)]
 
 1. Deployment options
-  1. Deploment models
+    1. Deploment models
-  1. Trust types
+    1. Trust types
 1. Authentication
-  1. Device registration
+    1. Device registration
-  1. Key registration
+    1. Key registration
-  1. Directory synchronization
+    1. Directory synchronization
-  1. Multifactor authentication
+    1. Multifactor authentication
 1. Device configuration
 1. Public Key Infrastructure
 1. Licensing for cloud services

windows/security/identity-protection/hello-for-business/deploy/index.md

@@ -26,20 +26,20 @@ Read this document and record your decisions. When finished, you should have all
 
 There are 8 major categories to consider when planning a Windows Hello for Business deployment:
 
-- Deployment options
+1. Deployment options
-  - Deploment models
+    1. Deploment models
-  - Trust types
+    1. Trust types
-- Authentication
+1. Authentication
-  - Device registration
+    1. Device registration
-  - Key registration
+    1. Key registration
-  - Directory synchronization
+    1. Directory synchronization
-  - Multifactor authentication
+    1. Multifactor authentication
-- Device configuration
+1. Device configuration
-- Public Key Infrastructure
+1. Public Key Infrastructure
-- Licensing for cloud services
+1. Licensing for cloud services
-- Windows requirements
+1. Windows requirements
-- Windows Server requirements
+1. Windows Server requirements
-- Prepare users to use Windows Hello
+1. Prepare users to use Windows Hello
 
 ## Deployment Options
 

windows/security/identity-protection/hello-for-business/how-it-works.md

@@ -81,4 +81,8 @@ Changes to a user account password doesn't affect sign-in or unlock, since Windo
 
 - Certificate private keys can be protected by the Windows Hello container and the Windows Hello gesture.
 
-For details, see [How Windows Hello for Business works](hello-how-it-works.md).
+## Next steps
+
+> [!div class="nextstepaction"]
+>
+> [Learn how Windows Hello for Business works >](how-it-works.md)

windows/security/identity-protection/hello-for-business/index.md

@@ -167,11 +167,16 @@ If you only had a biometric sign-in configured and, for any reason, were unable
 
 Windows Hello for Business provisioning begins immediately after the user signs in, after the user profile is loaded, but before the user can access their desktop. Windows only launches the provisioning experience if all the prerequisite checks pass. If the prerequisites aren't met, Windows doesn't launch the provisioning experience and the user can't enroll in Windows Hello for Business.
 
-
-
 > [!NOTE]
 > You must allow access to the URL `account.microsoft.com` to initiate Windows Hello for Business provisioning. This URL launches the subsequent steps in the provisioning process and is required to successfully complete Windows Hello for Business provisioning. This URL doesn't require any authentication and as such, doesn't collect any user data.
 
+## Next steps
+
+> [!div class="nextstepaction"]
+>
+> [Plan a Windows Hello for Business Deployment](deploy/index.md)
+
+
 <!--
 
 ## Conditional access considerations