From 76f9a1b7853c5d38f3182773cef48844385259b3 Mon Sep 17 00:00:00 2001 From: Xiuyu Li Date: Fri, 3 Mar 2017 14:40:34 +0800 Subject: [PATCH] remove redundant a Signed-off-by: Xiuyu Li --- docs/user-guide/deployments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/deployments.md b/docs/user-guide/deployments.md index f2e854690e..d99909916c 100644 --- a/docs/user-guide/deployments.md +++ b/docs/user-guide/deployments.md @@ -621,7 +621,7 @@ See the [Kubernetes API conventions](https://github.com/kubernetes/community/blo Note that in version 1.5, Kubernetes will take no action on a stalled Deployment other than to report a status condition with `Reason=ProgressDeadlineExceeded`. -**Note:** If you pause a Deployment, Kubernetes does not check progress against your specified deadline. You can safely pause a Deployment in the middle of a rollout and resume without triggering a the condition for exceeding the deadline. +**Note:** If you pause a Deployment, Kubernetes does not check progress against your specified deadline. You can safely pause a Deployment in the middle of a rollout and resume without triggering the condition for exceeding the deadline. You may experience transient errors with your Deployments, either due to a low timeout that you have set or due to any other kind of error that can be treated as transient. For example, let's suppose you have insufficient quota. If you describe the Deployment