From 635cba0a85782db53a9d71018cc4e09bdb40fee8 Mon Sep 17 00:00:00 2001 From: chenhonggc Date: Tue, 3 Oct 2017 00:29:59 +0800 Subject: [PATCH] spelling mistakes (#5713) --- 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 a15313f447..ac90c3e4df 100644 --- a/docs/concepts/workloads/controllers/jobs-run-to-completion.md +++ b/docs/concepts/workloads/controllers/jobs-run-to-completion.md @@ -125,7 +125,7 @@ There are three main types of jobs: - the job is complete when there is one successful pod for each value in the range 1 to `.spec.completions`. - **not implemented yet:** each pod passed a different index in the range 1 to `.spec.completions`. 1. Parallel Jobs with a *work queue*: -  - do not specify `.spec.completions`, default to `.spec.Parallelism`. +  - do not specify `.spec.completions`, default to `.spec.parallelism`.  - the pods must coordinate with themselves or an external service to determine what each should work on. - each pod is independently capable of determining whether or not all its peers are done, thus the entire Job is done. - when _any_ pod terminates with success, no new pods are created.