Minor improvements in ELisp manual.

 doc/lispref/compile.texi (Byte-Code Objects): Add index entry.
 (Disassembly): Add cross-references.

2 files changed, 9 insertions, 2 deletions

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index 40dff3c854a..416bb1eec98 100644
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,8 @@
+2013-03-24  Eli Zaretskii  <eliz@gnu.org>
+
+        * compile.texi (Byte-Code Objects): Add index entry.
+        (Disassembly): Add cross-references.
+
 2013-03-23  Eli Zaretskii  <eliz@gnu.org>
 
         * frames.texi (Size Parameters): More accurate description of the
diff --git a/doc/lispref/compile.texi b/doc/lispref/compile.texi
index d60ffebae70..522a88da61e 100644
--- a/doc/lispref/compile.texi
+++ b/doc/lispref/compile.texi
@@ -514,6 +514,7 @@ one you intend to suppress.
 @section Byte-Code Function Objects
 @cindex compiled function
 @cindex byte-code function
+@cindex byte-code object
 
   Byte-compiled functions have a special data type: they are
 @dfn{byte-code function objects}.  Whenever such an object appears as
@@ -606,8 +607,9 @@ name of an existing buffer.  Then the output goes there, at point, and
 point is left before the output.
 
 The argument @var{object} can be a function name, a lambda expression
-or a byte-code object.  If it is a lambda expression, @code{disassemble}
-compiles it and disassembles the resulting compiled code.
+(@pxref{Lambda Expressions}), or a byte-code object (@pxref{Byte-Code
+Objects}).  If it is a lambda expression, @code{disassemble} compiles
+it and disassembles the resulting compiled code.
 @end deffn
 
   Here are two examples of using the @code{disassemble} function.  We