diff --git a/website/content/docs/k8s/connect/health.mdx b/website/content/docs/k8s/connect/health.mdx
index 7f84608c54..ca43e7ffa9 100644
--- a/website/content/docs/k8s/connect/health.mdx
+++ b/website/content/docs/k8s/connect/health.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Configure Health Checks for Consul on Kubernetes
 description: >-
-  Kubernetes has built-in health probes you can sync with Consul's health checks to ensure service mesh traffic is routed to healthy pods. Learn how to register a TTL Health check and use mutating webhooks to redirect k8s liveness, readiness, and startup probes through Envoy proxies.
+  Kubernetes has built-in health probes you can sync with Consul's health checks to ensure service mesh traffic is routed to healthy pods.
 ---
 
 # Configure Health Checks for Consul on Kubernetes
@@ -14,14 +14,17 @@ Health check synchronization with Consul is done automatically whenever `connect
 
 For each Kubernetes pod that is connect-injected the following will be configured:
 
-1. A [TTL health check](/docs/discovery/checks#ttl) is registered within Consul.
-The Consul health check's state will reflect the pod's readiness status,
-which is the combination of all Kubernetes probes registered with the pod.
+1. A [Consul health check](/consul/api-docs/catalog#register-entity) is registered within Consul catalog.
+The Consul health check's state will reflect the pod's readiness status.
 
-1. If the pod is utilizing [Transparent Proxy](/docs/connect/transparent-proxy) mode, the mutating webhook will mutate all `http` based Startup, Liveness, and Readiness probes in the pod to redirect through the Envoy proxy.
-This is done with [`ExposePaths` configuration](/docs/connect/registration/service-registration#expose-paths-configuration-reference) for each probe so that kubelet can access the endpoint through the Envoy proxy.
+1. If the pod is using [Transparent Proxy](/docs/connect/transparent-proxy) mode,
+the mutating webhook will mutate all `http` based Startup, Liveness, and Readiness probes in the pod to redirect through the Envoy proxy.
+This is done with
+[`ExposePaths` configuration](/docs/connect/registration/service-registration#expose-paths-configuration-reference)
+for each probe so that kubelet can access the endpoint through the Envoy proxy.
 
-~> The mutation behavior can be disabled by either setting the `consul.hashicorp.com/transparent-proxy-overwrite-probes` pod annotation to `false` or the `connectInject.defaultOverwriteProbes` Helm value to `false`.
+~> The mutation behavior can be disabled by either setting the `consul.hashicorp.com/transparent-proxy-overwrite-probes`
+pod annotation to `false` or the `connectInject.defaultOverwriteProbes` Helm value to `false`.
 
 When readiness probes are set for a pod, the status of the pod will be reflected within Consul and will cause Consul to redirect service
 mesh traffic to the pod based on the pod's health. If the pod has failing health checks, Consul will no longer use