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

diff --git a/doc/debug.texi b/doc/debug.texi
index 27d4f26..62d951a 100644
--- a/doc/debug.texi
+++ b/doc/debug.texi
@@ -118,7 +118,7 @@ Alternatively, it could be that the @file{kernel.o} you passed to
 @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