X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fstandards.texi;h=8e4b3703432025bb5191ef4ccfca24ec503647c5;hb=d92d837ee458bff7687e4208607e98c5b8e017c2;hp=8e0f0e02bc4a79a4fd1243d2f6d4435fc809ed4e;hpb=8abbb333aea445641d967befd3ca477502ea770b;p=pintos-anon

diff --git a/doc/standards.texi b/doc/standards.texi
index 8e0f0e0..8e4b370 100644
--- a/doc/standards.texi
+++ b/doc/standards.texi
@@ -1,12 +1,7 @@
-@node Coding Standards, Project Documentation, 4.4BSD Scheduler, Top
+@node Coding Standards
 @appendix Coding Standards
 
-All of you should have taken a class like CS 107, so we expect you to be
-familiar with some set of coding standards such as
-@uref{http://www.stanford.edu/class/cs140/projects/misc/CodingStandards.pdf,
-, CS 107 Coding Standards}. Even if you've taken 107, we recommend
-reviewing that document.  We expect code at the ``Peer-Review Quality''
-level described there.
+@localcodingstandards{}
 
 Our standards for coding are most important for grading.  We want to
 stress that aside from the fact that we are explicitly basing part of
@@ -45,7 +40,7 @@ Please limit C source file lines to at most 79 characters long.
 Pintos comments sometimes refer to external standards or
 specifications by writing a name inside square brackets, like this:
 @code{[IA32-v3a]}.  These names refer to the reference names used in
-this documentation (@pxref{References}).
+this documentation (@pxref{Bibliography}).
 
 If you remove existing Pintos code, please delete it from your source
 file entirely.  Don't just put it into a comment or a conditional