diff --git a/akka-docs/src/main/paradox/coordinated-shutdown.md b/akka-docs/src/main/paradox/coordinated-shutdown.md
index c949a377f9b..fa27ba621d1 100644
--- a/akka-docs/src/main/paradox/coordinated-shutdown.md
+++ b/akka-docs/src/main/paradox/coordinated-shutdown.md
@@ -104,7 +104,7 @@ akka.coordinated-shutdown.run-by-jvm-shutdown-hook=off
 Note that if running in Kubernetes, a SIGKILL will be issued after a set amount of time has passed
 since SIGTERM.  By default this time is 30 seconds ([`terminationGracePeriodSeconds`](https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#hook-handler-execution)):
 it may be worth adjusting the Kubernetes configuration or the phase timeouts to make `CoordinatedShutdown`
-more likely to completely exectue before SIGKILL is received.
+more likely to completely execute before SIGKILL is received.
 
 If you have application specific JVM shutdown hooks it's recommended that you register them via the
 `CoordinatedShutdown` so that they are running before Akka internal shutdown hooks, e.g.