Update taint-and-toleration.md

fixed some typos

Author: maxakwu

content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md

@@ -220,7 +220,7 @@ are true. The following taints are built in:
     as unusable. After a controller from the cloud-controller-manager initializes
     this node, the kubelet removes this taint.
 
-In case a node is to be evicted, the node controller or the kubelet adds relevant taints
+In case a Pod is to be evicted, the node controller or the kubelet adds relevant taints
 with `NoExecute` effect. If the fault condition returns to normal the kubelet or node
 controller can remove the relevant taint(s).
 
@@ -230,7 +230,7 @@ the kubelet until communication with the API server is re-established. In the me
 the pods that are scheduled for deletion may continue to run on the partitioned node.
 
 {{< note >}}
-The control plane limits the rate of adding node new taints to nodes. This rate limiting
+The control plane limits the rate of adding new node taints to nodes. This rate limiting
 manages the number of evictions that are triggered when many nodes become unreachable at
 once (for example: if there is a network disruption).
 {{< /note >}}