Minor fixes (#1410)

Co-authored-by: GitHub Actions <[email protected]>

Author: jmagak

assemblies/assembly-rhdh-default-configuration.adoc

@@ -15,7 +15,7 @@ include::modules/configuring-external-databases/con-multiple-resources.adoc[leve
 
 include::modules/configuring-external-databases/con-default-base-urls.adoc[leveloffset=+2]
 
-include::modules/configuring-external-databases/con-configuring-default-secret-pvc-mounts.adoc[leveloffset=+1]
+include::modules/configuring-external-databases/con-mounts-for-default-secret-pvc-mounts.adoc[leveloffset=+1]
 
 include::modules/configuring-external-databases/proc-configuring-mount-paths.adoc[leveloffset=+2]
 

modules/configuring-external-databases/con-configuring-default-secret-pvc-mounts.adoc renamed to modules/configuring-external-databases/con-mounts-for-default-secret-pvc-mounts.adoc

@@ -1,6 +1,6 @@
 :_mod-docs-content-type: CONCEPT
 
-[id="con-configuring-default-secret-pvc-mounts_{context}"]
-= Configuring mounts for default Secrets and Persistent Volume Claims (PVCs)
+[id="con-mounts-for-default-secret-pvc-mounts_{context}"]
+= Mounts for default Secrets and Persistent Volume Claims (PVCs)
 
 You can use annotations to configure mount paths and specify containers for Secrets and Persistent Volume Claims (PVCs) that are attached to the Operator default resources in your {product} deployment. This method is specific for default objects, for instance, the {product-custom-resource-type} Deployment that the Operator manages.

modules/configuring-external-databases/con-multiple-resources.adoc

@@ -5,7 +5,7 @@
 
 You can define and create multiple resources of the same type in a single YAML file. This is applicable to any resource type that is a `list` in the resource table. To define multiple resources, use the `---` delimiter to separate each resource definition.
 
-For example, adding the following code snip to `pvcs.yaml` creates two PersistentVolumeClaims (PVCs) called `backstage-{cr-name}-myclaim1` and `backstage-{cr-name}-myclaim2` and mounts them to {product-custom-resource-type} container accordingly.
+For example, adding the following code snip to `pvcs.yaml` creates two PersistentVolumeClaims (PVCs) called `backstage-{cr-name}-myclaim1` and `backstage-{cr-name}-myclaim2` and mounts them to the {product-custom-resource-type} container accordingly.
 
 .Example creating multiple PVCs
 [source,yaml]

modules/configuring-external-databases/ref-rhdh-default-configuration.adoc

@@ -83,7 +83,7 @@ The Operator automatically creates the following resources in the specified {pro
 | `dynamic-plugins.yaml`
 | `v1/ConfigMap`
 | `backstage-dynamic-plugins-{cr-name}`
-| (Optional) Specifies dynamic plugins to be installed into {product-custom-resource-type} instance.
+| (Optional) Specifies the dynamic plugins that the Operator installs into the {product-custom-resource-type} instance.
 
 | `pvcs.yaml`
 | list of `v1/PersistentVolumeClaim`