- @kbd{C-h f} is also useful for Lisp functions that you are planning
-to use in a Lisp program. For example, if you have just written the
-expression @code{(make-vector len)} and want to check that you are
-using @code{make-vector} properly, type @kbd{C-h f make-vector
-@key{RET}}. Because @kbd{C-h f} allows all function names, not just
-command names, you may find that some of your favorite completion
-abbreviations that work in @kbd{M-x} don't work in @kbd{C-h f}. An
-abbreviation may be unique among command names, yet fail to be unique
-when other function names are allowed.
-
- The default function name for @kbd{C-h f} to describe, if you type
-just @key{RET}, is the name of the function called by the innermost Lisp
-expression in the buffer around point, @emph{provided} that is a valid,
-defined Lisp function name. For example, if point is located following
-the text @samp{(make-vector (car x)}, the innermost list containing
-point is the one that starts with @samp{(make-vector}, so the default is
-to describe the function @code{make-vector}.
-
- @kbd{C-h f} is often useful just to verify that you have the right
-spelling for the function name. If @kbd{C-h f} mentions a name from the
-buffer as the default, that name must be defined as a Lisp function. If
-that is all you want to know, just type @kbd{C-g} to cancel the @kbd{C-h
-f} command, then go on editing.
-
- @kbd{C-h v} (@code{describe-variable}) is like @kbd{C-h f} but describes
-Lisp variables instead of Lisp functions. Its default is the Lisp symbol
-around or before point, but only if that is the name of a known Lisp
-variable. @xref{Variables}.
-
- Help buffers describing Emacs variables and functions normally have
-hyperlinks to the definition, if you have the source files installed.
-(@xref{Hyperlinking}.) If you know Lisp (or C), this provides the
-ultimate documentation. If you don't know Lisp, you should learn it.
-(The Introduction to Emacs Lisp Programming, available from the FSF
-through fsf.org, is a good way to get started.) Emacs won't be happy
-if it feels you are just @emph{using} Emacs, treating it as an object
-program. If you really love Emacs, show that you care by reading the
-source code.
+ @kbd{C-h f} is also useful for Lisp functions that you use in a Lisp
+program. For example, if you have just written the expression
+@code{(make-vector len)} and want to check that you are using
+@code{make-vector} properly, type @kbd{C-h f make-vector @key{RET}}.
+Because @kbd{C-h f} allows all function names, not just command names,
+you may find that some of your favorite completion abbreviations that
+work in @kbd{M-x} don't work in @kbd{C-h f}. An abbreviation that is
+unique among command names may not be unique among all function names.
+
+ If you type @kbd{C-h f @key{RET}}, it describes the function called
+by the innermost Lisp expression in the buffer around point,
+@emph{provided} that function name is a valid, defined Lisp function.
+(That name appears as the default while you enter the argument.) For
+example, if point is located following the text @samp{(make-vector
+(car x)}, the innermost list containing point is the one that starts
+with @samp{(make-vector}, so @kbd{C-h f @key{RET}} will describe the
+function @code{make-vector}.
+
+ @kbd{C-h f} is also useful just to verify that you spelled a
+function name correctly. If the minibuffer prompt for @kbd{C-h f}
+shows the function name from the buffer as the default, it means that
+name is defined as a Lisp function. Type @kbd{C-g} to cancel the
+@kbd{C-h f} command if you don't really want to view the
+documentation.
+
+@kindex C-h v
+@findex describe-variable
+ @kbd{C-h v} (@code{describe-variable}) is like @kbd{C-h f} but
+describes Lisp variables instead of Lisp functions. Its default is
+the Lisp symbol around or before point, if that is the name of a
+defined Lisp variable. @xref{Variables}.
+
+ Help buffers that describe Emacs variables and functions normally
+have hyperlinks to the corresponding source definition, if you have
+the source files installed. (@xref{Hyperlinking}.) If you know Lisp
+(or C), this provides the ultimate documentation. If you don't know
+Lisp, you should learn it. (The Introduction to Emacs Lisp
+Programming, available from the FSF through fsf.org, is a good way to
+get started.) If Emacs feels you are just @emph{using} it, treating
+it as an object program, its feelings may be hurt. For real intimacy,
+read the Emacs source code.