clarity regarding mandatory vs. optional fields, work on vocabulary

Signed-off-by: Fabrice Flore-Thébault <[email protected]>

Author: themr0c

modules/configuring/proc-using-the-operator-to-run-rhdh-with-your-custom-configuration.adoc

@@ -75,10 +75,18 @@ spec:
 ----
 ====
 
-spec.application.appConfig.configMaps::
+Mandatory fields::
+
+No fields are mandatory.
+You can create an empty {product-custom-resource-type} custom resource
+and run {product-short} with the default configuration.
+
+Optional fields::
+
+`spec.application.appConfig.configMaps`:::
 Enter your config map name list.
 +
-.Register the `{my-app-config-config-map}` config map.
+.Mount files in the `{my-app-config-config-map}` config map.
 ====
 [source,yaml,subs="+attributes,+quotes"]
 ----
@@ -91,7 +99,7 @@ spec:
 ----
 ====
 +
-.Register the `{my-app-config-config-map}` and `rbac-policies` config maps.
+.Mount files in the `{my-app-config-config-map}` and `rbac-policies` config maps.
 ====
 [source,yaml,subs="+attributes,+quotes"]
 ----
@@ -104,10 +112,11 @@ spec:
          - name: rbac-policies
 ----
 ====
-spec.application.extraEnvs.envs::
+
+`spec.application.extraEnvs.envs`:::
 Optionally, enter your additional environment variables that are not secrets, such as xref:proc-configuring-proxy-in-operator-deployment_running-behind-a-proxy[your proxy environment variables].
 +
-.Register your `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` environment variables.
+.Inject your `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` environment variables.
 ====
 [source,yaml,subs="+attributes,+quotes"]
 ----
@@ -124,10 +133,10 @@ spec:
 ----
 ====
 
-spec.application.extraEnvs.secrets::
+`spec.application.extraEnvs.secrets`:::
 Enter your environment variables secret name list.
 +
-.Register the `{my-product-secrets}` secret
+.Inject the environment variables in your `{my-product-secrets}` secret
 ====
 [source,yaml,subs="+attributes,+quotes"]
 ----
@@ -139,7 +148,7 @@ spec:
 ----
 ====
 +
-.Register the `{my-product-secrets}` and `{my-product-database-secrets}` secrets
+.Inject the envvironment variables in the `{my-product-secrets}` and `{my-product-database-secrets}` secrets
 ====
 [source,yaml,subs="+attributes,+quotes"]
 ----
@@ -152,10 +161,10 @@ spec:
 ----
 ====
 
-spec.application.extraFiles.secrets::
+`spec.application.extraFiles.secrets`:::
 Enter your certificates files secret name and files list.
 +
-.Register the `{my-product-database-certificates-secrets}` secret containing the `postgres-crt.pem`, `postgres-ca.pem`, and `postgres-key.key` files
+.Mount the `postgres-crt.pem`, `postgres-ca.pem`, and `postgres-key.key` files contained in the `{my-product-database-certificates-secrets}` secret
 [source,yaml,subs="+attributes,+quotes"]
 ----
 spec:
@@ -167,7 +176,7 @@ spec:
           key: postgres-crt.pem, postgres-ca.pem, postgres-key.key
 ----
 
-spec.database.enableLocalDb::
+`spec.database.enableLocalDb`:::
 Enable or disable the local PostgreSQL database.
 +
 .Disable the local PostgreSQL database generation to use an external postgreSQL database
@@ -186,7 +195,7 @@ spec:
     enableLocalDb: true
 ----
 
-spec.deployment::
+`spec.deployment`:::
 Optionally, xref:configuring-the-deployment[enter your deployment configuration].
 
 . Apply your {product-custom-resource-type} custom resource to start or update your {product-short} instance.