Skip to content

Commit f8749d9

Browse files
Merge pull request #44811 from Xorima/patch-1
Production should be products
2 parents 20e7761 + 87edc94 commit f8749d9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/container-registry/container-registry-best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ To learn how to use geo-replication, see the three-part tutorial, [Geo-replicati
2828

2929
By leveraging repository namespaces, you can allow sharing a single registry across multiple groups within your organization. Registries can be shared across deployments and teams. Azure Container Registry supports nested namespaces, enabling group isolation.
3030

31-
For example, consider the following container image tags. Images that are used corporate-wide, like `aspnetcore`, are placed in the root namespace, while container images owned by the Production and Marketing groups each use their own namespaces.
31+
For example, consider the following container image tags. Images that are used corporate-wide, like `aspnetcore`, are placed in the root namespace, while container images owned by the Products and Marketing groups each use their own namespaces.
3232

3333
```
3434
contoso.azurecr.io/aspnetcore:2.0

0 commit comments

Comments
 (0)