[commit: ghc] ghc-7.10: Update user guide, fixing #10772 (45f7392)

[git at git.haskell.org]

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

On branch  : ghc-7.10
Link       : http://ghc.haskell.org/trac/ghc/changeset/45f73924c36fb61f87413b18951b4b1121ea2bfa/ghc

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

commit 45f73924c36fb61f87413b18951b4b1121ea2bfa
Author: Richard Eisenberg <eir at cis.upenn.edu>
Date:   Sat Sep 19 14:45:28 2015 -0400

    Update user guide, fixing #10772


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

45f73924c36fb61f87413b18951b4b1121ea2bfa
 docs/users_guide/glasgow_exts.xml | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/docs/users_guide/glasgow_exts.xml b/docs/users_guide/glasgow_exts.xml
index fb4837a..3dfd40a 100644
--- a/docs/users_guide/glasgow_exts.xml
+++ b/docs/users_guide/glasgow_exts.xml
@@ -2840,8 +2840,11 @@ GHC allows type constructors, classes, and type variables to be operators, and
 to be written infix, very much like expressions.  More specifically:
 <itemizedlist>
 <listitem><para>
-  A type constructor or class can be an operator, beginning with a colon; e.g. <literal>:*:</literal>.
-  The lexical syntax is the same as that for data constructors.
+  A type constructor or class can be any non-reserved operator.
+  Symbols used in types are always like capitalized identifiers; they
+  are never variables. Note that this is different from the lexical
+  syntax of data constructors, which are required to begin with a
+  <literal>:</literal>.
   </para></listitem>
 <listitem><para>
   Data type and type-synonym declarations can be written infix, parenthesised