consistent indentation

Author: kaitlynmichael

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

@@ -19,7 +19,6 @@ To deploy Redis Enterprise Software for Kubernetes and start your Redis Enterpri
 
 This guide works with most supported Kubernetes distributions. If you're using OpenShift, see [Redis Enterprise on OpenShift]({{< relref "/operate/kubernetes/deployment/openshift" >}}). For details on what is currently supported, see [supported distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}).
 
-
 ## Prerequisites
 
 To deploy Redis Enterprise for Kubernetes, you'll need:
@@ -37,15 +36,15 @@ Throughout this guide, each command is applied to the namespace in which the Red
 
 1. Create a new namespace
 
-  ```sh
-  kubectl create namespace <rec-namespace>
-  ```
+    ```sh
+   kubectl create namespace <rec-namespace>
+   ```
 
-2. Change the namespace context to make the newly created namespace default for future commands.
+1. Change the namespace context to make the newly created namespace default for future commands.
 
-  ```sh
-  kubectl config set-context --current --namespace=<rec-namespace>
-  ```
+    ```sh
+    kubectl config set-context --current --namespace=<rec-namespace>
+   ```
 
 You can use an existing namespace as long as it does not contain any existing Redis Enterprise cluster resources. It's best practice to create a new namespace to make sure there are no Redis Enterprise resources that could interfere with the deployment.
 
@@ -115,7 +114,10 @@ that contains cluster specifications.
 The following example creates a minimal Redis Enterprise cluster. See the [RedisEnterpriseCluster API reference]({{<relref "/operate/kubernetes/reference/redis_enterprise_cluster_api">}}) for more information on the various options available.
 
 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.{{</note>}}
+
+    {{<note>}}
+    The REC name (`my-rec` in this example) cannot be changed after cluster creation.
+    {{</note>}}
 
     ```sh
     cat <<EOF > my-rec.yaml
@@ -152,28 +154,28 @@ The following example creates a minimal Redis Enterprise cluster. See the [Redis
   
 1. Apply your custom resource file in the same namespace as `my-rec.yaml`.
 
-  ```sh
-  kubectl apply -f 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
-  ```
+    ```sh
+    kubectl get rec
+    ```
 
   You should see a result similar to this:
 
-  ```sh
-  NAME           AGE
-  my-rec   1m
-  ```
+    ```sh
+    NAME           AGE
+    my-rec   1m
+    ```
 
    At this point, the operator will go through the process of creating various
    services and pod deployments.

content/operate/kubernetes/upgrade/upgrade-redis-cluster.md

@@ -14,16 +14,16 @@ weight: 10
 Redis implements rolling updates for software upgrades in Kubernetes deployments. The upgrade process includes updating three components:
 
   1. [Upgrade the Redis Enterprise operator](#upgrade-the-operator)
-  2. [Upgrade the Redis Enterprise cluster (REC)](#upgrade-the-redis-enterprise-cluster-rec)
-  3. [Upgrade Redis Enterprise databases (REDB)](#upgrade-databases)
+  1. [Upgrade the Redis Enterprise cluster (REC)](#upgrade-the-redis-enterprise-cluster-rec)
+  1. [Upgrade Redis Enterprise databases (REDB)](#upgrade-databases)
 
-## Prerequisite
+## Prerequisites
 
 1. Check [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) to make sure your Kubernetes distribution is supported.
 
-2. Use `kubectl get rec` and verify the `LICENSE STATE` is valid on your REC before you start the upgrade process.
+1. Use `kubectl get rec` and verify the `LICENSE STATE` is valid on your REC before you start the upgrade process.
 
-3. Verify you are upgrading from Redis Enterprise operator version 6.2.10-45 or later. If you are not, you must upgrade to 6.2.10-45 before upgrading to versions 6.2.18 or later.
+1. Verify you are upgrading from Redis Enterprise operator version 6.2.10-45 or later. If you are not, you must upgrade to 6.2.10-45 before upgrading to versions 6.2.18 or later.
 
 {{<warning>}}**Upgrade cluster operating system** If your databases use modules, you need to update all nodes in the cluster to Redis Enterprise 7.2.4 or later before upgrading your operating system. See [Upgrade a cluster's operating system]({{< relref "/operate/rs/installing-upgrading/upgrading/upgrade-os" >}})in the Redis Enterprise Software documentation for more details.{{</warning>}}
 
@@ -96,8 +96,8 @@ redis-enterprise-operator   1/1     1            1           0m36s
 ```
 
 {{< warning >}}
- We recommend upgrading the REC as soon as possible after updating the operator. After the operator upgrade completes, the operator suspends the management of the REC and its associated REDBs, until the REC upgrade completes.
- {{< /warning >}}
+We recommend upgrading the REC as soon as possible after updating the operator. After the operator upgrade completes, the operator suspends the management of the REC and its associated REDBs, until the REC upgrade completes.
+{{< /warning >}}
 
 ## Upgrade the Redis Enterprise cluster (REC)
 
@@ -115,8 +115,9 @@ After the operator upgrade is complete, you can upgrade Redis Enterprise cluster
 
 ### Upgrade an REC with an Active-Active database
 
-- We recommend upgrading all participating clusters to the same operator version. 
-- If you are upgrading from a preview version of the Active-Active controller, you can remove the following environment variables: `ACTIVE_ACTIVE_DATABASE_CONTROLLER_ENABLED`, `REMOTE_CLUSTER_CONTROLLER_ENABLED`, and `ENABLE_ALPHA_FEATURES`.
+We recommend upgrading all participating clusters to the same operator version.
+
+If you are upgrading from a preview version of the Active-Active controller, you can remove the following environment variables: `ACTIVE_ACTIVE_DATABASE_CONTROLLER_ENABLED`, `REMOTE_CLUSTER_CONTROLLER_ENABLED`, and `ENABLE_ALPHA_FEATURES`.
 
 ### Edit `redisEnterpriseImageSpec` in the REC spec
 
@@ -171,4 +172,3 @@ For more details on how to [upgrade a database]({{< relref "/operate/rs/installi
 For Active-Active databases, see [Upgrade an Active-Active database]({{<relref "/operate/rs/installing-upgrading/upgrading/upgrade-active-active">}}).
 
 Note that if your cluster [`redisUpgradePolicy`]({{< relref "/operate/kubernetes/reference/redis_enterprise_cluster_api#redisupgradepolicy" >}}) or your database [`redisVersion`]({{< relref "/operate/kubernetes/reference/redis_enterprise_database_api#redisversion" >}}) are set to `major`, you won't be able to upgrade those databases to minor versions. See [Redis upgrade policy]({{< relref "/operate/rs/installing-upgrading/upgrading#redis-upgrade-policy" >}}) for more details.
-