From f73f2f97e6e053617488c505e2e36962eff4c0ba Mon Sep 17 00:00:00 2001
From: Reece Peacock <49645174+Reeced40@users.noreply.github.com>
Date: Thu, 8 Aug 2019 08:21:28 +0200
Subject: [PATCH] Update
 windows/security/identity-protection/hello-for-business/hello-deployment-guide.md

Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com>
---
 .../hello-for-business/hello-deployment-guide.md                | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/identity-protection/hello-for-business/hello-deployment-guide.md b/windows/security/identity-protection/hello-for-business/hello-deployment-guide.md
index 99429b15fc..b011fa19f8 100644
--- a/windows/security/identity-protection/hello-for-business/hello-deployment-guide.md
+++ b/windows/security/identity-protection/hello-for-business/hello-deployment-guide.md
@@ -26,7 +26,7 @@ Windows Hello for Business is the springboard to a world without passwords. It r
 This deployment guide is to guide you through deploying Windows Hello for Business, based on the planning decisions made using the Planning a Windows Hello for Business Deployment Guide. It provides you with the information needed to successfully deploy Windows Hello for Business in an existing environment.
 
 > [!NOTE]
-> Two Azure AD Connect synchronisations are required in order for WHfB to begin working.
+> Two Azure AD Connect synchronizations are required in order for WHfB to begin working.
 > For more features, see [Windows Hello for Business Features](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-features#remote-desktop-with-biometrics).
 
 ## Assumptions