just a couple grammar/spelling errors I noticed

AdamDang · Feb 2, 2018 · 257ca33 · 257ca33
1 parent f58d7b2
commit 257ca33
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/boot-sequence.md b/docs/boot-sequence.md
@@ -79,7 +79,7 @@ kops uses DNS to allow nodes and end-users to discover the api-server.  The apis
 
 ## etcd bringup
 
-etcd is where we have put all of our synchronization logic, so it is more complicated that most other pieces,
+etcd is where we have put all of our synchronization logic, so it is more complicated than most other pieces,
 and we must be really careful when bringing it up.
 
 kops follows CoreOS's recommend procedure for [bring-up of etcd on clouds](https://github.com/coreos/etcd/issues/5418):
@@ -107,7 +107,7 @@ Most of this has focused on things that happen on the master, but the node bring
 * nodeup installs docker & kubelet
 * in /etc/kubernetes/manifests, we have kube-proxy
 
-So kubelet will start up, and will kube-proxy.  It will try to reach the api-server on the internal DNS name,
+So kubelet will start up, as will kube-proxy.  It will try to reach the api-server on the internal DNS name,
 and once the master is up it will succeed.  Then:
 
 * kubelet creates a Node object representing itself

diff --git a/pkg/apis/kops/cluster.go b/pkg/apis/kops/cluster.go
@@ -48,7 +48,7 @@ type ClusterSpec struct {
 	// The Channel we are following
 	Channel string `json:"channel,omitempty"`
 	// ConfigBase is the path where we store configuration for the cluster
-	// This might be different that the location when the cluster spec itself is stored,
+	// This might be different than the location where the cluster spec itself is stored,
 	// both because this must be accessible to the cluster,
 	// and because it might be on a different cloud or storage system (etcd vs S3)
 	ConfigBase string `json:"configBase,omitempty"`