From b5d4d883f30d9183400a69518f11efabe7f2bc9a Mon Sep 17 00:00:00 2001
From: ImranHabib <47118050+joinimran@users.noreply.github.com>
Date: Sun, 3 Nov 2019 09:50:05 +0500
Subject: [PATCH] Update
 windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md

Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com>
---
 .../hello-for-business/hello-cert-trust-adfs.md                 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md
index 0bceea2876..977d7b9dd5 100644
--- a/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md
+++ b/windows/security/identity-protection/hello-for-business/hello-cert-trust-adfs.md
@@ -364,7 +364,7 @@ Approximately 60 days prior to enrollment agent certificate’s expiration, the
 
 ### Service Connection Point (SCP) in Active Directory for ADFS Device Registration Service
 > [!NOTE]
-> Normally this script is not needed as enabling Device Registration via the ADFS Management console already creates the objects. You can validate the SCP using the below script.
+> Normally this script is not needed, as enabling Device Registration via the ADFS Management console already creates the objects. You can validate the SCP using the below script.
 
 Now you will add the Service connection Point to ADFS device registration Service for your Active directory by running the following script: