From 24e4b6edc7e8fd2b9db6c8ba7362b982bc8cf156 Mon Sep 17 00:00:00 2001
From: erkok <unknown>
Date: Tue, 1 Oct 2002 17:48:37 +0000
Subject: [PATCH] [project @ 2002-10-01 17:48:37 by erkok] wibbles on
 mdo-documentation

---
 ghc/docs/users_guide/glasgow_exts.sgml |    7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/ghc/docs/users_guide/glasgow_exts.sgml b/ghc/docs/users_guide/glasgow_exts.sgml
index d4a39be..499d982 100644
--- a/ghc/docs/users_guide/glasgow_exts.sgml
+++ b/ghc/docs/users_guide/glasgow_exts.sgml
@@ -2671,8 +2671,8 @@ then that monad must be declared an instance of the <literal>MonadFix</literal>
 For details, see the above mentioned reference.
 </para>
 <para>
-The <literal>MonadFix</literal> library automatically declares List, Maybe, IO, and
-state monads (both lazy and strict) as instances of the <literal>MonadFix</literal> class.
+The following instances of <literal>MonadFix</literal> is automatically provided: List, Maybe, IO, and
+state monads (both lazy and strict).
 </para>
 <para>
 There are three important points in using the recursive-do notation:
@@ -2689,7 +2689,8 @@ writing a type constraint), then your program should <literal>import Control.Mon
 Otherwise, you don't need to import any special libraries to use the mdo-notation. That is,
 as long as you only use the predefined instances mentioned above, the mdo-notation will
 be automatically available. (Note: This differs from the Hugs implementation, where
-<literal>MonadFix</literal> should always be imported.)
+<literal>MonadFix</literal> should always be imported.) To be on the safe side, of course, you can
+simply import it in all cases.
 </para></listitem>
 
 <listitem><para>
-- 
1.7.10.4