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/administer-cluster/guaranteed-scheduling-critical-addon-pods.md

@@ -4,11 +4,10 @@ reviewers:
 - filipg
 - piosz
 title: Guaranteed Scheduling For Critical Add-On Pods
+content_template: templates/concept
 ---
 
-{{< toc >}}
-
-## Overview
+{{% capture overview %}}
 
 In addition to Kubernetes core components like api-server, scheduler, controller-manager running on a master machine
 there are a number of add-ons which, for various reasons, must run on a regular cluster node (rather than the Kubernetes master).
@@ -17,6 +16,12 @@ A cluster may stop working properly if a critical add-on is evicted (either manu
 and becomes pending (for example when the cluster is highly utilized and either there are other pending pods that schedule into the space
 vacated by the evicted critical add-on pod or the amount of resources available on the node changed for some other reason).
 
+{{% /capture %}}
+
+{{< toc >}}
+
+{{% capture body %}}
+
 ## Rescheduler: guaranteed scheduling of critical add-ons
 **Rescheduler is deprecated as of Kubernetes 1.10 and will be removed in version 1.12 in
 accordance with the [deprecation policy](/docs/reference/deprecation-policy) for beta features.**
@@ -62,3 +67,5 @@ A pod could also be considered critical, if its priority is greater than or equa
 To be considered critical, the pod has to run in the `kube-system` namespace (configurable via flag) and
 
 * Have the priorityClass set as "system-cluster-critical" or "system-node-critical", the latter being the highest for entire cluster and `scheduler.alpha.kubernetes.io/critical-pod` annotation set to empty string(This will be deprecated too).
+
+{{% /capture %}}