Update multi-namespace-redb/README.md

Co-authored-by: Kaitlyn Michael <76962844+kaitlynmichael@users.noreply.github.com>

Author: yuvallevy2

multi-namespace-redb/README.md

@@ -76,4 +76,4 @@ kubectl patch configmap/operator-environment-config \
 * When deploying multiple Redis Enterprise Operators within the same K8s cluster, do not configure more than one of the operators to watch the same namespace.
 * Only configure the operator to watch a namespace once the namespace is created and configured with the role/role_binding as explained above. If configured to watch a namespace without setting those permissions or a namespace that is not created yet, the operator will fail and not perform normal operations.
 * The Redis Enterprise Operator creates a service named after the REDB within the REDB namespace. The service is of type "External Name". This service can only be accessed from within the K8s cluster. Configuring Load Balancer/Node Port services automatically is not supported at this time. The service type configuration within the Redis Enterprise Cluster custom resource will be ignored. The External Name service will point to another ClusterIP service created within the operator namespace, exposing the actual Redis endpoint.
-* When deploying a RedisEnterpriseCluster, the operator will read environment variables from a configmap named operator-environment-config within the operator namespace. Adding new values to this configmap will reset the operator's pod and propagate the new variables to its containers. Note that this configmap can be created manually before deploying the RedisEnterpriseCluster, or the operator will automatically create it once a RedisEnterpriseCluster is deployed.
+* When deploying a RedisEnterpriseCluster, the operator will read environment variables from a configmap named `operator-environment-config` within the operator namespace. Adding new values to this configmap will reset the operator's pod and propagate the new variables to its containers. Note that this configmap can be created manually before deploying the RedisEnterpriseCluster, or the operator will automatically create it once a RedisEnterpriseCluster is deployed.