From fd16a9a072b60233528a081850c043c11fba3d65 Mon Sep 17 00:00:00 2001
From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com>
Date: Mon, 12 Apr 2021 22:38:39 +0500
Subject: [PATCH] Update windows/client-management/introduction-page-file.md

Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
 windows/client-management/introduction-page-file.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/client-management/introduction-page-file.md b/windows/client-management/introduction-page-file.md
index 53ff0d9764..c5fd6c874c 100644
--- a/windows/client-management/introduction-page-file.md
+++ b/windows/client-management/introduction-page-file.md
@@ -66,5 +66,5 @@ The system commit charge is the total committed or "promised" memory of all comm
 
 The system committed charge and system committed limit can be measured on the **Performance** tab in Task Manager or by using the "\Memory\Committed Bytes" and "\Memory\Commit Limit" performance counters. The \Memory\% Committed Bytes In Use counter is a ratio of \Memory\Committed Bytes to \Memory\Commit Limit values.
 
->[!Note]
+> [!NOTE]
 >System-managed page files automatically grow up to three times the physical memory or 4 GB (whichever is larger, but no more than 1/8 of the volume size) when the system commit charge reaches 90 percent of the system commit limit. This assumes that enough free disk space is available to accommodate the growth.