Update copy and add new screenshot

ee/dtr/user/manage-repository-events.md

@@ -10,11 +10,11 @@ keywords: registry, events, log, activity stream
 
 ## Overview 
 
-Actions at their core are events which happen in a particular repository to a particular image. As of v2.6, individual repositories now include an **Activity** tab which shows a paginated list of the most recent events within a given repository. The list of events displayed will vary according to your repository privileges. Additionally, DTR administrators can enable auto-deletion of repository events as part of maintenance and cleanup.
+Actions at their core are events which happen to a particular image within a particular repository. To provide a quick summary of these events, DTR 2.6 now includes an **Activity** tab on each repository displaying a paginated list of the most recent events. The type of events listed will vary according to your [repository permission level](../admin/manage-users/permission-levels/). Additionally, DTR administrators can enable auto-deletion of repository events as part of maintenance and cleanup.
   
 In the following section, we will show you how to:
 
-* View the list of events in a repository, including event types associated with your access level
+* View the list of events in a repository, including <a href="#event-types">event types</a> associated with your permission level
 * Enable auto-deletion of repository events based on your specified conditions
 
 ## View List of Events
@@ -23,40 +23,27 @@ To view the list of events within a repository, navigate to `https://<dtr-url>`a
 
 ![](../images/tag-pruning-0.png){: .with-border}
 
-Select the **Activity** tab. You should see a list of events based on your repository access level. Pull events are excluded by default and are only visible to repository and trusted registry administrators. Uncheck "Exclude pull" to view pull events.  
+Select the **Activity** tab. You should see a list of events based on your repository permission level. Pull events are excluded by default and are only visible to repository and DTR administrators. Uncheck "Exclude pull" to view pull events.  
 
-![](../images/tag-pruning-1.png){: .with-border}
+![](../images/manage-repo-events-0.png){: .with-border}
 
 
-DTR allows you to set your pruning triggers based on the following image attributes:
+### Streamed Events
 
-| Name            | Description                                        | Example           |
+Note that the event types may reflect a different friendly name in the web interface and includes the relevant [CRUD operation](https://en.wikipedia.org/wiki/Create,_read,_update_and_delete).
+
+| Event Type          | Description                                        | Permission Level        |
 |:----------------|:---------------------------------------------------| :----------------|
-| Tag name        | Whether the tag name equals, starts with, ends with, contains, is one of, or is not one of your specified string values | Tag name = `test`|
+| Push        |  | Authenticated Users |
-| Component name  | Whether the image has a given component and the component name equals, starts with, ends with, contains, is one of, or is not one of your specified string values | Component name starts with `b` |
+|        |  | Authenticated Users |
-| Vulnerabilities | Whether the image has vulnerabilities &ndash; critical, major, minor, or all &ndash; and your selected vulnerability filter is greater than or equals, greater than, equals, not equals, less than or equals, or less than your specified number | Critical vulnerabilities = `3` |
+| Scan        |  | Authenticated Users |
-| License         | Whether the image uses an intellectual property license and is one of or not one of your specified words | License name = `docker` | 
+| Promotion        |  | Repository Admin |
-| Last updated at | Whether the last image update was before your specified number of hours, days, weeks, or months. For details on valid time units, see [Go's ParseDuration function](https://golang.org/pkg/time/#ParseDuration). |  Last updated at: Hours = `12` |
+| Delete        |  | Authenticated Users |
+| Pull        |  | Repository Admin |
+| Mirror        |  | Repository Admin |
+| Create repo        |  | Authenticated Users |
 
-Specify one or more image attributes to add to your pruning criteria, then choose:
+## Enable auto-deletion of repository events
- 
-	**Prune future tags** to save the policy and apply your selection to future tags. Only qualifying tags pushed after the policy addition will be pruned during garbage collection.
-
- 	**Prune all tags** to save the policy and evaluate existing and future tags on your repository. 
-
-Upon selection, you will see a confirmation message and will be redirected to your newly updated **Pruning** tab. 
-
-
-![](../images/tag-pruning-2.png){: .with-border}
-
-
-If you have specified multiple pruning policies on the repository, the **Pruning** tab will display a list of your prune triggers and details on when the last tag pruning was performed based on the trigger, a toggle for deactivating or reactivating the trigger, and a **View** link for modifying or deleting your selected trigger.
-
-![](../images/tag-pruning-3.png){: .with-border}
-
-All tag pruning policies on your account are evaluated every 15 minutes. Any qualifying tags are then deleted from the metadata store. If a tag pruning policy is modified or created, then the tag pruning policy for the *affected* repository will be evaluated.
-
-## Set a tag limit
 
 In addition to pruning policies, you can also set tag limits on repositories that you manage to restrict the number of tags on a given repository. Repository tag limits are processed in a first in first out (FIFO) manner. For example, if you set a tag limit of 2, adding a third tag would push out the first.
 
@@ -69,19 +56,4 @@ To set a tag limit, select the repository that you want to update and click the
 
 ## Where to go next
 
-- [Garbage collection](../../admin/configure/garbage-collection.md)
-To get started, 
-
-| Name            | Description                                        | Example           |
-|:----------------|:---------------------------------------------------| :----------------|
-| Tag name        | Whether the tag name equals, starts with, ends with, contains, is one of, or is not one of your specified string values | Tag name = `test`|
-| Component name  | Whether the image has a given component and the component name equals, starts with, ends with, contains, is one of, or is not one of your specified string values | Component name starts with `b` |
-| Vulnerabilities | Whether the image has vulnerabilities &ndash; critical, major, minor, or all &ndash; and your selected vulnerability filter is greater than or equals, greater than, equals, not equals, less than or equals, or less than your specified number | Critical vulnerabilities = `3` |
-| License         | Whether the image uses an intellectual property license and is one of or not one of your specified words | License name = `docker` | 
-| Last updated at | Whether the last image update was before your specified number of hours, days, weeks, or months. For details on valid time units, see [Go's ParseDuration function](https://golang.org/pkg/time/#ParseDuration). |  Last updated at: Hours = `12` |
-
-![](../../images/view-repo-events-0.png){: .img-fluid .with-border}
-
-## Where to go next
-
 - [Delete images](delete-images.md)