Fixes

windows/security/identity-protection/hello-for-business/feature-multifactor-unlock.md

@@ -279,7 +279,8 @@ The Group Policy object contains the policy settings needed to trigger Windows H
  ## Troubleshooting
 Mulitfactor unlock writes events to event log under **Application and Services Logs\Microsoft\Windows\HelloForBusiness** with the category name **Device Unlock**.
 
-**Events **
+### Events
+
 |Event ID|Details|
 |:********:|:*******|
 |3520|Unlock attempt initiated|
@@ -287,3 +288,5 @@ Mulitfactor unlock writes events to event log under **Application and Services L
 |6520|Warning event|
 |7520|Error event|
 |8520|Success event| 
+
+

windows/security/identity-protection/hello-for-business/hello-cert-trust-deploy-mfa.md

@@ -6,10 +6,10 @@ ms.prod: w10
 ms.mktglfcycl: deploy
 ms.sitesec: library
 ms.pagetype: security, mobile
-author: DaniHalfin
-ms.localizationpriority: high
-ms.author: daniha
-ms.date: 07/27/2017
+author: mikestephens-MS
+ms.author: mstephen
+localizationpriority: high
+ms.date: 03/5/2018
 ---
 # Configure or Deploy Multifactor Authentication Services
 
@@ -523,7 +523,7 @@ Before you continue with the deployment, validate your deployment progress by re
 * Confirm you saved the changes to the web.config file.
 * Confirm you restarted the AD FS Service after completing the configuration.
 
-## Test AD FS with the Multifactor Authentication connector
+## Test Multifactor Authentication
 
 Now, you should test your Azure Multi-Factor Authentication server configuration before proceeding any further in the deployment.  The AD FS and Azure Multi-Factor Authentication server configurations are complete.