Update Helm references for case consistency

Author: KerryKovacevic

dell-csi-helm-installer/README.md

@@ -19,7 +19,7 @@ Installing any of the Dell EMC CSI Drivers requires a few utilities to be instal
 | Dependency    | Usage  |
 | ------------- | ----- |
 | `kubectl`     | Kubectl is used to validate that the Kubernetes system meets the requirements of the driver. |
-| `helm`        | Helm v3 is used as the deployment tool for Charts. See, [Install HELM 3](https://helm.sh/docs/intro/install/) for instructions to install HELM 3. |
+| `helm`        | Helm v3 is used as the deployment tool for Charts. See, [Install Helm 3](https://helm.sh/docs/intro/install/) for instructions to install Helm 3. |
 | `sshpass`     | sshpass is used to check certain pre-requisities in worker nodes (in chosen drivers). |
 
 

dell-csi-helm-installer/csi-offline-bundle.md

@@ -2,7 +2,7 @@
 
 ## Description
 
-The `csi-offline-bundle.sh` script can be used to create a package usable for offline installation of the Dell EMC CSI Storage Providers, via Helm. 
+The `csi-offline-bundle.sh` script can be used to create a package for offline installation of Dell CSI storage providers for deployment via Helm.  
 
 This includes the following drivers:
 * [PowerFlex](https://github.com/dell/csi-vxflexos)
@@ -11,7 +11,7 @@ This includes the following drivers:
 * [PowerStore](https://github.com/dell/csi-powerstore)
 * [Unity](https://github.com/dell/csi-unity)
 
-the `csm-offline-bundle.sh` script can be used to create a package usable for offline installation of the Dell EMC CSI Storage Providers, via the CSM Operator.
+The `csm-offline-bundle.sh` script can be used to create a package for offline installation of Dell CSI storage providers for deployment via the CSM Operator.
 * [Dell CSM Operator](https://github.com/dell/csm-operator)
 
 ## Dependencies
@@ -45,7 +45,7 @@ To perform an offline installation of a driver or the Operator, the following st
 This needs to be performed on a linux system with access to the internet as a git repo will need to be cloned, and container images pulled from public registries.
 
 The build an offline bundle, the following steps are needed:
-1. Perform a `git clone` of the desired repository. For a helm based install, the specific driver repo should be cloned. For an Operator based deployment, the Dell CSM Operator repo should be cloned
+1. Perform a `git clone` of the desired repository. For a Helm based install, the specific driver repo should be cloned. For an Operator based deployment, the Dell CSM Operator repo should be cloned
 2. Run the offline bundle script with an argument of `-c` in order to create an offline bundle
   - For Helm installs, the `csi-offline-bundle.sh` script will be found in the `dell-csi-helm-installer` directory
   - For Operator installs, the `csm-offline-bundle.sh` script will be found in the `scripts` directory

test/helm/README.md

@@ -1,4 +1,4 @@
-This directory contains various test helm charts and test scripts:
+This directory contains various test Helm charts and test scripts:
 
 Helm charts:
 2replicas  Creates 2 filesystem mounts like 2vols but with Replicas = 2
@@ -11,10 +11,10 @@ block1  Create a block volume using a pvc (NOT WORKING)
 block2  Create a block volume using a pvc+pv+existing volume (NOT WORKING)
 
 Scripts:
-starttest.sh  -- Used to instantiate one of the helm charts above. Requires argument of directory name (e.g. 2vols)
-stoptest.sh -- Stops currently running helm chart
-snapcgtest.sh -- Used after starting a helm chart; tests snapping the persistent volumes into a consistency group
-snaprestoretest.sh -- Used without previously starting a helm test; instantiates 2vols; then upgrades it to 2vols+restore (with volume from snapshot)
+starttest.sh  -- Used to instantiate one of the Helm charts above. Requires argument of directory name (e.g. 2vols)
+stoptest.sh -- Stops currently running Helm chart
+snapcgtest.sh -- Used after starting a Helm chart; tests snapping the persistent volumes into a consistency group
+snaprestoretest.sh -- Used without previously starting a Helm test; instantiates 2vols; then upgrades it to 2vols+restore (with volume from snapshot)
 snaptest.sh -- Used after starting 2vols; snaps pvol0 twice
 
 See the release notes for additional information and examples of using these tests.

test/helm/blocksnap/README.md

@@ -17,10 +17,10 @@ Execute "sh run.sh" to run the test in a kubernetes environment that supports v1
 the vxflexos CSI torage system in run.sh. You can edit run.sh and change the storageclass, snapclass (the volumesnapshotclass name),
 and namespace parameters to run the test for a different type of CSI storage.
 
-The test is constructed from three helm charts that are deployed in the following sequence:
+The test is constructed from three Helm charts that are deployed in the following sequence:
 1. 1vol creates one volume and deploys it in a pod
 2. 1snap creates a snapshot from the volume in step 1.
 3. 1volfromsnap creates a volume from the snapshot and deploys it in a second pod.
 
 If the test runs succssfully, it compares the data generated in the first pod with the data from the snap in the second pod
-to make sure they match. Then it deletes the helm deployments and waits until the pvcs in the namespace are deleted.
+to make sure they match. Then it deletes the Helm deployments and waits until the pvcs in the namespace are deleted.