diff --git a/docs/concepts/workloads/pods/disruptions.md b/docs/concepts/workloads/pods/disruptions.md
index 4d2e752626..d0a6fb93b1 100644
--- a/docs/concepts/workloads/pods/disruptions.md
+++ b/docs/concepts/workloads/pods/disruptions.md
@@ -32,7 +32,7 @@ an application.  Examples are:
 - cluster administrator deletes VM (instance) by mistake
 - cloud provider or hypervisor failure makes VM disappear
 - a kernel panic
-- if the node to disappears from the cluster due to cluster network partition
+- the node disappears from the cluster due to cluster network partition
 - eviction of a pod due to the node being [out-of-resources](/docs/tasks/administer-cluster/out-of-resource/).
 
 Except for the out-of-resources condition, all these conditions
@@ -145,7 +145,7 @@ Initially, the pods are laid out as follows:
 | pod-a  *available*   | pod-b *available*   | pod-c *available*  |
 | pod-x  *available*   |                     |                    |
 
-All 3 pods are part of an deployment, and they collectively have a PDB which requires
+All 3 pods are part of a deployment, and they collectively have a PDB which requires
 there be at least 2 of the 3 pods to be available at all times.
 
 For example, assume the cluster administrator wants to reboot into a new kernel version to fix a bug in the kernel.
@@ -174,7 +174,7 @@ Now the cluster is in this state:
 | pod-a  *terminating* | pod-b *available*   | pod-c *available*  |
 | pod-x  *terminating* | pod-d *starting*    | pod-y              |
 
-At some point, the pods terminate, and the cluster look like this:
+At some point, the pods terminate, and the cluster looks like this:
 
 |    node-1 *drained*  |       node-2        |       node-3       |
 |:--------------------:|:-------------------:|:------------------:|