updates

website/content/docs/enterprise/index.mdx

@@ -28,9 +28,9 @@ Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
 enhances performance and availability through Advanced Autopilot features such
 as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
 
-## Long Term Supported Releases
+## Long Term Support (LTS) Releases
 
-Nomad Enterprise initiatied the Long-Term Support (LTS) release program with
+Nomad Enterprise initiated the Long-Term Support (LTS) release program with
 Nomad 1.8. Going forward, the first major release of each calendar year will be
 an LTS release.
 
@@ -116,13 +116,16 @@ available for the specified Nomad task at hand.
 
 See the [Vault Integration documentation](/nomad/docs/integrations/vault-integration#enterprise-configuration) for more information.
 
-## Multiple Vault and Consul Clusters
+### Multiple Vault and Consul Clusters
+
+Nomad Enteprise allows sepcifying multiple integrations for Consul and Vault in
+the [vault](/nomad/docs/configuration/vault) and
+[consul](/nomad/docs/configuration/consul) portions of the Nomad agent
+configuration. After the agents are configured, Nomad jobspec writers can pick
+which Consul or Vault cluster to use in their job. Nomad administrators may
+also set default clusters for each in Nomad namespace configuration, as well as
+deny access to certain clusters by namespace.
 
-Nomad administrators can now define multiple integrations in the [vault](/nomad/docs/configuration/vault) and
-[consul](/nomad/docs/configuration/consul) portions of the Nomad agent configuration. Then, Nomad jobspec writers
-can pick which Consul or Vault cluster to use in their job. Nomad
-administrators can also set default clusters for each in Nomad namespace
-configuration, as well as deny access to certain clusters by namespace.
 
 ## Governance & Policy
 

website/content/docs/release-notes/nomad/v1_8_x.mdx

@@ -46,6 +46,23 @@ We are pleased to announce the following Nomad updates.
   now deprecated. Official support will be removed and the repo will be
   archived when Nomad 1.9 is released. Users are encouraged to migrate their
   workloads to Amazon ECS or to another Nomad task driver.
+
+- **`stop_after_client_disconnect`, `max_client_disconnect`,
+  `prevent_reschedule_on_lost` fields:** Nomad 1.8.0 introduces a [disconnect](/nomad/docs/job-specification/disconnect)
+  block meant to group all the configuration options related to disconnected
+  client's and server's behavior, causing the deprecation of the fields
+  stop_after_client_disconnect, max_client_disconnect and
+  prevent_reschedule_on_lost. This block also introduces new options for
+  allocations reconciliation if the client regains connectivity.
+
+
+## What's removed
+
+- **raw_exec option `no_cgroups`:**: In Nomad 1.7.0 the raw_exec plugin option
+  for no_cgroups became ineffective. Starting in Nomad 1.8.0 attempting to set
+  the no_cgroups in raw_exec plugin configuration will result in an error when
+  starting the agent.
+
 
 ## Upgrading