Skip to content

Commit 34d2a2e

Browse files
islinwbsteveperry-53
authored andcommitted
fix typos in /admin/authorization/rbac.md (#5427)
1 parent c8adeb0 commit 34d2a2e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/admin/authorization/rbac.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ This allows administrators to define a set of common roles for the entire cluste
102102
then reuse them within multiple namespaces.
103103

104104
For instance, even though the following `RoleBinding` refers to a `ClusterRole`,
105-
"dave" (the subject) will only be able read secrets in the "development"
105+
"dave" (the subject) will only be able to read secrets in the "development"
106106
namespace (the namespace of the `RoleBinding`).
107107

108108
```yaml
@@ -258,7 +258,7 @@ A `RoleBinding` or `ClusterRoleBinding` binds a role to *subjects*.
258258
Subjects can be groups, users or service accounts.
259259

260260
Users are represented by strings. These can be plain usernames, like
261-
"alice", email-style names, like "[email protected]", or numeric ids
261+
"alice", email-style names, like "[email protected]", or numeric IDs
262262
represented as a string. It is up to the Kubernetes admin to configure
263263
the [authentication modules](/docs/admin/authentication/) to produce
264264
usernames in the desired format. The RBAC authorization system does

0 commit comments

Comments
 (0)