X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fintro.texi;h=ede0a69b58fccc85b6fc9a6cc33fb08dffc678ef;hb=2b4cbbd50d1752a6b26341ba78e7e285f7b947f3;hp=afa067d86a659ba7e828bd6664702a25925cc22f;hpb=fd24c2387f5cf1b802e885c7430ba1f1bb852e13;p=pintos-anon

diff --git a/doc/intro.texi b/doc/intro.texi
index afa067d..ede0a69 100644
--- a/doc/intro.texi
+++ b/doc/intro.texi
@@ -82,7 +82,7 @@ you log in.
 Now you can extract the source for Pintos into a directory named
 @file{pintos/src}, by executing
 @example
-tar xzf /usr/class/cs140/pintos/pintos.tar.gz
+zcat /usr/class/cs140/pintos/pintos.tar.gz | tar x
 @end example
 Alternatively, fetch
 @uref{http://@/www.stanford.edu/@/class/@/cs140/@/pintos/@/pintos.@/tar.gz}
@@ -385,7 +385,8 @@ We will judge your design based on the design document and the source
 code that you submit.  We will read your entire design document and much
 of your source code.  
 
-Don't forget that the design document is 50% of your project grade.  It
+Don't forget that design quality, including the design document, is 50%
+of your project grade.  It
 is better to spend one or two hours writing a good design document than
 it is to spend that time getting the last 5% of the points for tests and
 then trying to rush through writing the design document in the last 15
@@ -491,7 +492,8 @@ make your code self-consistent at the very least.  There should not be a
 patchwork of different styles that makes it obvious that three different
 people wrote the code.  Use horizontal and vertical white space to make
 code readable.  Add a brief comment on every structure, structure
-member, global or static variable, and function definition.  Update
+member, global or static variable, typedef, enumeration, and function
+definition.  Update
 existing comments as you modify code.  Don't comment out or use the
 preprocessor to ignore blocks of code (instead, remove it entirely).
 Use assertions to document key invariants.  Decompose code into