[docs/release_guide.pod] updates and improvements

docs/release_guide.pod

@@ -28,12 +28,12 @@ part of monthly Parrot releases.
   2010-03-18   Rakudo #27 "Copenhagen"         (smash)
   2010-04-22   Rakudo #28 "Moscow"             (moritz)
   2010-05-20   Rakudo #29 "Erlangen"           (colomon)
+  2010-06-17   Rakudo #30 "Kiev"               (masak)
 
 =head2 Planned 2010 releases
 
 Dates are based on Parrot's expected release schedule.
 
-  2010-06-17   Rakudo #30 "Kiev"               (masak)
   2010-07-22   Rakudo #31 "Atlanta"            (Coke)
   2010-08-19   Rakudo #32                      -vacant-
   2010-09-23   Rakudo #33                      -vacant-
@@ -45,8 +45,6 @@ Dates are based on Parrot's expected release schedule.
 
   BristolBath.pm
   Milan.pm
-  Kiev.pm - awesome hackathon, see
-        http://use.perl.org/~JonathanWorthington/journal/40399
 
 More names can be gotten from L<http://www.pm.org> if you 
 can't think of one with any particular significance to Perl 
@@ -148,7 +146,7 @@ update spectest-progress.csv or to count tests that won't run.
 Include a list of contributors since the last release in the announcement.
 You can get an automatically generated list by running
 
-  $ tools/contributors.pl
+  $ perl tools/contributors.pl
 
 Please check the result manually for duplicates and other errors.
 
@@ -188,9 +186,9 @@ Make sure any locally modified files have been pushed back to github.
 
 =item 9.
 
-Create an initial tarball by entering C<make release VERSION=YYYY.MM>,
+Create a tarball by entering C<make release VERSION=YYYY.MM>,
 where YYYY.MM is the month for which the release is being made.
-This will create a candidate tarball file named <rakudo-YYYY.MM.tgz>.
+This will create a tarball file named <rakudo-YYYY.MM.tgz>.
 
 B<Caution>: this steps removes your C<t/spec> directory and all files
 contained therein, and replaces it by a fresh svn export. So please make a
@@ -217,7 +215,7 @@ L<http://github.com/rakudo/rakudo/downloads>.
 
 =item 13.
 
-Publish the release announcement (from #5) above to appropriate
+Publish the release announcement (from #5) to appropriate
 locations, including rakudo.org, use.perl, perl6-language,
 perl6-announce, perl6-users, and others.