@@ -41,7 +41,7 @@ it every time.
4141### package sets
4242
4343We often rely on either package sets as provided by stackage or
44−computed by cabal. `nixpkgs` provides it's own curated package set
44+computed by cabal. `nixpkgs` provides its own curated package set
4545which might or might not work for the projects we work on.
4646`stack2nix` tries to solve this issue, here we go one step further and
4747provide the infrastructure to allow any form of package set.
@@ -62,13 +62,13 @@ occur if you have mutually dependent components.
6262
6363### build times
6464
65−The Haskell builder in nixpkgs build package sequentially, first the
66−library than the executables and finally the tests. It then executes
65+The Haskell builder in nixpkgs builds a package sequentially, first the
66+library then the executables and finally the tests. It then executes
6767the tests before the package is considered done. The upshot of this
6868is that packages are only considered done if the test-suites
6969passed. The downside is that if you have to compile multiple packages
7070the likelihood of them failing is low, you have unnecessarily
71−serialized you build. In a more aggressive setting libraries could
71+serialized your build. In a more aggressive setting libraries could
7272start building as early as their dependent libraries are built. Of
7373course they will have to be invalidated later should the test-suites
7474of their dependencies fail, but this way we can make use of parallel