summaryrefslogtreecommitdiff
path: root/docs/users_guide/exts/explicit_forall.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/users_guide/exts/explicit_forall.rst')
-rw-r--r--docs/users_guide/exts/explicit_forall.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/users_guide/exts/explicit_forall.rst b/docs/users_guide/exts/explicit_forall.rst
index 6b4fc9cef7..8287e510dc 100644
--- a/docs/users_guide/exts/explicit_forall.rst
+++ b/docs/users_guide/exts/explicit_forall.rst
@@ -112,9 +112,9 @@ Notes:
{-# RULES "f" forall (g :: forall a. a -> b) x. f g x = g x :: b #-}
-- GADT constructors are extra particular about their ``forall``s. In addition
+- GADT constructors are extra particular about their ``forall``\ s. In addition
to adhering to the ``forall``-or-nothing rule, GADT constructors also forbid
- nested ``forall``s. For example, GHC would reject the following GADT: ::
+ nested ``forall``\ s. For example, GHC would reject the following GADT: ::
data T where
MkT :: (forall a. a -> b -> T)
@@ -122,4 +122,4 @@ Notes:
Because of the lack of an outermost ``forall`` in the type of ``MkT``, the
``b`` would be implicitly quantified. In effect, it would be as if one had
written ``MkT :: forall b. (forall a. a -> b -> T)``, which contains nested
- ``forall``s. See :ref:`formal-gadt-syntax`.
+ ``forall``\ s. See :ref:`formal-gadt-syntax`.