building/running-tests.md

@@ -14,21 +14,10 @@ GHC includes a comprehensive testsuite for catching any regressions.
 ## Using the Testsuite as a user
 
 
-If you just want to run the whole testsuite, then in the root of the GHC tree, typing:
-
-```wiki
-$ make fasttest # (GHC <= 7.10: make test)
-```
-
-
-will do a run in "fast" mode (which gives an idea whether there are major problems). On the other hand, typing:
-
-```wiki
-$ make fulltest
-```
+In the root directory of the ghc repository or source distribution, run either `make fasttest`, `make test` (which uses the normal speed settings) or `make slowtest` (called `fulltest` for GHC \<= 7.10).
 
 
-will do a full testsuite run (more thorough, but takes a lot longer). You should expect that there are no test case failures for the "fast" mode as that is a quality level that all GHC developers are expected to maintain when they check in code. There will usually be some test case failures for the full testsuite run though.
+You should expect that there are no test case failures for the "normal" mode as that is a quality level that all GHC developers are expected to maintain when they check in code. There will usually be some test case failures for the full testsuite run though, and it takes a lot longer to run.
 
 
 The run time of the testsuite can be reduced by running it with multiple threads. For instance if your machine has 8 cores, the following is probably appropriate: