diff --git a/incubator/burrow/Chart.yaml b/incubator/burrow/Chart.yaml
index c8ed3c2c61..288b0c0f6f 100644
--- a/incubator/burrow/Chart.yaml
+++ b/incubator/burrow/Chart.yaml
@@ -1,5 +1,5 @@
 name: burrow
-version: 0.3.0
+version: 0.3.1
 appVersion: 0.17.1
 description: Burrow is a permissionable smart contract machine
 icon: https://pbs.twimg.com/profile_images/697035383679295488/_6vl74tM_400x400.png
diff --git a/incubator/burrow/README.md b/incubator/burrow/README.md
index 331e8f014d..4f85d2e58b 100644
--- a/incubator/burrow/README.md
+++ b/incubator/burrow/README.md
@@ -157,7 +157,7 @@ There are a few other considerations underpinning how this chart was developed.
 
 ### Deployments versus StatefulSets
 
-The first consideration is whether to utilize multiple deployments or a statefulSet. The chart maintainer has (to date) found it significantly easier to work with multiple deployments than with a statefulSet because the config files and keys differ subltely between and across each blockchain node. StatefulSets are currently not able to as elegantly handle the 1-to-1 linkages between the various key secrets and config files that are necessary to operate each blockchain node within the cluster.
+The first consideration is whether to utilize multiple deployments or a statefulSet. The chart maintainer has (to date) found it significantly easier to work with multiple deployments than with a statefulSet because the config files and keys differ subtly between and across each blockchain node. StatefulSets are currently not able to as elegantly handle the 1-to-1 linkages between the various key secrets and config files that are necessary to operate each blockchain node within the cluster.
 
 ### Running multiple chains within your cluster