X-Git-Url: http://git.megacz.com/?p=ghc-hetmet.git;a=blobdiff_plain;f=docs%2Fusers_guide%2Fusing.xml;h=eb032df28336bcf7b1d3498fc357cd810ed3ecda;hp=a44ddfc2f31968e9bd8d359e0a7da531f8c999a3;hb=194e778d542875df662986c48a0e8832be880247;hpb=637457650520c7021c5859e9663458ec8d8e1e1c
diff --git a/docs/users_guide/using.xml b/docs/users_guide/using.xml
index a44ddfc..eb032df 100644
--- a/docs/users_guide/using.xml
+++ b/docs/users_guide/using.xml
@@ -379,9 +379,9 @@ module X where
interfaces, and include files (usually something like
/usr/local/lib/ghc-5.04 on Unix). This
is the value of
- $libdirlibdir
- in the package configuration file (see ).
+ $libdirlibdir
+ in the package configuration file
+ (see ).
@@ -394,7 +394,7 @@ module X where
When given the option,
GHC will build a multi-module Haskell program by following
- dependencies from a single root module (usually
+ dependencies from one or more root modules (usually just
Main). For example, if your
Main module is in a file called
Main.hs, you could compile and link the
@@ -408,7 +408,7 @@ ghc ––make Main.hs
names or module names; GHC will figure out all the modules in
the program by following the imports from these initial modules.
It will then attempt to compile each module which is out of
- date, and finally if there is a Main module,
+ date, and finally, if there is a Main module,
the program will also be linked into an executable.The main advantages to using ghc
@@ -503,7 +503,7 @@ olleh
The first phase to run is determined by each input-file
suffix, and the last phase is determined by a flag. If no
- relevant flag is present, then go all the way through linking.
+ relevant flag is present, then go all the way through to linking.
This table summarises: