removed bug documentation from upstream

Signed-off-by: Kartikey Mamgain <[email protected]>

Author: Kartikey-star

docs/userguide/modules/getting-started/pages/installing-service-binding.adoc

@@ -61,30 +61,6 @@ displayed with the Operator details.
 +
 image:sbo_post_install.png[sbo_post_install]
 
-NOTE:
-Service Binding Operator should ideally  be installed in all namespaces and not in any specific namespace. If you cannot install 
-the Service Binding Operator in the `all namespaces` installation mode then you need to create a  rolebinding
-where you map service-binding-operator service account to specific cluster role into the namespace where the Service Binding Operator is installed.
-In the following example we are creating a RoleBinding for service-binding-operator service account installed in a specific namespace roleref to 
-service-binding-crunchy-postgres-viewer-role.
-for example:
-+
-.Example: Role binding for Crunchy Postgres Operator
-[source,yaml]
-----
-kind: RoleBinding
-apiVersion: rbac.authorization.k8s.io/v1
-metadata:
-  name: service-binding-crunchy-postgres-viewer
-subjects:
-  - kind: ServiceAccount
-    name: service-binding-operator
-roleRef:
-  apiGroup: rbac.authorization.k8s.io
-  kind: ClusterRole
-  name: service-binding-crunchy-postgres-viewer-role
-----
-
 [#installing-the-service-binding-operator-from-the-service-binding-operator-helm-chart]
 == Installing the service binding operator from the service binding operator helm chart