Typo fixes found by Godmar Back's TA.

diff --git a/doc/intro.texi b/doc/intro.texi
index 220b51e746546503079ab488812db1ac740e43e1..16f833a823edf159956022ea6932f287b4b547d3 100644 (file)
--- a/doc/intro.texi
+++ b/doc/intro.texi
@@ -264,7 +264,7 @@ using @option{-h}, e.g.@: @code{pintos -h}.
 @node Debugging versus Testing
 @subsection Debugging versus Testing
 
-When you're debugging code, it's useful to be able to be able to run a
+When you're debugging code, it's useful to be able to run a
 program twice and have it do exactly the same thing.  On second and
 later runs, you can make new observations without having to discard or
 verify your old observations.  This property is called

diff --git a/doc/tour.texi b/doc/tour.texi
index 41b6ffa359b07fd122d0a82e1a1dfb1b38288c53..750145b184d7ae267e77adcd079d837843ae1748 100644 (file)
--- a/doc/tour.texi
+++ b/doc/tour.texi
@@ -392,7 +392,7 @@ thread statistics and triggers the scheduler when a time slice expires.
 Called during Pintos shutdown to print thread statistics.
 @end deftypefun
 
-@deftypefun void thread_create (const char *@var{name}, int @var{priority}, thread_func *@var{func}, void *@var{aux})
+@deftypefun tid_t thread_create (const char *@var{name}, int @var{priority}, thread_func *@var{func}, void *@var{aux})
 Creates and starts a new thread named @var{name} with the given
 @var{priority}, returning the new thread's tid.  The thread executes
 @var{func}, passing @var{aux} as the function's single argument.
@@ -1050,7 +1050,7 @@ kernel threads.  Thus, they do need to synchronize with other threads
 on shared data and other resources (@pxref{Synchronization}).
 
 @deftypefun void intr_register_int (uint8_t @var{vec}, int @var{dpl}, enum intr_level @var{level}, intr_handler_func *@var{handler}, const char *@var{name})
-Registers @var{func} to be called when internal interrupt numbered
+Registers @var{handler} to be called when internal interrupt numbered
 @var{vec} is triggered.  Names the interrupt @var{name} for debugging
 purposes.
 
@@ -1071,8 +1071,8 @@ starting with project 2).
 
 Whereas an internal interrupt runs in the context of the thread that
 caused it, external interrupts do not have any predictable context.
-They are asynchronous, so it can be invoked at any time that
-interrupts have not been enabled.  We say that an external interrupt
+They are asynchronous, so they can be invoked at any time that
+interrupts have not been disabled.  We say that an external interrupt
 runs in an ``interrupt context.''
 
 In an external interrupt, the @struct{intr_frame} passed to the

diff --git a/doc/vm.texi b/doc/vm.texi
index 28754c76da50086d0dfa96ad63b71e1ab67e7df9..6e5d5a076b281bdb6dd72515e9b2c22b792fbf93 100644 (file)
--- a/doc/vm.texi
+++ b/doc/vm.texi
@@ -625,7 +625,7 @@ modified by the reference solution.
  17 files changed, 1532 insertions(+), 104 deletions(-)
 @end verbatim
 
-@item Do we need a working HW 2 to implement HW 3?
+@item Do we need a working Project 2 to implement Project 3?
 
 Yes.