diff --git a/website/content/docs/job-specification/group.mdx b/website/content/docs/job-specification/group.mdx
index fd522cae1..ed6213bae 100644
--- a/website/content/docs/job-specification/group.mdx
+++ b/website/content/docs/job-specification/group.mdx
@@ -86,10 +86,10 @@ job "docs" {
   servers. By default, a client will not stop an allocation until explicitly
   told to by a server. A client that fails to heartbeat to a server within the
   [`heartbeat_grace`] window and any allocations running on it will be marked
-  "lost" and Nomad will schedule replacement allocations. The replaced 
+  "lost" and Nomad will schedule replacement allocations. The replaced
   allocations will normally continue to run on the non-responsive client. But
-  you may want them to stop instead — for example, allocations requiring 
-  exclusive access to an external resource. When specified, the Nomad client 
+  you may want them to stop instead — for example, allocations requiring
+  exclusive access to an external resource. When specified, the Nomad client
   will stop them after this duration.
   The Nomad client process must be running for this to occur. This setting
   cannot be used with [`max_client_disconnect`].
@@ -329,6 +329,12 @@ group "second" {
 }
 ```
 
+~> **Note:** The `max_client_disconnect` feature is only supported on Nomad
+version 1.3.0 and above. If you run a job with `max_client_disconnect` on servers
+where some servers are not upgraded to 1.3.0, the `max_client_disconnect`
+flag will be _ignored_. Deploying a job with `max_client_disconnect` to a
+`datacenter` of Nomad clients where all clients are not 1.3.0 or above is unsupported.
+
 [task]: /docs/job-specification/task 'Nomad task Job Specification'
 [job]: /docs/job-specification/job 'Nomad job Job Specification'
 [constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'