diff --git a/website/pages/docs/integrations/consul-connect.mdx b/website/pages/docs/integrations/consul-connect.mdx
index e1121906c..4fe18b43a 100644
--- a/website/pages/docs/integrations/consul-connect.mdx
+++ b/website/pages/docs/integrations/consul-connect.mdx
@@ -329,8 +329,8 @@ dashes (`-`) are converted to underscores (`_`) in environment variables so
 - The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
   proxy sidecar on client nodes.
 - Consul Connect using network namespaces is only supported on Linux.
-- Prior to Nomad 1.0 and Consul 1.9, the Envoy sidecar proxy may drop and stop
-  accepting connections while the Nomad agent is restarting.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
 
 [count-dashboard]: /img/count-dashboard.png
 [gh6120]: https://github.com/hashicorp/nomad/issues/6120
diff --git a/website/pages/docs/upgrade/upgrade-specific.mdx b/website/pages/docs/upgrade/upgrade-specific.mdx
index 40f32d878..ebb9ed9cc 100644
--- a/website/pages/docs/upgrade/upgrade-specific.mdx
+++ b/website/pages/docs/upgrade/upgrade-specific.mdx
@@ -91,7 +91,7 @@ ideal upgrade path is:
 3. [Drain][drain-cli] and shutdown old Nomad client nodes.
 
 While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
-Envoy proxies may drop and stop accepting connections while the Nomad agent is
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
 restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
 
 #### Envoy proxy versions