remove references to premium sku from using tokens and scope maps

Author: cegraybl

articles/container-registry/container-registry-repository-scoped-permissions.md

@@ -1,6 +1,6 @@
 ---
 title: Permissions to repositories in Azure Container Registry
-description: Create a token with permissions scoped to specific repositories in a Premium registry to pull or push images, or perform other actions
+description: Create a token with permissions scoped to specific repositories in a registry to pull or push images, or perform other actions
 ms.topic: article
 author: tejaswikolli-web
 ms.author: tejaswikolli
@@ -11,24 +11,21 @@ ms.devlang: azurecli
 
 # Create a token with repository-scoped permissions
 
-This article describes how to create tokens and scope maps to manage access to specific repositories in your container registry. By creating tokens, a registry owner can provide users or services with scoped, time-limited access to repositories to pull or push images or perform other actions. A token provides more fine-grained permissions than other registry [authentication options](container-registry-authentication.md), which scope permissions to an entire registry. 
+This article describes how to create tokens and scope maps to manage access to specific repositories in your container registry. By creating tokens, a registry owner can provide users or services with scoped, time-limited access to repositories to pull or push images or perform other actions. A token provides more fine-grained permissions than other registry [authentication options](container-registry-authentication.md), which scope permissions to an entire registry.
 
 Scenarios for creating a token include:
 
 * Allow IoT devices with individual tokens to pull an image from a repository
 * Provide an external organization with permissions to a specific repository 
 * Limit repository access to different user groups in your organization. For example, provide write and read access to developers who build images that target specific repositories, and read access to teams that deploy from those repositories.
 
-This feature is available in the **Premium** container registry service tier. For information about registry service tiers and limits, see [Azure Container Registry service tiers](container-registry-skus.md).
-
 ## Limitations
 
 * You can't currently assign repository-scoped permissions to an Azure Active Directory identity, such as a service principal or managed identity.
 
-
 ## Concepts
 
-To configure repository-scoped permissions, you create a *token* with an associated *scope map*. 
+To configure repository-scoped permissions, you create a *token* with an associated *scope map*.
 
 * A **token** along with a generated password lets the user authenticate with the registry. You can set an expiration date for a token password, or disable a token at any time.
 
@@ -46,8 +43,8 @@ To configure repository-scoped permissions, you create a *token* with an associa
 
    With a scope map:
 
-    * Configure multiple tokens with identical permissions to a set of repositories
-    * Update token permissions when you add or remove repository actions in the scope map, or apply a different scope map 
+  * Configure multiple tokens with identical permissions to a set of repositories
+  * Update token permissions when you add or remove repository actions in the scope map, or apply a different scope map
 
   Azure Container Registry also provides several system-defined scope maps you can apply when creating tokens. The permissions of system-defined scope maps apply to all repositories in your registry.The individual *actions* corresponds to the limit of [Repositories per scope map.](container-registry-skus.md)
 
@@ -59,7 +56,7 @@ The following image shows the relationship between tokens and scope maps.
 
 * **Azure CLI** - Azure CLI command examples in this article require Azure CLI version 2.17.0 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli).
 * **Docker** - To authenticate with the registry to pull or push images, you need a local Docker installation. Docker provides installation instructions for [macOS](https://docs.docker.com/docker-for-mac/), [Windows](https://docs.docker.com/docker-for-windows/), and [Linux](https://docs.docker.com/engine/installation/#supported-platforms) systems.
-* **Container registry** - If you don't have one, create a Premium container registry in your Azure subscription, or upgrade an existing registry. For example, use the [Azure portal](container-registry-get-started-portal.md) or the [Azure CLI](container-registry-get-started-azure-cli.md). 
+* **Container registry** - If you don't have one, create a container registry in your Azure subscription. For example, use the [Azure portal](container-registry-get-started-portal.md) or the [Azure CLI](container-registry-get-started-azure-cli.md).
 
 ## Create token - CLI