In documentation of Workload Availability for Red Hat OpenShift , both sections for "2.3. Installing the Self Node Remediation Operator by using the web console" [1] and "2.4. Installing the Self Node Remediation Operator by using the CLI " [2] mentions different namespaces.

Those sections should be consistent if the recommended namespace is openshift-workload-availability.

Actually, console based installation references openshift-operators as the namespace to use and emphasizes on choosing it, whereas the CLI based version references openshift-workload-availability as the namespace to use.
However, the operator itself in version 0.10.2 presents the default namespace to choose as openshift-workload-availability.

[1]https://docs.redhat.com/en/documentation/workload_availability_for_red_hat_openshift/23.3/html/remediation_fencing_and_maintenance/self-node-remediation-operator-remediate-nodes#installing-self-node-remediation-operator-using-web-console_self-node-remediation-operator-remediate-nodes

[2] https://docs.redhat.com/en/documentation/workload_availability_for_red_hat_openshift/23.3/html/remediation_fencing_and_maintenance/self-node-remediation-operator-remediate-nodes#installing-self-node-remediation-operator-using-cli_self-node-remediation-operator-remediate-nodes