From d7b9833ea3d3dfcdf5a7beb9e4b8413664a1676d Mon Sep 17 00:00:00 2001 From: Jason Boxman Date: Wed, 20 Feb 2019 16:58:16 -0500 Subject: [PATCH] Fix typo in descheduler introduction - https://github.com/openshift/openshift-docs/issues/13684 --- admin_guide/scheduling/descheduler.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/admin_guide/scheduling/descheduler.adoc b/admin_guide/scheduling/descheduler.adoc index 1263393c921b..1f49b5f4ba04 100644 --- a/admin_guide/scheduling/descheduler.adoc +++ b/admin_guide/scheduling/descheduler.adoc @@ -18,7 +18,7 @@ onto more appropriate nodes. Your cluster can benefit from descheduling and rescheduling already-running pods for various reasons: * Nodes are under- or over-utilized. -* Pod and node affinity requirements, such as taints or labels, have changed and the original scheduling decisions are longer appropriate for certain nodes. +* Pod and node affinity requirements, such as taints or labels, have changed and the original scheduling decisions are no longer appropriate for certain nodes. * Node failure requires pods to be moved. * New nodes are added to clusters.