Another review pass

gravitational · Feb 22, 2022 · 87b8e62 · 87b8e62
1 parent af64534
commit 87b8e62
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/docs/pages/desktop-access/rbac.mdx b/docs/pages/desktop-access/rbac.mdx
@@ -90,9 +90,9 @@ For desktops discovered via LDAP, Teleport applies the following labels automati
 ## Logins
 
 The `windows_desktop_logins` role setting lists the Windows user accounts that
-the role permits access to. Like with SSH access, the
-`{{internal.windows_logins}}` variable can be used for local users, which maps
-to any logins that are supplied when the user is created with
+the role permits access to. For local users, the `{{internal.windows_logins}}`
+variable can be used as a placeholder for the user's `windows_logins` trait. The
+`windows_logins` trait can be specified when the user is created with
 `tctl users add alice --windows-logins=Administrator,DBUser`.
 
 New clusters automatically populate the preset `access` role with the following:

diff --git a/docs/pages/desktop-access/reference/configuration.mdx b/docs/pages/desktop-access/reference/configuration.mdx
@@ -20,7 +20,7 @@ description: Configuration reference for Teleport Desktop Access.
 
 The Windows Desktop Service can be deployed in two modes.
 
-### Direct Mode
+### Direct mode
 
 In *direct* mode, Windows Desktop Services registers directly with the Teleport
 Auth Server, and listens for desktop connections from the Teleport Proxy. To
@@ -29,7 +29,7 @@ enable direct mode, set `windows_desktop_service.listen_addr` in
 Auth Server. Direct mode requires network connectivity from the Teleport Proxy
 to Windows Desktop Service, and from Windows Desktop Service to the Auth Server.
 
-### IoT Mode (Reverse Tunnel)
+### IoT mode (reverse tunnel)
 
 In *IoT mode*, Windows Desktop Service only needs to be able to make an outbound
 connection to a Teleport Proxy. The Windows Desktop Service establishes a