docs: fix typos

Author: tbroadley

ChangeLog.md

@@ -62,7 +62,7 @@ Behavior changes:
 * The `package-indices` setting with Hackage no longer works with the
   `00-index.tar.gz` tarball, but must use the `01-index.tar.gz` file
   to allow revised packages to be found.
-* Options passsed via `--ghci-options` are now passed to the end of the
+* Options passed via `--ghci-options` are now passed to the end of the
   invocation of ghci, instead of the middle.  This allows using `+RTS`
   without an accompanying `-RTS`.
 * When auto-detecting `--ghc-build`, `tinfo6` is now preferred over
@@ -153,7 +153,7 @@ Other enhancements:
 * Stack will now try to detect the width of the running terminal
   (only on POSIX for the moment) and use that to better display
   output messages. Work is ongoing, so some messages will not
-  be optimal yet. The terminal width can be overriden with the
+  be optimal yet. The terminal width can be overridden with the
   new `--terminal-width` command-line option (this works even on
   non-POSIX).
 * Passing non local packages as targets to `stack ghci` will now
@@ -427,7 +427,7 @@ Other enhancements:
 * The script interpreter will now output error logging.  In particular,
   this means it will output info about plan construction errors.
   ([#2879](https://github.com/commercialhaskell/stack/issues/2879))
-* `stack ghci` now takes `--flag` and `--ghc-options` again (inadverently
+* `stack ghci` now takes `--flag` and `--ghc-options` again (inadvertently
   removed in 1.3.0).
   ([#2986](https://github.com/commercialhaskell/stack/issues/2986))
 * `stack exec` now takes `--rts-options` which passes the given arguments inside of
@@ -699,7 +699,7 @@ Other enhancements:
 * Parse CLI arguments and configuration files into less permissive types,
   improving error messages for bad inputs.
   [#2267](https://github.com/commercialhaskell/stack/issues/2267)
-* Add the ability to explictly specify a gcc executable.
+* Add the ability to explicitly specify a gcc executable.
   [#593](https://github.com/commercialhaskell/stack/issues/593)
 * Nix: No longer uses LTS mirroring in nixpkgs. Gives to nix-shell a derivation
   like `haskell.compiler.ghc801`
@@ -1106,7 +1106,7 @@ Other enhancements:
   [docs](http://docs.haskellstack.org/en/stable/yaml_configuration/#image)
 - Specify which executables to include in images for `stack image container`
   [docs](http://docs.haskellstack.org/en/stable/yaml_configuration/#image)
-- Docker: pass supplemantary groups and umask into container
+- Docker: pass supplementary groups and umask into container
 - If git fetch fails wipe the directory and try again from scratch
   [#1418](https://github.com/commercialhaskell/stack/issues/1418)
 - Warn if newly installed executables won't be available on the PATH
@@ -1165,7 +1165,7 @@ Enhancements:
   profiling, but instead of generating a report for `--bench` and
   `--test`, prints out a stack trace on exception. Great for using
   like `stack build --test --trace`
-* Nix: all options can be overriden on command line
+* Nix: all options can be overridden on command line
   [#1483](https://github.com/commercialhaskell/stack/issues/1483)
 * Nix: build environments (shells) are now pure by default.
 * Make verbosity silent by default in script interpreter mode
@@ -1278,7 +1278,7 @@ Bug fixes:
   [#1401](https://github.com/commercialhaskell/stack/issues/1401)
 * GHCi: cpp-options in cabal files weren't used
   [#1419](https://github.com/commercialhaskell/stack/issues/1419)
-* Benchmarks couldn't be run independently of eachother
+* Benchmarks couldn't be run independently of each other
   [#1412](https://github.com/commercialhaskell/stack/issues/1412)
 * Send output of building setup to stderr
   [#1410](https://github.com/commercialhaskell/stack/issues/1410)
@@ -1465,7 +1465,7 @@ Other enhancements:
 
 * Added the `--docker-env` argument, to set environment variables in Docker container.
 * Set locale environment variables to UTF-8 encoding for builds to avoid "commitBuffer: invalid argument" errors from GHC [#793](https://github.com/commercialhaskell/stack/issues/793)
-* Enable translitation for encoding on stdout and stderr [#824](https://github.com/commercialhaskell/stack/issues/824)
+* Enable transliteration for encoding on stdout and stderr [#824](https://github.com/commercialhaskell/stack/issues/824)
 * By default, `stack upgrade` automatically installs GHC as necessary [#797](https://github.com/commercialhaskell/stack/issues/797)
 * Added the `ghc-options` field to stack.yaml [#796](https://github.com/commercialhaskell/stack/issues/796)
 * Added the `extra-path` field to stack.yaml

doc/MAINTAINER_GUIDE.md

@@ -90,7 +90,7 @@ consistent and clean stack version.
 
 * Create a
   [new draft Github release](https://github.com/commercialhaskell/stack/releases/new)
-  with tag and name `vX.Y.Z` (where X.Y.Z is the stack package's version), targetting the
+  with tag and name `vX.Y.Z` (where X.Y.Z is the stack package's version), targeting the
   RC branch
 
 * On each machine you'll be releasing from, set environment variables:
@@ -295,7 +295,7 @@ the shell.
 
 ### Install clang+llvm
 
-NOTE: the Debian jessie `llvm` packge does not work (executables built with it
+NOTE: the Debian jessie `llvm` package does not work (executables built with it
 just exit with "schedule: re-entered unsafely.").
 
 The version of LLVM needed depends on the version of GHC you need.

doc/faq.md

@@ -393,7 +393,7 @@ If you are using a powershell session, it is easy to automate even that step:
 
     $env:Path = ( stack setup | %{ $_ -replace '[^ ]+ ', ''} ), $env:Path -join ";"
 
-## How do I reset / remove Stack (such as to to do a completely fresh build)?
+## How do I reset / remove Stack (such as to do a completely fresh build)?
 
 The first thing to remove is project-specific `.stack-work` directory within
 the project's directory. Next, remove `~/.stack` directory overall. You may

doc/ghcjs.md

@@ -12,7 +12,7 @@ You can also build existing stack projects which target GHC, and instead build
 them with GHCJS.  For example: `stack build --compiler ghcjs-0.2.0.9006020_ghc-7.10.3`
 
 There are advanced options for `stack setup`: `--ghcjs-boot-options` (one word at a time) and `--[no-]ghcjs-boot-clean`
-which will passyour settings down to the `ghcjs-boot`. You will need to know exacty what you are doing with them.  
+which will pass your settings down to the `ghcjs-boot`. You will need to know exactly what you are doing with them.  
 
 Sidenote: If you receive a message like
 `The program 'ghcjs' version >=0.1 is required but the version of .../ghcjs could not be determined.`,
@@ -56,9 +56,9 @@ setup-info:
            sha1: d2cfc25f9cda32a25a87d9af68891b2186ee52f9
 ```
 The later can be generated via: https://github.com/tolysz/prepare-ghcjs
-the fromer is a bit more manual. Those bundles are only tested against the latest `node-7.4.0`.
+the former is a bit more manual. Those bundles are only tested against the latest `node-7.4.0`.
 
-In order to corrrectly boot and use ghcjs, one might need to install `alex` `happy` `hscolour` `hsc2hs` with the normal ghc.
+In order to correctly boot and use ghcjs, one might need to install `alex` `happy` `hscolour` `hsc2hs` with the normal ghc.
 
 Older resolvers:
 

doc/nix_integration.md

@@ -35,7 +35,7 @@ etc) should be available.  If they are not, it should be because the file
 located at `$HOME/.nix-profile/etc/profile.d/nix.sh` is not sourced by your shell.
 
 You should either run `source ~/.nix-profile/etc/profile.d/nix.sh` manually
-everytime you open a terminal and need Nix or add this command to your
+every time you open a terminal and need Nix or add this command to your
 `~/.bashrc` or `~/.bash_profile`.
 
 ### Additions to your `stack.yaml`

doc/yaml_configuration.md

@@ -537,7 +537,7 @@ automatically promote it to a local package (much like setting a
 custom package flag). However, setting options via `$everything` on all flags
 will not do so (see
 [Github discussion](https://github.com/commercialhaskell/stack/issues/849#issuecomment-320892095)
-for reasoning). This can lead to unpredicable behavior by affecting
+for reasoning). This can lead to unpredictable behavior by affecting
 your snapshot packages.
 
 The behavior of the `$locals`, `$targets`, and `$everything` special