[commit: hadrian] master: Update README.md (#578) (64da39c)

[git at git.haskell.org]

Repository : ssh://git@git.haskell.org/hadrian

On branch  : master
Link       : http://git.haskell.org/hadrian.git/commitdiff/64da39cc9f955d7c1492ab39927a8e0849b23f00

>---------------------------------------------------------------

commit 64da39cc9f955d7c1492ab39927a8e0849b23f00
Author: Alp Mestanogullari <alpmestan at gmail.com>
Date:   Mon Apr 23 14:21:55 2018 +0200

    Update README.md (#578)
    
    I noticed that one sentence from the README is out of date, so here's a tentative wording that reflects the current state of things.


>---------------------------------------------------------------

64da39cc9f955d7c1492ab39927a8e0849b23f00
 README.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 2509dae..5da7990 100644
--- a/README.md
+++ b/README.md
@@ -10,9 +10,10 @@ project and the architecture of the build system you can find more details in
 this [Haskell Symposium 2016 paper](https://dl.acm.org/authorize?N41275) and this
 [Haskell eXchange 2016 talk][talk].
 
-The new build system can work side-by-side with the existing build system. Note, there is
-some interaction between them: they put (some) build results in the same directories,
-e.g. the resulting GHC is `inplace/bin/ghc-stage2`.
+The new build system can work side-by-side with the existing build system, since it
+places all build artefacts under a dedicated directory. The only thing they both share
+is the need to run the `./boot` and `./configure` scripts, even though Hadrian can do it
+for you (see the documentation for the `-c` flag below).
 
 Your first build
 ----------------