; Elaborate minibuffer file name reading documentation

* doc/emacs/mini.texi (Minibuffer File): Slightly elaborate.
(Completion Commands): Fix markup.

diff --git a/doc/emacs/mini.texi b/doc/emacs/mini.texi
index 072b707ace3330097187b79e02844eb440baccf9..a2487f2e295dfd9f3130908e37a558c6a497c45e 100644 (file)
--- a/doc/emacs/mini.texi
+++ b/doc/emacs/mini.texi
@@ -108,6 +108,12 @@ for information about the default directory.
   Alternative defaults for the file name you may want are available by
 typing @kbd{M-n}, see @ref{Minibuffer History}.
 
+  While typing a file name in the minibuffer, you can use completion to
+insert the name of an existing file that matches your current input.
+@xref{Completion}.  You can sort the completion candidates in different
+ways, including sorting by last modified time, by typing @kbd{C-x C-v}
+in the minibuffer.  @xref{Sort Completions}.
+
   You can specify a file in the parent directory with @file{..}:
 @file{/a/b/../foo.el} is equivalent to @file{/a/foo.el}.
 Alternatively, you can use @kbd{M-@key{DEL}} to kill directory names
@@ -135,7 +141,7 @@ second slash in the pair.  In the example above,
 the terminal allows it.  (To disable this dimming, turn off File Name
 Shadow mode with the command @w{@kbd{M-x file-name-shadow-mode}}.)
 
-  When completing remote file names (@pxref{Remote Files}), a double
+  When entering remote file names (@pxref{Remote Files}), a double
 slash behaves slightly differently: it causes Emacs to ignore only the
 file-name part, leaving the rest (method, host and username, etc.)
 intact.  Typing three slashes in a row ignores everything in remote
@@ -171,9 +177,6 @@ file names, change the variable @code{insert-default-directory} to
 Nonetheless, relative file name arguments are still interpreted based
 on the same default directory.
 
-  You can also enter remote file names in the minibuffer.
-@xref{Remote Files}.
-
 @node Minibuffer Edit
 @section Editing in the Minibuffer
 
@@ -393,9 +396,12 @@ all the way to @samp{auto-fill-mode}.
 the minibuffer, or completes it and then submits it, depending on the
 ``strictness'' of the completion.  @xref{Completion Exit}.
 
+@anchor{Sort Completions}
+@cindex sort completions
+@cindex completions sort order
 @kindex C-x C-v @r{(completion)}
 @findex minibuffer-sort-completions
-  @key{C-x C-v} (@code{minibuffer-sort-completions}) changes the order
+  @kbd{C-x C-v} (@code{minibuffer-sort-completions}) changes the order
 of the completions list.  By default, Emacs sorts the list of possible
 completion candidates in the order that you specify in user option
 @code{completions-sort} (@pxref{Completion Options}).  This command
@@ -409,7 +415,7 @@ minibuffer history, and no sorting at all.  Some commands that use
 minibuffer completion also provide additional sorting options that are
 specifically useful with their completion candidates.  For example,
 during file name completion, as in @kbd{C-x C-f} (@pxref{Visiting}),
-you can use @key{C-x C-v} to sort candidate file names chronologically
+you can use @kbd{C-x C-v} to sort candidate file names chronologically
 by their last modified time.
 
 @kindex C-x n n @r{(completion)}