Clarify OLM vs CVO Operators in book index

Author: adellape

operators/index.adoc

@@ -8,12 +8,16 @@ toc::[]
 
 include::modules/operators-overview.adoc[leveloffset=+1]
 
-With Operators, you can create applications to monitor the running services in the cluster. Operators are designed specifically for your applications. Operators implement and automate the common Day 1 operations such as installation and configuration as well as Day 2 operations such as autoscaling up and down and creating backups. All these activities are in a piece of software running inside your cluster.
+Operators are designed specifically for Kubernetes-native applications to implement and automate common Day 1 operations on a {product-title} cluster, such as installation and configuration. Operators can also automate Day 2 operations, such as autoscaling up and down and creating backups. All these activities are in a piece of software running inside your cluster.
 
-[id="operators-overview-developer-tasks"]
+Operator Lifecycle Manager (OLM) and OperatorHub are default components in {product-title} that help manage add-on Operators. Together they provide the system for discovering, installing, and managing optional Operators available on the cluster, also known as _OLM-based Operators_.
+
+In {product-title}, all cluster functions are divided into a series of default _cluster Operators_. Cluster Operators are a different type of Operator that manage a particular area of cluster functionality, such as cluster-wide application logging, management of the Kubernetes control plane, or the machine provisioning system. Cluster Operators are installed by default, unless otherwise noted, and are managed by the Cluster Version Operator (CVO) and not by OLM.
+
+[id="operators-overview-developer-tasks_{context}"]
 == For developers
 
-As a developer, you can perform the following Operator tasks:
+As an Operator author, you can perform the following tasks for OLM-based Operators:
 
 ** xref:../operators/operator_sdk/osdk-installing-cli.adoc#osdk-installing-cli[Install Operator SDK CLI].
 // The Operator quickstarts aren't published for OSD/ROSA, so for OSD/ROSA, these xrefs point to the tutorials instead.
@@ -37,11 +41,11 @@ ifndef::openshift-dedicated,openshift-rosa[]
 * xref:../machine_management/deleting-machine.adoc#machine-lifecycle-hook-deletion-uses_deleting-machine[Machine deletion lifecycle hook examples for Operator developers]
 endif::openshift-dedicated,openshift-rosa[]
 
-[id="operators-overview-administrator-tasks"]
+[id="operators-overview-administrator-tasks_{context}"]
 == For administrators
 
 ifndef::openshift-dedicated,openshift-rosa[]
-As a cluster administrator, you can perform the following Operator tasks:
+As a cluster administrator, you can perform the following OLM-based Operator tasks:
 endif::openshift-dedicated,openshift-rosa[]
 
 ifdef::openshift-dedicated,openshift-rosa[]
@@ -66,7 +70,7 @@ endif::openshift-dedicated,openshift-rosa[]
 ifndef::openshift-dedicated,openshift-rosa[]
 ** xref:../operators/admin/olm-restricted-networks.adoc#olm-restricted-networks[Use Operator Lifecycle Manager on restricted networks].
 
-To know all about the cluster Operators that Red Hat provides, see xref:../operators/operator-reference.adoc#cluster-operators-ref[Cluster Operators reference].
+For information about the cluster Operators that Red Hat provides, see xref:../operators/operator-reference.adoc#cluster-operators-ref[Cluster Operators reference].
 endif::openshift-dedicated,openshift-rosa[]
 
 [id="operators-overview-next-steps"]