From 3e7d5a1ec0b93ad4f91d05c846a069f2959b1779 Mon Sep 17 00:00:00 2001 From: Tejaswi Kolli Date: Wed, 6 Dec 2023 14:55:29 -0800 Subject: [PATCH] Update container-registry-repository-scoped-permissions.md --- .../container-registry-repository-scoped-permissions.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/articles/container-registry/container-registry-repository-scoped-permissions.md b/articles/container-registry/container-registry-repository-scoped-permissions.md index b20da0ec201b1..9a5c815d3f92f 100644 --- a/articles/container-registry/container-registry-repository-scoped-permissions.md +++ b/articles/container-registry/container-registry-repository-scoped-permissions.md @@ -46,8 +46,6 @@ To configure repository-scoped permissions, you create a *token* with an associa * A **scope map** groups the repository permissions you apply to a token and can reapply to other tokens. Every token is associated with a single scope map. With a scope map, you can: - 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.