anchor.diff:  +
   An Operator manifest describes how to display, create, and manage the
   application, in this case Memcached, as a whole. It is defined by a
  -`CustomServiceVersion` (CSV) object and is required for the OLM to function.
  +`ClusterServiceVersion` (CSV) object and is required for the OLM to function.
  ++
  +You can use the following command to generate CSV manifests:
  ++
  +----
  +$ operator-sdk olm-catalog gen-csv --csv-version 0.0.1
  +----
  ++
  +NOTE: This command is run from the `memcached-operator/` directory that was created when you built the Memcached Operator.
   +
   For the purpose of this guide, we will continue with this
   link:https://github.com/operator-framework/getting-started/blob/master/memcachedoperator.0.0.1.csv.yaml[predefined manifest file]
   for the next steps. You can alter the image field within this manifest to
  -reflect the image you built in previous steps, but it is unnecessary. In the
  -future, the Operator SDK CLI will generate an Operator manifest for you, a
  -feature that is planned for the next release of the Operator SDK.
  +reflect the image you built in previous steps, but it is unnecessary.
   +
   [NOTE]
   ====
  
positive.code: 
  . *Deploy the Operator.*
  
  .. Deploy an Operator by applying the Operator’s manifest to the desired namespace
  in the cluster:
  +
  ----
  $ curl -Lo memcachedoperator.0.0.1.csv.yaml https://raw.githubusercontent.com/operator-framework/getting-started/master/memcachedoperator.0.0.1.csv.yaml
  $ oc apply -f memcachedoperator.0.0.1.csv.yaml
  $ oc get ClusterServiceVersion memcachedoperator.v0.0.1 -o json | jq '.status'
  ----
  
  .. After applying this manifest, nothing has happened yet, because the cluster does
  not meet the requirements specified in our manifest. Create the RBAC rules and
  `CustomResourceDefinition` for the Memcached type managed by the Operator:
  +
  ----
  $ oc apply -f deploy/rbac.yaml
  $ oc apply -f deploy/crd.yaml
  ----
  +
  NOTE: The `rbac.yaml` and `crd.yaml` files were generated into the `deploy/`
  directory by the Operator SDK when you built the Memcached Operator.
  +
  Because the OLM creates Operators in a particular namespace when a manifest is
  applied, administrators can leverage the native Kubernetes RBAC permission model
  
negative.code: 
  . *Create an application instance.*
  +
  The Memcached Operator is now running in the `default` namespace. Users
  interact with Operators via instances of `CustomResources`; in this case, the
  resource has the kind `Memcached`. Native Kubernetes RBAC also applies to
  `CustomResources`, providing administrators control over who can interact with
  