From 568036158373020b847c9c9bce9b730e0e983573 Mon Sep 17 00:00:00 2001
From: ayushpatil2122 <112652819+ayushpatil2122@users.noreply.github.com>
Date: Fri, 13 Sep 2024 11:46:20 +0530
Subject: [PATCH] Update garbage-collection.md

---
 content/en/docs/concepts/architecture/garbage-collection.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/content/en/docs/concepts/architecture/garbage-collection.md b/content/en/docs/concepts/architecture/garbage-collection.md
index d6ac44a652b58..d9ca70f796219 100644
--- a/content/en/docs/concepts/architecture/garbage-collection.md
+++ b/content/en/docs/concepts/architecture/garbage-collection.md
@@ -144,9 +144,8 @@ until disk usage reaches the `LowThresholdPercent` value.
 As a beta feature, you can specify the maximum time a local image can be unused for,
 regardless of disk usage. This is a kubelet setting that you configure for each node.
 
-To configure the setting, enable the `ImageMaximumGCAge`
-[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the kubelet,
-and also set a value for the `imageMaximumGCAge` field in the kubelet configuration file.
+To configure the setting, you need to set a value for the `imageMaximumGCAge` 
+field in the kubelet configuration file.
 
 The value is specified as a Kubernetes _duration_; 
 Valid time units for the `imageMaximumGCAge` field in the kubelet configuration file are: