diff --git a/website/content/docs/connect/config-entries/mesh.mdx b/website/content/docs/connect/config-entries/mesh.mdx
index e7f199b95b..a323a6d90f 100644
--- a/website/content/docs/connect/config-entries/mesh.mdx
+++ b/website/content/docs/connect/config-entries/mesh.mdx
@@ -342,7 +342,7 @@ Note that the Kubernetes example does not include a `partition` field. Configura
       name: 'AllowEnablingPermissiveMutualTLS',
       type: 'bool: false',
       description:
-        'Controls whether `MutualTLSMode=permissive` can be set in the `proxy-defaults` and `service-defaults` config entries. Added in v1.16.0.'
+        'Controls whether `MutualTLSMode=permissive` can be set in the `proxy-defaults` and `service-defaults` configuration entries. '
     },
     {
       name: 'TLS',
diff --git a/website/content/docs/connect/config-entries/proxy-defaults.mdx b/website/content/docs/connect/config-entries/proxy-defaults.mdx
index d2d1f95c59..48ea1dc89a 100644
--- a/website/content/docs/connect/config-entries/proxy-defaults.mdx
+++ b/website/content/docs/connect/config-entries/proxy-defaults.mdx
@@ -418,9 +418,9 @@ spec:
                     supported for services with transparent proxy enabled. One of \`""\`, \`strict\`, or \`permissive\`.
                     When unset or \`""\`, the mode defaults to \`strict\`. When set to \`strict\`, the sidecar proxy
                     requires mutual TLS for incoming traffic. When set to \`permissive\`, the sidecar proxy accepts
-                    mutual TLS traffic on the sidecar proxy service port, and accepts any traffic on the destination
+                    mutual TLS traffic on the sidecar proxy service port and accepts any traffic on the destination
                     service port. We recommend only using \`permissive\` mode if necessary while onboarding services to
-                    the service mesh. Added in v1.16.0.`,
+                    the service mesh. ,
     },
     {
       name: 'MeshGateway',