anchor.diff:  // Module included in the following assemblies:
   //
  -// * nodes/nodes-scheduler-taints-tolerations.adoc
  +// * nodes/scheduling/nodes-scheduler-taints-tolerations.adoc
   
   [id="nodes-scheduler-taints-tolerations-about_{context}"]
   = Understanding taints and tolerations
   
  -A _taint_ allows a node to refuse pod to be scheduled unless that pod has a matching _toleration_.
  -
  -You apply taints to a node through the node specification (`NodeSpec`) and apply tolerations to a pod through the pod specification (`PodSpec`). A taint on a node instructs the node to repel all pods that do not tolerate the taint.
  +A _taint_ allows a node to refuse Pod to be scheduled unless that Pod has a matching _toleration_.
  +
  +You apply taints to a node through the node specification (`NodeSpec`) and apply tolerations to a Pod through the Pod specification (`PodSpec`). A taint on a node instructs the node to repel all Pods that do not tolerate the taint.
   
   Taints and tolerations consist of a key, value, and effect. An operator allows you to leave one of these parameters empty.
   
  
positive.code:   tolerationSeconds: 3600
  ----
  
  Here, if this pod is running but does not have a matching taint, the pod stays bound to the node for 3,600 seconds and then be evicted. If the taint is removed before that time, the pod is not evicted.
  
  [id="nodes-scheduler-taints-tolerations-about-multiple_{context}"]
  == Understanding how to use multiple taints
  
  You can put multiple taints on the same node and multiple tolerations on the same pod. {product-title} processes multiple taints and tolerations as follows:
  
  . Process the taints for which the pod has a matching toleration.
  . The remaining unmatched taints have the indicated effects on the pod:
  +
  * If there is at least one unmatched taint with effect `NoSchedule`, {product-title} cannot schedule a pod onto that node.
  * If there is no unmatched taint with effect `NoSchedule` but there is at least one unmatched taint with effect `PreferNoSchedule`, {product-title} tries to not schedule the pod onto the node.
  * If there is at least one unmatched taint with effect `NoExecute`, {product-title} evicts the pod from the node (if it is already running on the node), or the pod is not scheduled onto the node (if it is not yet running on the node).
  +
  ** Pods that do not tolerate the taint are evicted immediately.
  +
  
negative.code: $ oc adm taint nodes node1 key2=value2:NoSchedule
  ----
  
  * The Pod has the following tolerations:
  +
  [source, yaml]
  ----
  