remove definition of namespace scope from CRD scope section.
@@ -7,7 +7,7 @@ weight: 60
## Overview
The CustomResourceDefinition (CRD) scope can also be changed for cluster-scoped operators so that there is only a single
-instance (for a given name) of the CRD to manage across the cluster.
+instance (for a given name) of the Custom Resource (CR) to manage across the cluster.
The CRD manifests are generated in `config/crd/bases`. For each CRD that needs to be cluster-scoped, its manifest
should specify `spec.scope: Cluster`.
@@ -18,14 +18,9 @@ above the CRD's Go type definition in `api/<version>/<kind>_types.go` or `apis/<
if you are using the `multigroup` layout. Note that the `<resource>`
element must be the same lower-case plural value of the CRD's Kind, `spec.names.plural`.
-## CRD cluster-scoped usage
-
-A cluster scope is ideal for operators that manage custom resources (CR's) that can be created in more than
-one namespace in a cluster.
-
**NOTE**: When a `Manager` instance is created in the `main.go` file, it receives the namespace(s) as Options.
These namespace(s) should be watched and cached for the Client which is provided by the Controllers. Only clients
-provided by cluster-scoped projects where the `Namespace` attribute is `""` will be able to manage cluster-scoped CRD's.
+provided by cluster-scoped projects where the `Namespace` attribute is `""` will be able to manage cluster-scoped CRs.
For more information see the [Manager][manager_user_guide] topic in the user guide and the
[Manager Options][manager_options].
