; * doc/lispref/edebug.texi (Edebug Views): Fix wording of last change.

1 files changed, 8 insertions, 8 deletions

diff --git a/doc/lispref/edebug.texi b/doc/lispref/edebug.texi
index 97909e2bb55..2f5e4d27c46 100644
--- a/doc/lispref/edebug.texi
+++ b/doc/lispref/edebug.texi
@@ -691,13 +691,10 @@ before returning to Edebug.  With a prefix argument @var{n}, pause for
 @findex edebug-bounce-to-previous-value
 @item P
 Temporarily display the outside current buffer with the outside point
-corresponding to the previous value
-(@code{edebug-bounce-to-previous-value}).  The previous value is what
-Edebug has evaluated before its last stop point or what you have
-evaluated in the context outside of Edebug, for example, with
-@kbd{C-x C-e}.  This command pauses for one second before returning to
-Edebug.  With a prefix argument @var{n}, it pauses for @var{n} seconds
-instead.
+corresponding to the previously-evaluated value
+(@code{edebug-bounce-to-previous-value}), pausing for one second
+before returning to Edebug.  With a prefix argument @var{n}, pause for
+@var{n} seconds instead.
 
 @findex edebug-where
 @item w
@@ -735,7 +732,10 @@ and you would like to know where @code{beg} and @code{end} are located
 in the outside buffer.  Then you could either evaluate these, for
 example, with @kbd{C-x C-e}, or step over them with @kbd{n}, and
 immediately after that press @kbd{P}, to bounce to the position you have
-previously evaluated.
+previously evaluated.  The previous value for the purpose of the @kbd{P}
+command is what Edebug has evaluated before its last stop point or what
+you have evaluated in the context outside of Edebug, for example, with
+@kbd{C-x C-e}.
 
   After moving point, you may wish to jump back to the stop point.
 You can do that with @kbd{w} from a source code buffer.  You can jump