X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fstandards.texi;h=7d30a4b4cfbe1c218a6390f752c4fb16ff484364;hb=919347c164606c3f1544b2e8bd62f505aeda80a1;hp=b1296c76f18baa1b700cb1adf9fb684568f52e46;hpb=f415a37905c57f61b444806bf84f5405184452aa;p=pintos-anon

diff --git a/doc/standards.texi b/doc/standards.texi
index b1296c7..7d30a4b 100644
--- a/doc/standards.texi
+++ b/doc/standards.texi
@@ -1,12 +1,7 @@
 @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
@@ -156,7 +151,7 @@ A few of the string functions declared in the standard
 The worst offenders are intentionally not included in the Pintos C
 library:
 
-@table @func
+@table @code
 @item strcpy
 When used carelessly this function can overflow the buffer reserved
 for its output string.  Use @func{strlcpy} instead.  Refer to