docs: spelling corrections 📘

Author: robin-wayve

docs/csi-debug.md

@@ -17,7 +17,7 @@ kubectl logs csi-blob-controller-56bfddd689-dh5tk -c blob -n kube-system > csi-b
 > `kubectl logs deploy/csi-blob-controller -c blob -f -n kube-system`
 
 ### Case#2: volume mount/unmount failed
- - locate csi driver pod and make sure which pod do tha actual volume mount/unmount
+ - locate csi driver pod and make sure which pod does the actual volume mount/unmount
 ```console
 kubectl get po -o wide -n kube-system | grep csi-blob-node
 ```
@@ -36,7 +36,7 @@ kubectl logs csi-blob-node-cvgbs -c blob -n kube-system > csi-blob-node.log
 > kubectl logs daemonset/csi-blob-node -c blob -n kube-system -f
 > ```
 
-#### Update driver version quickly by editting driver deployment directly
+#### Update driver version quickly by editing driver deployment directly
  - update controller deployment
 ```console
 kubectl edit deployment csi-blob-controller -n kube-system

docs/csi-dev.md

@@ -22,7 +22,7 @@ $ make verify
 helm package charts/latest/blob-csi-driver -d charts/latest/
 ```
 
- - Build continer image and push to dockerhub
+ - Build container image and push to dockerhub
 ```console
 export REGISTRY_NAME=<dockerhub-alias>
 make push-latest

docs/design.md

@@ -1,5 +1,5 @@
 # Azure Blob Storage CSI driver design goals
- > Azure Blob Storage CSI driver is implemented as compatitable as possible with built-in [blobfuse](https://kubernetes.io/docs/concepts/storage/volumes/#blobfuse) plugin, it has following goals:
+ > Azure Blob Storage CSI driver is implemented as compatible as possible with built-in [blobfuse](https://kubernetes.io/docs/concepts/storage/volumes/#blobfuse) plugin, it has following goals:
 
 Goal | Status | Notes
 --- | --- | --- |

docs/install-csi-driver-v0.1.0.md

@@ -1,4 +1,4 @@
-# Install blobfuse CSI driveri v0.1.0-alpha on a kubernetes cluster
+# Install blobfuse CSI driver v0.1.0-alpha on a kubernetes cluster
 
 If you have already installed Helm, you can also use it to install blobfuse CSI driver. Please see [Installation with Helm](../charts/README.md).
 

docs/install-csi-driver-v0.2.0.md

@@ -1,4 +1,4 @@
-# Install blobfuse CSI driveri v0.2.0 on a kubernetes cluster
+# Install blobfuse CSI driver v0.2.0 on a kubernetes cluster
 
 If you have already installed Helm, you can also use it to install blobfuse CSI driver. Please see [Installation with Helm](../charts/README.md).
 

docs/install-csi-driver-v0.3.0.md

@@ -1,4 +1,4 @@
-# Install blobfuse CSI driveri v0.3.0 on a kubernetes cluster
+# Install blobfuse CSI driver v0.3.0 on a kubernetes cluster
 
 If you have already installed Helm, you can also use it to install blobfuse CSI driver. Please see [Installation with Helm](../charts/README.md).
 

docs/install-csi-driver-v0.4.0.md

@@ -1,4 +1,4 @@
-# Install blobfuse CSI driveri v0.4.0 on a kubernetes cluster
+# Install blobfuse CSI driver v0.4.0 on a kubernetes cluster
 
 If you have already installed Helm, you can also use it to install blobfuse CSI driver. Please see [Installation with Helm](../charts/README.md).
 

docs/install-driver-on-aks.md

@@ -2,13 +2,14 @@
 
  - Prerequisites
 
-AKS cluster is created with user asissnged identity by default, make sure cluster identity has `Contributor` role on node resource group, follow below instruction to set up `Contributor` role on node resource group
+An AKS cluster is created with a user assigned identity by default.
+Make sure the cluster identity has a `Contributor` role assignment on the cluster resource group.
+See below how to assign a `Contributor` role on the cluster resource group
 ![image](https://user-images.githubusercontent.com/4178417/120978367-f68f0a00-c7a6-11eb-8e87-89247d1ddc0b.png):
 
-
  - Install CSI driver
 
-install latest **released** CSI driver version, following guide [here](./install-blob-csi-driver.md)
+Install latest **released** CSI driver version, following guide [here](./install-blob-csi-driver.md)
 
  - Set up new storage classes
 ```console

test/e2e/testsuites/testsuites.go

@@ -480,7 +480,7 @@ var podFailedCondition = func(pod *v1.Pod) (bool, error) {
 		ginkgo.By("Saw pod failure")
 		return true, nil
 	case v1.PodSucceeded:
-		return true, fmt.Errorf("pod %q successed with reason: %q, message: %q", pod.Name, pod.Status.Reason, pod.Status.Message)
+		return true, fmt.Errorf("pod %q succeeded with reason: %q, message: %q", pod.Name, pod.Status.Reason, pod.Status.Message)
 	default:
 		return false, nil
 	}