Incorporated comments

redhat-developer · Jan 28, 2025 · e329158 · e329158
1 parent 11623a4
commit e329158
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/...ation/proc-defining-authorizations-in-external-files-by-using-the-operator.adoc b/...ation/proc-defining-authorizations-in-external-files-by-using-the-operator.adoc
@@ -75,9 +75,9 @@ $ oc create configmap rbac-policies \
      --from-file=rbac-conditional-policies.yaml
 ----
 
-. 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:
+. Update link:{configuring-book-url}[your `{product-custom-resource-type}` custom resource] to mount in the {product-short} filesystem your files from the `rbac-policies` config map:
 +
-.`{product-custom-resource-type}` Custom resource fragment
+.`{product-custom-resource-type}` custom resource fragment
 [source,yaml]
 ----
 apiVersion: rhdh.redhat.com/v1alpha3

diff --git a/modules/configuring-a-proxy/proc-configuring-proxy-in-operator-deployment.adoc b/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}` custom resource file as shown in the following example:
+* As a developer, set the proxy information in your `{product-custom-resource-type}` CR file as shown in the following example:
 + 
 .Example: Setting proxy variables in a CR file
 [source, yaml]

diff --git a/...s/configuring-deployment/proc-configuring-deployment-by-using-the-operator.adoc b/...s/configuring-deployment/proc-configuring-deployment-by-using-the-operator.adoc
@@ -1,11 +1,11 @@
 [id="configuring-the-deployment"]
 = Configuring {product} deployment when using the Operator
 
-The {product} Operator exposes a `rhdh.redhat.com/v1alpha2` API Version of its Custom Resource Definition (CRD). This CRD exposes a generic `spec.deployment.patch` field, which gives you full control over the {product-short} Deployment resource. This field can be a fragment of the standard `apps.Deployment` Kubernetes object.
+The {product} Operator exposes a `rhdh.redhat.com/v1alpha2` API Version of its custom resource (CR). This CR exposes a generic `spec.deployment.patch` field, which gives you full control over the {product-short} Deployment resource. This field can be a fragment of the standard `apps.Deployment` Kubernetes object.
 
 .Procedure
 
-. Create a `{product-custom-resource-type}` custom resource with the following fields:
+. Create a `{product-custom-resource-type}` CR with the following fields:
 
 --
 .Example

diff --git a/...iguring/proc-using-the-operator-to-run-rhdh-with-your-custom-configuration.adoc b/...iguring/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} custom resource in a `{my-product-cr-name}.yaml` file to use your custom config maps and secrets.
+. Author your {product-custom-resource-type} CR 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
 ====