Apply suggestions from code review

Co-authored-by: David Yu <dyu@hashicorp.com>
Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>

website/content/docs/connect/failover/index.mdx

@@ -21,7 +21,7 @@ The following table compares these strategies in deployments with multiple datac
 | Failover Strategy | Supports WAN Federation | Supports Cluster Peering | Multi-Datacenter Failover Strength | Multi-Datacenter Usage Scenario |
 | :---------------: | :---------------------: | :----------------------: | :--------------------------------- | :------------------------------ |
 | `Failover` stanza | ✅                 | ✅                  | Enables more granular logic for failover targeting | Configuring failover for a single service or service subset, especially for testing or debugging purposes |
-| Prepared query    | ✅                 | ❌                 | Central policies that can automatically target the nearest datacenter | WAN-federated deployments where a primary datacenter is configured |
+| Prepared query    | ✅                 |   ✅              | Central policies that can automatically target the nearest datacenter | WAN-federated deployments where a primary datacenter is configured. Prepared queries are not replicated over peer connections. |
 | Sameness groups   | ❌                | ✅                  | Group size changes without edits to existing member configurations | Cluster peering deployments with consistently named services and namespaces |
 
 ### Failover configurations for a service mesh with a single datacenter

website/content/docs/k8s/connect/onboarding-tproxy-mode.mdx

@@ -34,7 +34,8 @@ Permissive mTLS is only supported for services running in transparent proxy mode
 
 ## Configure global settings
 
-Configure the mesh to allow services that are already in the mesh to send non-mTLS messages to services outside the mesh. You can also configure the mesh to allow services to run in permissive mTLS mode. Set both configurations in the mesh gateway configuration entry, which is the global configuration that defines service mesh proxy behavior.
+Configure Consul to allow services that are already in the mesh to send non-mTLS messages to services outside the mesh. You can also Consul to allow services to run in permissive mTLS mode. Set both configurations in the mesh gateway configuration entry, which is the global configuration that defines service mesh proxy behavior.
+
 ### Allow outgoing non-mTLS traffic
 
 You can configure a global setting that allows services in the mesh to send non-mTLS messages to services outside the mesh.
@@ -122,7 +123,7 @@ You can change this setting back to `false` at any time, even if there are servi
 
 Depending on the services you are onboarding, you may not need to enable permissive mTLS mode. If the service does not accept incoming traffic or accepts traffic from downstream services that are already part of the service mesh, then permissive mTLS mode is not required to continue. 
 
-To enable permissive mTLS mode for the service, set `MutualTLSMode=permissive` in the service defaults configuration entry for the service. The following example shows how to configure this setting for a service named `example-service`.
+To enable permissive mTLS mode for the service, set [`MutualTLSMode=permissive`](/consul/docs/connect/config-entries/service-defaults#mutualtlsmode) in the service defaults configuration entry for the service. The following example shows how to configure this setting for a service named `example-service`.
 
 <CodeTabs heading="Enable permissive mTLS for applicable services">