X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fdebug.texi;fp=doc%2Fdebug.texi;h=27d4f260e72a93bf80ad926be5d1f942e23fa571;hb=2fd7bdd665beacb360dc7958d2f7135a6f5a6bfa;hp=e671b7495b2cc9a6e403abe6b252e1fa0ab24d35;hpb=c75a1a1b7c79c1a516256b8cf072631a7aa575eb;p=pintos-anon

diff --git a/doc/debug.texi b/doc/debug.texi
index e671b74..27d4f26 100644
--- a/doc/debug.texi
+++ b/doc/debug.texi
@@ -115,7 +115,7 @@ 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.