From 250089d828d765c881cb41693a911bf249907ea8 Mon Sep 17 00:00:00 2001
From: Orlando Rodriguez <49177883+ojrb@users.noreply.github.com>
Date: Mon, 13 May 2019 11:58:41 -0500
Subject: [PATCH] Update
 windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md

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

diff --git a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md
index 2e9bd1375c..cfa4d2724c 100644
--- a/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md
+++ b/windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md
@@ -60,7 +60,7 @@ Key trust deployments do not need client issued certificates for on-premises aut
 
 The minimum required enterprise certificate authority that can be used with Windows Hello for Business is Windows Server 2012, but you can also use a third-party enterprise certification authority. The detailed requirements for the Domain Controller certificate are shown below.
 
-* The certificate must have a CRL distribution-point extension that points to a valid certificate revocation list (CRL).
+* The certificate must have a Certificate Revocation List (CRL) distribution point extension that points to a valid CRL.
 * Optionally, the certificate Subject section should contain the directory path of the server object (the distinguished name) 
 * The certificate Key Usage section must contain:
 Digital Signature, Key Encipherment