diff --git a/stable/redis-ha/Chart.yaml b/stable/redis-ha/Chart.yaml
index eecb68c2b8..576f7275e0 100644
--- a/stable/redis-ha/Chart.yaml
+++ b/stable/redis-ha/Chart.yaml
@@ -5,7 +5,7 @@ keywords:
 - redis
 - keyvalue
 - database
-version: 2.1.0
+version: 2.1.1
 appVersion: 4.0.8-r0
 description: Highly available Redis cluster with multiple sentinels and standbys.
 icon: https://upload.wikimedia.org/wikipedia/en/thumb/6/6b/Redis_Logo.svg/1200px-Redis_Logo.svg.png
diff --git a/stable/redis-ha/README.md b/stable/redis-ha/README.md
index 8c75d2d0fa..40f0a97923 100644
--- a/stable/redis-ha/README.md
+++ b/stable/redis-ha/README.md
@@ -56,7 +56,7 @@ $ helm install \
 
 ## Configuration
 
-The following tables lists the configurable parameters of the Redis chart and their default values.
+The following table lists the configurable parameters of the Redis chart and their default values.
 
 | Parameter                        | Description                                                                                                                  | Default                                                   |
 | -------------------------------- | -----------------------------------------------------                                                                        | --------------------------------------------------------- |
@@ -104,7 +104,7 @@ can be seen through.
 The redis-role=master pod is the key for the cluster to get started. Sentinels will wait for it to appear
 in the LB before they finish launching. All other pods wait for the Sentinels to ID the master. Running
 Pods also set the labels podIP and runID. runID is the first few characters of the unique run_id value
-generated by each Redis sever.
+generated by each Redis server.
 
 During normal operation, there should be only one redis-role=master pod. If it fails, the Sentinels
 will nominate a new master and change all the redis-role values appropriately.