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/static-pod.md

@@ -2,8 +2,11 @@
 reviewers:
 - jsafrane
 title: Static Pods
+content_template: templates/concept
 ---
 
+{{% capture overview %}}
+
 **If you are running clustered Kubernetes and are using static pods to run a pod on every node, you should probably be using a [DaemonSet](/docs/concepts/workloads/controllers/daemonset/)!**
 
 *Static pods* are managed directly by kubelet daemon on a specific node, without the API server observing it. It does not have an associated replication controller, and kubelet daemon itself watches it and restarts it when it crashes. There is no health check. Static pods are always bound to one kubelet daemon and always run on the same node with it.
@@ -11,6 +14,12 @@ title: Static Pods
 Kubelet automatically tries to create a *mirror pod* on the Kubernetes API server for each static pod.
 This means that the pods are visible on the API server but cannot be controlled from there.
 
+{{% /capture %}}
+
+{{< toc >}}
+
+{{% capture body %}}
+
 ## Static pod creation
 
 Static pod can be created in two ways: either by using configuration file(s) or by HTTP.
@@ -108,7 +117,7 @@ static-web-my-node1        1/1       Running   0          12s
 
 Back to our `my-node1` host, we can try to stop the container manually and see, that kubelet automatically restarts it in a while:
 
-```shell
+```none
 [joe@host ~] $ ssh my-node1
 [joe@my-node1 ~] $ docker stop f6d05272b57e
 [joe@my-node1 ~] $ sleep 20
@@ -132,3 +141,5 @@ Running kubelet periodically scans the configured directory (`/etc/kubelet.d` in
 CONTAINER ID        IMAGE         COMMAND                CREATED           ...
 e7a62e3427f1        nginx:latest  "nginx -g 'daemon of   27 seconds ago
 ```
+
+{{% /capture %}}