Update the enabling authentication with rhbk

Author: GitHub Actions

modules/authentication/proc-enabling-authentication-with-rhbk.adoc

@@ -39,11 +39,11 @@ Save the value for the next step:
 [source,yaml]
 ----
 auth:
-  environment: production # <1>
+  environment: production
   providers:
     oidc:
       production:
-        metadataUrl: ${AUTH_OIDC_METADATA_URL} # <2>
+        metadataUrl: ${AUTH_OIDC_METADATA_URL}
         clientId: ${AUTH_OIDC_CLIENT_ID}
         clientSecret: ${AUTH_OIDC_CLIENT_SECRET}
         prompt: auto
@@ -73,10 +73,10 @@ Optional: Consider adding the following optional fields:
 +
 --
 To enable authentication without requiring to provision users in the {product-short} software catalog.
-+
+
 WARNING: Use this option to explore {product-short} features, but do not use it in production.
-+
-.`{my-app-config-file}` fragment with optional field to allow authenticating users absent from the software catalog
+
+`{my-app-config-file}` fragment with optional field to allow authenticating users absent from the software catalog
 [source,yaml]
 ----
 auth:
@@ -151,14 +151,14 @@ After successful authentication, the user signing in must be resolved to an exis
 +
 The authentication provider tries each sign-in resolver in order until it succeeds, and fails if none succeed.
 +
-WARNING: In production mode, only configure one resolver to ensure users are securely matched. 
+WARNING: In production mode, only configure one resolver to ensure users are securely matched.
 `resolver`::::
 Enter the sign-in resolver name.
 Available values:
 * `emailLocalPartMatchingUserEntityName`
 * `emailMatchingUserEntityProfileEmail`
 * `preferredUsernameMatchingUserEntityName`
-+
+
 .`{my-app-config-file}` fragment with optional `resolvers` list
 [source,yaml]
 ----
@@ -235,4 +235,4 @@ If multiple valid refresh tokens are issued due to frequent refresh token reques
 .Verification
 . Go to the {product-short} login page.
 . Your {product-short} sign-in page displays *Sign in using OIDC* and the Guest user sign-in is disabled.
-. Log in with OIDC by using the saved **Username** and **Password** values.
+. Log in with OIDC by using the saved **Username** and **Password** values.