diff --git a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad.md b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad.md
index 2f6dd70c1e1..cb4651bf118 100644
--- a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad.md
+++ b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad.md
@@ -135,11 +135,11 @@ Here are a few examples of permission combinations that satisfy Rancher's needs:
 
 #### 4. Allow Public Client Flows
 
-To login from Rancher CLI you will need to allow Public Client Flows.
+To login from Rancher CLI you must allow Public Client Flows.
 
-1. From the navigation pane on, select **Authentication**.
+1. From the left navigation menu, select **Authentication**.
 
-1. In the **Advanced Settings** enable the **public client flows**.
+1. Under **Advanced Settings**, enable **public client flows**.
 
     ![Allow Public Client Flows](/img/azure-public-client-flows.png)