Merge pull request #4887 from sunlintong/slt-5

spell correct
kubernetes · Apr 3, 2018 · a46e3f1 · a46e3f1
2 parents 0d0c86a + 8351cfb
commit a46e3f1
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/etcd_backup.md b/docs/etcd_backup.md
@@ -43,7 +43,7 @@ protokube will look for the following tags:
 
 * `KubernetesCluster` containing the cluster name (e.g. `k8s.mycompany.tld`)
 * `Name` containing the volume name (e.g. `eu-central-1a.etcd-main.k8s.mycompany.tld`)
-* `k8s.io/etcd/main` containg the availability zone of the volume (e.g. `eu-central-1a/eu-central-1a`)
+* `k8s.io/etcd/main` containing the availability zone of the volume (e.g. `eu-central-1a/eu-central-1a`)
 * `k8s.io/role/master` with the value `1`
 
 After fully restoring the volume ensure that the old volume is no longer there,

diff --git a/docs/instance_groups.md b/docs/instance_groups.md
@@ -67,7 +67,7 @@ The procedure to resize the root volume works the same way:
 
 * Edit the instance group, set `rootVolumeSize` and/or `rootVolumeType` to the desired values: `kops edit ig nodes`
 * `rootVolumeType` must be one of [supported volume types](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html), e.g. `gp2` (default), `io1` (high performance) or `standard` (for testing).
-* If `rootVolumeType` is set to `io1` then you can define the number of Iops by specifing `rootVolumeIops` (defaults to 100 if not defined)
+* If `rootVolumeType` is set to `io1` then you can define the number of Iops by specifying `rootVolumeIops` (defaults to 100 if not defined)
 * Preview changes: `kops update cluster <clustername>`
 * Apply changes: `kops update cluster <clustername> --yes`
 * Rolling update to update existing instances: `kops rolling-update cluster --yes`