From dfb8b79b15ddea13a96fefee9dd30666ca1b7464 Mon Sep 17 00:00:00 2001
From: ztewyk <10110918@zte.com.cn>
Date: Thu, 16 Feb 2017 16:44:45 +0800
Subject: [PATCH] Parallel Jobs with a *work queue*:

do not specify `.spec.completions`, default to `.spec.Parallelism`, not  default to 1
---
 docs/user-guide/jobs.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/user-guide/jobs.md b/docs/user-guide/jobs.md
index d64ae9d730..438b63dff7 100644
--- a/docs/user-guide/jobs.md
+++ b/docs/user-guide/jobs.md
@@ -120,7 +120,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`
+  - 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.