docs: improve wording around autoconfiguration via Consul (#20139)

Fixes: #20132

website/content/docs/configuration/consul.mdx

@@ -28,9 +28,10 @@ consul {
 A default `consul` block is automatically merged with all Nomad agent
 configurations. These sensible defaults automatically enable Consul integration
 if Consul is detected on the system. This allows for seamless bootstrapping of
-the cluster with zero configuration. To put it another way: if you have a
-Consul agent running on the same host as the Nomad agent with the default
-configuration, Nomad will automatically connect and configure with Consul.
+the cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will be able to automatically connect to the rest of the
+Nomad cluster.
 
 If the local Consul agent is configured and accessible by the Nomad agents, the
 Nomad cluster will [automatically bootstrap][bootstrap] provided
@@ -157,13 +158,13 @@ agents with [`client.enabled`][] set to `true`.
   agents. Will default to the `CONSUL_GRPC_CACERT` environment variable if set.
 
   <Warning>
-  
+
     Consul does not support incoming TLS verification of Envoy
     sidecars. You should set `tls.grpc.verify_incoming = false` in your
-    Consul configuration when using Connect. See 
+    Consul configuration when using Connect. See
     [Consul/#13088](https://github.com/hashicorp/consul/issues/13088) for
     more details.
-    
+
   </Warning>
 
 - `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share