Updates a few Operator config docs (quay#1343)

Co-authored-by: Steven Smith <[email protected]>

Author: stevsmit

modules/on-prem-configuration-overview.adoc

@@ -15,4 +15,4 @@ This chapter provides an overview of the following concepts:
 * The minimal required configuration fields.
 * How to edit and manage your configuration after deployment.
 
-This section applies specifically to on premise {productname} deployment types. For information about configuring {productname-ocp}, see. . . 
+This section applies specifically to on premise {productname} deployment types. For information about configuring {productname-ocp}, see "{productname-ocp} configuration overview".

modules/operator-components-intro.adoc

@@ -1,11 +1,11 @@
 :_content-type: CONCEPT
 [id="operator-components-intro"]
-= {productname} Operator configuration overview
+= {productname-ocp} configuration overview
 
 When deploying {productname} using the Operator on {ocp}, configuration is managed declaratively through the `QuayRegistry` custom resource (CR). This model allows cluster administrators to define the desired state of the {productname} deployment, including which components are enabled, storage backends, SSL/TLS configuration, and other core features.
 
 After deploying {productname-ocp} with the Operator, administrators can further customize their registry by updating the `config.yaml` file and referencing it in a Kubernetes secret. This configuration bundle is linked to the `QuayRegistry` CR through the `configBundleSecret` field.
 
 The Operator reconciles the state defined in the `QuayRegistry` CR and its associated configuration, automatically deploying or updating registry components as needed.
 
-This guide covers the basic concepts behind the `QuayRegistry` CR and modifying your `config.yaml` file on {productname-ocp} deployments. More advanced topics, such as using unmanaged components within the `QuayRegistry` CR, can be found in link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/deploying_the_red_hat_quay_operator_on_openshift_container_platform/index[Deploying {productname} Operator on {ocp}].
+This guide covers the basic concepts behind the `QuayRegistry` CR and modifying your `config.yaml` file on {productname-ocp} deployments. More advanced topics, such as using unmanaged components within the `QuayRegistry` CR, can be found in link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/deploying_the_red_hat_quay_operator_on_openshift_container_platform/index[Deploying {productname} Operator on {ocp}].