Copy edits for typos (resubmitted)

docs/user-guide/compute-resources.md

@@ -196,7 +196,7 @@ TotalResourceLimits:
 [ ... lines removed for clarity ...]
 ```
 
-Here you can see from the `Allocated resorces` section that that a pod which ask for more than
+Here you can see from the `Allocated resources` section that that a pod which ask for more than
 90 millicpus or more than 1341MiB of memory will not be able to fit on this node.
 
 Looking at the `Pods` section, you can see which pods are taking up space on the node.

docs/user-guide/deploying-applications.md

@@ -53,7 +53,7 @@ Kubernetes creates and manages sets of replicated containers (actually, replicat
 
 A replication controller simply ensures that a specified number of pod "replicas" are running at any one time. If there are too many, it will kill some. If there are too few, it will start more. It’s analogous to Google Compute Engine’s [Instance Group Manager](https://cloud.google.com/compute/docs/instance-groups/manager/) or AWS’s [Auto-scaling Group](http://docs.aws.amazon.com/AutoScaling/latest/DeveloperGuide/AutoScalingGroup.html) (with no scaling policies).
 
-The replication controller created to run nginx by `kubctl run` in the [Quick start](quick-start.md) could be specified using YAML as follows:
+The replication controller created to run nginx by `kubectl run` in the [Quick start](quick-start.md) could be specified using YAML as follows:
 
 ```yaml
 apiVersion: v1

docs/user-guide/environment-guide/README.md

@@ -81,7 +81,7 @@ Pod Name: show-rc-xxu6i
 Pod Namespace: default
 USER_VAR: important information
 
-Kubenertes environment variables
+Kubernetes environment variables
 BACKEND_SRV_SERVICE_HOST = 10.147.252.185
 BACKEND_SRV_SERVICE_PORT = 5000
 KUBERNETES_RO_SERVICE_HOST = 10.147.240.1
@@ -99,7 +99,7 @@ Backend Namespace: default
 ```
 
 First the frontend pod's information is printed. The pod name and
-[namespace](../../../docs/design/namespaces.md) are retreived from the
+[namespace](../../../docs/design/namespaces.md) are retrieved from the
 [Downward API](../../../docs/user-guide/downward-api.md). Next, `USER_VAR` is the name of
 an environment variable set in the [pod
 definition](show-rc.yaml). Then, the dynamic Kubernetes environment

docs/user-guide/environment-guide/containers/show/show.go

@@ -70,7 +70,7 @@ func printInfo(resp http.ResponseWriter, req *http.Request) {
 	envvar := os.Getenv("USER_VAR")
 	fmt.Fprintf(resp, "USER_VAR: %v \n", envvar)
 
-	fmt.Fprintf(resp, "\nKubenertes environment variables\n")
+	fmt.Fprintf(resp, "\nKubernetes environment variables\n")
 	var keys []string
 	for key := range kubeVars {
 		keys = append(keys, key)

docs/user-guide/secrets.md

@@ -73,7 +73,7 @@ more control over how it is used, and reduces the risk of accidental exposure.
 Users can create secrets, and the system also creates some secrets.
 
 To use a secret, a pod needs to reference the secret.
-A secret can be used with a pod in two ways: eithe as files in a [volume](volumes.md) mounted on one or more of
+A secret can be used with a pod in two ways: either as files in a [volume](volumes.md) mounted on one or more of
 its containers, or used by kubelet when pulling images for the pod.
 
 ### Service Accounts Automatically Create and Attach Secrets with API Credentials

docs/user-guide/services.md

@@ -368,7 +368,7 @@ address, other services should be visible only from inside of the cluster.
 Kubernetes `ServiceTypes` allow you to specify what kind of service you want.
 The default and base type is `ClusterIP`, which exposes a service to connection
 from inside the cluster. `NodePort` and `LoadBalancer` are two types that expose
-services to external trafic.
+services to external traffic.
 
 Valid values for the `ServiceType` field are: