From f7558e55397cc84c7beab8a7735e677b09f31501 Mon Sep 17 00:00:00 2001
From: ImranHabib <47118050+joinimran@users.noreply.github.com>
Date: Thu, 31 Oct 2019 12:55:38 +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 16e5b256e2..91d3354350 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
@@ -363,7 +363,7 @@ Active Directory Federation Server used for Windows Hello for Business certifica
 Approximately 60 days prior to enrollment agent certificate’s expiration, the AD FS service attempts to renew the certificate until it is successful.  If the certificate fails to renew, and the certificate expires, the AD FS server will request a new enrollment agent certificate.  You can view the AD FS event logs to determine the status of the enrollment agent certificate.
 
 ### Service Connection Point (SCP) in Active Directory for ADFS Device Registration Service
->[!NOTE]
+> [!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.
 
 Now you will add the Service connection Point to ADFS device registration Service for your Active directory by running the following script: