From a566046166f4760a620f4ece72ce1d410aad036e Mon Sep 17 00:00:00 2001
From: Vivek Thomas <varkey@varkey.in>
Date: Wed, 4 May 2022 17:26:46 +0530
Subject: [PATCH] Update probe-level grace period behaviour in 1.22

---
 .../configure-liveness-readiness-startup-probes.md              | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
index b26baabe9e..66de8ae700 100644
--- a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
+++ b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
@@ -506,7 +506,7 @@ those existing Pods.
 
 When you (or the control plane, or some other component) create replacement
 Pods, and the feature gate `ProbeTerminationGracePeriod` is disabled, then the
-API server ignores the Pod-level `terminationGracePeriodSeconds` field, even if
+API server ignores the Probe-level `terminationGracePeriodSeconds` field, even if
 a Pod or pod template specifies it.
 {{< /note >}}