doc: add recommendation to the best practices (#5985)

* doc: add recommendation to the best practices

* Update website/content/en/docs/best-practices/pod-security-standards.md

Co-authored-by: Bryce Palmer <[email protected]>

Co-authored-by: Bryce Palmer <[email protected]>

Author: camilamacedo86

website/content/en/docs/best-practices/pod-security-standards.md

@@ -112,15 +112,11 @@ with the requirements in the same way. You can find some examples by looking at
 
 - **For workloads that need elevated permissions:** it is recommended that you ensure the namespace containing your 
 solution is labeled accordingly. You can either update your operator to manage the namespace labels or include 
-the namespace labeling as part of the manual install instructions. Following the labels for this case scenario:
+the namespace labeling as part of the manual install instructions. 
 
-```yaml
-  labels:
-    ...
-    pod-security.kubernetes.io/enforce: privileged
-    pod-security.kubernetes.io/audit: privileged
-    pod-security.kubernetes.io/warn: privileged
-```
+It is recommended that you provide a description to help cluster admins understand why elevated permissions are required.
+You can add this information and the prerequisites to the description of your 
+Operator Bundle (CSV).
 
 Following you will find a detailed description of how to configure and test your solutions. 
 The most straightforward way to ensure if your workloads will work in a restricted namespace is verifying if your solution can run in namespaces enforced as restricted.