X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fdebug.texi;h=62d951add313c9a3f8ba48c304ff5b773594561f;hb=0c6f5592b956c6a5c11c3b422e523d961f8afa45;hp=e671b7495b2cc9a6e403abe6b252e1fa0ab24d35;hpb=611e2d49c1776917a455c7741db8ed1606c0f446;p=pintos-anon

diff --git a/doc/debug.texi b/doc/debug.texi
index e671b74..62d951a 100644
--- a/doc/debug.texi
+++ b/doc/debug.texi
@@ -115,10 +115,10 @@ sense (e.g.@: function A is listed above function B, but B doesn't
 call A), then it's a good sign that you're corrupting a kernel
 thread's stack, because the backtrace is extracted from the stack.
 Alternatively, it could be that the @file{kernel.o} you passed to
-@command{backtrace} does not correspond to the kernel that produced
+@command{backtrace} is not the same kernel that produced
 the backtrace.
 
-Sometimes backtraces can be confusing without implying corruption.
+Sometimes backtraces can be confusing without any corruption.
 Compiler optimizations can cause surprising behavior.  When a function
 has called another function as its final action (a @dfn{tail call}), the
 calling function may not appear in a backtrace at all.  Similarly, when