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/debug-application-cluster/events-stackdriver.md

@@ -2,10 +2,11 @@
 reviewers:
 - piosz
 - x13n
+content_template: templates/concept
 title: Events in Stackdriver
 ---
 
-
+{{% capture overview %}}
 
 Kubernetes events are objects that provide insight into what is happening
 inside a cluster, such as what decisions were made by scheduler or why some
@@ -23,18 +24,24 @@ to capture events.
 This article describes a solution that exports Kubernetes events to
 Stackdriver Logging, where they can be processed and analyzed.
 
+{{< note >}}
 **Note:** it is not guaranteed that all events happening in a cluster will be
 exported to Stackdriver. One possible scenario when events will not be
 exported is when event exporter is not running (e.g. during restart or
 upgrade). In most cases it's fine to use events for purposes like setting up
 [metrics][sdLogMetrics] and [alerts][sdAlerts], but you should be aware
 of the potential inaccuracy.
+{{< /note >}}
 
 [sdLogMetrics]: https://cloud.google.com/logging/docs/view/logs_based_metrics
 [sdAlerts]: https://cloud.google.com/logging/docs/view/logs_based_metrics#creating_an_alerting_policy
 
+{{% /capture %}}
+
 {{< toc >}}
 
+{{% capture body %}}
+
 ## Deployment
 
 ### Google Kubernetes Engine
@@ -85,4 +92,6 @@ jsonPayload.source.component="default-scheduler"
 jsonPayload.involvedObject.name:"nginx-deployment"
 ```
 
-<img src="/images/docs/stackdriver-event-exporter-filter.png" alt="Filtered events in the Stackdriver Logging interface" width="500">
+{{< figure src="/images/docs/stackdriver-event-exporter-filter.png" alt="Filtered events in the Stackdriver Logging interface" width="500" >}}
+
+{{% /capture %}}