Merge pull request #13543 from adellape/olm_typos

Fix Operator topic typos

Author: adellape

_topic_map.yml

@@ -192,8 +192,9 @@ Distros: openshift-*
 Topics:
 - Name: What are Operators?
   File: olm-what-are-operators
-- Name: Adding Operators to your cluster
+- Name: Adding Operators to a cluster
   File: olm-adding-operators-to-cluster
+  Distros: openshift-enterprise,openshift-origin
 - Name: Creating applications from installed Operators
   File: olm-creating-apps-from-installed-operators
 - Name: Getting started with the Operator SDK
@@ -261,4 +262,3 @@ Topics:
   File: efk-logging-troubleshooting
 - Name: Exported fields
   File: efk-logging-exported-fields
-

modules/olm-installing-operator-using-operatorhub.adoc

@@ -11,7 +11,7 @@ your cluster. This procedure uses the etcd Operator as an example.
 
 .Prerequisites
 
-- Access to an {product-title} v4 cluster using an account with `cluster-admin`
+- Access to an {product-title} 4 cluster using an account with `cluster-admin`
 permissions.
 
 .Procedure

modules/olm-operator-framework.adoc

@@ -6,9 +6,9 @@
 = Operator Framework
 
 The Operator Framework is a family of tools and capabilities to deliver on the
-customer experience describe above. It is not just about writing code; testing,
+customer experience described above. It is not just about writing code; testing,
 delivering, and updating Operators is just as important. The Operator Framework
-components consiss of open source tools to tackle these problems:
+components consist of open source tools to tackle these problems:
 
 Operator SDK::
 Assists Operator authors in bootstrapping, building, testing, and packaging