From bdaf9cda9116b3482c187d06e6e9b642e34f45d9 Mon Sep 17 00:00:00 2001
From: Charlie Voiselle <464492+angrycub@users.noreply.github.com>
Date: Wed, 8 Jan 2020 13:08:54 -0500
Subject: [PATCH] Change consul agent note to callout

Because this is such a common misconfig, it is probably worth
highlighting
---
 website/source/docs/configuration/consul.html.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/source/docs/configuration/consul.html.md b/website/source/docs/configuration/consul.html.md
index 3dac4d9a8c3..577281db9d6 100644
--- a/website/source/docs/configuration/consul.html.md
+++ b/website/source/docs/configuration/consul.html.md
@@ -41,7 +41,7 @@ cluster with zero configuration. To put it another way: if you have a Consul
 agent running on the same host as the Nomad agent with the default
 configuration, Nomad will automatically connect and configure with Consul.
 
-An important requirement is that each Nomad agent talks to a unique Consul
+~> An important requirement is that each Nomad agent talks to a unique Consul
 agent. Nomad agents should be configured to talk to Consul agents and not
 Consul servers. If you are observing flapping services, you may have 
 multiple Nomad agents talking to the same Consul agent. As such avoid