diff --git a/pkg/preflights/host-preflight.yaml b/pkg/preflights/host-preflight.yaml
index a173cd41d..c43c3fce9 100644
--- a/pkg/preflights/host-preflight.yaml
+++ b/pkg/preflights/host-preflight.yaml
@@ -436,330 +436,330 @@ spec:
               message: Connection to port 2379/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 2379/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 2379/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 2379/TCP. Ensure that your firewall doesn't block port 2379/TCP.
+              message: Port 2379/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 2379/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 2379/TCP
+              message: Port 2379/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 2379/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 2379/TCP
+              message: Port 2379/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: ETCD External Port Availability
         collectorName: ETCD External Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 2380/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 2380/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 2380/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 2380/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 2380/TCP. Ensure that your firewall doesn't block port 2380/TCP.
+              message: Port 2380/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 2380/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 2380/TCP
+              message: Port 2380/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 2380/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 2380/TCP
+              message: Port 2380/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: Local Artifact Mirror Port Availability
         collectorName: Local Artifact Mirror Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 50000/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 50000/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 50000/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 50000/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 50000/TCP. Ensure that your firewall doesn't block port 50000/TCP.
+              message: Port 50000/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 50000/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 50000/TCP
+              message: Port 50000/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 50000/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 50000/TCP
+              message: Port 50000/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: Calico External TCP Port Availability
         collectorName: Calico External TCP Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 9091/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 9091/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 9091/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 9091/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 9091/TCP. Ensure that your firewall doesn't block port 9091/TCP.
+              message: Port 9091/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 9091/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 9091/TCP
+              message: Port 9091/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 9091/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 9091/TCP
+              message: Port 9091/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: Kube API Server Port Availability
         collectorName: Kube API Server Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 6443/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 6443/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 6443/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 6443/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 6443/TCP. Ensure that your firewall doesn't block port 6443/TCP.
+              message: Port 6443/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 6443/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 6443/TCP
+              message: Port 6443/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 6443/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 6443/TCP
+              message: Port 6443/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: Envoy Port Availability
         collectorName: Envoy Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 7443/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 7443/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 7443/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 7443/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 7443/TCP. Ensure that your firewall doesn't block port 7443/TCP.
+              message: Port 7443/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 7443/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 7443/TCP
+              message: Port 7443/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 7443/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 7443/TCP
+              message: Port 7443/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: Kotsadm Node Port Availability
         collectorName: Kotsadm Node Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 30000/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 30000/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 30000/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 30000/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 30000/TCP. Ensure that your firewall doesn't block port 30000/TCP.
+              message: Port 30000/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 30000/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 30000/TCP
+              message: Port 30000/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 30000/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 30000/TCP
+              message: Port 30000/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: Kubelet Port Availability
         collectorName: Kubelet Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 10250/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 10250/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 10250/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 10250/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 10250/TCP. Ensure that your firewall doesn't block port 10250/TCP.
+              message: Port 10250/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 10250/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 10250/TCP
+              message: Port 10250/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 10250/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 10250/TCP
+              message: Port 10250/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: K0s API Port Availability
         collectorName: K0s API Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 9443/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 9443/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 9443/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 9443/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 9443/TCP. Ensure that your firewall doesn't block port 9443/TCP.
+              message: Port 9443/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 9443/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 9443/TCP
+              message: Port 9443/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 9443/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 9443/TCP
+              message: Port 9443/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: Calico Node Internal Port Availability
         collectorName: Calico Node Internal Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 9099/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 9099/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 9099/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 9099/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 9099/TCP. Ensure that your firewall doesn't block port 9099/TCP.
+              message: Port 9099/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 9099/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 9099/TCP
+              message: Port 9099/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 9099/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 9099/TCP
+              message: Port 9099/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: Kube Proxy Health Port Availability
         collectorName: Kube Proxy Health Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 10256/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 10256/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 10256/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 10256/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 10256/TCP. Ensure that your firewall doesn't block port 10256/TCP.
+              message: Port 10256/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 10256/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 10256/TCP
+              message: Port 10256/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 10256/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 10256/TCP
+              message: Port 10256/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: Kube Proxy Metrics Port Availability
         collectorName: Kube Proxy Metrics Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 10249/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 10249/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 10249/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 10249/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 10249/TCP. Ensure that your firewall doesn't block port 10249/TCP.
+              message: Port 10249/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 10249/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 10249/TCP
+              message: Port 10249/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 10249/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 10249/TCP
+              message: Port 10249/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: Kube Scheduler Secure Port Availability
         collectorName: Kube Scheduler Secure Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 10259/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 10259/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 10259/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 10259/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 10259/TCP. Ensure that your firewall doesn't block port 10259/TCP.
+              message: Port 10259/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 10259/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 10259/TCP
+              message: Port 10259/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 10259/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 10259/TCP
+              message: Port 10259/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: Kube Controller Secure Port Availability
         collectorName: Kube Controller Secure Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 10257/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 10257/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 10257/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 10257/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 10257/TCP. Ensure that your firewall doesn't block port 10257/TCP.
+              message: Port 10257/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 10257/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 10257/TCP
+              message: Port 10257/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 10257/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 10257/TCP
+              message: Port 10257/TCP is required, but an unexpected error occurred when trying to connect to it
     - tcpPortStatus:
         checkName: Kubelet Health Port Availability
         collectorName: Kubelet Health Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 10248/TCP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 10248/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 10248/TCP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 10248/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 10248/TCP. Ensure that your firewall doesn't block port 10248/TCP.
+              message: Port 10248/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 10248/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 10248/TCP
+              message: Port 10248/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
               message: Port 10248/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 10248/TCP
+              message: Port 10248/TCP is required, but an unexpected error occurred when trying to connect to it
     - udpPortStatus:
         checkName: Calico Communication Port Availability
         collectorName: Calico Communication Port
         outcomes:
           - fail:
               when: "connection-refused"
-              message: Connection to port 4789/UDP was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
+              message: Port 4789/TCP is required, but the connection was refused. This may indicate that the connection is being redirected to somewhere else on your network (perhaps a proxy configuration).
           - fail:
               when: "address-in-use"
-              message: Port 4789/UDP is required but another process is already listening on it. Relocate that process to continue.
+              message: Port 4789/TCP is required, but another process is already listening on it. Relocate the conflicting process to continue.
           - fail:
               when: "connection-timeout"
-              message: Timed out connecting to port 4789/UDP. Ensure that your firewall doesn't block port 4789/UDP.
+              message: Port 4789/TCP is required, but the connection timed out. Ensure that your firewall doesn't block port 4789/TCP.
           - fail:
               when: "error"
-              message: Unexpected error when trying to connect to port 4789/UDP
+              message: Port 4789/TCP is required, but an unexpected error occurred when trying to connect to it
           - pass:
               when: "connected"
-              message: Port 4789/UDP is available
+              message: Port 4789/TCP is available
           - error:
-              message: Unexpected error when trying to connect to port 4789/UDP
+              message: Port 4789/TCP is required, but an unexpected error occurred when trying to connect to it