Merge pull request #1637 from lubomir/fix-typos

Fix typos in documentation

Author: mgsloan

doc/MAINTAINER_GUIDE.md

@@ -28,7 +28,7 @@ to go:
           due to merges
 * In master branch:
     * Bump version to next odd second-to-last component
-    * Add new "unreleased changes" secion in changelog
+    * Add new "unreleased changes" section in changelog
     * Bump to use latest LTS version
 * Review documentation for any changes that need to be made
     * Search for old Stack version, unstable stack version, and the next

doc/docker_integration.md

@@ -116,7 +116,7 @@ otherwise noted.
       # the case.
       enable: true
 
-      # The name of the repository to pull the image from.  See the "reposities"
+      # The name of the repository to pull the image from.  See the "repositories"
       # section of this document for more information about available repositories.
       # If this includes a tag (e.g. "my/image:tag"), that tagged image will be
       # used.  Without a tag specified, the LTS version slug is added automatically.
@@ -271,7 +271,7 @@ user. For example (from
     # Restart the Docker daemon.
     sudo service docker restart
 
-You will now need to log out and log in again for the the group addition
+You will now need to log out and log in again for the group addition
 to take effect.
 
 Note the above has security implications.  See [security](#security) for more.
@@ -281,7 +281,7 @@ Security
 
 Having `docker` usable as a non-root user is always a security risk, and will
 allow root access to your system. It is also possible to craft a `stack.yaml`
-that will run arbitrary commands in an arbirary docker container through that
+that will run arbitrary commands in an arbitrary docker container through that
 vector, thus a `stack.yaml` could cause stack to run arbitrary commands as root.
 While this is a risk, it is not really a greater risk than is posed by the
 docker permissions in the first place (for example, if you ever run an unknown
@@ -325,7 +325,7 @@ by default, meaning a process running in the container can connect to
 services running on the host, and a server process run within the container
 can be accessed from the host without needing to explicitly publish its port.
 To run the container with an isolated network, use `--docker-run-args` to pass
-a the `--net` argument to `docker-run`.  For example:
+the `--net` argument to `docker-run`.  For example:
 
     stack --docker-run-args='--net=bridge --publish=3000:3000' \
           exec some-server

doc/nix_integration.md

@@ -145,7 +145,7 @@ in your `stack.yaml` will do the same.
 
 ## Command-line options
 
-The configuration present in your `stack.yaml` can be overriden on the
+The configuration present in your `stack.yaml` can be overridden on the
 command-line. See `stack --nix-help` for a list of all Nix options.
 
 ## Configuration

doc/travis_ci.md

@@ -80,7 +80,7 @@ addons:
 
 Travis apt plugin doesn't yet support installing apt packages dynamically
 (https://github.com/travis-ci/travis-ci/issues/4291). That for we need to write
-a bit repetetive `.travis.yml`.
+a bit repetitive `.travis.yml`.
 
 Also for different GHC versions, you probably want to use different `stack.yaml`
 files.