diff --git a/ee/dtr/admin/configure/auto-delete-repo-events.md b/ee/dtr/admin/configure/auto-delete-repo-events.md
index e95f082c30..54eef0316b 100644
--- a/ee/dtr/admin/configure/auto-delete-repo-events.md
+++ b/ee/dtr/admin/configure/auto-delete-repo-events.md
@@ -10,7 +10,7 @@ keywords: registry, events, log, activity stream
 
 ## Overview 
 
-Auto-deletion of repository events is a Docker Trusted Registry (DTR) global setting which allows event records to be removed as part of [garbage collection](../admin/configure/garbage-collection.md). As a DTR administrator, you can enable auto-deletion of repository events in DTR 2.6 based on your specified conditions. 
+Docker Trusted Registry has a global setting for repository event auto-deletion. This allows event records to be removed as part of [garbage collection](../admin/configure/garbage-collection.md). DTR administrators can enable auto-deletion of repository events in DTR 2.6 based on specified conditions which are covered below.
 
 ## Steps
 
@@ -22,18 +22,18 @@ Auto-deletion of repository events is a Docker Trusted Registry (DTR) global set
 
 ![](../../images/auto-delete-repo-events-0.png){: .img-fluid .with-border}
 
-4. Specify the conditions with which an event deletion will be triggered.
+4. Specify the conditions with which an event auto-deletion will be triggered.
 
 ![](../../images/auto-delete-repo-events-1.png){: .img-fluid .with-border}
 
-DTR allows you to set your deletion triggers based on the following optional event attributes:
+DTR allows you to set your auto-deletion conditions based on the following optional repository event attributes:
 
 | Name            | Description                                        | Example           |
 |:----------------|:---------------------------------------------------| :----------------|
 | Age        | Lets you remove events older than your specified number of  hours, days, weeks or months| `2 months` |
 | Max number of events  | Lets you specify the maximum number of events allowed in the repositories.  | `6000` |
 
-If you specify both, events in your repositories will be removed during garbage collection if either condition is met. You should see a "settings saved successfully" confirmation right away.
+If you check and specify both, events in your repositories will be removed during garbage collection if either condition is met. You should see a confirmation message right away.
 
 5. Click **Start GC** if you're ready. Read more about [garbage collection](../admin/configure/garbage-collection/#under-the-hood) if you're unsure about this operation.
 
diff --git a/ee/dtr/user/manage-repository-events.md b/ee/dtr/user/manage-repository-events.md
index a1c0291e65..2bc4e295e4 100644
--- a/ee/dtr/user/manage-repository-events.md
+++ b/ee/dtr/user/manage-repository-events.md
@@ -46,7 +46,7 @@ To view the list of events within a repository, select the **Activity** tab. You
 
 ### Activity Stream
  
-Let's break down the data included in an event. We will use the highlighted "Create Promotion Policy" event as our example.
+The following table breaks down the data included in an event and uses the highlighted "Create Promotion Policy" event as an example.
 
 | Event Detail          | Description                                        | Example |
 |:----------------|:-------------------------------------------------|:--------|