Spelling fixes inspired by github.com/client9/misspell

docs/user-guide/ingress.md

@@ -55,7 +55,7 @@ Documentation for other releases can be found at
 
 __Terminology__
 
-Throughout this doc you will see a few terms that are sometimes used interchangably elsewhere, that might cause confusion. This section attempts to clarify them.
+Throughout this doc you will see a few terms that are sometimes used interchangeably elsewhere, that might cause confusion. This section attempts to clarify them.
 
 * Node: A single virtual or physical machine in a Kubernetes cluster.
 * Cluster: A group of nodes firewalled from the internet, that are the primary compute resources managed by Kubernetes.

docs/user-guide/jobs.md

@@ -239,7 +239,7 @@ parallelism, for a variety or reasons:
 
 - For Fixed Completion Count jobs, the actual number of pods running in parallel will not exceed the number of
   remaining completions.   Higher values of `.spec.parallelism` are effectively ignored.
-- For work queue jobs, no new pods are started after any pod has succeded -- remaining pods are allowed to complete, however.
+- For work queue jobs, no new pods are started after any pod has succeeded -- remaining pods are allowed to complete, however.
 - If the controller has not had time to react.
 - If the controller failed to create pods for any reason (lack of ResourceQuota, lack of permission, etc),
   then there may be fewer pods than requested.

docs/user-guide/kubectl-overview.md

@@ -305,7 +305,7 @@ Use the following set of examples to help you familiarize yourself with running
 		// Return a snapshot of the logs from pod <pod-name>.
 		$ kubectl logs <pod-name>
 
-		// Start streaming the logs from pod <pod-name>. This is similiar to the 'tail -f' Linux command.
+		// Start streaming the logs from pod <pod-name>. This is similar to the 'tail -f' Linux command.
 		$ kubectl logs -f <pod-name>
 
 

docs/user-guide/replication-controller.md

@@ -68,7 +68,7 @@ Documentation for other releases can be found at
 ## What is a _replication controller_?
 
 A _replication controller_ ensures that a specified number of pod "replicas" are running at any one
-time. In other words, a replication controller makes sure that a pod or homogenous set of pods are
+time. In other words, a replication controller makes sure that a pod or homogeneous set of pods are
 always up and available.
 If there are too many pods, it will kill some. If there are too few, the
 replication controller will start more. Unlike manually created pods, the pods maintained by a

docs/user-guide/walkthrough/k8s201.md

@@ -108,7 +108,7 @@ They are a core concept used by two additional Kubernetes building blocks: Repli
 
 ## Replication Controllers
 
-OK, now you know how to make awesome, multi-container, labeled pods and you want to use them to build an application, you might be tempted to just start building a whole bunch of individual pods, but if you do that, a whole host of operational concerns pop up.  For example: how will you scale the number of pods up or down and how will you ensure that all pods are homogenous?
+OK, now you know how to make awesome, multi-container, labeled pods and you want to use them to build an application, you might be tempted to just start building a whole bunch of individual pods, but if you do that, a whole host of operational concerns pop up.  For example: how will you scale the number of pods up or down and how will you ensure that all pods are homogeneous?
 
 Replication controllers are the objects to answer these questions.  A replication controller combines a template for pod creation (a "cookie-cutter" if you will) and a number of desired replicas, into a single Kubernetes object.  The replication controller also contains a label selector that identifies the set of objects managed by the replication controller.  The replication controller constantly measures the size of this set relative to the desired size, and takes action by creating or deleting pods.