review edits

Author: kaitlynmichael

content/operate/kubernetes/deployment/helm.md

@@ -75,7 +75,7 @@ To monitor the installation add the `--debug` flag. The installation runs severa
 
 ```sh
 helm install <operator-name> <repo-name>/redis-enterprise-operator \
-    --version <release-name> \
+    --version <chart-version> \
     --namespace <namespace-name> \
     --create-namespace
     --set <key1>=<value1> \
@@ -92,7 +92,7 @@ helm install <operator-name> <repo-name>/redis-enterprise-operator \
 
 ```sh
 helm install <operator-name> <repo-name>/redis-enterprise-operator \
-    --version <release-name> \
+    --version <chart-version> \
     --namespace <namespace-name> \
     --create-namespace \
     --values <path-to-values-file>
@@ -107,7 +107,7 @@ To migrate an existing non-Helm installation of the Redis Enterprise operator to
 2. [Install](#install) the Helm chart adding the `--take-ownership` flag:
 
    ```sh
-   helm install <release-name> <path-to-chart> --take-ownership
+   helm install <release-name> <repo-name>/redis-enterprise-operator --take-ownership
    ```
 
    - The `--take-ownership` flag is available with Helm versions 3.18 or later.
@@ -120,34 +120,29 @@ To migrate an existing non-Helm installation of the Redis Enterprise operator to
    kubectl delete validatingwebhookconfiguration redis-enterprise-admission
    ```
 
-   This step is only needed when the `admission.limitToNamespace` chart value is set to `true` (the default). In this case, the webhook object installed by the chart is named `redis-enterprise-admission-<namespace>`. If `admission.limitToNamespace` is set to `false`, the webhook installed by the chart is named `redis-enterprise-admission`, and the existing webhook object is reused.
+   This step is only needed when the `admission.limitToNamespace` chart value is set to `true` (the default). In this case, the webhook object installed by the chart is named `redis-enterprise-admission-<namespace>`, and the original webhook object, named `redis-enterprise-admission`, becomes redundant. If `admission.limitToNamespace` is set to `false`, the webhook installed by the chart is named `redis-enterprise-admission`, and the existing webhook object is reused.
 
 ## Upgrade the chart
 
 To upgrade an existing Helm chart installation:
 
 ```sh
-helm upgrade <release-name> <path-to-chart>
+helm upgrade <release-name> <repo-name>/redis-enterprise-operator --version <chart-version>
 ```
 
-For example, to upgrade a chart with the release name `my-redis-enterprise` from the chart's root directory:
+You can also upgrade from a local directory:
 
 ```sh
-helm upgrade my-redis-enterprise .
+helm upgrade <release-name> <path-to-chart>
 ```
 
-You can also upgrade using the Redis Helm repository:
+For example, to upgrade a chart with the release name `my-redis-enterprise` from the chart's root directory:
 
 ```sh
-helm upgrade <release-name> <repo-name>/redis-enterprise-operator --version <chart-version>
+helm upgrade my-redis-enterprise .
 ```
 
-To upgrade the chart on **OpenShift**, include the `openshift.mode=true` parameter:
-
-```sh
-helm upgrade <release-name> <path-to-chart> \
-     --set openshift.mode=true
-```
+To upgrade with OpenShift, add `--set openshift.mode=true`.
 
 The upgrade process automatically updates the operator and its components, including the Custom Resource Definitions (CRDs). The CRDs are versioned and update only if the new version is higher than the existing version.
 

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

@@ -64,14 +64,14 @@ If you installed the Redis Enterprise operator using Helm charts on OpenShift, y
 To upgrade using Helm on OpenShift:
 
 ```sh
-helm upgrade <release-name> redis/redis-enterprise-operator --version <chart-version> \
+helm upgrade <release-name> <repo-name>/redis-enterprise-operator --version <chart-version> \
     --set openshift.mode=true
 ```
 
 For example:
 
 ```sh
-helm upgrade my-redis-enterprise redis/redis-enterprise-operator --version 7.8.2-2 \
+helm upgrade my-redis-enterprise <repo-name>/redis-enterprise-operator --version 7.8.2-2 \
     --set openshift.mode=true
 ```
 

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

@@ -57,28 +57,6 @@ See [Upgrade modules]({{<relref "/operate/oss_and_stack/stack-with-enterprise/in
 
 Use `kubectl get rec` and verify the `LICENSE STATE` is valid on your REC before you start the upgrade process.
 
-## Upgrade with Helm charts
-
-If you installed the Redis Enterprise operator using Helm charts on OpenShift, you can upgrade using Helm commands instead of the OperatorHub. This method automatically handles the operator upgrade and Custom Resource Definition (CRD) updates.
-
-To upgrade using Helm on OpenShift:
-
-```sh
-helm upgrade <release-name> redis/redis-enterprise-operator --version <chart-version> \
-    --set openshift.mode=true
-```
-
-For example:
-
-```sh
-helm upgrade my-redis-enterprise redis/redis-enterprise-operator --version 7.8.2-2 \
-    --set openshift.mode=true
-```
-
-After the Helm upgrade completes, continue with [upgrading the Redis Enterprise cluster](#upgrade-the-redis-enterprise-cluster) and [upgrading databases](#upgrade-databases).
-
-For detailed Helm upgrade instructions, see [Upgrade the chart]({{<relref "/operate/kubernetes/deployment/helm#upgrade-the-chart">}}).
-
 ## Upgrade the Redis Enterprise operator
 
 1. Select the **Redis Enterprise Operator** from the **Operators**>**Installed Operators** page.