X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fglasgow_exts.xml;h=e1795f2b28e159f308dbbc108ee85afd4c4b1f68;hb=67d845652defc09807eaf134c6d30c8bd26b665a;hp=2490855393030fb4540b5dfa24052296cc2fc795;hpb=9c2dfd97d008c04c2f86a4a58fa7c3c956f7bedc;p=ghc-hetmet.git

diff --git a/docs/users_guide/glasgow_exts.xml b/docs/users_guide/glasgow_exts.xml
index 2490855..e1795f2 100644
--- a/docs/users_guide/glasgow_exts.xml
+++ b/docs/users_guide/glasgow_exts.xml
@@ -427,7 +427,7 @@ Indeed, the bindings can even be recursive.
 
       <para>The hash sign does not change semantics at all.  We tend to use variable
 	names ending in "&num;" for unboxed values or types (e.g. <literal>Int&num;</literal>),
-	but there is no requirement to do so; they are just plain ordinary variables.
+        but there is no requirement to do so; they are just plain ordinary variables.
 	Nor does the <option>-XMagicHash</option> extension bring anything into scope.
 	For example, to bring <literal>Int&num;</literal> into scope you must
 	import <literal>GHC.Prim</literal> (see <xref linkend="primitives"/>);
@@ -2799,7 +2799,7 @@ different constructors.  For example, this is fine:
     T1 :: Eq b => b -> b -> T b
     T2 :: (Show c, Ix c) => c -> [c] -> T c
 </programlisting>
-When patten matching, these constraints are made available to discharge constraints
+When pattern matching, these constraints are made available to discharge constraints
 in the body of the match. For example:
 <programlisting>
   f :: T a -> String
@@ -4031,7 +4031,7 @@ But these are not:
 <programlisting>
       -- Context assertion no smaller than head
   instance C a => C a where ...
-      -- (C b b) has more more occurrences of b than the head
+      -- (C b b) has more occurrences of b than the head
   instance C b b => Foo [b] where ...
 </programlisting>
 </para>
@@ -6464,7 +6464,7 @@ Wiki page</ulink>.
                     must have type <literal>Q [Dec]</literal></para></listitem>
 		    </itemizedlist>
             Note that pattern splices are not supported.
-	    Inside a splice you can can only call functions defined in imported modules,
+            Inside a splice you can only call functions defined in imported modules,
 	    not functions defined elsewhere in the same module.</para></listitem>
 
 	      <listitem><para>
@@ -7518,7 +7518,7 @@ That leaves let expressions, whose translation is given in
 of the Haskell Report.
 In the translation box, first apply
 the following transformation:  for each pattern <literal>pi</literal> that is of
-form <literal>!qi = ei</literal>, transform it to <literal>(xi,!qi) = ((),ei)</literal>, and and replace <literal>e0</literal>
+form <literal>!qi = ei</literal>, transform it to <literal>(xi,!qi) = ((),ei)</literal>, and replace <literal>e0</literal>
 by <literal>(xi `seq` e0)</literal>.  Then, when none of the left-hand-side patterns
 have a bang at the top, apply the rules in the existing box.
 </para>