Truncate docs to 80 chars and add localhost to spelling wordlist

Author: Luke Addison

docs/spelling_wordlist.txt

@@ -73,3 +73,4 @@ offline
 admin
 plugin
 checklist
+localhost

docs/user-guide.rst

@@ -153,7 +153,10 @@ The Pod Security Policy manifests can be found within the tarmak directory at
 Cluster Autoscaler
 ~~~~~~~~~~~~~~~~~~
 
-Tarmak supports deploying `Cluster Autoscaler <https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler>`_ when spinning up a Kubernetes cluster. The following `tarmak.yaml` snippet shows how you would enable Cluster Autoscaler. 
+Tarmak supports deploying `Cluster Autoscaler
+<https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler>`_ when
+spinning up a Kubernetes cluster. The following `tarmak.yaml` snippet shows how
+you would enable Cluster Autoscaler. 
 
 .. code-block:: yaml
 
@@ -162,14 +165,24 @@ Tarmak supports deploying `Cluster Autoscaler <https://github.com/kubernetes/aut
         enabled: true
     ...
 
-The above configuration would deploy Cluster Autoscaler with an image of `gcr.io/google_containers/cluster-autoscaler` using the recommend version based on the version of your Kubernetes cluster. The configuration block accepts two optional fields of `image` and `version` allowing you to change these defaults. Note that the final image tag used when deploying Cluster Autoscaler will be the configured version prepended with the letter `v`.
+The above configuration would deploy Cluster Autoscaler with an image of
+`gcr.io/google_containers/cluster-autoscaler` using the recommend version based
+on the version of your Kubernetes cluster. The configuration block accepts two
+optional fields of `image` and `version` allowing you to change these defaults.
+Note that the final image tag used when deploying Cluster Autoscaler will be the
+configured version prepended with the letter `v`.
 
-The current implementation will configure the first instance pool of type worker in your cluster configuration to scale between `minCount` and `maxCount`. We plan to add support for an arbitrary number of worker instance pools.
+The current implementation will configure the first instance pool of type worker
+in your cluster configuration to scale between `minCount` and `maxCount`. We
+plan to add support for an arbitrary number of worker instance pools.
 
 Dashboard
 ~~~~~~~~~
 
-Tarmak supports deploying `Kubernetes Dashboard <https://github.com/kubernetes/dashboard>`_ when spinning up a Kubernetes cluster. The following `tarmak.yaml` snippet shows how you would enable Kubernetes Dashboard. 
+Tarmak supports deploying `Kubernetes Dashboard
+<https://github.com/kubernetes/dashboard>`_ when spinning up a Kubernetes
+cluster. The following `tarmak.yaml` snippet shows how you would enable
+Kubernetes Dashboard. 
 
 .. code-block:: yaml
 
@@ -178,12 +191,21 @@ Tarmak supports deploying `Kubernetes Dashboard <https://github.com/kubernetes/d
         enabled: true
     ...
 
-The above configuration would deploy Kubernetes Dashboard with an image of `gcr.io/google_containers/kubernetes-dashboard-amd64` with a fixed tag. The configuration block accepts two optional fields of `image` and `version` allowing you to change these defaults. The `version` field directly translates to the image tag used.
+The above configuration would deploy Kubernetes Dashboard with an image of
+`gcr.io/google_containers/kubernetes-dashboard-amd64` with a fixed tag. The
+configuration block accepts two optional fields of `image` and `version`
+allowing you to change these defaults. The `version` field directly translates
+to the image tag used.
 
 Tiller
 ~~~~~~
 
-Tarmak supports deploying Tiller, the server-side component of `Helm <https://github.com/kubernetes/helm>`_, when spinning up a Kubernetes cluster. Tiller is configured to listen on localhost only which prevents arbitrary Pods in the cluster connecting to its unauthenticated endpoint. Helm clients can still talk to Tiller by port forwarding through the Kubernetes API Server. The following `tarmak.yaml` snippet shows how you would enable Tiller.
+Tarmak supports deploying Tiller, the server-side component of `Helm
+<https://github.com/kubernetes/helm>`_, when spinning up a Kubernetes cluster.
+Tiller is configured to listen on localhost only which prevents arbitrary Pods
+in the cluster connecting to its unauthenticated endpoint. Helm clients can
+still talk to Tiller by port forwarding through the Kubernetes API Server. The
+following `tarmak.yaml` snippet shows how you would enable Tiller.
 
 .. code-block:: yaml
 
@@ -192,7 +214,12 @@ Tarmak supports deploying Tiller, the server-side component of `Helm <https://gi
         enabled: true
     ...
 
-The above configuration would deploy Tiller with an image of `gcr.io/kubernetes-helm/tiller` with a fixed tag. The configuration block accepts two optional fields of `image` and `version` allowing you to change these defaults. The `version` field directly translates to the image tag used. The version is particularly important when deploying Tiller since its minor version must match the minor version of any Helm clients.
+The above configuration would deploy Tiller with an image of
+`gcr.io/kubernetes-helm/tiller` with a fixed tag. The configuration block
+accepts two optional fields of `image` and `version` allowing you to change
+these defaults. The `version` field directly translates to the image tag used.
+The version is particularly important when deploying Tiller since its minor
+version must match the minor version of any Helm clients.
 
 .. warning::
    Tiller is deployed with full ``cluster-admin`` ClusterRole bound to its