diff --git a/docs/promtail.md b/docs/promtail.md
index bcd7fc5a287022c63f17e4131c863e7ed6192a1b..edfa7c5fb0f8c7e0b2e0a2e00d7b22182abee664 100644
--- a/docs/promtail.md
+++ b/docs/promtail.md
@@ -17,21 +17,21 @@ The term "label" here is used in more than one different way and they can be eas
 * Labels starting with \_\_meta_kubernetes_pod_label_* are "meta labels" which are generated based on your kubernetes
   pod labels. Example: If your kubernetes pod has a label "name" set to "foobar" then the scrape_configs section
   will have a label \_\_meta_kubernetes_pod_label_name with value set to "foobar".
-* There are other __meta_kubernetes_* labels based on the Kubernetes metadadata, such as the namespace the pod is
-  running (__meta_kubernetes_namespace) or the name of the container inside the pod (\_\_meta_kubernetes_pod_container_name)
+* There are other \_\_meta_kubernetes_* labels based on the Kubernetes metadadata, such as the namespace the pod is
+  running (\_\_meta_kubernetes_namespace) or the name of the container inside the pod (\_\_meta_kubernetes_pod_container_name)
 * The label \_\_path\_\_ is a special label which Promtail will read to find out where the log files are to be read in.
 
 The most important part of each entry is the *relabel_configs* which are a list of operations which creates,
 renames, modifies or alters labels. A single scrape_config can also reject logs by doing an "action: drop" which means
 that this particular scrape_config will not forward logs from a particular pod, but another scrape_config might.
 
-Many of the scrape_configs read labels from __meta_kubernetes_* meta-labels, assign them to intermediate labels
+Many of the scrape_configs read labels from \_\_meta_kubernetes_* meta-labels, assign them to intermediate labels
 such as \_\_service\_\_ based on a few different logic, possibly drop the processing if the \_\_service\_\_ was empty
 and finally set visible labels (such as "job") based on the \_\_service\_\_ label.
 
 In general, all of the default Promtail scrape_configs do the following:
  * They read pod logs from under /var/log/pods/$1/*.log.
- * They set "namespace" label directly from the __meta_kubernetes_namespace.
+ * They set "namespace" label directly from the \_\_meta_kubernetes_namespace.
  * They expect to see your pod name in the "name" label
  * They set a "job" label which is roughly "your namespace/your job name"