final (hopefully) indent fix

Author: kaitlynmichael

content/embeds/k8s-642-redb-admission-webhook-name-change.md

@@ -10,4 +10,5 @@
 
         ```sh
         kubectl apply -f deploy/admission/webhook.yaml
-        ```
+        ```
+        

content/embeds/k8s-admission-webhook-cert.md

@@ -41,5 +41,5 @@
 
     ```sh
     kubectl patch ValidatingWebhookConfiguration \
-      redis-enterprise-admission --patch "$(cat modified-webhook.yaml)"
+        redis-enterprise-admission --patch "$(cat modified-webhook.yaml)"
     ```

content/operate/kubernetes/deployment/openshift/openshift-cli.md

@@ -39,16 +39,17 @@ To see which version of Redis Enterprise for Kubernetes supports your OpenShift
     git clone https://github.com/RedisLabs/redis-enterprise-k8s-docs
     ```
 
-
 1. Deploy the OpenShift operator bundle.
 
-   If you are using version 6.2.18-41 or earlier, you must [apply the security context constraint](#install-security-context-constraint) before the operator bundle.
-    
+    If you are using version 6.2.18-41 or earlier, you must [apply the security context constraint](#install-security-context-constraint) before the operator bundle.
+
     ```sh
     oc apply -f openshift.bundle.yaml
     ```
 
-    {{< warning >}}Changes to the `openshift.bundle.yaml` file can cause unexpected results.{{< /warning >}}
+    {{< warning >}}
+Changes to the `openshift.bundle.yaml` file can cause unexpected results.
+    {{< /warning >}}
 
 1. Verify that your `redis-enterprise-operator` deployment is running.
 
@@ -63,15 +64,19 @@ To see which version of Redis Enterprise for Kubernetes supports your OpenShift
     redis-enterprise-operator   1/1     1            1           0m36s
     ```
 
-{{<warning>}}DO NOT modify or delete the StatefulSet created during the deployment process. Doing so could destroy your Redis Enterprise cluster (REC).{{</warning>}}
+    {{<warning>}}
+DO NOT modify or delete the StatefulSet created during the deployment process. Doing so could destroy your Redis Enterprise cluster (REC).
+    {{</warning>}}
 
 ## Install security context constraint
 
 The Redis Enterprise pods must run in OpenShift with privileges set in a [Security Context Constraint](https://docs.openshift.com/container-platform/4.4/authentication/managing-security-context-constraints.html#security-context-constraints-about_configuring-internal-oauth). This grants the pod various rights, such as the ability to change system limits or run as a particular user.
 
 1. Apply the file `scc.yaml` file.
 
-   {{<warning>}}Do not edit this file. {{</warning>}}
+   {{<warning>}}
+Do not edit this file.
+    {{</warning>}}
 
     ```sh
     oc apply -f openshift/scc.yaml
@@ -92,12 +97,14 @@ The Redis Enterprise pods must run in OpenShift with privileges set in a [Securi
       system:serviceaccount:<my-project>:<rec>
     ```
 
-    {{<note>}} If you are using version 6.2.18-41 or earlier, add additional permissions for your cluster.
-
-    oc adm policy add-scc-to-user redis-enterprise-scc \
-    system:serviceaccount:<my-project>:redis-enterprise-operator
+    {{<note>}}
+If you are using version 6.2.18-41 or earlier, add additional permissions for your cluster.
 
-    {{</note>}}
+```sh
+oc adm policy add-scc-to-user redis-enterprise-scc \
+system:serviceaccount:<my-project>:redis-enterprise-operator
+```
+{{</note>}}
 
   You can check the name of your project using the `oc project` command. To replace the project name, use `oc edit project myproject`. Replace `rec` with the name of your Redis Enterprise cluster, if different.
 
@@ -110,7 +117,7 @@ The Redis Enterprise pods must run in OpenShift with privileges set in a [Securi
     The REC name cannot be changed after cluster creation.
 
     {{<note>}}
-    Each Redis Enterprise cluster requires at least 3 nodes. Single-node RECs are not supported.
+Each Redis Enterprise cluster requires at least 3 nodes. Single-node RECs are not supported.
     {{</note>}}
 
 2. Apply the custom resource file to create your Redis Enterprise cluster.
@@ -121,13 +128,13 @@ The Redis Enterprise pods must run in OpenShift with privileges set in a [Securi
 
   The operator typically creates the REC within a few minutes.
 
-3. Check the cluster status.
+1. Check the cluster status.
 
     ```sh
     oc get pod
     ```
 
-  You should receive a response similar to the following:
+    You should receive a response similar to the following:
 
     ```sh
      NAME                             | READY | STATUS  | RESTARTS | AGE |
@@ -158,7 +165,7 @@ If not limited, the webhook intercepts requests from all namespaces. If you have
     name: staging
     ```
 
-1. Patch the webhook spec with the `namespaceSelector` field. 
+1. Patch the webhook spec with the `namespaceSelector` field.
 
     ```sh
     cat > modified-webhook.yaml <<EOF
@@ -170,22 +177,22 @@ If not limited, the webhook intercepts requests from all namespaces. If you have
     EOF
     ```
 
-3. Apply the patch.
+1. Apply the patch.
 
     ```sh
     oc patch ValidatingWebhookConfiguration \
       redis-enterprise-admission --patch "$(cat modified-webhook.yaml)"
     ```
 
     {{<note>}}
-    For releases before 6.4.2-4, use this command instead:
-
-      ```sh
-      oc patch ValidatingWebhookConfiguration \
-        redb-admission --patch "$(cat modified-webhook.yaml)"
-      ```
-      
-    The 6.4.2-4 release introduces a new `ValidatingWebhookConfiguration` to replace `redb-admission`. See the [6.4.2-4 release notes]({{< relref "/operate/kubernetes/release-notes/6-4-2-releases/" >}}).
+For releases before 6.4.2-4, use this command instead:
+
+```sh
+oc patch ValidatingWebhookConfiguration \
+  redb-admission --patch "$(cat modified-webhook.yaml)"
+```
+
+The 6.4.2-4 release introduces a new `ValidatingWebhookConfiguration` to replace `redb-admission`. See the [6.4.2-4 release notes]({{< relref "/operate/kubernetes/release-notes/6-4-2-releases/" >}}).
     {{</note>}}
 
 ### Verify admission controller installation

content/operate/kubernetes/deployment/quick-start.md

@@ -23,10 +23,10 @@ This guide works with most supported Kubernetes distributions. If you're using O
 
 To deploy Redis Enterprise for Kubernetes, you'll need:
 
-* a Kubernetes cluster in a [supported distribution]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}})
-* a minimum of three worker nodes
-* a Kubernetes client (kubectl)
-* access to DockerHub, RedHat Container Catalog, or a private repository that can hold the required images.
+- Kubernetes cluster in a [supported distribution]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}})
+- minimum of three worker nodes
+- Kubernetes client (kubectl)
+- access to DockerHub, RedHat Container Catalog, or a private repository that can hold the required images.
 
 ### Create a new namespace
 
@@ -116,7 +116,7 @@ The following example creates a minimal Redis Enterprise cluster. See the [Redis
 1. Create a file that defines a Redis Enterprise cluster with three nodes.
 
     {{<note>}}
-    The REC name (`my-rec` in this example) cannot be changed after cluster creation.
+The REC name (`my-rec` in this example) cannot be changed after cluster creation.
     {{</note>}}
 
     ```sh
@@ -130,12 +130,11 @@ The following example creates a minimal Redis Enterprise cluster. See the [Redis
     EOF
     ```
 
-    This will request a cluster with three Redis Enterprise nodes using the
-    default requests (i.e., 2 CPUs and 4GB of memory per node).
+   This will request a cluster with three Redis Enterprise nodes using the default requests (i.e., 2 CPUs and 4GB of memory per node).
 
-    To test with a larger configuration, use the example below to add node resources to the `spec` section of your test cluster (`my-rec.yaml`).
+   To test with a larger configuration, use the example below to add node resources to the `spec` section of your test cluster (`my-rec.yaml`).
 
-    ```yaml
+    ```sh
     redisEnterpriseNodeResources:
       limits:
         cpu: 2000m
@@ -146,52 +145,49 @@ The following example creates a minimal Redis Enterprise cluster. See the [Redis
     ```
 
     {{<note>}}
-    Each cluster must have at least 3 nodes. Single-node RECs are not supported.
+Each cluster must have at least 3 nodes. Single-node RECs are not supported.
     {{</note>}}
 
-    See the [Redis Enterprise hardware requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}}) for more
-    information on sizing Redis Enterprise node resource requests.
+    See the [Redis Enterprise hardware requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}}) for more information on sizing Redis Enterprise node resource requests.
 
 1. Apply your custom resource file in the same namespace as `my-rec.yaml`.
 
     ```sh
     kubectl apply -f my-rec.yaml
     ```
 
-    You should see a result similar to this:
+   You should see a result similar to this:
 
-    ```sh
-    redisenterprisecluster.app.redislabs.com/my-rec created
-    ```
+   ```sh
+   redisenterprisecluster.app.redislabs.com/my-rec created
+   ```
 
 1. You can verify the creation of the cluster with:
 
     ```sh
     kubectl get rec
     ```
 
-  You should see a result similar to this:
+    You should see a result similar to this:
 
     ```sh
     NAME           AGE
     my-rec   1m
     ```
 
-   At this point, the operator will go through the process of creating various
-   services and pod deployments.
+    At this point, the operator will go through the process of creating various services and pod deployments.
 
-   You can track the progress by examining the
-   StatefulSet associated with the cluster:
+    You can track the progress by examining the StatefulSet associated with the cluster:
 
-   ```sh
-   kubectl rollout status sts/my-rec
-   ```
+    ```sh
+    kubectl rollout status sts/my-rec
+    ```
 
-   or by looking at the status of all of the resources in your namespace:
+    or by looking at the status of all of the resources in your namespace:
 
-   ```sh
-   kubectl get all
-   ```
+    ```sh
+    kubectl get all
+    ```
 
 ## Enable the admission controller
 
@@ -250,15 +246,14 @@ The operator bundle includes a webhook file. The webhook will intercept requests
     EOF
     ```
 
-You should see your request was denied by the `admission webhook "redisenterprise.admission.redislabs"`.
+    You should see your request was denied by the `admission webhook "redisenterprise.admission.redislabs"`.
 
-```sh
-Error from server: error when creating "STDIN": admission webhook "redisenterprise.admission.redislabs" denied the request: eviction_policy: u'illegal' is not one of [u'volatile-lru', u'volatile-ttl', u'volatile-random', u'allkeys-lru', u'allkeys-random', u'noeviction', u'volatile-lfu', u'allkeys-lfu']
-```
+    ```sh
+    Error from server: error when creating "STDIN": admission webhook "redisenterprise.admission.redislabs" denied the request: eviction_policy: u'illegal' is not one of [u'volatile-lru', u'volatile-ttl', u'volatile-random', u'allkeys-lru', u'allkeys-random', u'noeviction', u'volatile-lfu', u'allkeys-lfu']
+    ```
 
 ## Create a Redis Enterprise Database (REDB)
 
 You can create multiple databases within the same namespace as your REC or in other namespaces.
 
 See [manage Redis Enterprise databases for Kubernetes]({{< relref "/operate/kubernetes/re-databases/db-controller.md" >}}) to create a new REDB.
-