From 156fbcbc0c504e78e89dccd254c0c4740f81a557 Mon Sep 17 00:00:00 2001
From: Ashwin Venkatesh <ashwin@hashicorp.com>
Date: Wed, 10 Aug 2022 16:53:45 -0400
Subject: [PATCH] Update website/content/docs/connect/cluster-peering/k8s.mdx

Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
---
 website/content/docs/connect/cluster-peering/k8s.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/content/docs/connect/cluster-peering/k8s.mdx b/website/content/docs/connect/cluster-peering/k8s.mdx
index b23bf74b16..26d86cf312 100644
--- a/website/content/docs/connect/cluster-peering/k8s.mdx
+++ b/website/content/docs/connect/cluster-peering/k8s.mdx
@@ -244,7 +244,7 @@ To recreate or reset the peering connection, you need to generate a new peering
 
 1. You can do this by creating or updating the annotation `consul.hashicorp.com/peering-version` on the `PeeringAcceptor`. If the annotation already exists, update its value to a version that is higher.
 
-    <CodeBlockConfig filename="acceptor.yml">
+    <CodeBlockConfig filename="acceptor.yml" highlight="6" hideClipboard>
 
     ```yaml
     apiVersion: consul.hashicorp.com/v1alpha1