minor spelling update

using mispellings https://pypi.python.org/pypi/misspellings

README.md

@@ -67,7 +67,7 @@ Your copy of the site will then be viewable at: [http://localhost:4000](http://l
 
 ## GitHub help
 
-If you're a bit rusty with git/GitHub, you might wanna read
+If you're a bit rusty with git/GitHub, you might want to read
 [this](http://readwrite.com/2013/10/02/github-for-beginners-part-2) for a refresher.
 
 ## Common Tasks

docs/admin/authentication.md

@@ -228,7 +228,7 @@ it must be an array of strings.
 
 Kubernetes does not provide an OpenID Connect Identity Provider.
 You can use an existing public OpenID Connect Identity Provider (such as Google, or [others](http://connect2id.com/products/nimbus-oauth-openid-connect-sdk/openid-connect-providers)).
-Or, you can run your own Identity Provider, such as CoreOS [dex](https://github.com/coreos/dex), [Keycloak](https://github.com/keycloak/keycloak) or CloudFoundary [UAA](https://github.com/cloudfoundry/uaa).
+Or, you can run your own Identity Provider, such as CoreOS [dex](https://github.com/coreos/dex), [Keycloak](https://github.com/keycloak/keycloak) or CloudFoundry [UAA](https://github.com/cloudfoundry/uaa).
 
 The provider needs to support [OpenID connect discovery](https://openid.net/specs/openid-connect-discovery-1_0.html); not all do.
 

docs/admin/cluster-management.md

@@ -84,7 +84,7 @@ no node that has enough free capacity (or doesn't match other pod requirements)
 to wait until some pods are terminated or a new node is added.
 
 Cluster autoscaler looks for the pods that cannot be scheduled and checks if adding a new node, similar
-to the other in the cluster, would help. If yes, then it resizes the cluster to accomodate the waiting pods.
+to the other in the cluster, would help. If yes, then it resizes the cluster to accommodate the waiting pods.
 
 Cluster autoscaler also scales down the cluster if it notices that some node is not needed anymore for
 an extended period of time (10min but it may change in the future).

docs/admin/garbage-collection.md

@@ -52,5 +52,5 @@ Containers can potentially be garbage collected before their usefulness has expi
 can contain logs and other data that can be useful for troubleshooting. A sufficiently large value for
 `maximum-dead-containers-per-container` is highly recommended to allow at least 2 dead containers to be
 retained per expected container. A higher value for `maximum-dead-containers` is also recommended for a
-similiar reason.
+similar reason.
 See [this issue](https://github.com/kubernetes/kubernetes/issues/13287) for more details.

docs/admin/multiple-zones.md

@@ -39,7 +39,7 @@ or service across nodes in a single-zone cluster (to reduce the impact of
 failures.)  With multiple-zone clusters, this spreading behaviour is
 extended across zones (to reduce the impact of zone failures.)  (This is
 achieved via `SelectorSpreadPriority`).  This is a best-effort
-placement, and so if the zones in your cluster are heterogenous
+placement, and so if the zones in your cluster are heterogeneous
 (e.g. different numbers of nodes, different types of nodes, or
 different pod resource requirements), this might prevent perfectly
 even spreading of your pods across zones. If desired, you can use

docs/hellonode.md

@@ -117,7 +117,7 @@ curl http://localhost:8080
 
 You should see `Hello World!`
 
-**Note:** *If you recieve a `Connection refused` message from Docker for Mac, ensure you are using the latest version of Docker (1.12 or later). Alternatively, if you are using Docker Toolbox on OSX, make sure you are using the VM's IP and not localhost:*
+**Note:** *If you receive a `Connection refused` message from Docker for Mac, ensure you are using the latest version of Docker (1.12 or later). Alternatively, if you are using Docker Toolbox on OSX, make sure you are using the VM's IP and not localhost:*
 
 ```shell
 curl "http://$(docker-machine ip YOUR-VM-MACHINE-NAME):8080"

docs/templatedemos/filledout.md

@@ -42,7 +42,7 @@ kubectl get pod <name>
 
 | Return Value | Description |
 |--------------|-------------|
-| `READY` | Describes the number of containers that are ready to recieve traffic. |
+| `READY` | Describes the number of containers that are ready to receive traffic. |
 | `STATUS` | A value from the `PodPhase` enum describing the current status of the pod. Can be `Running`, `Pending`, `Succeeded`, `Failed`, and `Unknown`. |
 
 TODO: Link to refpage for `kubectl get pod`
@@ -77,4 +77,4 @@ YAML EXAMPLE HERE
 
 {% endcapture %}
 
-{% include templates/concept-overview.md %}
+{% include templates/concept-overview.md %}

docs/user-guide/petset/bootstrapping/index.md

@@ -19,7 +19,7 @@ This example shows you how to "carry over" runtime state across Pet restart by s
 
 ### Background
 
-Applications that incrementally build state usually need strong guarantees that they will not restart for extended durations. This is tricky to achieve with containers, so instead, we will ensure that the results of previous computations are trasferred to future pets. Doing so is straightforward using vanilla Persistent Volumes (which Pet Set already gives you), unless the volume mount point itself needs to be initialized for the Pet to start. This is exactly the case with "virtual machine" docker images, like those based on ubuntu or fedora. Such images embed the entier rootfs of the distro, including package managers like `apt-get` that assume a certain layout of the filesystem. Meaning:
+Applications that incrementally build state usually need strong guarantees that they will not restart for extended durations. This is tricky to achieve with containers, so instead, we will ensure that the results of previous computations are transferred to future pets. Doing so is straightforward using vanilla Persistent Volumes (which Pet Set already gives you), unless the volume mount point itself needs to be initialized for the Pet to start. This is exactly the case with "virtual machine" docker images, like those based on ubuntu or fedora. Such images embed the entire rootfs of the distro, including package managers like `apt-get` that assume a certain layout of the filesystem. Meaning:
 
 * If you mount an empty volume under `/usr`, you won't be able to `apt-get`
 * If you mount an empty volume under `/lib`, all your `apt-gets` will fail because there are no system libraries
@@ -130,7 +130,7 @@ Here's a tiny peer finder helper script that handles peer discovery, [available
 
 * A DNS domain
 * An `on-start` script to run with the initial constituency of the given domain as input
-* An `on-change` script to run everytime the constituency of the given domain changes
+* An `on-change` script to run every time the constituency of the given domain changes
 
 The role of the peer finder: