summaryrefslogtreecommitdiff
path: root/doc/lispref/help.texi
diff options
context:
space:
mode:
authorLars Magne Ingebrigtsen <larsi@gnus.org>2011-07-14 02:02:09 +0200
committerLars Magne Ingebrigtsen <larsi@gnus.org>2011-07-14 02:02:09 +0200
commitf2027cdf5adf8bcb620a31addf5a5851e542affd (patch)
tree81767fa264a100dba3050212458de009dc098af5 /doc/lispref/help.texi
parent837c31f8306d5e21689e325807ef2fff4e5bae9e (diff)
downloademacs-f2027cdf5adf8bcb620a31addf5a5851e542affd.tar.gz
(Documentation Basics): Add a link to the Function Documentation node.
Fixes: debbugs:6580
Diffstat (limited to 'doc/lispref/help.texi')
-rw-r--r--doc/lispref/help.texi11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/lispref/help.texi b/doc/lispref/help.texi
index 63fc06c929b..0ce05d55a07 100644
--- a/doc/lispref/help.texi
+++ b/doc/lispref/help.texi
@@ -78,11 +78,12 @@ function or variable that it describes:
@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