From ae8f0655b3473c121fce57a2d757c5f408b19ff7 Mon Sep 17 00:00:00 2001
From: Praitk <68642400+pratikbalar@users.noreply.github.com>
Date: Wed, 11 Nov 2020 11:53:26 +0530
Subject: [PATCH] Highlighting Note

Highlighting Note in order to it visible first cause after analyzing some issues, i find people are ignoring this note section (including my self)
---
 docs/multi-cluster-services.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/multi-cluster-services.md b/docs/multi-cluster-services.md
index de3d410..5d3c920 100644
--- a/docs/multi-cluster-services.md
+++ b/docs/multi-cluster-services.md
@@ -5,7 +5,7 @@ This enables clusters to provide services to other clusters over a secure connec
 For example, a cluster on AWS with access to GPUs could run a machine learning service that could be consumed by workloads running in a another location, e.g. an on-prem cluster without GPUs.
 Unlike services exposed via Ingresses or NodePort Services, multi-cluster services can remain private and internal to the clusters.
 
-*Note*: in order for connected clusters to be fully routable, the allowed IPs that they declare must be non-overlapping, i.e. the Kilo, pod, and service CIDRs.
+> **Note**: in order for connected clusters to be fully routable, the allowed IPs that they declare must be non-overlapping, i.e. the Kilo, pod, and service CIDRs.
 
 ## Getting Started