From 811674d526c118c42d6f76972253dc10bed4c564 Mon Sep 17 00:00:00 2001
From: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
Date: Tue, 14 Jun 2022 17:28:06 -0500
Subject: [PATCH] Update
 website/content/docs/connect/cluster-peering/create-manage-peering.mdx

---
 .../docs/connect/cluster-peering/create-manage-peering.mdx      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx
index 84771616a3..42b27e05b0 100644
--- a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx
+++ b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx
@@ -90,7 +90,7 @@ Before you can call services from peered clusters, you must set service intentio
 
 First, create a configuration entry and specify the `Kind` as `“service-intentions”`. Declare the service on "cluster-02" that can access the service in "cluster-01." The following example sets service intentions so that "backend-service" can access "frontend-service."
 
-<CodeBlockConfig filename="peering-intentions.hcl">
+<CodeBlockConfig filename="peering-intentions.hcl" highlight="1" hideClipboard>
 
 ```shell-session
 Kind      = "service-intentions"