edits

Author: tejaswikolli-web

articles/container-registry/container-registry-auto-purge.md

@@ -42,7 +42,7 @@ At a minimum, specify the following when you run `acr purge`:
 
 `acr purge` supports several optional parameters. The following two are used in examples in this article:
 
-* `--untagged` - Specifies that all manifests that don't have associated tags (*untagged manifests*) are deleted. This parameter also deletes untagged manifests in addition to tags that are already being deleted.
+* `--untagged` - Specifies that all manifests that don't have associated tags (*untagged manifests*) are deleted. This parameter also deletes untagged manifests in addition to tags that are already being deleted. Remove all tags associated with a manifest to purge it; only then you can purge a tag free manifest using `--untagged`.
 * `--dry-run` - Specifies that no data is deleted, but the output is the same as if the command is run without this flag. This parameter is useful for testing a purge command to make sure it does not inadvertently delete data you intend to preserve.
 * `--keep` - Specifies that the latest x number of to-be-deleted tags are retained. The latest tags are determined by the last modified time of the tag.
 * `--concurrency` - Specifies a number of purge tasks to process concurrently. A default value is used if this parameter is not provided.

articles/container-registry/monitor-service-reference.md

@@ -24,9 +24,9 @@ Resource Provider and Type: [Microsoft.ContainerRegistry/registries](../azure-mo
 |     AgentPoolCPUTime   | Yes |   Seconds   | Total |   CPU time used by [ACR tasks](container-registry-tasks-overview.md) running on dedicated [agent pools](tasks-agent-pools.md)	         | None | 
 |     RunDuration   | Yes |  Milliseconds   |  Total |  Duration of [ACR tasks](container-registry-tasks-overview.md) runs       | None | 
 |     StorageUsed   |  No | Bytes   |   Average | Storage used by the container registry<br/><br/>Sum of storage for unique and shared layers, manifest files, and replica copies in all repositories<sup>1</sup>	         | Geolocation | 
-|     SuccessfulPullCount | Yes  |   Count   | Total | Successful pulls of container images and other artifacts from the registry	           | None | 
-|     SuccessfulPushCount   | Yes |   Count   | Total | Successful pushes of container images and other artifacts to the registry          | None | 
-|     TotalPullCount   |   Yes | Count   |     Total |  Total pulls of container images and other artifacts from the registry	      | None | 
+|     SuccessfulPullCount | Yes  |   Count   | Total | Successful pulls of container images and other artifacts from the registry. Total get requests to registry v2 manifest api with 200 response.	           | None | 
+|     SuccessfulPushCount   | Yes |   Count   | Total | Successful pushes of container images and other artifacts to the registry.         | None | 
+|     TotalPullCount   |   Yes | Count   |     Total |  Total pulls of container images and other artifacts from the registry. Total get requests to registry v2 manifest api.      | None | 
 |     TotalPushCount   | Yes |  Count   |   Total |  Total pushes of container images and other artifacts to the registry	        | None | 
 
 <sup>1</sup>Because of layer sharing, registry storage used may be less than the sum of storage for individual repositories. When you [delete](container-registry-delete.md) a repository or tag, you recover only the storage used by manifest files and the unique layers referenced.