OSDOCS#15857: Change *OperatorHub* to *Software Catalog* &tc.

Author: michaelryanpeter

_topic_maps/_topic_map.yml

@@ -1968,7 +1968,7 @@ Topics:
       File: olm-understanding-metrics
     - Name: Webhooks
       File: olm-webhooks
-  - Name: OperatorHub
+  - Name: Software catalog
     Distros: openshift-enterprise,openshift-origin
     File: olm-understanding-operatorhub
   - Name: Red Hat-provided Operator catalogs

_topic_maps/_topic_map_osd.yml

@@ -689,7 +689,7 @@ Topics:
       File: olm-understanding-metrics
     - Name: Webhooks
       File: olm-webhooks
-  - Name: OperatorHub
+  - Name: Software catalog
     File: olm-understanding-operatorhub
   - Name: Red Hat-provided Operator catalogs
     File: olm-rh-catalogs

_topic_maps/_topic_map_rosa.yml

@@ -895,7 +895,7 @@ Topics:
       File: olm-understanding-metrics
     - Name: Webhooks
       File: olm-webhooks
-  - Name: OperatorHub
+  - Name: Software catalog
     File: olm-understanding-operatorhub
   - Name: Red Hat-provided Operator catalogs
     File: olm-rh-catalogs

_topic_maps/_topic_map_rosa_hcp.yml

@@ -757,7 +757,7 @@ Topics:
       File: olm-understanding-metrics
     - Name: Webhooks
       File: olm-webhooks
-  - Name: OperatorHub
+  - Name: Software catalog
     File: olm-understanding-operatorhub
   - Name: Red Hat-provided Operator catalogs
     File: olm-rh-catalogs

applications/connecting_applications_to_services/getting-started-with-service-binding-ibm-power-ibm-z.adoc

@@ -16,7 +16,7 @@ The {servicebinding-title} manages the data plane for workloads and backing serv
 
 * You have access to an {product-title} cluster using an account with `cluster-admin` permissions.
 * You have installed the `oc` CLI.
-* You have installed the {servicebinding-title} from OperatorHub.
+* You have installed the {servicebinding-title} from the software catalog.
 
 //Deploying PostgreSQL operator
 include::modules/sbo-deploying-a-postgresql-database-operator-power-z.adoc[leveloffset=+1]

applications/connecting_applications_to_services/getting-started-with-service-binding.adoc

@@ -21,17 +21,17 @@ ifdef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have access to an {product-title} cluster using an account with `dedicated-admin` permissions.
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have installed the `oc` CLI.
-* You have installed {servicebinding-title} from OperatorHub.
+* You have installed {servicebinding-title} from the software catalog.
 ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
-* You have installed the 5.1.2 version of the Crunchy Postgres for Kubernetes Operator from OperatorHub using the *v5* Update channel. The installed Operator is available in an appropriate namespace, such as the `my-petclinic` namespace.
+* You have installed the 5.1.2 version of the Crunchy Postgres for Kubernetes Operator from the software catalog using the *v5* Update channel. The installed Operator is available in an appropriate namespace, such as the `my-petclinic` namespace.
 +
 [NOTE]
 ====
 You can create the namespace using the `oc create namespace my-petclinic` command.
 ====
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
-* You have installed the 5.1.2 version of the Crunchy Postgres for Kubernetes Operator from OperatorHub using the *v5* Update channel. The installed Operator is available in an appropriate project, such as the `my-petclinic` project.
+* You have installed the 5.1.2 version of the Crunchy Postgres for Kubernetes Operator from the software catalog using the *v5* Update channel. The installed Operator is available in an appropriate project, such as the `my-petclinic` project.
 +
 [NOTE]
 ====

applications/odc-exporting-applications.adoc

@@ -11,7 +11,7 @@ As a developer, you can export your application in the ZIP file format. Based on
 [id="prerequisites_odc-exporting-applications"]
 == Prerequisites
 
-* You have installed the gitops-primer Operator from the OperatorHub.
+* You have installed the gitops-primer Operator from the software catalog.
 +
 [NOTE]
 ====

architecture/control-plane.adoc

@@ -55,7 +55,7 @@ include::modules/arch-olm-operators.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 * xref:../operators/understanding/olm/olm-understanding-olm.adoc#olm-understanding-olm[Operator Lifecycle Manager (OLM) concepts and resources]
-* xref:../operators/understanding/olm-understanding-operatorhub.adoc#olm-understanding-operatorhub[Understanding OperatorHub].
+* xref:../operators/understanding/olm-understanding-operatorhub.adoc#olm-understanding-operatorhub[Understanding the software catalog].
 
 include::modules/etcd-overview.adoc[leveloffset=+1]
 

architecture/index.adoc

@@ -73,7 +73,7 @@ endif::openshift-dedicated,openshift-rosa[]
 As a developer, you can use different tools, methods, and formats to xref:../architecture/understanding-development.adoc#understanding-development[develop your containerized application] based on your unique requirements, for example:
 
 * Use various build-tool, base-image, and registry options to build a simple container application.
-* Use supporting components such as OperatorHub and templates to develop your application.
+* Use supporting components such as the software catalog and templates to develop your application.
 * Package and deploy your application as an Operator.
 
 You can also create a Kubernetes manifest and store it in a Git repository.

architecture/understanding-development.adoc

@@ -327,8 +327,8 @@ a logging component. To fulfill that need, you might be able to obtain the
 required component from the following Catalogs that are available in the
 {product-title} web console:
 
-* OperatorHub, which is available in each {product-title} {product-version}
-cluster. The OperatorHub makes Operators available from Red Hat,
+* The software catalog, which is available in each {product-title} {product-version}
+cluster. The software catalog makes Operators available from Red Hat,
 certified Red Hat partners, and community members to the cluster operator. The
 cluster operator can make those Operators available in all or selected
 namespaces in the cluster, so developers can launch them and configure them