From 1089ebbf410fd2cd69bb227059d5d06cc4f49d1a Mon Sep 17 00:00:00 2001
From: JuleeB1 <42522858+JuleeB1@users.noreply.github.com>
Date: Mon, 20 Aug 2018 15:34:13 -0500
Subject: [PATCH] Added Note Formatting (#9932)

Added note tags to the text
---
 .../logging-stackdriver.md                          | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/content/en/docs/tasks/debug-application-cluster/logging-stackdriver.md b/content/en/docs/tasks/debug-application-cluster/logging-stackdriver.md
index fd6b0bff7d..b9251fc989 100644
--- a/content/en/docs/tasks/debug-application-cluster/logging-stackdriver.md
+++ b/content/en/docs/tasks/debug-application-cluster/logging-stackdriver.md
@@ -89,9 +89,9 @@ than Google Kubernetes Engine. Proceed at your own risk.
     kubectl label node $NODE_NAME beta.kubernetes.io/fluentd-ds-ready=true
     ```
 
-    **Note:** If a node fails and has to be recreated, you must re-apply the label to
+    {{< note >}}**Note:** If a node fails and has to be recreated, you must re-apply the label to
     the recreated node. To make this easier, you can use Kubelet's command-line parameter
-    for applying node labels in your node startup script.
+    for applying node labels in your node startup script.{{< /note >}}
 
 1. Deploy a `ConfigMap` with the logging agent configuration by running the following command:
 
@@ -263,9 +263,9 @@ In this case you need to be able to change the parameters of `DaemonSet` and `Co
 
 If you're using GKE and Stackdriver Logging is enabled in your cluster, you
 cannot change its configuration, because it's managed and supported by GKE.
-However, you can disable the default integration and deploy your own. Note,
-that you will have to support and maintain a newly deployed configuration
-yourself: update the image and configuration, adjust the resources and so on.
+However, you can disable the default integration and deploy your own. 
+{{< note >}}**Note:** You will have to support and maintain a newly deployed configuration
+yourself: update the image and configuration, adjust the resources and so on.{{< /note >}}
 To disable the default logging integration, use the following command:
 
 ```
@@ -325,7 +325,8 @@ kubectl get cm fluentd-gcp-config --namespace kube-system -o yaml > fluentd-gcp-
 ```
 
 Then in the value for the key `containers.input.conf` insert a new filter right after
-the `source` section. **Note:** Order is important.
+the `source` section. 
+{{< note >}}**Note:** Order is important.{{< /note >}}
 
 Updating `ConfigMap` in the apiserver is more complicated than updating `DaemonSet`. It's better
 to consider `ConfigMap` to be immutable. Then, in order to update the configuration, you should