From 0763ed3447e200b368e09d3546324a6c12bbc8b6 Mon Sep 17 00:00:00 2001
From: Razvan-Daniel Mihai <84674+razvan@users.noreply.github.com>
Date: Fri, 27 Sep 2024 10:46:46 -0400
Subject: [PATCH] Update
 docs/modules/hdfs/pages/usage-guide/operations/graceful-shutdown.adoc

---
 .../hdfs/pages/usage-guide/operations/graceful-shutdown.adoc    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/modules/hdfs/pages/usage-guide/operations/graceful-shutdown.adoc b/docs/modules/hdfs/pages/usage-guide/operations/graceful-shutdown.adoc
index 3f933b31..0fcce4ba 100644
--- a/docs/modules/hdfs/pages/usage-guide/operations/graceful-shutdown.adoc
+++ b/docs/modules/hdfs/pages/usage-guide/operations/graceful-shutdown.adoc
@@ -8,7 +8,7 @@ As a default, JournalNodes have `15 minutes` to shut down gracefully.
 
 The JournalNode process receives a `SIGTERM` signal when Kubernetes wants to terminate the Pod.
 It logs the received signal as shown in the log below and initiate a graceful shutdown.
-After the graceful shutdown timeout runs out, and the process still didn't exit, Kubernetes issues a `SIGKILL` signal.
+After the graceful shutdown timeout runs out, and the process is still running, Kubernetes issues a `SIGKILL` signal.
 
 https://github.com/apache/hadoop/blob/a585a73c3e02ac62350c136643a5e7f6095a3dbb/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/server/JournalNode.java#L272[This] is the relevant code that gets executed in the JournalNodes as of HDFS version `3.3.4`.