From a4f5548b00fd516770dc92e05c18719648dce9a2 Mon Sep 17 00:00:00 2001
From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com>
Date: Wed, 6 Mar 2024 09:41:11 -0500
Subject: [PATCH] Update prerequisites description in how-it-works.md

---
 .../identity-protection/hello-for-business/how-it-works.md      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/identity-protection/hello-for-business/how-it-works.md b/windows/security/identity-protection/hello-for-business/how-it-works.md
index 74131ef057..c4c40ed7e9 100644
--- a/windows/security/identity-protection/hello-for-business/how-it-works.md
+++ b/windows/security/identity-protection/hello-for-business/how-it-works.md
@@ -105,7 +105,7 @@ For detailed sequence diagrams, see [how device registration works][ENTRA-4].
 > - The Windows Hello for Business policy is enabled
 > - The user is not connected to the machine via Remote Desktop
 >
-> Additional prerequisites are required for specific deployment types, as described in the article [Plan a Windows Hello for Business deployment](deploy/index.md).
+> Additional prerequisites for specific deployment types are described in the article [Plan a Windows Hello for Business deployment](deploy/index.md).
 
 
 During the provisioning phase, a *Windows Hello container* is created. A Windows Hello container is a logical grouping of *key material*, or data. The container holds organization's credentials only on devices that are *registered* with the organization's IdP.