Review responses

1 files changed, 7 insertions, 4 deletions

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index b38653de3c5..15fbc3930dc 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -4876,9 +4876,9 @@ The contract between @value{GDBN} and the reverse executing target
 requires only that the target do something reasonable when
 @value{GDBN} tells it to execute backwards, and then report the 
 results back to @value{GDBN}.  Whatever the target reports back to
-@value{GDBN}, @value{GDBN} will report back to the user.  We assume 
-that the memory and registers that the target reports to us are in a
-consistant state, but we accept whatever we are given.
+@value{GDBN}, @value{GDBN} will report back to the user.  @value{GDBN}
+assumes that the memory and registers that the target reports are in a
+consistant state, but @value{GDBN} accepts whatever it is given.
 }.
 
 If you are debugging in a target environment that supports
@@ -4926,7 +4926,10 @@ Run backward to the beginning of the previous line executed in
 the current (innermost) stack frame.  If the line contains function
 calls, they will be ``un-executed'' without stopping.  Starting from
 the first line of a function, @code{reverse-next} will take you back
-to the caller of that function, @emph{before} the function was called.
+to the caller of that function, @emph{before} the function was called,
+just as the normal @code{next} command would take you from the last 
+line of a function back to its return to its caller
+@footnote{Unles the code is too heavily optimized.}.
 
 @kindex reverse-nexti
 @kindex rni @r{(@code{reverse-nexti})}