Rev 2371: (Ian Clatworthy) Minor corrections to HACKING. in http://bzr.arbash-meinel.com/branches/bzr/jam-integration

[John Arbash Meinel]

At http://bzr.arbash-meinel.com/branches/bzr/jam-integration

------------------------------------------------------------
revno: 2371
revision-id: john at arbash-meinel.com-20070322141340-wq5w000eof7tpmgj
parent: pqm at pqm.ubuntu.com-20070321071219-55447700ec71371f
parent: ian.clatworthy at internode.on.net-20070322010207-r8xcwjshipoahmcx
committer: John Arbash Meinel <john at arbash-meinel.com>
branch nick: jam-integration
timestamp: Thu 2007-03-22 09:13:40 -0500
message:
  (Ian Clatworthy) Minor corrections to HACKING.
modified:
  HACKING                        HACKING-20050805200004-2a5dc975d870f78c
    ------------------------------------------------------------
    revno: 2370.1.1
    merged: ian.clatworthy at internode.on.net-20070322010207-r8xcwjshipoahmcx
    parent: pqm at pqm.ubuntu.com-20070321071219-55447700ec71371f
    committer: Ian Clatworthy <ian.clatworthy at internode.on.net>
    branch nick: bzr.dev
    timestamp: Thu 2007-03-22 11:02:07 +1000
    message:
      Minor corrections to HACKING
-------------- next part --------------
=== modified file 'HACKING'
--- a/HACKING	2007-01-24 19:42:26 +0000
+++ b/HACKING	2007-03-22 01:02:07 +0000
@@ -295,7 +295,7 @@
 At this point, all of these exist as a ``ImportReplacer`` object, ready to
 be imported once a member is accessed. Also, when importing a module into
 the local namespace, which is likely to clash with variable names, it is
-recommended to prefix it as ``_mod_<module>``. This makes it clean that
+recommended to prefix it as ``_mod_<module>``. This makes it clearer that
 the variable is a module, and these object should be hidden anyway, since
 they shouldn't be imported into other namespaces.
 
@@ -376,7 +376,7 @@
 tests subdirectory under the package being tested.
 
 For example, tests for merge3 in bzrlib belong in bzrlib/tests/test_merge3.py.
-See bzrlib/selftest/test_sampler.py for a template test script.
+See bzrlib/tests/test_sampler.py for a template test script.
 
 Tests can be written for the UI or for individual areas of the library.
 Choose whichever is appropriate: if adding a new command, or a new command