From de82a8820e2dcf3ef221682aa9c112b7f4838f5d Mon Sep 17 00:00:00 2001 From: Rui Cao Date: Thu, 27 Sep 2018 22:08:57 +0800 Subject: [PATCH] Fix typo: speficied -> specified (#10395) Signed-off-by: Rui Cao --- content/en/docs/concepts/configuration/assign-pod-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/configuration/assign-pod-node.md b/content/en/docs/concepts/configuration/assign-pod-node.md index b7f88ffbb4..1bb887fa52 100644 --- a/content/en/docs/concepts/configuration/assign-pod-node.md +++ b/content/en/docs/concepts/configuration/assign-pod-node.md @@ -178,7 +178,7 @@ in the section [Interlude: built-in node labels](#interlude-built-in-node-labels processing which can slow down scheduling in large clusters significantly. We do not recommend using them in clusters larger than several hundred nodes. -**Note:** Pod anti-affinity requires nodes to be consistently labelled, i.e. every node in the cluster must have an appropriate label matching `topologyKey`. If some or all nodes are missing the speficied `topologyKey` label, it can lead to unintended behavior. +**Note:** Pod anti-affinity requires nodes to be consistently labelled, i.e. every node in the cluster must have an appropriate label matching `topologyKey`. If some or all nodes are missing the specified `topologyKey` label, it can lead to unintended behavior. As with node affinity, there are currently two types of pod affinity and anti-affinity, called `requiredDuringSchedulingIgnoredDuringExecution` and `preferredDuringSchedulingIgnoredDuringExecution` which denote "hard" vs. "soft" requirements.