From 3e80f2b5777a6ba91c4f8701338bdb1045212e83 Mon Sep 17 00:00:00 2001
From: botmoto <42125490+botmoto@users.noreply.github.com>
Date: Thu, 9 May 2019 04:57:14 -0700
Subject: [PATCH] Update credential-guard-manage.md

Cosmetic formatting
---
 .../credential-guard/credential-guard-manage.md                | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/windows/security/identity-protection/credential-guard/credential-guard-manage.md b/windows/security/identity-protection/credential-guard/credential-guard-manage.md
index e02b561b04..59b6865e4e 100644
--- a/windows/security/identity-protection/credential-guard/credential-guard-manage.md
+++ b/windows/security/identity-protection/credential-guard/credential-guard-manage.md
@@ -128,8 +128,7 @@ DG_Readiness_Tool_v3.5.ps1 -Ready
 ```
 
 > [!NOTE]
-
-For client machines that are running Windows 10 1703, LsaIso.exe is running whenever virtualization-based security is enabled for other features.
+> For client machines that are running Windows 10 1703, LsaIso.exe is running whenever virtualization-based security is enabled for other features.
 
 -   We recommend enabling Windows Defender Credential Guard before a device is joined to a domain. If Windows Defender Credential Guard is enabled after domain join, the user and device secrets may already be compromised. In other words, enabling Credential Guard will not help to secure a device or identity that has already been compromised, which is why we recommend turning on Credential Guard as early as possible.