From 13b6ea0707cefd294376141860adc9fc9597148e Mon Sep 17 00:00:00 2001 From: XsWack Date: Thu, 10 Aug 2017 14:51:34 +0800 Subject: [PATCH] Update jobs-run-to-completion.md fix typo --- docs/concepts/workloads/controllers/jobs-run-to-completion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/workloads/controllers/jobs-run-to-completion.md b/docs/concepts/workloads/controllers/jobs-run-to-completion.md index c065e40bfc..23f604abab 100644 --- a/docs/concepts/workloads/controllers/jobs-run-to-completion.md +++ b/docs/concepts/workloads/controllers/jobs-run-to-completion.md @@ -291,7 +291,7 @@ unique to the pods of that job, and which matches unrelated pods, then pods of t job may be deleted, or this job may count other pods as completing it, or one or both of the jobs may refuse to create pods or run to completion. If a non-unique selector is chosen, then other controllers (e.g. ReplicationController) and their pods may behave -in unpredicatable ways too. Kubernetes will not stop you from making a mistake when +in unpredictable ways too. Kubernetes will not stop you from making a mistake when specifying `spec.selector`. Here is an example of a case when you might want to use this feature.