Update the config in installation

Author: GitHub Actions

modules/installation/proc-install-rhdh-ocp-operator.adoc

@@ -7,7 +7,7 @@
 As a developer, you can deploy a {product} instance on {ocp-short} by using the *Developer Catalog* in the {ocp-brand-name} web console. This deployment method uses the {product} Operator.
 
 .Prerequisites
-* You have set the `baseUrl` in your `{my-app-config-file}` to match the external URL of your {product-short} instance. Without it, frontend and backend services cannot communicate, and features may not work as expected.
+* You have set the `baseUrl` in your `{my-app-config-file}` to match the external URL of your {product-short} instance. Without it, frontend and backend services cannot communicate, and features might not work as expected.
 * xref:proc-install-operator_{context}[An {ocp-short} administrator has installed the {product} Operator].
 * xref:{configuring-book-url}#provisioning-your-custom-configuration[You have provisioned your custom config maps and secrets in your `_<{my-product-namespace}>_` project].
 * xref:{configuring-book-url}#using-the-operator-to-run-rhdh-with-your-custom-configuration[You have authored your {product-custom-resource-type} custom resource].
@@ -18,7 +18,7 @@ As a developer, you can deploy a {product} instance on {ocp-short} by using the
 . From the *Developer* perspective on the {ocp-short} web console, click *Add*.
 . From the *Developer Catalog* panel, click *Operator Backed*.
 . In the *Filter by keyword* box, enter _{product-short}_ and click the *{product}* card.
-. Provision your custom configuration, using the following template:
+. Provision your custom configuration using the following template:
 +
 [source,yaml,subs="attributes+"]
 ----
@@ -52,7 +52,7 @@ To create and apply these configuration resources, follow the steps in xref:{con
 The `app-config-rhdh` config map must include your customized `app-config.yaml` file. This config map is mounted into the {product-short} container at runtime.
 ====
 
-. Create a secret named `{my-product-secrets}` and add a key named `BACKEND_SECRET` with a `Base64-encoded` string as value:
+. Create a secret named `{my-product-secrets}` and add a key named `BACKEND_SECRET` with a `Base64-encoded` string as value, as shown in the following example:
 +
 --
 [source,yaml,subs="+attributes,+quotes"]