From 754ba959918db8e95cb1bebab94e0f0112c5876e Mon Sep 17 00:00:00 2001
From: naseemkullah <naseemkullah@gmail.com>
Date: Sun, 22 Apr 2018 22:31:04 -0400
Subject: [PATCH] Update Monitoring external etcd.md

---
 docs/Monitoring external etcd.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/Monitoring external etcd.md b/docs/Monitoring external etcd.md
index edf9af42..f46f4010 100644
--- a/docs/Monitoring external etcd.md	
+++ b/docs/Monitoring external etcd.md	
@@ -46,7 +46,7 @@ If your Prometheus Operator is already in place, update it:
 
 The below manifest creates a Service to expose etcd metrics (port 2379)
 
-* Replace I`P_OF_YOUR_ETCD_NODE_[0/1/2]` with the IP addresses of your etcd nodes. If you have more than one node, add them to the same list.
+* Replace `IP_OF_YOUR_ETCD_NODE_[0/1/2]` with the IP addresses of your etcd nodes. If you have more than one node, add them to the same list.
 * Use `#insecureSkipVerify: true` or replace `ETCD_DNS_OR_ALTERNAME_NAME` with a valid name for the certificate. 
 
 In case you have generated the etcd certificated with kube-aws, you will need to use insecureSkipVerify as the valid certificate domain will be different for each etcd node (etcd0, etcd1, etcd2). If you only have one etcd node, you can use the value from `etcd.internalDomainName` speficied in your kube-aws `cluster.yaml`
-- 
GitLab