- removed @ref to "printf Reboots" since this no longer applies and the @anchor is...

- fixed typo print -> printf

diff --git a/doc/debug.texi b/doc/debug.texi
index 0d5a79deaf6917be4c46e750a1993ef778b29170..958e51b3bafcb2e3288ed28aa58ed4605ddfe4da 100644 (file)
--- a/doc/debug.texi
+++ b/doc/debug.texi
@@ -21,13 +21,12 @@ introduces you to a few of them.
 Don't underestimate the value of @func{printf}.  The way
 @func{printf} is implemented in Pintos, you can call it from
 practically anywhere in the kernel, whether it's in a kernel thread or
-an interrupt handler, almost regardless of what locks are held (but see
-@ref{printf Reboots} for a counterexample).
+an interrupt handler, almost regardless of what locks are held.
 
 @func{printf} is useful for more than just examining data.
 It can also help figure out when and where something goes wrong, even
 when the kernel crashes or panics without a useful error message.  The
-strategy is to sprinkle calls to @func{print} with different strings
+strategy is to sprinkle calls to @func{printf} with different strings
 (e.g.@: @code{"<1>"}, @code{"<2>"}, @dots{}) throughout the pieces of
 code you suspect are failing.  If you don't even see @code{<1>} printed,
 then something bad happened before that point, if you see @code{<1>}