* doc/lispref/keymaps.texi (Extended Menu Items): Tweak :key-sequence

Don't make it sound like `:key-sequence nil` is any different than the
absence of `:key-sequence`.  And the performance advantage of
`:key-sequence` disappeared long ago.

diff --git a/doc/lispref/keymaps.texi b/doc/lispref/keymaps.texi
index 259efea32489fadcd0e0383fa9e3b1c03865dc1c..f3c984848e7d45f3d7706eceb3366e1a4c77da3e 100644 (file)
--- a/doc/lispref/keymaps.texi
+++ b/doc/lispref/keymaps.texi
@@ -2224,23 +2224,13 @@ set the variable so that the button you clicked on becomes selected.
 
 @item :key-sequence @var{key-sequence}
 This property specifies which key sequence is likely to be bound to the
-same command invoked by this menu item.  If you specify the right key
-sequence, that makes preparing the menu for display run much faster.
+same command invoked by this menu item.  If you specify a correct key
+sequence, that sequence will be preferred over others.
 
-If you specify the wrong key sequence, it has no effect; before Emacs
+If you specify in incorrect key sequence, it has no effect; before Emacs
 displays @var{key-sequence} in the menu, it verifies that
 @var{key-sequence} is really equivalent to this menu item.
 
-@item :key-sequence nil
-This property indicates that there is normally no key binding which is
-equivalent to this menu item.  Using this property saves time in
-preparing the menu for display, because Emacs does not need to search
-the keymaps for a keyboard equivalent for this menu item.
-
-However, if the user has rebound this item's definition to a key
-sequence, Emacs ignores the @code{:keys} property and finds the keyboard
-equivalent anyway.
-
 @item :keys @var{string}
 This property specifies that @var{string} is the string to display
 as the keyboard equivalent for this menu item.  You can use