fix typos

mikhail-klimko · mikhail-klimko · commit a1de5361da9c · 2021-06-09T19:19:40.000+03:00
diff --git a/_docs/administration/codefresh-runner.md b/_docs/administration/codefresh-runner.md
@@ -1314,7 +1314,7 @@ If you want to use  *LocalSSD* in GKE:
 
 *Prerequisites:* [GKE cluster with local SSD](https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/local-ssd)
 
-Install runner using GKE Local SSD:
+Install Runner using GKE Local SSD:
 ```
 codefresh runner init [options] --set-value=Storage.LocalVolumeParentDir=/mnt/disks/ssd0/codefresh-volumes \
                             --build-node-selector=cloud.google.com/gke-local-ssd=true
@@ -1337,20 +1337,20 @@ codefresh runner init [options] --set-value=Storage.LocalVolumeParentDir=/mnt/di
 {% endraw %}
 {% endhighlight %}
 
-To configure existing Runner with Local SSD follow this article:
+To configure existing Runner with Local SSDs follow this article:
 
 [How-to: Configuring an existing Runtime Environment with Local SSDs (GKE only)](https://support.codefresh.io/hc/en-us/articles/360016652920-How-to-Configuring-an-existing-Runtime-Environment-with-Local-SSDs-GKE-only-)
 
 ##### GCE Disks
 If you want to use  *GCE Disks*:
 
-*Prerequisite:* volume provisioner (dind-volume-provisioner) should have permissions to create/delete/get of Google disks
+*Prerequisites:* volume provisioner (dind-volume-provisioner) should have permissions to create/delete/get GCE disks
 
 There are 3 options to provide cloud credentials on GCE:
 
-* run `dind-volume-provisioner-runner` on node with iam role which is allowed to create/delete/get of Google disks
-* create Google Service Account with `ComputeEngine.StorageAdmin`, download its key and pass it to venona installed with `--set-file=Storage.GooogleServiceAccount=/path/to/google-service-account.json`
-* use [Google Workload Identity](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity) to assign iam role to `volume-provisioner-venona` service account 
+* run `dind-volume-provisioner-runner` pod on a node with IAM role which is allowed to create/delete/get GCE disks
+* create Google Service Account with `ComputeEngine.StorageAdmin` role, download its key is JSON format and pass it to `codefresh runner init` with `--set-file=Storage.GooogleServiceAccount=/path/to/google-service-account.json`
+* use [Google Workload Identity](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity) to assign IAM role to `volume-provisioner-runner` service account 
 
 Notice that builds will be running in a single availability zone, so you must specify AvailabilityZone parameters.
 
@@ -1359,6 +1359,7 @@ Install Runner using GCE Disks:
 ```
 codefresh runner init [options] --set-value=Storage.Backend=gcedisk \
                             --set-value=Storage.AvailabilityZone=us-central1-a \
+                            [--kube-node-selector=failure-domain.beta.kubernetes.io/zone=us-central1-a \]
                             --build-node-selector=failure-domain.beta.kubernetes.io/zone=us-central1-a \
                             [--set-file=Storage.GoogleServiceAccount=/path/to/google-service-account.json]
 ```
@@ -1393,7 +1394,7 @@ codefresh runner init [options] --set-value=Storage.Backend=gcedisk \
 {% endraw %}
 {% endhighlight %}
 
-To configure existing Runner with GCE disks follow this article:
+To configure existing Runner with GCE Disks follow this article:
 
 [How-to: Configuring an existing Runtime Environment with GCE disks](https://support.codefresh.io/hc/en-us/articles/360016652900-How-to-Configuring-an-existing-Runtime-Environment-with-GCE-disks)
 
