Small doc updates for debugging

* doc/lispref/debugging.texi (Debugger Commands): Tiny edits.

* lisp/jit-lock.el (jit-lock-mode): Doc fix.

* etc/NEWS: Related edits.

2 files changed, 7 insertions, 3 deletions

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index c304cac04ba..f10577faf77 100644
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,7 @@
+2014-02-13  Glenn Morris  <rgm@gnu.org>
+
+        * debugging.texi (Debugger Commands): Tiny edits.
+
 2014-02-12  Glenn Morris  <rgm@gnu.org>
 
         * package.texi (Simple Packages): Describe URL and Keywords headers.
diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index 774ac594e0d..a9d0c1c4ed0 100644
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -425,7 +425,8 @@ Flag the current frame like @kbd{b}.  Then continue execution like
 are set up to do so by @code{debug-on-entry}.
 
 @item e
-Read a Lisp expression in the minibuffer, evaluate it, and print the
+Read a Lisp expression in the minibuffer, evaluate it (with the
+relevant lexical environment, if applicable), and print the
 value in the echo area.  The debugger alters certain important
 variables, and the current buffer, as part of its operation; @kbd{e}
 temporarily restores their values from outside the debugger, so you can
@@ -465,8 +466,7 @@ function and thus cancel the effect of @code{debug-on-entry}, it may
 erroneously show up in this list.
 
 @item v
-Display local variables (@pxref{Local Variables}) of the current stack
-frame.  Press @kbd{e} again to hide them.
+Toggle the display of local variables of the current stack frame.
 @end table
 
 @node Invoking the Debugger