diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
index 59ddd17dbc..98125e3758 100644
--- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
+++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
@@ -159,7 +159,7 @@ once bound to a node, a Pod will never be rebound to another node.
 In general, Pods do not disappear until someone destroys them. This might be a
 human or a controller. The only exception to
 this rule is that Pods with a `phase` of Succeeded or Failed for more than some
-duration (determined by the master) will expire and be automatically destroyed.
+duration (determined by `terminated-pod-gc-threshold` in the master) will expire and be automatically destroyed.
 
 Three types of controllers are available: