From f9fe0bacd05dec56e748025e0709036dcf2549f3 Mon Sep 17 00:00:00 2001
From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com>
Date: Fri, 24 Jan 2020 09:45:35 +0500
Subject: [PATCH] Update hello-hybrid-key-whfb-settings-pki.md

---
 .../hello-for-business/hello-hybrid-key-whfb-settings-pki.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-pki.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-pki.md
index 41d11386b2..d15d87fde6 100644
--- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-pki.md
+++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-pki.md
@@ -78,7 +78,7 @@ Sign-in a certificate authority or management workstations with _Enterprise Admi
 The certificate template is configured to supersede all the certificate templates provided in the certificate templates superseded templates list.  However, the certificate template and the superseding of certificate templates is not active until you publish the certificate template to one or more certificate authorities.
 
 >[!NOTE]
->The Domain Controller Certificate must be present in the NTAuth store. By default, Microsoft Enterprise CAs are added to the NTAuth store. If you are using a 3rd party CA, this may not be done by default. If the Domain Controller Certificate is not present in the NTAuth store, user authentication will fail. 
+>The root certificate of the certification authority must be present in the NTAuth store. By default, Active Directory Certificate Authority's root certificate is added to the NTAuth store. If you are using a 3rd party CA, this may not be done by default. If the certificate authority's root certificate is not present in the NTAuth store, user authentication will fail. 
 
 ### Publish Certificate Templates to a Certificate Authority