From 22b6f743f5d027bfce819ac268013b881e94bc82 Mon Sep 17 00:00:00 2001 From: Fawaz Mohammed Date: Sat, 28 Oct 2017 12:57:42 +0400 Subject: [PATCH] A typo fixed --- docs/concepts/workloads/pods/disruptions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/workloads/pods/disruptions.md b/docs/concepts/workloads/pods/disruptions.md index e1af0e4382..f19e179692 100644 --- a/docs/concepts/workloads/pods/disruptions.md +++ b/docs/concepts/workloads/pods/disruptions.md @@ -81,7 +81,7 @@ no voluntary disruptions at all. However, your cluster administrator or hosting may run some additional services which cause voluntary disruptions. For example, rolling out node software updates can cause voluntary disruptions. Also, some implementations of cluster (node) autoscaling may cause voluntary disruptions to defragment and compact nodes. -You cluster administrator or hosting provider should have documented what level of voluntary +Your cluster administrator or hosting provider should have documented what level of voluntary disruptions, if any, to expect. Kubernetes offers features to help run highly available applications at the same