Index: doc/hacking.texinfo
===================================================================
RCS file: /cvsroot/classpath/classpath/doc/hacking.texinfo,v
retrieving revision 1.36
diff -u -p -r1.36 hacking.texinfo
--- doc/hacking.texinfo	4 Jul 2005 14:31:01 -0000	1.36
+++ doc/hacking.texinfo	7 Jul 2005 21:04:16 -0000
@@ -458,12 +458,12 @@ java.lang.StrictMath.
 @chapter Programming Standards
 
 For C source code, follow the
address@hidden://www.fsf.org/prep/standards_toc.html,GNU Coding Standards}.
address@hidden://www.gnu.org/prep/standards/,GNU Coding Standards}.
 The standards also specify various things like the install directory
 structure.  These should be followed if possible.
 
 For Java source code, please follow the
address@hidden://www.fsf.org/prep/standards_toc.html,GNU Coding
address@hidden://www.gnu.org/prep/standards/,GNU Coding
 Standards}, as much as possible.  There are a number of exceptions to
 the GNU Coding Standards that we make for GNU Classpath as documented
 in this guide.  We will hopefully be providing developers with a code
@@ -484,7 +484,7 @@ guidelines more tailored to GNU Classpat
 
 Here is a list of some specific rules used when hacking on GNU
 Classpath java source code. We try to follow the standard
address@hidden://www.gnu.org/prep/standards_23.html,GNU Coding Standards}
address@hidden://www.gnu.org/prep/standards/,GNU Coding Standards}
 for that. There are lots of tools that can automatically generate it
 (although most tools assume C source, not java source code) and it
 seems as good a standard as any. There are a couple of exceptions and