From 00425ef91f99ba177655531536d75a5dd22e954c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Igor=20Lon=C4=8Darevi=C4=87?=
 <44137847+carnivorelogic@users.noreply.github.com>
Date: Tue, 29 Nov 2022 19:08:49 +0100
Subject: [PATCH] Update memory-manager.md

Typo
---
 content/en/docs/tasks/administer-cluster/memory-manager.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/administer-cluster/memory-manager.md b/content/en/docs/tasks/administer-cluster/memory-manager.md
index 282c3e064a..d73c5c5ccc 100644
--- a/content/en/docs/tasks/administer-cluster/memory-manager.md
+++ b/content/en/docs/tasks/administer-cluster/memory-manager.md
@@ -92,7 +92,7 @@ illustrates how the management of groups occurs.
 
 ## Memory Manager configuration
 
-Other Managers should be first pre-configured. Next, the Memory Manger feature should be enabled
+Other Managers should be first pre-configured. Next, the Memory Manager feature should be enabled
 and be run with `Static` policy (section [Static policy](#policy-static)).
 Optionally, some amount of memory can be reserved for system or kubelet processes to increase
 node stability (section [Reserved memory flag](#reserved-memory-flag)).