typo (#948)

Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>

docs/Tutorials/Kubernetes/Maintenance.md

@@ -12,10 +12,10 @@ description: Maintenance for Besu on a Kubernetes cluster
 
 ## Update a persistent volume claim size
 
-Over time, as the chain grows so will the amount of space used by the persistent volume claim (PVC).
+Over time, as the chain grows, so will the amount of space used by the persistent volume claim (PVC).
 As of Kubernetes v1.11, [certain types of Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/#allow-volume-expansion)
 allow volume resizing.
-Production charts for Azure use Azure Files and on AWS use EBS Block Store which allow for volume expansion.
+Production charts for Azure use Azure Files, and on AWS use EBS Block Store which allow for volume expansion.
 
 To update the volume size, you must update the override values file.
 For example, to increase the size on the transaction nodes volumes, add the following snippet to the
@@ -38,7 +38,7 @@ helm upgrade tx-1 ./charts/besu-node --namespace besu --values ./values/txnode.y
 
 !!! important
 
-    When updating Besu nodes across a cluster, perform the updatesas a rolling update and not all at once,
+    When updating Besu nodes across a cluster, perform the updates as a rolling update and not all at once,
     especially for the validator pool. If all the validators are taken offline, the
     chain halts, and you must wait for round changes to expire before blocks are created again.