# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1118244790 0
# Node ID ca65a2108220ce0023d6c231c170a12d82c01600
# Parent  2244564c10dee9a602c3cbdba0f070fc0b17bbf6
(Defining Faces): Explain that face name should not end in `-face'.

diff -r 2244564c10de -r ca65a2108220 lispref/display.texi
--- a/lispref/display.texi	Wed Jun 08 15:32:01 2005 +0000
+++ b/lispref/display.texi	Wed Jun 08 15:33:10 2005 +0000
@@ -1795,14 +1795,15 @@
   The way to define a new face is with @code{defface}.  This creates a
 kind of customization item (@pxref{Customization}) which the user can
 customize using the Customization buffer (@pxref{Easy Customization,,,
-emacs, The GNU Emacs Manual}).
+emacs, The GNU Emacs Manual}).  
 
 @defmac defface face spec doc [keyword value]...
-This declares @var{face} as a customizable face that defaults according
-to @var{spec}.  You should not quote the symbol @var{face}.  The
+This declares @var{face} as a customizable face that defaults
+according to @var{spec}.  You should not quote the symbol @var{face},
+and it should not end in @samp{-face} (that would be redundant).  The
 argument @var{doc} specifies the face documentation.  The keywords you
-can use in @code{defface} are the same ones that are meaningful in both
-@code{defgroup} and @code{defcustom} (@pxref{Common Keywords}).
+can use in @code{defface} are the same as in @code{defgroup} and
+@code{defcustom} (@pxref{Common Keywords}).
 
 When @code{defface} executes, it defines the face according to
 @var{spec}, then uses any customizations that were read from the