Merge pull request #21559 from AdamGS/patch-1

Fix numbering in the "Parallel Jobs" section

Author: k8s-ci-robot

content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md

@@ -140,19 +140,19 @@ See section [specifying your own pod selector](#specifying-your-own-pod-selector
 There are three main types of task suitable to run as a Job:
 
 1. Non-parallel Jobs
-  - normally, only one Pod is started, unless the Pod fails.
-  - the Job is complete as soon as its Pod terminates successfully.
+   - normally, only one Pod is started, unless the Pod fails.
+   - the Job is complete as soon as its Pod terminates successfully.
 1. Parallel Jobs with a *fixed completion count*:
-  - specify a non-zero positive value for `.spec.completions`.
-  - the Job represents the overall task, and is complete when there is one successful Pod for each value in the range 1 to `.spec.completions`.
-  - **not implemented yet:** Each Pod is passed a different index in the range 1 to `.spec.completions`.
+   - specify a non-zero positive value for `.spec.completions`.
+   - the Job represents the overall task, and is complete when there is one successful Pod for each value in the range 1 to `.spec.completions`.
+   - **not implemented yet:** Each Pod is 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`.
-  - the Pods must coordinate amongst themselves or an external service to determine what each should work on. For example, a Pod might fetch a batch of up to N items from the work queue.
-  - each Pod is independently capable of determining whether or not all its peers are done, and thus that the entire Job is done.
-  - when _any_ Pod from the Job terminates with success, no new Pods are created.
-  - once at least one Pod has terminated with success and all Pods are terminated, then the Job is completed with success.
-  - once any Pod has exited with success, no other Pod should still be doing any work for this task or writing any output.  They should all be in the process of exiting.
+   - do not specify `.spec.completions`, default to `.spec.parallelism`.
+   - the Pods must coordinate amongst themselves or an external service to determine what each should work on. For example, a Pod might fetch a batch of up to N items from the work queue.
+   - each Pod is independently capable of determining whether or not all its peers are done, and thus that the entire Job is done.
+   - when _any_ Pod from the Job terminates with success, no new Pods are created.
+   - once at least one Pod has terminated with success and all Pods are terminated, then the Job is completed with success.
+   - once any Pod has exited with success, no other Pod should still be doing any work for this task or writing any output.  They should all be in the process of exiting.
 
 For a _non-parallel_ Job, you can leave both `.spec.completions` and `.spec.parallelism` unset.  When both are
 unset, both are defaulted to 1.