address kevin's comment:

* make the instruction more generic
* provide an example for operator-sdk

Signed-off-by: Simone-Rodigari <[email protected]>

Author: SRodi

content/en/docs/Tasks/make-catalog-available-on-cluster.md

@@ -85,9 +85,12 @@ spec:
       interval: 10m
 ```
 
-If the `imagePullSecret` is referenced in the bundle, for instance when the controller-manager image is pulled from a private registry, there is no place in the API to tell OLM to attach the `imagePullSecrets`. As a consequence, permissions to pull the image should be added directly to the controller-manager deployment configurations. This can be achieved by updating `config/manager/manager.yaml` and adding `deployment.spec.template.spec.imagePullSecrets` with the required secret name. 
+If the `imagePullSecret` is referenced in the bundle, for instance when the controller-manager image is pulled from a private registry, there is no place in the API to tell OLM to attach the `imagePullSecrets`. As a consequence, permissions to pull the image should be added directly to the operator Deployment's manifest by adding the required secret name to the list `deployment.spec.template.spec.imagePullSecrets`. 
+
+For the [operator-sdk](https://sdk.operatorframework.io/) abstraction, the operator Deployment's manifest is found under `config/manager/manager.yaml`. Below is an example of a controller-manager Deployment's manifest configured with an `imagePullSecret` to pull container images from a private registry.
 
 ```yaml
+# config/manager/manager.yaml
 apiVersion: apps/v1
 kind: Deployment
 metadata: