diff --git a/content/en/docs/concepts/workloads/pods/disruptions.md b/content/en/docs/concepts/workloads/pods/disruptions.md
index 6725c887f4..b441213cb0 100644
--- a/content/en/docs/concepts/workloads/pods/disruptions.md
+++ b/content/en/docs/concepts/workloads/pods/disruptions.md
@@ -249,7 +249,7 @@ If you are a Cluster Administrator, and you need to perform a disruptive action
 the nodes in your cluster, such as a node or system software upgrade, here are some options:
 
 - Accept downtime during the upgrade.
-- Fail over to another complete replica cluster.
+- Failover to another complete replica cluster.
    -  No downtime, but may be costly both for the duplicated nodes,
      and for human effort to orchestrate the switchover.
 - Write disruption tolerant applications and use PDBs.