X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fstandards.texi;h=a13058a91cf6a0de30483cda7ec622d853655001;hb=c49ca891e62eb091e3c923a77bf2ea907d73220f;hp=7af266e9c10b9cecb5be44f8ae190acf9a8048ef;hpb=01679e7fec5244d137cc9b2cfc2d72e946c4d9d2;p=pintos-anon

diff --git a/doc/standards.texi b/doc/standards.texi
index 7af266e..a13058a 100644
--- a/doc/standards.texi
+++ b/doc/standards.texi
@@ -39,9 +39,10 @@ follows the @uref{http://www.gnu.org/prep/standards_toc.html, , GNU
 Coding Standards}.  We encourage you to follow the applicable parts of
 them too, especially chapter 5, ``Making the Best Use of C.''  Using a
 different style won't cause actual problems, but it's ugly to see
-gratuitous differences in style from one function to another.
+gratuitous differences in style from one function to another.  If your
+code is too ugly, it will cost you points.
 
-Pintos comments sometimes refer to outside standards or
+Pintos comments sometimes refer to external standards or
 specifications by writing a name inside square brackets, like this:
 @code{[IA32-v3]}.  These names refer to the reference names used in
 this documentation (@pxref{References}).