# 
# patch "HACKING"
#  from [8da0054d1405c4e4a377c1c96acc217f633c3b5f]
#    to [78f1b3b23bb59c292a2c3a48498459ad04b84c76]
# 
# patch "INSTALL"
#  from [9349d923d2c4f21860659bdd8b90bc4418ae300b]
#    to [91300af1b7411653bb3eff5608a548b6a5ed633b]
# 
# patch "ROADMAP"
#  from [d4911b06c0fea0e9609928b34394e1b714ab57f5]
#    to [97276b1ae6610c5689ca34f24f3f9caa22adaa2a]
# 
--- HACKING
+++ HACKING
@@ -41,7 +41,7 @@
 development team of a problem.
 
 All changes to monotone that alter monotone's behaviour should include a new
-test.  This includes most changes, but use your judgement about adding tests
+test.  This includes most changes, but use your judgment about adding tests
 for very small changes..  The tests are located in the source tree in the
 tests/ directory, documentation on writing tests is available in
 tests/README.
--- INSTALL
+++ INSTALL
@@ -120,7 +120,7 @@
        build a version of monotone without the internal "bundled"
        copies of lua and sqlite libraries. normally monotone will use
        copies of these libraries it was bundled with. If you set these
-       flags to "no", it will try to use librarise it finds on your
+       flags to "no", it will try to use libraries it finds on your
        system, and use the bundled versions only if you do not have
        your own copies.
 
--- ROADMAP
+++ ROADMAP
@@ -8,7 +8,7 @@
 The roadmap does *not* include release points, because it is our
 intention (though at times not our demonstrated behavior) to stick as
 close as possible to time-based releases, once per month. Even if we
-happen to hold up a release for some unforseen reason -- usually lack
+happen to hold up a release for some unforeseen reason -- usually lack
 of available effort -- the *plan* is to operate in a time-based
 cycle.