@@ -207,7 +207,7 @@ You'll need to get your SSH public key added to the machine. ~/.ssh/config info:
207207```
208208Host stackage-build
209209 User curators
210− Hostname ec2-52-5-20-252.compute-1.amazonaws.com
210+ Hostname build.stackage.org
211211```
212212
213213### Running the build script
@@ -279,15 +279,15 @@ Replace nightly with `lts7` to wipe the LTS 7 cache.
279279
280280## Local curator setup
281281
282−We don't run the full stackage build locally as that might take too
282+We do not run the full stackage build locally as that might take too
283283much time. Some steps on the other hand are much faster to do
284284yourself.
285285
286−It's useful to be able to modify constraints locally before pushing to
286+It is useful to be able to modify constraints locally before pushing to
287287the repository. To do this first install stackage-curator:
288288`git clone git@github.com:fpco/stackage-curator.git && cd stackage-curator && stack install`
289289or get the linux binary: https://s3.amazonaws.com/stackage-travis/stackage-curator/stackage-curator.bz2
290−(it's a good idea to upgrade stackage-curator at least at the start of your week as curator).
290+(it is a good idea to upgrade stackage-curator at least at the start of your week as curator).
291291Then clone the stackage repo `git clone git@github.com:fpco/stackage.git`.
292292Inside it run `stack update && stackage-curator check` to get new packages and do dependency resolution.
293293
@@ -295,5 +295,10 @@ This can be used to make sure all version bounds are in place
295295(including for test suites and benchmarks), to check whether bounds
296296can be lifted, and to get `tell-me-when-its-released` notifications.
297297
298−Notably this doesn't build anything, so you won't see any compilation
298+Notably this does not build anything, so you wont see any compilation
299299errors for builds/tests/benchmarks.
300+
301+## Adding new curators
302+
303+1. Add public ssh key to `~/.ssh/authorized_keys` on build server
304+2. Add to fpco/stackage project.