summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Fischer <daniel.is.fischer@googlemail.com>2011-05-30 11:16:15 +0200
committerSimon Marlow <marlowsd@gmail.com>2011-05-31 10:52:57 +0100
commit1c5e89eda88dc79061ec885ccf21eed55c7d7440 (patch)
tree8f6275222d9cefe97bd3a8ff5b84808536cdcb9d
parentcffe2f0044d1c0d209435eb17c8190dbe31fd96c (diff)
downloadhaskell-1c5e89eda88dc79061ec885ccf21eed55c7d7440.tar.gz
glasgow_exts.xml whitespace
-rw-r--r--docs/users_guide/glasgow_exts.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/users_guide/glasgow_exts.xml b/docs/users_guide/glasgow_exts.xml
index 2490855393..f44bf7968a 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"/>);