Incorporate technical suggestions

Author: GitHub Actions

modules/configuring-external-databases/proc-configuring-pvc-mounts.adoc renamed to modules/configuring-external-databases/proc-configuring-default-configuration-for-secrets-and-pvcs.adoc

@@ -1,8 +1,8 @@
 :_mod-docs-content-type: PROCEDURE
-[id="proc-configuring-pvc-mounts_{context}"]
-= Configuring Persistent Volume Claim (PVC) mounts
+[id="proc-default-configuration-for-secrets-and-pvcs_{context}"]
+= Configuring default configuration for Secrets and PVCs
 
-You can configure which containers the Persistent Volume Claim (PVC) mounts to by adding `rhdh.redhat.com/containers` to your configuration file. You can configure multiple secrets by using annotations to specify mount paths for each secret and target specific containers where the secrets should mount. Adding annotations ensures flexible storage and secrets management across different containers. The `default-config/deployment.yaml` file defines the dynamic plugins directory, as shown in the following example:
+By default, the mount path is the {product-short} container's working directory, and if you do not define the mount path, it defaults to `/opt/app-root/src`. `app-config`, `configmap-files`, `secret-files`, `dynamic-plugins`, and PVCs mount to the container as either files or directories. The `default-config/deployment.yaml` file defines the dynamic plugins directory, as shown in the following example:
 
 [source,yaml]
 ----
@@ -17,9 +17,11 @@ You can configure which containers the Persistent Volume Claim (PVC) mounts to b
   name: dynamic-plugins-root
 ----
 
+You can add the `rhdh.redhat.com/containers` annotation to your configuration file to specify the mount path.
+
 .Procedure
 
-. Specify the container where the PVC mounts by adding the `rhdh.redhat.com/mount-path` annotation to your configuration as shown in the following example:
+. Specify the mount path where the PVC mounts to by adding the `rhdh.redhat.com/mount-path` annotation to your configuration as shown in the following example:
 +
 .Example specifying where the PVC mounts
 [source,yaml,subs="+attributes,+quotes"]
@@ -33,10 +35,10 @@ metadata:
 ----
 where:
 
-`rhdh.redhat.com/mount-path`:: Specifies which container the PVC mounts to.
+`rhdh.redhat.com/mount-path`:: Specifies which mount path the PVC mounts to.
 <my_claim>:: Specifies the PVC to mount.
 
-. Specify the container where the Secret mounts by adding the `rhdh.redhat.com/mount-path` annotation to your configuration as shown in the following example:
+. Specify the mount path where the Secret mounts to by adding the `rhdh.redhat.com/mount-path` annotation to your configuration as shown in the following example:
 +
 .Example specifying where the Secret mounts
 [source,yaml,subs="+attributes,+quotes"]
@@ -52,7 +54,7 @@ where:
 
 <my_secret>:: Specifies the Secret name.
 
-. Use the following configuration to mount PVCs to all containers:
+. Use the following configuration to mount Secrets to all containers:
 +
 .Example configuration for mounting to all containers
 [source,yaml,subs="+attributes,+quotes"]

titles/configuring/master.adoc

@@ -33,7 +33,7 @@ include::modules/installation/proc-configuring-an-rhdh-instance-with-tls-in-kube
 include::modules/dynamic-plugins/con-dynamic-plugins-cache.adoc[ leveloffset=+1]
 
 
-include::modules/configuring-external-databases/proc-configuring-pvc-mounts.adoc[leveloffset=+1]
+include::modules/configuring-external-databases/proc-configuring-default-configuration-for-secrets-and-pvcs.adoc[leveloffset=+1]
 
 
 include::modules/dynamic-plugins/proc-installing-and-configuring-redis-cache.adoc[leveloffset=+1]