From cea9d904e636839312d0af0907f4f90b5b732963 Mon Sep 17 00:00:00 2001 From: Vijay Bellur Date: Tue, 22 May 2018 22:45:32 -0700 Subject: [PATCH] Update safely-drain-node.md (#8683) Fix a minor typo --- content/en/docs/tasks/administer-cluster/safely-drain-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/administer-cluster/safely-drain-node.md b/content/en/docs/tasks/administer-cluster/safely-drain-node.md index 495129fb43..cea4c00af0 100644 --- a/content/en/docs/tasks/administer-cluster/safely-drain-node.md +++ b/content/en/docs/tasks/administer-cluster/safely-drain-node.md @@ -75,7 +75,7 @@ afterwards to tell Kubernetes that it can resume scheduling new pods onto the no The `kubectl drain` command should only be issued to a single node at a time. However, you can run multiple `kubectl drain` commands for -different node in parallel, in different terminals or in the +different nodes in parallel, in different terminals or in the background. Multiple drain commands running concurrently will still respect the `PodDisruptionBudget` you specify.