copy edits

Author: kaitlynmichael

content/operate/kubernetes/security/enable-privileged-mode.md

@@ -60,11 +60,11 @@ securityContext:
 
 OpenShift users upgrading to 7.22.0-6 need to make changes to your existing SCC (security context constraint).
 
-## OpenShift Upgrades
+## OpenShift upgrades
 
-If running in **unprivileged mode**, remove the custom `redis-enterprise-scc-v2` and disconnect it from the REC service account after completing your upgrade.
+If running in **unprivileged mode**, remove the custom `redis-enterprise-scc-v2` SCC and unbind it from the REC service account after completing your upgrade.
 
-If running in **privileged mode**, manually reapply the [security context constraints (SCC)](https://docs.openshift.com/container-platform/4.8/authentication/managing-security-context-constraints.html) file ([`scc.yaml`]({{< relref "/operate/kubernetes/deployment/openshift/openshift-cli#deploy-the-operator" >}})) and bind it to your service account. 
+If running in **privileged mode**, manually reapply the [security context constraints (SCC)](https://docs.openshift.com/container-platform/4.8/authentication/managing-security-context-constraints.html) file ([`scc.yaml`]({{< relref "/operate/kubernetes/deployment/openshift/openshift-cli#deploy-the-operator" >}})) and rebind it to the REC service account.
 
 ```sh
 oc apply -f openshift/scc.yaml
@@ -81,7 +81,7 @@ New installations of Redis Enterprise for Kubernetes 7.22.0-6 and later automati
 
 To enable **privileged mode** after installation, apply and grant permissions to the `redis-enterprise-scc-v2` SCC.
 
-1. Apply the file `scc.yaml` file.
+1. Apply the `scc.yaml` file.
 
    {{<warning>}}
 Do not edit this file.
@@ -108,9 +108,8 @@ Do not edit this file.
 
 The `SYS_RESOURCE` capability may be required if processes in the container need to raise resource limits, such as the maximum number of open file descriptors.
 
-Some Redis Enterprise processes require the ability to open at least 100,000 file descriptors. If the default limit is lower and the container lacks the `SYS_RESOURCE` capability, the process may fail repeatedly, rendering the cluster unusable. To use unprivileged mode, configure your Kubernetes worker nodes to ensure a default file descriptor limit of at least 100,000. 
+Some Redis Enterprise processes require the ability to open at least 100,000 file descriptors. If the default limit is lower and the container lacks the `SYS_RESOURCE` capability, the process may fail repeatedly, rendering the cluster unusable. To use unprivileged mode, configure your Kubernetes worker nodes to ensure a default file descriptor limit of at least 100,000.
 
 If you are already running a Redis Enterprise Cluster on Kubernetes, your worker nodes are likely configured correctly. In this case, it is safe to upgrade the operator and use unprivileged mode.
 
 Based on our testing, all major cloud providers configure Kubernetes worker nodes with file descriptor limits well above the required minimum. These setups are compatible with unprivileged mode. The only known exception is clusters created with [Kubespray](hhttps://kubespray.io/#/), which sets default file descriptor limits below the required 100,000. If you use Kubespray with default settings, you must run the operator in privileged mode.
-

content/operate/kubernetes/upgrade/upgrade-olm.md

@@ -75,7 +75,6 @@ You can monitor the upgrade from the **Installed Operators** page. A new Redis E
 
 ## Reapply the SCC
 
-
 If you are using OpenShift, you must manually reappply the [security context constraints (SCC)](https://docs.openshift.com/container-platform/4.8/authentication/managing-security-context-constraints.html) file ([`scc.yaml`]({{< relref "/operate/kubernetes/deployment/openshift/openshift-cli#deploy-the-operator" >}})) and bind it to your service account.
 
 ```sh
@@ -86,6 +85,7 @@ oc apply -f openshift/scc.yaml
 oc adm policy add-scc-to-user redis-enterprise-scc-v2 \
   system:serviceaccount:<my-project>:<rec-name>
 ```
+
 ## Upgrade the Redis Enterprise Cluster 
 
 {{<warning>}}