Reword paragraph.

[pintos-anon] / doc / intro.texi

diff --git a/doc/intro.texi b/doc/intro.texi
index e1eefab50bbad3ac2217f8a5cc870bf80448bea0..f22ba76e20b0a187e41002cba3b71cf8ec88e20a 100644 (file)
--- a/doc/intro.texi
+++ b/doc/intro.texi
@@ -60,10 +60,11 @@ with this command:@footnote{The term @samp{`uname -m`} expands to either
 @file{sun4u} or @file{i686} according to the type of computer you're
 logged into.}
 @example
-set path = ( $path /usr/class/cs140/`uname -m`/bin )
+set path = ( /usr/class/cs140/`uname -m`/bin $path )
 @end example
 @noindent
-(Notice that both @samp{`} are left single quotes or ``backticks.'')
+@strong{Notice that both @samp{`} are left single quotes or
+``backticks,'' not apostrophes (@samp{'}).}
 It is a good idea to add this line to the @file{.cshrc} file
 in your home directory.  Otherwise, you'll have to type it every time
 you log in.
@@ -469,7 +470,7 @@ should be, please let me know.
 
 Example code for condition variables (@pxref{Condition Variables}) is
 from classroom slides originally by Dawson Engler and updated by Mendel
-Roseblum.
+Rosenblum.
 
 @node Trivia
 @section Trivia
@@ -477,9 +478,9 @@ Roseblum.
 Pintos originated as a replacement for Nachos with a similar design.
 Since then Pintos has greatly diverged from the Nachos design.  Pintos
 differs from Nachos in two important ways.  First, Pintos runs on real
-or simulated 80@var{x}86 hardware, whereas Nachos runs as a process on a
-host operating system.  Second, like most real-world operating systems,
-Pintos is written in C, whereas Nachos is written in C++.
+or simulated 80@var{x}86 hardware, but Nachos runs as a process on a
+host operating system.  Second, Pintos is written in C like most
+real-world operating systems, but Nachos is written in C++.
 
 Why the name ``Pintos''?  First, like nachos, pinto beans are a common
 Mexican food.  Second, Pintos is small and a ``pint'' is a small amount.