[commit: ghc] ghc-8.2: Fix levity polymorphism docs (cac103f)

[git at git.haskell.org]

Repository : ssh://git@git.haskell.org/ghc

On branch  : ghc-8.2
Link       : http://ghc.haskell.org/trac/ghc/changeset/cac103f1bd2b7fa9dbe8cf17b4829c9175205257/ghc

>---------------------------------------------------------------

commit cac103f1bd2b7fa9dbe8cf17b4829c9175205257
Author: Alexey Vagarenko <vagarenko at gmail.com>
Date:   Sun May 21 15:08:41 2017 +0500

    Fix levity polymorphism docs
    
    (cherry picked from commit 6f8c3ce4b1dac02acf93c351862d3b6c46815840)


>---------------------------------------------------------------

cac103f1bd2b7fa9dbe8cf17b4829c9175205257
 docs/users_guide/glasgow_exts.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/users_guide/glasgow_exts.rst b/docs/users_guide/glasgow_exts.rst
index 89b243b..4a7ef74 100644
--- a/docs/users_guide/glasgow_exts.rst
+++ b/docs/users_guide/glasgow_exts.rst
@@ -8351,7 +8351,7 @@ think about compiling this to runnable code, though, problems appear.
 In particular, when we call ``bad``, we must somehow pass ``x`` into
 ``bad``. How wide (that is, how many bits) is ``x``? Is it a pointer?
 What kind of register (floating-point or integral) should ``x`` go in?
-It's all impossible to say, because ``x``'s type, ``TYPE r2`` is
+It's all impossible to say, because ``x``'s type, ``a :: TYPE r1`` is
 levity polymorphic. We thus forbid such constructions, via the
 following straightforward rule: