diff --git a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md
index 9cd7197359b..668f6f22fd1 100644
--- a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md
+++ b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md
@@ -1,9 +1,11 @@
 # Content Version Cleanup
 
-A new version is created whenever you save and publish a content item in Umbraco. This is how you can roll back to a previous version. Every saved version stores a record in the database, not only for the version but also for each content item property for that version. In a multi-lingual site, further rows are added for every culture variation. Over time this amount of data can build and swallow up the capacity of your SQL Server and slow the performance of the Umbraco backoffice.
+A new version is created whenever you save and publish a content item in Umbraco. This is how you can roll back to a previous version. Every saved version stores a record in the database, not only for the version but also for each content item property for that version. In a multi-lingual site, further rows are added for every culture variation. Over time, this amount of data can build and swallow up your SQL Server's capacity and slow the Umbraco backoffice's performance.
 
 ## How it works
 
+A scheduled job will delete content versions regularly when the Content Version Cleanup Policy is enabled. For more information on how often content is deleted, read the [ContentSettings article](../../reference/configuration/contentsettings.md#enablecleanup).
+
 The default cleanup policy will:
 
 * Not delete any versions created over the previous 4 days. The recent version history is preserved. See the `KeepAllVersionsNewerThanDays` setting.
@@ -19,7 +21,7 @@ Based on the default cleanup policy, you can roll back content to the latest ver
 * Created within the last 90 days, or
 * Marked as "Prevent Cleanup" in the Backoffice version history.
 
-The **History** section, which acts as an audit log, is not cleared out, and will continue to show logs for versions older than 90 days.
+The **History** section, which acts as an audit log, is not cleared out and will continue to show logs for versions older than 90 days.
 {% endhint %}
 
 The feature can be configured in the `appSettings.json`:
@@ -40,11 +42,11 @@ The feature can be configured in the `appSettings.json`:
 }
 ```
 
-For sites with stricter requirements, it is possible to opt-out of both options globally, see [ContentSettings](../../reference/configuration/contentsettings.md#contentversioncleanuppolicy) and by Document Type.
+For sites with stricter requirements, it is possible to opt out of both options globally, see [ContentSettings](../../reference/configuration/contentsettings.md#contentversioncleanuppolicy) and by Document Type.
 
 Additionally, it is possible to keep the feature enabled but mark specific versions to keep forever.
 
-It is worth noting that whilst we delete rows, we do not shrink database files or rebuild indexes. For upgraded sites with a lot of history you may wish to perform these tasks. If they are not part of your regular database maintenance plan already.
+It is worth noting that whilst we delete rows, we do not shrink database files or rebuild indexes. For upgraded sites with a lot of history, you may wish to perform these tasks. If they are not part of your regular database maintenance plan already.
 
 ## Overriding global settings
 
@@ -56,7 +58,7 @@ It is possible to override the global settings per Document Type in the backoffi
 
 It is possible to mark important content versions as "prevent cleanup" to ensure they are never removed. This happens via the new and improved rollback modal which can be found on the "info" content app for each document.
 
-1.  Open rollback modal.
+1.  Open the rollback modal.
 
     <figure><img src="../../../../10/umbraco-cms/fundamentals/data/images/prevent-cleanup-part-1.png" alt=""><figcaption></figcaption></figure>
 2.  Click **Prevent cleanup** button for each important version.