[project @ 2001-08-27 11:45:23 by simonmar]

[ghc-hetmet.git] / ghc / docs / users_guide / sooner.sgml

diff --git a/ghc/docs/users_guide/sooner.sgml b/ghc/docs/users_guide/sooner.sgml
index 75508a5..76682d5 100644 (file)
--- a/ghc/docs/users_guide/sooner.sgml
+++ b/ghc/docs/users_guide/sooner.sgml
@@ -128,7 +128,7 @@ individually with <Option>-fno-strictness</Option>.
 
 <Para>
 To figure out which part of the compiler is badly behaved, the
-<Option>-v2</Option><IndexTerm><option>-v</option></primary>
+<option>-v2</option><indexterm><primary><option>-v</option></primary>
 </indexterm> option is your friend.
 </Para>
 
@@ -460,7 +460,7 @@ to compete with it, but link with it.
 </Para>
 
 <Para>
-<XRef LinkEnd="sec-ffi"> describes the foreign calling interface.
+<XRef LinkEnd="ffi"> describes the foreign function interface.
 </Para>
 </ListItem>
 </VarListEntry>
@@ -520,7 +520,7 @@ Decrease the &ldquo;go-for-it&rdquo; threshold for unfolding smallish
 expressions.  Give a
 <Option>-funfolding-use-threshold0</Option><IndexTerm><Primary>-funfolding-use-threshold0
 option</Primary></IndexTerm> option for the extreme case. (&ldquo;Only unfoldings with
-zero cost should proceed.&rdquo;)  Warning: except in certain specialiised
+zero cost should proceed.&rdquo;)  Warning: except in certain specialised
 cases (like Happy parsers) this is likely to actually
 <Emphasis>increase</Emphasis> the size of your program, because unfolding
 generally enables extra simplifying optimisations to be performed.