From 54ecd8a2a34fc51211037cf9292f70f4b1f96f76 Mon Sep 17 00:00:00 2001
From: simonmar <unknown>
Date: Thu, 18 Jan 2001 15:19:53 +0000
Subject: [PATCH] [project @ 2001-01-18 15:19:42 by simonmar] DocBook police

---
 ghc/docs/users_guide/glasgow_exts.sgml |   12 +++++-------
 ghc/docs/users_guide/utils.sgml        |    4 ++--
 2 files changed, 7 insertions(+), 9 deletions(-)

diff --git a/ghc/docs/users_guide/glasgow_exts.sgml b/ghc/docs/users_guide/glasgow_exts.sgml
index cbe282b..3e42fab 100644
--- a/ghc/docs/users_guide/glasgow_exts.sgml
+++ b/ghc/docs/users_guide/glasgow_exts.sgml
@@ -184,7 +184,7 @@ Only relevant if you also use <Option>-fglasgow-exts</Option>.
 <Term> <Option>-finline-phase</Option>:</Term>
 <ListItem>
 <Para> See <XRef LinkEnd="rewrite-rules">.
-Only relevant if you also use <Option>-fglasgow-exts</Option>.
+Only relevant if you also use <Option>-fglasgow-exts</Option>.</para>
 </ListItem> </VarListEntry>
 
 <VarListEntry>
@@ -196,6 +196,7 @@ Independent of <Option>-fglasgow-exts</Option>.
 </ListItem> </VarListEntry>
 
 </VariableList>
+  </sect1>
 
 <Sect1 id="primitives">
 <Title>Unboxed types and primitive operations
@@ -381,8 +382,8 @@ Note: we may relax some of these restrictions in the future.
 </Para>
 
 <Para>
-The <Literal>IO</Literal> and <Literal>ST</Literal> monads use unboxed tuples to avoid unnecessary
-allocation during sequences of operations.
+The <Literal>IO</Literal> and <Literal>ST</Literal> monads use unboxed
+tuples to avoid unnecessary allocation during sequences of operations.
 </Para>
 
 </Sect2>
@@ -390,16 +391,14 @@ allocation during sequences of operations.
 <Sect2>
 <Title>Character and numeric types</Title>
 
-<Para>
 <IndexTerm><Primary>character types, primitive</Primary></IndexTerm>
 <IndexTerm><Primary>numeric types, primitive</Primary></IndexTerm>
 <IndexTerm><Primary>integer types, primitive</Primary></IndexTerm>
 <IndexTerm><Primary>floating point types, primitive</Primary></IndexTerm>
+<Para>
 There are the following obvious primitive types:
 </Para>
 
-<Para>
-
 <ProgramListing>
 type Char#
 type Int#
@@ -419,7 +418,6 @@ type Word64#
 <IndexTerm><Primary><literal>Double&num;</literal></Primary></IndexTerm>
 <IndexTerm><Primary><literal>Int64&num;</literal></Primary></IndexTerm>
 <IndexTerm><Primary><literal>Word64&num;</literal></Primary></IndexTerm>
-</Para>
 
 <Para>
 If you really want to know their exact equivalents in C, see
diff --git a/ghc/docs/users_guide/utils.sgml b/ghc/docs/users_guide/utils.sgml
index fa4491d..ef81e66 100644
--- a/ghc/docs/users_guide/utils.sgml
+++ b/ghc/docs/users_guide/utils.sgml
@@ -396,7 +396,7 @@ tags:
 	    or be empty) applied to the appropriate integer value. You can
 	    have multiple <literal>#enum</literal> definitions with the same
 	    <literal>type</literal>; this construct does not emit the type
-	    definition itself.
+	    definition itself.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
@@ -425,7 +425,7 @@ tags:
       macro whose expansion uses other <literal>#let</literal> macros.
       Plain <literal>#let</literal> prepends <literal>hsc_</literal>
       to the macro name and wraps the defininition in a
-      <literal>printf</literal> call.
+      <literal>printf</literal> call.</para>
 
     </sect2>
 
-- 
1.7.10.4