Wordsmithing.

[pintos-anon] / doc / debug.texi

diff --git a/doc/debug.texi b/doc/debug.texi
index ba53f70e0f4a5a2dce6d9d153558c0fc2624880c..bd1aa6af1c601a3e805573550e08a37e21df0b32 100644 (file)
--- a/doc/debug.texi
+++ b/doc/debug.texi
@@ -127,7 +127,7 @@ optimize such that an unrelated function C appears in the backtrace
 instead of A.  Function C is simply the function that happens to be in
 memory just after A.  In the threads project, this is commonly seen in
 backtraces for test failures; see @ref{The pass function fails, ,
-@func{pass} Fails}), for more information.
+@func{pass} Fails}, for more information.
 
 @menu
 * Backtrace Example::           
@@ -170,9 +170,9 @@ The backtrace output would then look something like this:
 0x8048ac8: ?? (??:0)
 @end example
 
-(You will probably not get the same results if you run the command above
-on your own kernel binary, because the source code you compiled from is
-different from the source code that panicked.)
+(You will probably not see exactly the same addresses if you run the
+command above on your own kernel binary, because the source code you
+compiled and the compiler you used are probably different.)
 
 The first line in the backtrace refers to @func{debug_panic}, the
 function that implements kernel panics.  Because backtraces commonly