diff --git a/website/content/docs/k8s/multiport/reference/trafficpermissions.mdx b/website/content/docs/k8s/multiport/reference/trafficpermissions.mdx
index 60d1a06e1146..e442af7d2765 100644
--- a/website/content/docs/k8s/multiport/reference/trafficpermissions.mdx
+++ b/website/content/docs/k8s/multiport/reference/trafficpermissions.mdx
@@ -68,6 +68,7 @@ The following list outlines field hierarchy, language-specific data types, and r
         - [`pathPrefix`](#spec-permissions-destinationrules-exclude-pathprefix): string
         - [`pathRegex`](#spec-permissions-destinationrules-exclude-pathregex): string
         - [`portNames`](#spec-permissions-destinationrules-exclude-portNames): array of strings
+
 </Tab>
 </Tabs>
 
@@ -77,6 +78,10 @@ The previous section's [configuration model](#configuration-model) provides an o
 
 When every field is defined, a TrafficPermissions CRD has the following form:
 
+<Tabs>
+
+<Tab heading="YAML" group="yaml">
+
 ```yaml
 apiVersion: auth.consul.hashicorp.com/v2beta1    # required
 kind: TrafficPermissions                         # required
@@ -128,6 +133,9 @@ spec:
         pathRegex:
 ```
 
+</Tab>
+</Tabs>
+
 ## Specification
 
 This section provides details about the fields you can configure in the TrafficPermissions custom resource definition (CRD).