Adam PR Feedback

Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
hashicorp · Sep 6, 2022 · ffc5815 · ffc5815
1 parent d4f3a90
commit ffc5815
Showing 1 changed file with 72 additions and 72 deletions.
diff --git a/website/content/docs/connect/config-entries/mesh.mdx b/website/content/docs/connect/config-entries/mesh.mdx
@@ -191,80 +191,80 @@ Note that the Kubernetes example does not include a `partition` field. Configura
 
 ###  Peer Through Mesh Gateways
 
-Route peering control plane traffic through mesh gateways.
+Set the `PeerThroughMeshGateways` parameter to `true` to route peering control plane traffic through mesh gateways.
 
 <Tabs>
-  <Tab heading="Consul OSS">
-
-    <CodeTabs tabs={[ "HCL", "Kubernetes YAML", "JSON" ]}>
-
-      ```hcl
-      Kind = "mesh"
-      Peering {
-        PeerThroughMeshGateways = true
-      }
-      ```
-
-      ```yaml
-      apiVersion: consul.hashicorp.com/v1alpha1
-      kind: Mesh
-      metadata:
-        name: mesh
-      spec:
-        peering:
-          peerThroughMeshGateways: true
-      ```
-
-      ```json
-      {
-        "Kind": "mesh",
-        "Peering": {
-          "PeerThroughMeshGateways": true
-        }
-      }
-      ```
-
-    </CodeTabs>
-
-  </Tab>
-  <Tab heading="Consul Enterprise">
-
-    You can only set the `PeerThroughMeshGateways` attribute on `mesh` configuration entries in the `default` partition.
-    This is the partition that owns mesh gateways routing control plane traffic to Consul servers.
-
-    <CodeTabs tabs={[ "HCL", "Kubernetes YAML", "JSON" ]}>
-
-      ```hcl
-      Kind      = "mesh"
-
-      Peering {
-        PeerThroughMeshGateways = true
-      }
-      ```
-
-      ```yaml
-      apiVersion: consul.hashicorp.com/v1alpha1
-      kind: Mesh
-      metadata:
-        name: mesh
-        namespace: default
-      spec:
-        peering:
-          peerThroughMeshGateways: true
-      ```
-
-      ```json
-      {
-        "Kind": "mesh",
-        "Peering": {
-          "PeerThroughMeshGateways": true
-        }
-      }
-      ```
-
-    </CodeTabs>
-
-  </Tab>
+<Tab heading="Consul OSS">
+
+<CodeTabs tabs={[ "HCL", "Kubernetes YAML", "JSON" ]}>
+
+```hcl
+Kind = "mesh"
+Peering {
+  PeerThroughMeshGateways = true
+}
+```
+
+```yaml
+apiVersion: consul.hashicorp.com/v1alpha1
+kind: Mesh
+metadata:
+  name: mesh
+spec:
+  peering:
+    peerThroughMeshGateways: true
+```
+
+```json
+{
+  "Kind": "mesh",
+  "Peering": {
+    "PeerThroughMeshGateways": true
+  }
+}
+```
+
+</CodeTabs>
+
+</Tab>
+<Tab heading="Consul Enterprise">
+
+You can only set the `PeerThroughMeshGateways` attribute on `mesh` configuration entries in the `default` partition.
+This is the partition that owns mesh gateways routing control plane traffic to Consul servers.
+
+<CodeTabs tabs={[ "HCL", "Kubernetes YAML", "JSON" ]}>
+
+```hcl
+Kind = "mesh"
+
+Peering {
+  PeerThroughMeshGateways = true
+}
+```
+
+```yaml
+apiVersion: consul.hashicorp.com/v1alpha1
+kind: Mesh
+metadata:
+  name: mesh
+  namespace: default
+spec:
+  peering:
+    peerThroughMeshGateways: true
+```
+
+```json
+{
+  "Kind": "mesh",
+  "Peering": {
+    "PeerThroughMeshGateways": true
+  }
+}
+```
+
+</CodeTabs>
+
+</Tab>
 </Tabs>
 
 Note that the Kubernetes example does not include a `partition` field. Configuration entries are applied on Kubernetes using [custom resource definitions (CRD)](/docs/k8s/crds), which can only be scoped to their own partition.