diff --git a/docs/modules/hbase/pages/usage-guide/operations/graceful-shutdown.adoc b/docs/modules/hbase/pages/usage-guide/operations/graceful-shutdown.adoc
index b06864a7..6394aeb2 100644
--- a/docs/modules/hbase/pages/usage-guide/operations/graceful-shutdown.adoc
+++ b/docs/modules/hbase/pages/usage-guide/operations/graceful-shutdown.adoc
@@ -4,7 +4,7 @@ You can configure the graceful shutdown as described in xref:concepts:operations
 
 == Masters
 
-As a default, masters have `20` minutes to terminate gracefully.
+As a default, masters have `20 minutes` to terminate gracefully.
 
 The HBase master process will always run as PID `1` and will get a `SIGTERM` once Kubernetes wants to terminate the Pod.
 After the graceful shutdown timeout is passed and the master process still didn't exit, Kubernetes will issue an `SIGKILL`.
@@ -15,7 +15,7 @@ However, there is no acknowledge message in the log indicating a graceful shutdo
 
 == RegionServers
 
-As a default, RegionServers have `60` minutes to terminate gracefully.
+As a default, RegionServers have `60 minutes` to terminate gracefully.
 
 They go through the same mechanism as documented for the <<_masters>> above.
 They will also acknowledge the graceful shutdown with a message in the logs:
@@ -28,7 +28,7 @@ They will also acknowledge the graceful shutdown with a message in the logs:
 
 == RestServers
 
-As a default, RestServers have `5` minutes to terminate gracefully.
+As a default, RestServers have `5 minutes` to terminate gracefully.
 
 They go through the same mechanism as documented for the <<_masters>> above.
 They will also acknowledge the graceful shutdown with a message in the logs: