From 266bc964d6a1c6b7d44d70538195b9afac497144 Mon Sep 17 00:00:00 2001
From: Meghan Stewart <33289333+mestew@users.noreply.github.com>
Date: Wed, 30 Oct 2024 13:50:44 -0700
Subject: [PATCH] Update windows/deployment/do/mcc-ent-troubleshooting.md

formatting tweak
---
 windows/deployment/do/mcc-ent-troubleshooting.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/windows/deployment/do/mcc-ent-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md
index 775261fe17..9c947c80fe 100644
--- a/windows/deployment/do/mcc-ent-troubleshooting.md
+++ b/windows/deployment/do/mcc-ent-troubleshooting.md
@@ -87,7 +87,8 @@ You can use Task Scheduler on the host machine to check the status of this sched
 1. Select the scheduled task **MCC_Monitor_Task**
 1. Select the **Triggers** tab and confirm that the Status is **Enabled**
 
-**Note**: If the password of the runtime account changes, you'll need to update the user in all of the Connected Cache scheduled tasks in order for the Connected Cache node to continue functioning properly.
+> [!Note]
+>  If the password of the runtime account changes, you'll need to update the user in all of the Connected Cache scheduled tasks in order for the Connected Cache node to continue functioning properly.
 
 ## Troubleshooting cache node deployment to Linux host machine