From f89f0867e2ec64ad002b11db7b5617b48362f1ce Mon Sep 17 00:00:00 2001
From: Anne Henmi <41210220+ahh-docker@users.noreply.github.com>
Date: Wed, 2 Jan 2019 08:51:16 -0700
Subject: [PATCH] Update nginx.md

wording
---
 docs/recipes/nginx.md | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/docs/recipes/nginx.md b/docs/recipes/nginx.md
index 81c448467..1f039f611 100644
--- a/docs/recipes/nginx.md
+++ b/docs/recipes/nginx.md
@@ -38,11 +38,10 @@ you want through the secondary authentication mechanism implemented inside your
 proxy, it also requires that you move TLS termination from the Registry to the
 proxy itself.
 
-> Another important thing to note is that by binding your registry to
-> `localhost:5000` without authentication, you open up a potential loophole in
-> your Docker Registry security - anyone who can log on to the server where your
-> Docker Registry is running can push images to your registry, without
-> authentication. This could have potentially devastating effects.
+> ***NOTE:*** Docker does not recommend binding your registry to `localhost:5000` without
+> authentication. This creates a potential loophole in your Docker Registry security.
+> As a result, anyone with access to your Docker Registry can push images without
+> authentication. 
 
 Furthermore, introducing an extra http layer in your communication pipeline
 makes it more complex to deploy, maintain, and debug. Make sure the extra