[commit: ghc] master: Correct Simple to Complex wording (5ee9a1c)

[git at git.haskell.org]

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

On branch  : master
Link       : http://ghc.haskell.org/trac/ghc/changeset/5ee9a1cd0e633ad5ef9d905681d1a231ce1f616c/ghc

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

commit 5ee9a1cd0e633ad5ef9d905681d1a231ce1f616c
Author: Sasa Bogicevic <t4nt0r at protonmail.com>
Date:   Thu Jun 21 11:06:13 2018 +0200

    Correct Simple to Complex wording


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

5ee9a1cd0e633ad5ef9d905681d1a231ce1f616c
 docs/users_guide/glasgow_exts.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/users_guide/glasgow_exts.rst b/docs/users_guide/glasgow_exts.rst
index 678f75c..44db5ab 100644
--- a/docs/users_guide/glasgow_exts.rst
+++ b/docs/users_guide/glasgow_exts.rst
@@ -15867,8 +15867,8 @@ Here are some examples: ::
 The type ``Simple`` has its parameter at role representational, which is
 generally the most common case. ``Simple Age`` would have the same
 representation as ``Simple Int``. The type ``Complex``, on the other
-hand, has its parameter at role nominal, because ``Simple Age`` and
-``Simple Int`` are *not* the same. Lastly, ``Phant Age`` and
+hand, has its parameter at role nominal, because ``Complex Age`` and
+``Complex Int`` are *not* the same. Lastly, ``Phant Age`` and
 ``Phant Bool`` have the same representation, even though ``Age`` and
 ``Bool`` are unrelated.