Rev 4678: Review feedback. in http://bazaar.launchpad.net/~lifeless/bzr/docs

[Robert Collins]

At http://bazaar.launchpad.net/~lifeless/bzr/docs

------------------------------------------------------------
revno: 4678
revision-id: robertc at robertcollins.net-20090915051650-nahhg9o0387t0g9o
parent: robertc at robertcollins.net-20090907031628-za3l16685w4mccte
committer: Robert Collins <robertc at robertcollins.net>
branch nick: docs
timestamp: Tue 2009-09-15 15:16:50 +1000
message:
  Review feedback.
=== modified file 'doc/developers/bug-handling.txt'
--- a/doc/developers/bug-handling.txt	2009-09-07 03:08:30 +0000
+++ b/doc/developers/bug-handling.txt	2009-09-15 05:16:50 +0000
@@ -166,7 +166,7 @@
     require action. When setting a bug task to fix released, the bug target
     milestone should be set to the release the fix will be included in (or
     was included in, if you are updating an old bug). Don't spend too much time
-    updating this if you don't immediately know : its not critical that it be
+    updating this if you don't immediately know: its not critical that it be
     set.
 
 
@@ -217,7 +217,7 @@
 Therefore, we don't target bugs that we'd like to have fixed or that could
 be fixed in a particular release, we only target bugs that must be fixed
 and that will cause us to slip the release if they're not fixed.  At any time,
-very few if any of the bugs targetted to a release should be still open.  By
+very few if any of the bugs targeted to a release should be still open.  By
 definition, these bugs should normally be Critical priority.