diff --git a/docs/concepts/workloads/controllers/jobs-run-to-completion.md b/docs/concepts/workloads/controllers/jobs-run-to-completion.md
index b9aaed4b496..d8330943772 100644
--- a/docs/concepts/workloads/controllers/jobs-run-to-completion.md
+++ b/docs/concepts/workloads/controllers/jobs-run-to-completion.md
@@ -110,12 +110,12 @@ There are three main types of jobs:
   - normally only one pod is started, unless the pod fails.
   - job is complete as soon as Pod terminates successfully.
 1. Parallel Jobs with a *fixed completion count*:
-  - specify a non-zero positive value for `.spec.completions`
+  - specify a non-zero positive value for `.spec.completions`.
   - 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`
-  - the pods must coordinate with themselves or an external service to determine what each should work on
+  - 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.
   - once at least one pod has terminated with success and all pods are terminated, then the job is completed with success.