Merge pull request #219765 from julie-ng/patch-4

ACR tagging - do not use latest (anti-pattern)

Author: prmerger-automator[bot]

articles/container-registry/container-registry-image-tag-version.md

@@ -27,8 +27,6 @@ A framework team ships version 1.0. They know they’ll ship updates, including
 * `:1` – a stable tag for the major version. `1` represents the “newest” or “latest” 1.* version.
 * `:1.0`- a stable tag for version 1.0, allowing a developer to bind to updates of 1.0, and not be rolled forward to 1.1 when it is released.
 
-The team also uses the `:latest` tag, which points to the latest stable tag, no matter what the current major version is.
-
 When base image updates are available, or any type of servicing release of the framework, images with the stable tags are updated to the newest digest that represents the most current stable release of that version.
 
 In this case, both the major and minor tags are continually being serviced. From a base image scenario, this allows the image owner to provide serviced images.