From 99d2f6658cfc19b53c5076eb228992068bd7249c Mon Sep 17 00:00:00 2001
From: Luke Kysow <1034429+lkysow@users.noreply.github.com>
Date: Thu, 23 Jul 2020 09:19:33 -0700
Subject: [PATCH] Update terminating-gateways.mdx

* fix formatting issue
* use a command that will work with any pod id
---
 website/pages/docs/k8s/connect/terminating-gateways.mdx | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/website/pages/docs/k8s/connect/terminating-gateways.mdx b/website/pages/docs/k8s/connect/terminating-gateways.mdx
index 07d2902069..82f98dc497 100644
--- a/website/pages/docs/k8s/connect/terminating-gateways.mdx
+++ b/website/pages/docs/k8s/connect/terminating-gateways.mdx
@@ -116,6 +116,7 @@ If ACLs are enabled, update the terminating gateway acl token to have `service:
 being represented by the gateway:
 * Create a new policy that includes these permissions
 * Update the existing token to include the new policy
+
 ~> The CLI command should be run with the `-merge-policies`, `-merge-roles` and `-merge-service-identities` so
 nothing is removed from the terminating gateway token
 
@@ -207,5 +208,5 @@ $ kubectl apply -f static-client.yaml
 
 You can verify connectivity of the static-client and terminating gateway via a curl command:
 ```shell-session
-$ kubectl exec static-client-7cc6df495-qdtkp -- curl -vvvs -H "Host: example-https.com" http://localhost:1234/
+$ kubectl exec deploy/static-client -- curl -vvvs -H "Host: example-https.com" http://localhost:1234/
 ```