diff --git a/content/en/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md b/content/en/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md
index 78ef4bfe8f..ebd03d84d2 100644
--- a/content/en/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md
+++ b/content/en/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md
@@ -15,9 +15,11 @@ in the [Logging With Stackdriver Logging](/docs/user-guide/logging/stackdriver).
 This article describes how to set up a cluster to ingest logs into
 [Elasticsearch](https://www.elastic.co/products/elasticsearch) and view
 them using [Kibana](https://www.elastic.co/products/kibana), as an alternative to
-Stackdriver Logging when running on GCE. Note that Elasticsearch and Kibana
-cannot be setup automatically in the Kubernetes cluster hosted on
-Google Kubernetes Engine, you have to deploy it manually.
+Stackdriver Logging when running on GCE. 
+
+{{< note >}}
+**Note:** You cannot automatically deploy Elasticsearch and Kibana in the Kubernetes cluster hosted on Google Kubernetes Engine. You have to deploy them manually.
+{{< /note >}}
 
 {{% /capture %}}
 
@@ -115,4 +117,4 @@ Here is a typical view of ingested logs from the Kibana viewer:
 Kibana opens up all sorts of powerful options for exploring your logs! For some
 ideas on how to dig into it, check out [Kibana's documentation](https://www.elastic.co/guide/en/kibana/current/discover.html).
 
-{{% /capture %}}
\ No newline at end of file
+{{% /capture %}}