Apply templates to all concepts and tasks to fix double bullets in TOC (#9149)

* Apply concept template to fix double bullet issue.

* Apply concept template

* Apply templates to tasks

content/en/docs/tasks/job/coarse-parallel-processing-work-queue.md

@@ -1,20 +1,19 @@
 ---
 title: Coarse Parallel Processing Using a Work Queue
+content_template: templates/task
 weight: 30
 ---
 
 {{< toc >}}
 
-# Example: Job with Work Queue with Pod Per Work Item
+{{% capture overview %}}
 
 In this example, we will run a Kubernetes Job with multiple parallel
-worker processes.  You may want to be familiar with the basic,
-non-parallel, use of [Job](/docs/concepts/jobs/run-to-completion-finite-workloads/) first.
+worker processes. 
 
 In this example, as each pod is created, it picks up one unit of work
 from a task queue, completes it, deletes it from the queue, and exits.
 
-
 Here is an overview of the steps in this example:
 
 1. **Start a message queue service.**  In this example, we use RabbitMQ, but you could use another
@@ -24,6 +23,21 @@ Here is an overview of the steps in this example:
 1. **Start a Job that works on tasks from the queue**.  The Job starts several pods.  Each pod takes
   one task from the message queue, processes it, and repeats until the end of the queue is reached.
 
+{{% /capture %}}
+
+{{< toc >}}
+
+{{% capture prerequisites %}}
+
+Be familiar with the basic,
+non-parallel, use of [Job](/docs/concepts/jobs/run-to-completion-finite-workloads/).
+
+{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
+
+{{% /capture %}}
+
+{{% capture steps %}}
+
 ## Starting a message queue service
 
 This example uses RabbitMQ, but it should be easy to adapt to another AMQP-type message service.
@@ -260,6 +274,9 @@ Events:
 
 All our pods succeeded.  Yay.
 
+{{% /capture %}}
+
+{{% capture discussion %}}
 
 ## Alternatives
 
@@ -295,3 +312,5 @@ that the message is acknowledged by the amqp-consume command and the time that t
 exits with success, or if the node crashes before the kubelet is able to post the success of the pod
 back to the api-server, then the Job will not appear to be complete, even though all items
 in the queue have been processed.
+
+{{% /capture %}}

content/en/docs/tasks/job/fine-parallel-processing-work-queue.md

@@ -1,15 +1,13 @@
 ---
 title: Fine Parallel Processing Using a Work Queue
+content_template: templates/task
 weight: 40
 ---
 
-{{< toc >}}
-
-# Example: Job with Work Queue with Multiple Work Items Per Pod
+{{% capture overview %}}
 
 In this example, we will run a Kubernetes Job with multiple parallel
-worker processes.  You may want to be familiar with the basic,
-non-parallel, use of [Job](/docs/concepts/jobs/run-to-completion-finite-workloads/) first.
+worker processes in a given pod.
 
 In this example, as each pod is created, it picks up one unit of work
 from a task queue, processes it, and repeats until the end of the queue is reached.
@@ -27,6 +25,24 @@ Here is an overview of the steps in this example:
 1. **Start a Job that works on tasks from the queue**.  The Job starts several pods.  Each pod takes
   one task from the message queue, processes it, and repeats until the end of the queue is reached.
 
+{{% /capture %}}
+
+{{< toc >}}
+
+{{% capture prerequisites %}}
+
+{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
+
+{{% /capture %}}
+
+{{% capture steps %}}
+
+Be familiar with the basic,
+non-parallel, use of [Job](/docs/concepts/jobs/run-to-completion-finite-workloads/).
+
+{{% /capture %}}
+
+{{% capture steps %}}
 
 ## Starting Redis
 
@@ -212,6 +228,10 @@ Working on lemon
 
 As you can see, one of our pods worked on several work units.
 
+{{% /capture %}}
+
+{{% capture discussion %}}
+
 ## Alternatives
 
 If running a queue service or modifying your containers to use a work queue is inconvenient, you may
@@ -221,3 +241,5 @@ If you have a continuous stream of background processing work to run, then
 consider running your background workers with a `replicationController` instead,
 and consider running a background processing library such as
 [https://github.com/resque/resque](https://github.com/resque/resque).
+
+{{% /capture %}}

content/en/docs/tasks/job/parallel-processing-expansion.md

@@ -1,16 +1,21 @@
 ---
 title: Parallel Processing using Expansions
+content_template: templates/concept
 weight: 20
 ---
 
-{{< toc >}}
-
-# Example: Multiple Job Objects from Template Expansion
+{{% capture overview %}}
 
 In this example, we will run multiple Kubernetes Jobs created from
 a common template.  You may want to be familiar with the basic,
 non-parallel, use of [Jobs](/docs/concepts/jobs/run-to-completion-finite-workloads/) first.
 
+{{% /capture %}}
+
+{{< toc >}}
+
+{{% capture body %}}
+
 ## Basic Template Expansion
 
 First, download the following template of a job to a file called `job.yaml`
@@ -189,3 +194,5 @@ If you have a large number of job objects, you may find that:
 
 In this case, you can consider one of the
 other [job patterns](/docs/concepts/jobs/run-to-completion-finite-workloads/#job-patterns).
+
+{{% /capture %}}