From f3897e91327fc1746bc0767c0943872016056ea9 Mon Sep 17 00:00:00 2001 From: "Justin I. Nevill" Date: Tue, 6 Nov 2018 14:56:04 -0500 Subject: [PATCH] Kube typo fixed. --- ee/ucp/authorization/define-roles.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ee/ucp/authorization/define-roles.md b/ee/ucp/authorization/define-roles.md index a4de85f4cf..7160d8f6ec 100644 --- a/ee/ucp/authorization/define-roles.md +++ b/ee/ucp/authorization/define-roles.md @@ -25,7 +25,7 @@ You can define custom roles or use the following built-in roles: ## Create a custom role for Swarm When creating custom roles to use with Swarm, the **Roles** page lists all default and custom roles applicable in the -organization. To create custom roles for Kuberntetes, see [Configure native Kubernetes role-based access control](https://docs.docker.com/ee/ucp/admin/configure/configure-rbac-kube/). +organization. To create custom roles for Kubernetes, see [Configure native Kubernetes role-based access control](https://docs.docker.com/ee/ucp/admin/configure/configure-rbac-kube/). You can give a role a global name, such as "Remove Images", which might enable the **Remove** and **Force Remove** operations for images. You can apply a role with