From 95577c1fa5d1f6a89507b0ca30cf834734bc5295 Mon Sep 17 00:00:00 2001
From: Edward Rosen <31105434+edwardrosen@users.noreply.github.com>
Date: Tue, 29 Dec 2020 16:20:54 -0500
Subject: [PATCH] Update rbac.md

The page renders the third bullet as a run-on sentence. I'm suggesting the example be placed in parentheses.
---
 content/en/docs/reference/access-authn-authz/rbac.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/reference/access-authn-authz/rbac.md b/content/en/docs/reference/access-authn-authz/rbac.md
index d3e6dc118e..7a31013002 100644
--- a/content/en/docs/reference/access-authn-authz/rbac.md
+++ b/content/en/docs/reference/access-authn-authz/rbac.md
@@ -86,8 +86,8 @@ Because ClusterRoles are cluster-scoped, you can also use them to grant access t
 * cluster-scoped resources (like {{< glossary_tooltip text="nodes" term_id="node" >}})
 * non-resource endpoints (like `/healthz`)
 * namespaced resources (like Pods), across all namespaces
-  For example: you can use a ClusterRole to allow a particular user to run
-  `kubectl get pods --all-namespaces`.
+  (for example: you can use a ClusterRole to allow a particular user to run
+  `kubectl get pods --all-namespaces`)
 
 Here is an example of a ClusterRole that can be used to grant read access to
 {{< glossary_tooltip text="secrets" term_id="secret" >}} in any particular namespace,