Minor documentation updates

[pintos-anon] / doc / localsettings.texi

diff --git a/doc/localsettings.texi b/doc/localsettings.texi
index e8bb45b07e3a61f18c2e5ec31d0a1c1c20b07fba..3e41b8b1f7a4f0c0f3d44eadebc7d02a521a2c27 100644 (file)
--- a/doc/localsettings.texi
+++ b/doc/localsettings.texi
@@ -1,11 +1,9 @@
 @c Local settings
 
-@set coursenumber CS 140
 @set localpintostarpath /usr/class/cs140/pintos/pintos.tar.gz
 @set localpintoshttppath http://@/www.stanford.edu/@/class/@/cs140/@/pintos/@/pintos.@/tar.gz
 @set localpintosbindir /usr/class/cs140/`uname -m`/bin
 
-@set recommendsourceforge
 @set recommendvnc
 @clear recommendcygwin
 
@@ -18,8 +16,8 @@ ITSS webpage}.  You may use the Solaris or Linux machines.
 
 @macro localpathsetup{}
 Under @command{csh}, Stanford's login shell, you can do so
-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
+with this command:@footnote{The term @samp{`uname -m`} expands to a value
+such as @file{x86_64} that indicates the type of computer you're
 logged into.}
 @example
 set path = ( @value{localpintosbindir} $path )
@@ -58,8 +56,7 @@ inspired your own in your design documentation.
 
 @macro localcvspolicy{}
 Instead, we recommend integrating your team's changes early and often,
-using a source code control system such as CVS (@pxref{CVS}) or a
-group collaboration site such as SourceForge (@pxref{SourceForge}).
+using a source code control system such as CVS (@pxref{CVS}).
 This is less likely to produce surprises, because everyone can see
 everyone else's code as it is written, instead of just when it is
 finished.  These systems also make it possible to review changes and,