From 60f6948b0a944216513663e42f9371abccd4f144 Mon Sep 17 00:00:00 2001
From: Tu Nguyen <im2nguyen@users.noreply.github.com>
Date: Tue, 21 Jun 2022 16:13:39 -0700
Subject: [PATCH] Apply suggestions from code review

Co-authored-by: David Yu <dyu@hashicorp.com>
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
---
 .../content/docs/connect/cluster-peering/k8s.mdx    | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/website/content/docs/connect/cluster-peering/k8s.mdx b/website/content/docs/connect/cluster-peering/k8s.mdx
index 7b32d1743..0c411933d 100644
--- a/website/content/docs/connect/cluster-peering/k8s.mdx
+++ b/website/content/docs/connect/cluster-peering/k8s.mdx
@@ -27,8 +27,11 @@ To create and use cluster peering connections with Kubernetes, you need at least
 
 To establish cluster peering through Kubernetes, deploy clusters with the following Helm values.
 
+<CodeTabs heading="values.yaml">
+<CodeBlockConfig lineNumbers>
 ```yaml
 global:
+  image: "hashicorp/consul:1.13.0-alpha2"
   peering:
     enabled: true
 connectInject:
@@ -36,13 +39,19 @@ connectInject:
 meshGateway:
   enabled: true
   replicas: 1
-```
+  </CodeBlockConfig>
+  </CodeTabs>
+  
+Install Consul on Kubernetes using the values file `values.yaml` using the Helm CLI. 
 
+```shell-session 
+$ export HELM_RELEASE_NAME=peer1
+$ helm install ${HELM_RELEASE_NAME} hashicorp/consul --version "0.45.0" --values server.yaml
 ## Create a peering connection
 
 To peer Kubernetes clusters running Consul, you need to create a peering token and share it with the other cluster.
 
-1. In “cluster-01,” create the `PeeringAcceptor` custom resource.
+1. In `cluster-01`, create the `PeeringAcceptor` custom resource.
 
     <CodeBlockConfig filename="acceptor.yml">