From aeb36c0c72a226625435ab4a0b8f3995b6526b60 Mon Sep 17 00:00:00 2001
From: steve-hardman <132999137+steve-hardman@users.noreply.github.com>
Date: Sat, 20 Apr 2024 00:16:58 +0100
Subject: [PATCH] Fixed the featue state in pod-qos.md

---
 content/en/docs/concepts/workloads/pods/pod-qos.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/workloads/pods/pod-qos.md b/content/en/docs/concepts/workloads/pods/pod-qos.md
index e656208958..b164b02206 100644
--- a/content/en/docs/concepts/workloads/pods/pod-qos.md
+++ b/content/en/docs/concepts/workloads/pods/pod-qos.md
@@ -87,7 +87,7 @@ Containers in a Pod can request other resources (not CPU or memory) and still be
 
 ## Memory QoS with cgroup v2
 
-{{< feature-state feature-gate-name="MemoryQoS" >}}
+{{< feature-state feature_gate_name="MemoryQoS" >}}
 
 Memory QoS uses the memory controller of cgroup v2 to guarantee memory resources in Kubernetes.
 Memory requests and limits of containers in pod are used to set specific interfaces `memory.min`