Updates for vale

vcluster_versioned_docs/version-0.22.0/configure/vcluster-yaml/experimental/native-sleep-mode.mdx

@@ -53,7 +53,7 @@ experimental:
   * ReplicationControllers
   * DaemonSets
 
-**Waking** scales those resources back up, but it will be unable to restore bare pods.  To exempt resources from being
+**Waking** scales those resources back up, unable to restore bare pods that were killed.  To exempt resources from being
 put to sleep, either add the annotation `sleepmode.loft.sh/exclude: true` or configure sleep mode with labels to exclude and
 add that label to all the workloads you'd like to keep running.
 
@@ -64,15 +64,17 @@ To wake a sleeping cluster or to update the last active time, native sleep mode
  * Access of cluster resources.  _Think `kubectl get <resource>`_
  * Attempts to contact Ingress endpoints (NGINX only).
 
+<!-- vale disable Google.Will -->
 :::note
 Ingress activity detection is only available for [NGINX](https://github.com/kubernetes/ingress-nginx/tree/main)
 ingress controllers, making use of the [mirror-target](https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#mirror)
 annotation.  If you use this annotation, it will be overwritten for the sleep mode to function.
 :::
+<!-- vale enable Google.Will -->
 
 ### Ingress considerations
 
-If you install your ingress controller(s) in the vCluster you'll need to exempt the controller from sleeping so it remains
+If you install your ingress controllers in the vCluster you'll need to exempt the controller from sleeping so it remains
 active for requests that would wake the vCluster.  If you install the ingress controller in the host cluster, you'll need to
 enable syncing ingresses to the host.