Another pass on README/HACKING. Still room for improvement.

1 files changed, 20 insertions, 22 deletions

diff --git a/HACKING b/HACKING
index 21306625c..dc05bc82a 100644
--- a/HACKING
+++ b/HACKING
@@ -1,8 +1,8 @@
 ====================
-0: Table of Contents
+0: Table of contents
 ====================
 
-0: Table of Contents
+0: Table of contents
 1: Intro
 2: Using the leak checker
 
@@ -10,34 +10,32 @@
 1: Intro
 ========
 
-Nautilus source tree is available from cvs for the latest-cutting
-edge version and from tarballs whenever we really get tired of people 
-asking us for releases. 
+Nautilus source tree is available from CVS (the latest-cutting edge
+version) and in releases (tarballs).
 
-If you plan to hack on nautilus, please make sure you work from the cvs 
-version. cvs version is available by anonymous cvs from GNOME cvs server.
-http://developer.gnome.org/tools/cvs.html details how to get started 
-with cvs.
+If you plan to hack on Nautilus, please make sure you work from the
+CVS version. The CVS version is available on GNOME CVS. The page
+http://developer.gnome.org/tools/cvs.html details how to get started
+with GNOME CVS.
 
-If you want to contribute back patches, please, make sure you mail the 
-nautilus maintainer (namely, Dain Adler: <darin@eazel.com>) and 
-nautilus mailing list: <nautilus-list@lists.eazel.com> (subscribtions
-should be made to <nautilus-list-request@lists.eazel.com> with "subscribe"
-as a subject)
+If you want to contribute patches, please send mail to the nautilus
+maintainer (Darin Adler <darin@eazel.com>) and/or the nautilus mailing
+list: <nautilus-list@lists.eazel.com> (subscribtions should be made to
+<nautilus-list-request@lists.eazel.com> with "subscribe" as a
+subject).
 
-Patches should be made with 'cvs diff -u >patch' and should conform to 
-the nautilus coding style as detailed in docs/style-guide.html
-Please, make sure to read the relevant documents in the docs directory 
-too.
+Patches should be made with 'cvs diff -u >patch' and should conform to
+Nautilus coding style as described in docs/style-guide.html Please
+read other relevant documents in the docs directory too.
 
-===============================
+=========================
 2: Using the leak checker
-===============================
+=========================
 
 Nautilus is set up to use the libleakcheck.so leak checking libary. To
-use it run nautilus with LD_PRELOAD set to the path to the installed
+use it, run Nautilus with LD_PRELOAD set to the path to the installed
 libleakcheck.so libary. For example, if you are using a
-bourne-compatible shell, like bash, you can run nautilus this way to
+bourne-compatible shell, like bash, you can run Nautilus this way to
 run with leak checking:
 
 LD_PRELOAD=/gnome/libs/libleakcheck.so /gnome/bin/nautilus