@item
@kindex function-documentation
The documentation for a function is usually stored in the function
-definition itself (@pxref{Lambda Expressions}). The function
-@code{documentation} knows how to extract it. You can also put
-function documentation in the @code{function-documentation} property
-of the function name. That is useful with definitions such as
-keyboard macros that can't hold a documentation string.
+definition itself (@pxref{Lambda Expressions} and @pxref{Function
+Documentation}). The function @code{documentation} knows how to
+extract it. You can also put function documentation in the
+@code{function-documentation} property of the function name. That is
+useful with definitions such as keyboard macros that can't hold a
+documentation string.
@item
@kindex variable-documentation
@end defun
@defun documentation function &optional verbatim
-This function returns the documentation string of @var{function}.
-@code{documentation} handles macros, named keyboard macros, and
-special forms, as well as ordinary functions.
+This function returns the documentation string of @var{function}. It
+handles macros, named keyboard macros, and special forms, as well as
+ordinary functions.
If @var{function} is a symbol, this function first looks for the
@code{function-documentation} property of that symbol; if that has a
clicks on the @samp{Back} or @samp{Forward} buttons. Most commands
that use the @samp{*Help*} buffer should invoke this function before
clearing the buffer. The @var{item} argument should have the form
-@code{(@var{funtion} . @var{args})}, where @var{funtion} is a function
+@code{(@var{function} . @var{args})}, where @var{function} is a function
to call, with argument list @var{args}, to regenerate the help buffer.
The @var{interactive-p} argument is non-@code{nil} if the calling
command was invoked interactively; in that case, the stack of items