From 1415538e0dd514381de4e1b8112285fb21caca95 Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Thu, 27 Dec 2018 10:07:07 -0800 Subject: [PATCH] Minor edit --- ee/ucp/interlock/usage/tls.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ee/ucp/interlock/usage/tls.md b/ee/ucp/interlock/usage/tls.md index 67fb8ac058..7c52129323 100644 --- a/ee/ucp/interlock/usage/tls.md +++ b/ee/ucp/interlock/usage/tls.md @@ -139,12 +139,12 @@ If everything is properly configured you should get a JSON payload: ``` Since the proxy uses SNI to decide where to route traffic, make sure you're -using a version of curl that includes the SNI header with insecure requests. -If this doesn't happen, curl displays an error saying that the SSL handshake +using a version of `curl` that includes the SNI header with insecure requests. +If this doesn't happen, `curl` displays an error saying that the SSL handshake was aborterd. -NOTE: Currently there is no way to update expired certificates using this method. The proper way is to -create a new secret then update the corresponding service. +> ***NOTE:*** Currently there is no way to update expired certificates using this method. +> The proper way is to create a new secret then update the corresponding service. ## Let your service handle TLS