--- a/man/custom.texi	Mon Aug 13 09:24:19 2007 +0200
+++ b/man/custom.texi	Mon Aug 13 09:25:29 2007 +0200
@@ -13,7 +13,7 @@
 @comment  node-name,  next,  previous,  up
 @top The Customization Library
 
-Version: 1.69
+Version: 1.74
 
 @menu
 * Introduction::                
@@ -272,7 +272,8 @@
 
 It is possible to specify that a face should have different attributes
 on different device types.  For example, a face may make text red on a
-color device, and bold on a monochrome device.
+color device, and bold on a monochrome device.  You do this by
+activating `Edit All' in the state menu.
 
 The way this is presented in the customization buffer is to have a list
 of display specifications, and for each display specification a list of
@@ -282,8 +283,9 @@
 
 @example
  *** custom-invalid-face: (sample)
+ State: this item is unchanged from its factory setting.
  [ ] Face used when the customize item is invalid.
- [INS] [DEL] Display: [ ] Type: [ ] X [ ] TTY
+ [INS] [DEL] Display: [ ] Type: [ ] X [ ] PM [ ] Win32 [ ] DOS [ ] TTY
                       [X] Class: [X] Color [ ] Grayscale [ ] Monochrome
                       [ ] Background: [ ] Light [ ] Dark
              Attributes: [ ] Bold: off 
@@ -303,7 +305,7 @@
 @end example
 
 This has two display specifications.  The first will match all color
-displays, independently on whether the device is X11 or a tty, and
+displays, independently on what window system the device belongs to, and
 whether background color is dark or light.  For devices matching this
 specification, @samp{custom-invalid-face} will force text to be
 displayed in yellow on red, but leave all other attributes alone.
@@ -318,8 +320,7 @@
 the check boxes.  The first checkbox in each line in the display
 specification is special.  It specify whether this particular property
 will even be relevant.  By not checking the box in the first display, we
-match all device types, also device types other than X11 and tty, for
-example ms-windows, nextstep, and mac os.
+match all device types, also device types other than those listed.
 
 After modifying the face, you can activate the state button to make the
 changes take effect.  The menu items in the state button menu is similar
@@ -406,6 +407,10 @@
 @comment  node-name,  next,  previous,  up
 @section Declarations
 
+This section describes how to declare customization groups, variables,
+and faces.  It doesn't contain any examples, but please look at the file
+@file{cus-edit.el} which contains many declarations you can learn from.
+
 @menu
 * Declaring Groups::            
 * Declaring Variables::         
@@ -635,8 +640,7 @@
 should not be allowed to select the @samp{Factory} menu item.
 
 @item 
-We need @strong{much} better support for keyboard operations in the
-customize buffer.
+Better support for keyboard operations in the customize buffer.
 
 @item
 Integrate with @file{w3} so you can customization buffers with much
@@ -653,16 +657,16 @@
 variable.
 
 @item
-There should be a way to see only the "current" display when editing a
-face, and that should be "on" by default.
-
-@item
 Support undo using lmi's @file{gnus-undo.el}.
 
 @item
 Make it possible to append to `choice', `radio', and `set' options.
 
 @item
+Make it possible to customize code, for example to enable or disable a
+global minor mode.
+
+@item
 Ask whether set or modified variables should be saved in
 @code{kill-buffer-hook}. 
 
@@ -678,6 +682,9 @@
 Suggested by Jens Lautenbacher
 @samp{<jens@@lemming0.lem.uni-karlsruhe.de>}.@refill
 
+@item
+Empty customization groups should start open (harder than it looks).
+
 @end itemize
 
 @contents