Minor clean up JWT provider docs (#6952)

website/source/docs/auth/jwt_oidc_providers.html.md

@@ -7,56 +7,64 @@ description: |-
 
 # OIDC Provider Configuration
 
-This page collects high-level setup steps on how to configure an OIDC application for various
-providers. For more general usage and operation information, see the
-[Vault JWT/OIDC method documentation](https://www.vaultproject.io/docs/auth/jwt.html).
+This page collects high-level setup steps on how to configure an OIDC
+application for various providers. For more general usage and operation
+information, see the [Vault JWT/OIDC method documentation](https://www.vaultproject.io/docs/auth/jwt.html).
 
-OIDC providers are often highly configurable and you should become familiar with their
-recommended settings and best practices. The instructions below are intended only to help you get
-started. Corrections and additions may be submitted via the [Vault Github repository](https://github.com/hashicorp/vault).
+OIDC providers are often highly configurable and you should become familiar with
+their recommended settings and best practices. The instructions below are
+largely community-driven and intended to help you get started. Corrections
+and additions may be submitted via the [Vault Github repository](https://github.com/hashicorp/vault).
 
 ## Azure Active Directory (AAD)
 Reference: [Azure Active Directory v2.0 and the OpenID Connect protocol](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-protocols-oidc)
 
 1. Register or select an AAD application. Visit Overview page.
 1. Configure Redirect URIs ("Web" type). 
-    * you must include two redirect URIs here one for CLI access another one for web access
+    * You may include two redirect URIs, one for CLI access another one for Vault UI access.
        * http://localhost:8250/oidc/callback
        * https://hostname:port_number/ui/vault/auth/oidc/oidc/callback
-1. Record "Application (client) ID" you will need it as the oidc_client_id
+1. Record "Application (client) ID" as you will need it as the oidc_client_id
 1. Under API Permissions grant the following permission:
     * Microsoft Graph API permission [Group.Read.All](https://docs.microsoft.com/en-us/graph/permissions-reference#application-permissions-10)  
 1. Under "Endpoints", copy the OpenID Connect metadata document URL, omitting the `/well-known...` portion.
-    * endpoint url (oidc_discovery_url) should look as:  https://login.microsoftonline.com/tenant-guid-dead-beef-aaaa-aaaa/v2.0
+    * The endpoint url (oidc_discovery_url) will look like: https://login.microsoftonline.com/tenant-guid-dead-beef-aaaa-aaaa/v2.0
 1. Switch to Certificates & Secrets. Create a new client secret and record the generated value as
 it will not be accessible after you leave the page.
 
-Please note [Azure AD v2.0 endpoints](https://docs.microsoft.com/en-gb/azure/active-directory/develop/azure-ad-endpoint-comparison) are required for [external groups](https://www.vaultproject.io/docs/secrets/identity/index.html#external-vs-internal-groups) to work. 
-* `groupMembershipClaims` should be changed from `none` in the [App registration manifest](https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-app-manifest). Options are "All" or "Security"
+Please note [Azure AD v2.0 endpoints](https://docs.microsoft.com/en-gb/azure/active-directory/develop/azure-ad-endpoint-comparison)
+are required for [external groups](https://www.vaultproject.io/docs/secrets/identity/index.html#external-vs-internal-groups) to work.
 
-* In the [OIDC Role config](https://www.vaultproject.io/api/auth/jwt/index.html#create-role) the scope `"https://graph.microsoft.com/.default"` should be added to add groups to the jwt token and `groups_claim` should be set to `groups`. 
+* `groupMembershipClaims` should be changed from `none` in the 
+[App registration manifest](https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-app-manifest).
+Options are "All" or "Security"
+
+* In the [OIDC Role config](https://www.vaultproject.io/api/auth/jwt/index.html#create-role) 
+the scope `"https://graph.microsoft.com/.default"` should be added to add groups 
+to the jwt token and `groups_claim` should be set to `groups`. 
 
 * Finally Azure AD group can be referenced by using the groups `objectId` as the [group alias name](https://www.vaultproject.io/api/secret/identity/group-alias.html) for the external group.
+
 ### CLI setup instructions:
-You have to fill in the following values make sure to use the correct vault secret patch that matches the name of the authentication method such as /oidc/
+You have to fill in the following values make sure to use the correct vault secret 
+path that matches the name of the authentication method such as /oidc/
    * oidc_client_id = Application Client ID
    * oidc_client_secret = Secret obtained from the Certificates & Secrets Section
    * default_role = default role the user will be using when connecting. (see the second command)
    * oidc_discovery_url = Open ID endpoint retrieved from the App Registration wections.
 ```
-    vault write auth/oidc/config \
+vault write auth/oidc/config \
     oidc_client_id="your_client_id" \
     oidc_client_secret="your_client_secret" \
     default_role=“your_default_role” \
     oidc_discovery_url="https://login.microsoftonline.com/tenant_id/v2.0”
-    
 ```
 
 ```
 vault write auth/oidc/role/demo user_claim="email" \
-allowed_redirect_uris="http://localhost:8250/oidc/callback,https://online_version_hostname:port_number/ui/vault/auth/oidc/oidc/callback"  \
-groups_claim="groups" \
-policies=default
+    allowed_redirect_uris="http://localhost:8250/oidc/callback,https://online_version_hostname:port_number/ui/vault/auth/oidc/oidc/callback"  \
+    groups_claim="groups" \
+    policies=default
 ```
 
 ## Auth0
@@ -84,12 +92,13 @@ Main reference: [Using OAuth 2.0 to Access Google APIs](https://developers.googl
 1. Save client ID and secret.
 
 ## Keycloak
-1. Select/create a Realm and Client. Visit Settings.
+1. Select/create a Realm and Client. Select a Client and visit Settings.
 1. Client Protocol: openid-connect
 1. Access Type: confidential
 1. Standard Flow Enabled: On
 1. Configure Valid Redirect URIs.
-1. Visit Settings. Select Client ID and Secret and note the generated secret.
+1. Save.
+1. Visit Credentials. Select Client ID and Secret and note the generated secret.
 
 ## Okta