diff --git a/vcluster/_fragments/sleepmode-deployment-example.mdx b/vcluster/_fragments/sleepmode-deployment-example.mdx
index 357be288..a3f68268 100644
--- a/vcluster/_fragments/sleepmode-deployment-example.mdx
+++ b/vcluster/_fragments/sleepmode-deployment-example.mdx
@@ -6,7 +6,7 @@ import SleepModeDeploymentExample from '!!raw-loader!@site/vcluster/configure/vc
  - [Docker](https://www.docker.com/)
  - [Kind](https://kind.sigs.k8s.io/)
 
-#### In this example we will
+#### This example goes over the following
 
  - Create a kind cluster
  - Create a virtual cluster with sleepMode enabled, and a label exclusion configured.
@@ -43,7 +43,7 @@ Use the following deployment yaml to create two deployments
 
 
 The first deployment has nothing special about it related to sleep mode.  Feel free to use another in its place if you'd
-prefer.  The second has our special label **on the** `Deployment`.  As a result the `Deployment` won't be scaled down after the `30 seconds`.
+prefer.  The second has the/ special label **on the** `Deployment`.  As a result the `Deployment` won't be scaled down after the `30 seconds`.
 
 You can verify this by waiting `30 seconds` and then getting information about the `Deployments`.  For example
 
diff --git a/vcluster/_fragments/sleepmode-ingress-example.mdx b/vcluster/_fragments/sleepmode-ingress-example.mdx
index cc9d30bc..076253ad 100644
--- a/vcluster/_fragments/sleepmode-ingress-example.mdx
+++ b/vcluster/_fragments/sleepmode-ingress-example.mdx
@@ -8,7 +8,7 @@ import SleepmodeIngressExample from '!!raw-loader!@site/vcluster/configure/vclus
  - [Helm](https://helm.sh/)
  - [curl](https://curl.se/)
 
-#### In this example we will
+#### This example covers the following
 
  - Create a kind cluster with ports necessary for demonstrating `Ingress` capabilities.
  - Install an NGINX ingress controller on the host cluster, with syncing to host enabled.
@@ -70,7 +70,7 @@ step.
 Use the following manifest to create
 
  - A new `Namespace` called `bar`
- - A `Deployment` for the pods that will back the `Service`
+ - A `Deployment` for the pods backing the `Service`
  - A `Service` to back the `Ingress`
  - An `Ingress`
 
diff --git a/vcluster/_partials/config/experimental/native-sleep-mode.mdx b/vcluster/_partials/config/experimental/native-sleep-mode.mdx
index 61da5a66..d967bf6f 100644
--- a/vcluster/_partials/config/experimental/native-sleep-mode.mdx
+++ b/vcluster/_partials/config/experimental/native-sleep-mode.mdx
@@ -45,7 +45,7 @@ annotation.  This has the effect of overwriting any previously set mirror-target
 
 ### Ingress considerations
 
-#### Sync to Host
+#### Sync to host
 
 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
@@ -62,9 +62,9 @@ sync:
 
 In detecting ingress activity, the vCluster pod must be discoverable by the ingress controller. i.e. an `nslookup` for the
 `<vcluster-namespace>.<vcluster-svc-name>.svc.cluster.local` should be able to find the vCluster service.  If you're installing
-the ingress controller with helm be sure to set the `dnsPolicy` correctly, as we'll cover in the ingress example.
+the ingress controller with Helm be sure to set the `dnsPolicy` correctly, as is covered in the ingress example.
 
-### Full example with Deployments
+### Full example with `Deployments`
 
 <SleepModeDeploymentExample />
 
diff --git a/vcluster_versioned_docs/version-0.22.0/configure/vcluster-yaml/experimental/native-sleep-mode.mdx b/vcluster_versioned_docs/version-0.22.0/configure/vcluster-yaml/experimental/native-sleep-mode.mdx
index 61da5a66..d967bf6f 100644
--- a/vcluster_versioned_docs/version-0.22.0/configure/vcluster-yaml/experimental/native-sleep-mode.mdx
+++ b/vcluster_versioned_docs/version-0.22.0/configure/vcluster-yaml/experimental/native-sleep-mode.mdx
@@ -45,7 +45,7 @@ annotation.  This has the effect of overwriting any previously set mirror-target
 
 ### Ingress considerations
 
-#### Sync to Host
+#### Sync to host
 
 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
@@ -62,9 +62,9 @@ sync:
 
 In detecting ingress activity, the vCluster pod must be discoverable by the ingress controller. i.e. an `nslookup` for the
 `<vcluster-namespace>.<vcluster-svc-name>.svc.cluster.local` should be able to find the vCluster service.  If you're installing
-the ingress controller with helm be sure to set the `dnsPolicy` correctly, as we'll cover in the ingress example.
+the ingress controller with Helm be sure to set the `dnsPolicy` correctly, as is covered in the ingress example.
 
-### Full example with Deployments
+### Full example with `Deployments`
 
 <SleepModeDeploymentExample />