Incorporated Fabrice's comments

modules/authorization/proc-defining-authorizations-in-external-files-by-using-the-operator.adoc

@@ -75,7 +75,7 @@ $ oc create configmap rbac-policies \
      --from-file=rbac-conditional-policies.yaml
 ----
 
-. Update your `{product-custom-resource-type}` custom resource to mount in the {product-short} filesystem your files from the `rbac-policies` config map:
+. Update your `{product-custom-resource-type}` link:{configuring-book-url}[custom resource] to mount in the {product-short} filesystem your files from the `rbac-policies` config map:
 +
 .`{product-custom-resource-type}` Custom resource fragment
 [source,yaml]

modules/configuring-a-proxy/proc-configuring-proxy-in-operator-deployment.adoc

@@ -59,7 +59,7 @@ For Operator-based deployment, the approach you use for proxy configuration is b
 ----
 
 
-* As a developer, set the proxy information in your `{product-custom-resource-type}` CR file as shown in the following example:
+* As a developer, set the proxy information in your `{product-custom-resource-type}` custom resource file as shown in the following example:
 + 
 .Example: Setting proxy variables in a CR file
 [source, yaml]

modules/configuring-deployment/proc-configuring-deployment-by-using-the-operator.adoc

@@ -5,7 +5,7 @@ The {product} operator exposes a `rhdh.redhat.com/v1alpha2` API Version of its C
 
 .Procedure
 
-. Create a `{product-custom-resource-type}` Custom Resource Definition with the following fields:
+. Create a `{product-custom-resource-type}` custom resource with the following fields:
 
 --
 .Example

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

@@ -13,7 +13,7 @@ To use the {product-short} operator to run {product} with your custom configurat
 
 .Procedure
 
-. Author your {product-custom-resource-type} CR in a `{my-product-cr-name}.yaml` file to use your custom config maps and secrets.
+. Author your {product-custom-resource-type} custom resource in a `{my-product-cr-name}.yaml` file to use your custom config maps and secrets.
 +
 .Minimal `{my-product-cr-name}.yaml` custom resource example
 ====

modules/installation/proc-deploy-rhdh-instance-eks.adoc

@@ -82,7 +82,7 @@ kubectl patch serviceaccount default \
 ----
 --
 
-. Create a custom resource file using the following template:
+. Create your `{product-custom-resource-type}` custom resource using the following template:
 +
 --
 [source,yaml,subs="+attributes,+quotes"]

modules/observe/proc-admin-enabling-metrics-ocp-operator.adoc

@@ -41,7 +41,7 @@ spec:
   - port: http-metrics
     path: '/metrics'
 ----
-<1> Replace `<custom_resource_name>` with the name of your `{product-custom-resource-type}` CR.
+<1> Replace `<custom_resource_name>` with the name of your `{product-custom-resource-type}` custom resource.
 <2> Replace `<project_name>` with the name of the {ocp-short} project where your {product} instance is running.
 
 . Apply the `ServiceMonitor` CR by running the following command:

modules/observe/proc-disabling-telemetry-using-operator.adoc

@@ -33,7 +33,7 @@ data:
         disabled: true
 ----
 
-. Set the value of the `dynamicPluginsConfigMapName` parameter to the name of the ConfigMap file in your `{product-custom-resource-type}` custom resource:
+. Set the value of the `dynamicPluginsConfigMapName` parameter to the name of your `dynamic-plugins-rhdh` config map in your `{product-custom-resource-type}` custom resource:
 +
 [source,yaml]
 ----

modules/observe/proc-enabling-telemetry-using-operator.adoc

@@ -33,7 +33,7 @@ data:
         disabled: false
 ----
 
-. Set the value of the `dynamicPluginsConfigMapName` parameter to the name of the ConfigMap file in your `{product-custom-resource-type}` custom resource:
+. Set the value of the `dynamicPluginsConfigMapName` parameter to the name of your `dynamic-plugins-rhdh` config map in your `{product-custom-resource-type}` custom resource:
 +
 [source,yaml]
 ----