Apply suggestions from code review

Co-authored-by: Jana Vrbkova <[email protected]>

Author: themr0c

modules/authentication/proc-enabling-user-authentication-with-github-as-an-auxiliary-authentication-provider.adoc

@@ -3,9 +3,9 @@
 [id="enabling-user-authentication-with-github-as-an-auxiliary-authentication-provider"]
 = Enabling user authentication with GitHub as an auxiliary authentication provider
 
-If your primary authentication provider is not GitHub, users may lack the permissions needed for templates or plugins that require GitHub access. The recommended solution is to configure GitHub as an auxiliary authentication provider. This approach uses the primary provider for user identity management and the auxiliary provider to grant the necessary GitHub permissions, without re-resolving the user's identity.
+If your primary authentication provider is not GitHub, users might lack the permissions needed for templates or plugins that require GitHub access. The recommended solution is to configure GitHub as an auxiliary authentication provider. This approach uses the primary provider for user identity management and the auxiliary provider to grant the necessary GitHub permissions, without re-resolving the user's identity.
 
-Allow users to access these features by configuring GitHub as an auxiliary authentication provider.
+Give users access to these features by configuring GitHub as an auxiliary authentication provider.
 
 .Prerequisites
 include::snip-enabling-user-authentication-with-github-common-prerequisites.adoc[]

modules/authentication/snip-enabling-user-authentication-with-github-common-first-steps.adoc

@@ -16,7 +16,7 @@ Authorization callback URL::
 Enter your {product-short} authentication backend URL: `pass:c,a,q[{my-product-url}/api/auth/github/handler/frame]`.
 
 Webhook::
-Clear "Active", as this is not needed for authentication and catalog providers.
+Clear "Active".
 
 Organization permissions::
 Enable `Read-only` access to *Members*.
@@ -33,7 +33,7 @@ Select `Only on this account`.
 * **Client ID**
 * **Client secret**
 
-. To add your GitHub credentials to {product-short}, add the following key/value pairs to {configuring-book-link}#provisioning-your-custom-configuration[your {product-short} secrets].
+. Add your GitHub credentials to {product-short} by adding the following key/value pairs to {configuring-book-link}#provisioning-your-custom-configuration[your {product-short} secrets].
 You can use these secrets in the {product-short} configuration files by using their environment variable name.
 
 `GITHUB_CLIENT_ID`::
@@ -48,8 +48,7 @@ Enter the GitHub host domain: `github.com`.
 `GITHUB_ORG`::
 Enter your GitHub organization name, such as `__<your_github_organization_name>__`.
 
-. Enable the GitHub catalog provider plugin in your `dynamic-plugins.yaml` file.
-This plugin imports GitHub users and groups to the {product-short} software catalog.
+. Enable the GitHub catalog provider plugin in your `dynamic-plugins.yaml` file to import GitHub users and groups to the {product-short} software catalog.
 +
 [source,yaml]
 ----
@@ -58,7 +57,7 @@ plugins:
     disabled: false
 ----
 
-. Enable provisioning GitHub users and groups to the {product-short} software catalog, by adding the GitHub catalog provider section to your `{my-app-config-file}` file:
+. Enable provisioning GitHub users and groups to the {product-short} software catalog by adding the GitHub catalog provider section to your `{my-app-config-file}` file:
 +
 [id=githubProviderId]
 [source,yaml]

modules/authentication/snip-enabling-user-authentication-with-github-optional-authentication-provider-steps.adoc

@@ -54,5 +54,5 @@ Enter `true` to configure the sign-in resolver to bypass the user provisioning r
 +
 [WARNING]
 ====
-In production more, do not enable `dangerouslyAllowSignInWithoutUserInCatalog` in production.
+In production more, do not enable `dangerouslyAllowSignInWithoutUserInCatalog`.
 ====

modules/authentication/snip-enabling-user-authentication-with-rhbk-common-authentication-provider-steps.adoc

@@ -20,12 +20,12 @@ signInPage: oidc
 Mark the environment as `production` to hide the Guest login in the {product-short} home page.
 
 `metadataUrl`, `clientId`, `clientSecret`::
-To configure the OIDC provider with your secrets.
+Configure the OIDC provider with your secrets.
 
 `prompt`::
 Enter `auto` to allow the identity provider to automatically determine whether to prompt for credentials or bypass the login redirect if an active {rhsso} session exists.
 +
-The identity provider defaults to `none`, which assumes that you are already logged in and rejects sign-in requests without an active session.
+The identity provider defaults to `none`, which assumes that you are already logged in. Sign-in requests without an active session are rejected.
 
 `signInPage`::
 Enter `oidc` to enable the OIDC provider as default sign-in provider.

modules/authentication/snip-enabling-user-authentication-with-rhbk-optional-authentication-provider-steps.adoc

@@ -73,7 +73,7 @@ Configure the sign-in resolver to bypass the user provisioning requirement in th
 +
 [WARNING]
 ====
-Use this option to explore {product-short} features, but do not use it in production.
+In production mode, do not enable the `dangerouslyAllowSignInWithoutUserInCatalog` option. 
 ====
 
 `sessionDuration`::