Fix typos and linted_packages sorting

Author: koep

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing guidelines
 
-Want to hack on kubernetes? Yay!
+Want to hack on Kubernetes? Yay!
 
 ## Developer Guide
 

build-tools/README.md

@@ -45,20 +45,20 @@ All Docker names are suffixed with a hash derived from the file path (to allow c
 
 ## Proxy Settings
 
-If you are behind a proxy and you are letting these scripts use `docker-machine` to set up your local VM for you on macOS, you need to export proxy settings for kubernetes build, the following environment variables should be defined.
+If you are behind a proxy and you are letting these scripts use `docker-machine` to set up your local VM for you on macOS, you need to export proxy settings for Kubernetes build, the following environment variables should be defined.
 
 ```
 export KUBERNETES_HTTP_PROXY=http://username:password@proxyaddr:proxyport
 export KUBERNETES_HTTPS_PROXY=https://username:password@proxyaddr:proxyport
 ```
 
-Optionally, you can specify addresses of no proxy for kubernetes build, for example
+Optionally, you can specify addresses of no proxy for Kubernetes build, for example
 
 ```
 export KUBERNETES_NO_PROXY=127.0.0.1
 ```
 
-If you are using sudo to make kubernetes build for example make quick-release, you need run `sudo -E make quick-release` to pass the environment variables.
+If you are using sudo to make Kubernetes build for example make quick-release, you need run `sudo -E make quick-release` to pass the environment variables.
 
 ## Really Remote Docker Engine
 

cluster/README.md

@@ -1,6 +1,6 @@
 # Cluster Configuration
 
-##### Deprecation Notice: This directory has entered maintainence mode and will not be accepting new providers. Please submit new automation deployments to [kube-deploy](https://github.com/kubernetes/kube-deploy). Deployments in this directory will continue to be maintained and supported at their current level of support.
+##### Deprecation Notice: This directory has entered maintenance mode and will not be accepting new providers. Please submit new automation deployments to [kube-deploy](https://github.com/kubernetes/kube-deploy). Deployments in this directory will continue to be maintained and supported at their current level of support.
 
 The scripts and data in this directory automate creation and configuration of a Kubernetes cluster, including networking, DNS, nodes, and master components.
 

cluster/addons/python-image/README.md

@@ -1,6 +1,6 @@
 # Python image
 
 The python image here is used by OS distros that don't have python installed to
-run python scripts to parse the yaml files in the addon updator script.
+run python scripts to parse the yaml files in the addon updater script.
 
 [![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/cluster/addons/python-image/README.md?pixel)]()

cluster/addons/registry/README.md

@@ -91,7 +91,7 @@ spec:
 This tells Kubernetes that you want to use storage, and the `PersistentVolume`
 you created before will be bound to this claim (unless you have other
 `PersistentVolumes` in which case those might get bound instead).  This claim
-gives you the rigth to use this storage until you release the claim.
+gives you the right to use this storage until you release the claim.
 
 ## Run the registry
 

cluster/juju/bundles/README.md

@@ -24,7 +24,7 @@ deploy a bundle.
 
 You will need to
 [install the Juju client](https://jujucharms.com/get-started) and
-`juju-quickstart` as pre-requisites.  To deploy the bundle use
+`juju-quickstart` as prerequisites.  To deploy the bundle use
 `juju-quickstart` which runs on Mac OS (`brew install
 juju-quickstart`) or Ubuntu (`apt-get install juju-quickstart`).
 
@@ -191,7 +191,7 @@ Send us pull requests!  We'll send you a cookie if they include tests and docs.
 The charms and bundles are in the [kubernetes](https://github.com/kubernetes/kubernetes)
 repository in github.
 
- - [kubernetes-master charm on Github](https://github.com/kubernetes/kubernetes/tree/master/cluster/juju/charms/trusty/kubernetes-master)
+ - [kubernetes-master charm on GitHub](https://github.com/kubernetes/kubernetes/tree/master/cluster/juju/charms/trusty/kubernetes-master)
  - [kubernetes charm on GitHub](https://github.com/kubernetes/kubernetes/tree/master/cluster/juju/charms/trusty/kubernetes)
 
 

cmd/mungedocs/README.md

@@ -6,7 +6,7 @@ It basically does the following:
 - iterate over all files in the given doc root.
 - for each file split it into a slice (mungeLines) of lines (mungeLine)
 - a mungeline has metadata about each line typically determined by a 'fast' regex.
-  - metadata contains things like 'is inside a preformmatted block'
+  - metadata contains things like 'is inside a preformatted block'
   - contains a markdown header
   - has a link to another file
   - etc..

docs/proposals/apparmor.md

@@ -113,7 +113,7 @@ Ubuntu system. The profiles can be found at `{securityfs}/apparmor/profiles`
 
 ## API Changes
 
-The intial alpha support of AppArmor will follow the pattern
+The initial alpha support of AppArmor will follow the pattern
 [used by seccomp](https://github.com/kubernetes/kubernetes/pull/25324) and specify profiles through
 annotations. Profiles can be specified per-container through pod annotations. The annotation format
 is a key matching the container, and a profile name value:

docs/proposals/cluster-deployment.md

@@ -56,7 +56,7 @@ ship with all of the requirements for the node specification by default.
 
 **Objective**: Generate security certificates used to configure secure communication between client, master and nodes
 
-TODO: Enumerate ceritificates which have to be generated.
+TODO: Enumerate certificates which have to be generated.
 
 ## Step 3: Deploy master
 

docs/proposals/container-runtime-interface-v1.md

@@ -245,7 +245,7 @@ discussion and may be achieved alternatively:
 **Imperative pod-level interface**
 The interface contains only CreatePod(), StartPod(), StopPod() and RemovePod().
 This implies that the runtime needs to take over container lifecycle
-manangement (i.e., enforce restart policy), lifecycle hooks, liveness checks,
+management (i.e., enforce restart policy), lifecycle hooks, liveness checks,
 etc. Kubelet will mainly be responsible for interfacing with the apiserver, and
 can potentially become a very thin daemon.
  - Pros: Lower maintenance overhead for the Kubernetes maintainers if `Docker`