Fixing indentation error

Author: pabel-rh

artifacts/attributes.adoc

@@ -27,6 +27,7 @@
 :my-product-database-certificates-secrets: my-rhdh-database-certificates-secrets
 :my-product-database-secrets: my-rhdh-database-secrets
 :my-product-url: https://__<my_developer_hub_url>__
+:my-extra-file-configmap: my-project-configmap
 
 // Red Hat Platforms
 :ocp-brand-name: Red Hat OpenShift Container Platform

assemblies/assembly-provisioning-a-custom-configuration.adoc

@@ -22,7 +22,7 @@ include::modules/configuring/proc-provisioning-your-custom-configuration.adoc[le
 
 include::modules/configuring/proc-using-the-operator-to-run-rhdh-with-your-custom-configuration.adoc[leveloffset=+1]
 
-include::modules/configuring/proc-mounting-additional-files-in-your-custom-configuration-using-rhdh-operator.adoc[][leveloffset=+2]
+include::modules/configuring/proc-mounting-additional-files-in-your-custom-configuration-using-rhdh-operator.adoc[leveloffset=+2]
 
 include::modules/configuring/proc-using-the-helm-chart-to-run-rhdh-with-your-custom-configuration.adoc[leveloffset=+1]
 

modules/configuring/proc-mounting-additional-files-in-your-custom-configuration-using-rhdh-operator.adoc

@@ -1,7 +1,7 @@
 [id="mounting-additional-files-in-your-custom-configuration-using-rhdh-operator"]
 = Mounting additional files in your custom configuration using the {product} operator
 
-You can use the {product-short} operator to mount extra files, such as ConfigMaps and Secrets, to the container in a preferred location.
+You can use the {product-short} Operator to mount extra files, such as config maps and secrets, to the container in a preferred location.
 
 The `mountPath` field specifies the location where a ConfigMap or Secret is mounted. The behavior of the mount, whether it includes or excludes a `subPath`, depends on the specification of the `key` or `mountPath` fields.
 
@@ -11,8 +11,8 @@ The `mountPath` field specifies the location where a ConfigMap or Secret is moun
 
 [NOTE]
 ====
-* {ocp-short} does not automatically update a volume mounted with subPath. By default, the {product-very-short} operator monitors these Config Maps or Secrets and refreshes the {product-very-short} Pod when changes occur.
-* For security purposes, {product} restricts the Operator Service Account's read access to Secrets. As a result, mounting files from Secrets without specifying both mountPath and key is not supported.
+* {ocp-short} does not automatically update a volume mounted with subPath. By default, the {product-very-short} operator monitors these ConfigMaps or Secrets and refreshes the {product-very-short} Pod when changes occur.
+* For security purposes, {product} does not give the Operator Service Account read access to Secrets. As a result, mounting files from Secrets without specifying both mountPath and key is not supported.
 ====
 
 
@@ -22,16 +22,16 @@ The `mountPath` field specifies the location where a ConfigMap or Secret is moun
 
 .Procedure
 
-. In {ocp-short}, author your ConfigMap or Secret custom resource in a YAML file. For more information, see link:{installing-on-ocp-book-url}#provisioning-your-custom-configuration[].
+. In {ocp-short}, create your config map or secret with the following YAML codes:
 +
-.Minimal `{my-app-config-config-map}` custom resource example
+.Minimal `{my-extra-file-configmap}` config map example
 ====
 [source,yaml,subs="+attributes,+quotes"]
 ----
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  name: {my-product-cr-name}
+  name: {my-extra-file-configmap}
 data:
   file11.txt: |
     My file11 content
@@ -40,7 +40,7 @@ data:
 ----
 ====
 +
-.Minimal `{my-product-secrets}` custom resource example
+.Minimal `{my-product-secrets}` secret example
 ====
 [source,yaml,subs="+attributes,+quotes"]
 ----
@@ -53,8 +53,9 @@ StringData:
     secret-content
 ----
 ====
+For more information, see xref:provisioning-your-custom-configuration[Provisioning and using your custom {product} configuration].
 
-. Declare the ConfigMap or Secret file in your `{product-custom-resource-type}` custom resource.
+. Set the value of the `configMaps name` to the name of the config map or `secrets name` to the name of the secret file in your `{product-custom-resource-type}` CR. For example:
 ====
 [source,yaml,subs="+attributes,+quotes"]
 ----
@@ -63,11 +64,11 @@ spec:
     extraFiles:
       mountPath: /my/path
       configMaps:
-        - name: {my-app-config-config-map}
+        - name: {my-extra-file-configmap}
           key: file12.txt
           mountPath: /my/my-rhdh-config-map/path
       secrets:
-        - name: my-rhdh-secret
+        - name: {my-product-secrets}
           key: secret11.txt
           mountPath: /my/my-rhdh-secret/path
 

modules/release-notes/ref-release-notes-new-features.adoc

@@ -7,7 +7,7 @@ This section highlights new features in {product} {product-version}.
 [id="enhancement-rhidp-2200"]
 == Added an individual `mountPath`
 
-This update adds an additional individual `mountPath` for extra configmaps or secrets.
+This update adds an individual `mountPath` for link:{configuring-book-url}#proc-mounting-additional-files-in-your-custom-configuration-using-rhdh-operator[extra configmaps or secrets].
 
 [id="feature-rhidp-3621"]
 == `PersistentVolumeClaims` support is available