Apply suggestions from code review

Co-authored-by: Armel Soro <armel@rm3l.org>

modules/installation/proc-add-custom-app-config-file-ocp-operator.adoc

@@ -3,7 +3,7 @@
 
 A custom application configuration file is a ConfigMap that you can use to change the configuration of your {product} instance to meet the needs and preferences of your organization. If you are deploying your {product-short} instance on {ocp-brand-name}, you can use the {product} Operator to add a custom application configuration file to your {ocp-short} instance by creating the ConfigMap and referencing it in the {product-short} Custom Resource.
 
-The custom application configuration file contains a sensitive environment variable, named `BACKEND_SECRET`, which is a mandatory backend authentication key that {product-short} uses to reference an environment variable defined in an {ocp-short} Secret. To authenticate users, you must create a custom Secret, named 'secrets-rhdh', and reference it in the {product-short} Custom Resource.
+The custom application configuration file contains a sensitive environment variable, named `BACKEND_SECRET`, which is a mandatory backend authentication key that {product-short} uses to reference an environment variable defined in an {ocp-short} Secret. You must create a custom Secret, named 'secrets-rhdh', and reference it in the {product-short} Custom Resource.
 
 [NOTE]
 ====
@@ -13,7 +13,7 @@ You are responsible for protecting your {product} installation from external and
 .Prerequisites
 * You have an active {ocp-brand-name} account.
 * Your administrator has installed the {product} Operator in {ocp-short}. For more information, see link:{LinkAdminGuide}[Installing the {product} Operator].
-* Your administrator has created the {product} Custom Resource in {ocp-short}.
+* You have created the {product} Custom Resource in {ocp-short}.
 
 .Procedure
 . From the *Developer* perspective, select the *ConfigMaps* tab.
@@ -46,7 +46,7 @@ data:
 +
 [NOTE]
 ====
-You can use the `oc get ingresses.config/cluster -o jsonpath='{.spec.domain}'` command to display your ingress domain. If you want to use a different host or sub-domain, customize the `Custom Resource spec.application.route field` and adjust the application configuration accordingly.
+You can use the `oc get ingresses.config/cluster -o jsonpath='{.spec.domain}'` command to display your ingress domain. If you want to use a different host or sub-domain, customize the Custom Resource `spec.application.route` field and adjust the application configuration accordingly.
 ====
 
 . Click *Create*.