Hi, the attached patch contains a few small corrections/updates to issues.html.
Regards, Stefan
Index: issues.part.html =================================================================== --- issues.part.html (revision 1706325) +++ issues.part.html (working copy) @@ -141,8 +141,8 @@ href="mailto:[email protected]" >[email protected]</a>, or if you have already been there and been asked to file an issue, then go to the <a -href="http://subversion.tigris.org/issue-tracker.html";>Issue -Tracker</a> and follow the instructions there.</p> +href="http://subversion.tigris.org/issue-tracker.html";>issue +tracker</a> and follow the instructions there.</p> <p>Thanks. We know it's a lot of work to file an effective bug report, but a good report can save hours of a developer's time, and @@ -188,7 +188,7 @@ <a href="mailto:[email protected]" >[email protected]</a>.</p></li> -<li><p>If the bug is in Apache HTTPD 2.0, please report it to both of +<li><p>If the bug is in Apache HTTPD 2.x, please report it to both of these mailing lists: <a href="mailto:[email protected]" >[email protected]</a>, <a href="mailto:[email protected]" @@ -316,7 +316,7 @@ milestone adjusted to reflect the Subversion release which will first reflect that change. A resolved issue that gets backported to a previous release stream needs to have its milestone adjusted to point -that previous release's version number. Finally, a resolved issue +to that previous release's version number. Finally, a resolved issue that gets <tt>REOPENED</tt> needs to have its milestone reevaluated in terms of whether the issue is a release blocker (<tt><em>MINORVERSION</em>.0</tt>) or not @@ -372,7 +372,7 @@ elif issue_is_real_but_we_won't_fix_it(i): close_as_wontfix(i) elif issue_is_closeable_for_some_other_reason(i): - close_as_it_for_that_reason(i) + close_it_for_that_reason(i) # Else issue should remain open, so DTRT with it...
