[commit: ghc] master: Update user guide, fixing #10772 (d19a77a)

[git at git.haskell.org]

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

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

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

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

    Update user guide, fixing #10772


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

d19a77ab420dec1dbd9c95744b987283ef5aa4cc
 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 119de6b..7aaf1a8 100644
--- a/docs/users_guide/glasgow_exts.xml
+++ b/docs/users_guide/glasgow_exts.xml
@@ -3017,8 +3017,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