diff --git a/README.md b/README.md
index 5ddcd37..689d9a4 100644
--- a/README.md
+++ b/README.md
@@ -851,7 +851,7 @@ web-2                                        1/1     Running       0          26
 ds-test-c6xx8                                1/1     Running       0          18m
 ds-test-w45dv                                1/1     Running       5          28h
 ```
-Kubernetes knows something like a `--pod-eviction-timeout`, which is a grace period (**default: 5 minutes**) for deleting pods on failed nodes. This timeout is useful to keep pods on nodes, which are rebooted in term of maintenance reasons. So, first of all, nothing happens to the pods on failed nodes until *pod eviction timeout* exceeded. If the *pod eviction period* times out, Kubernetes re-schedules *workloads* (Deployments, StatefulSets) to working nodes. *DaemonSets* will not be re-scheduled on other nodes at all.
+Kubernetes knows something like a `--pod-eviction-timeout`, which is a grace period (**default: 5 minutes**) for deleting pods on failed nodes. This timeout is useful to keep pods on nodes, which are rebooted in term of maintenance reasons. So, first of all, nothing happens to the pods on failed nodes until *pod eviction timeout* exceeded. If the *pod eviction period* times out, Kubernetes re-schedules *workloads* (Deployments, StatefulSets) to working nodes. As *DaemonSets* are bound to a specific node they will not be re-scheduled on other nodes.
 
 Docs: https://kubernetes.io/docs/concepts/scheduling-eviction/eviction-policy/