diff --git a/docs/release_guide.pod b/docs/release_guide.pod
index a4bdf1f4520..10f9b514858 100644
--- a/docs/release_guide.pod
+++ b/docs/release_guide.pod
@@ -37,11 +37,12 @@ Dates are based on Parrot's expected release schedule.
   BristolBath.pm
   Milan.pm
   Seoul.pm
+  ThousandOaks.pm (http://www.lowlevelmanager.com/2009/09/perl-6-hackathon.html)
 
 =head2 Steps to create a release (for release managers)
 
 Each Rakudo development release is timed to occur two
-days after a Parrot monthly release.  
+days after a Parrot monthly release.
 
 =over 4
 
@@ -55,7 +56,7 @@ the Parrot release, it's a good idea to:
 =item *
 
 Remind people of the upcoming release, invite people to
-update the ChangeLog file, update the ROADMAP, choose a 
+update the ChangeLog file, update the ROADMAP, choose a
 release name, etc.
 
 =item *
@@ -83,12 +84,12 @@ the release announcement).
 
 =item 2.
 
-Once Parrot issues its monthly release, edit Rakudo's 
-build/PARROT_REVISION file to contain the subversion revision 
-number and release number corresponding to Parrot's monthly 
+Once Parrot issues its monthly release, edit Rakudo's
+build/PARROT_REVISION file to contain the subversion revision
+number and release number corresponding to Parrot's monthly
 release.  For example, for June 2009 PARROT_REVISION file
-contained "39599 1.3.0".  As always, test to make sure Rakudo 
-still builds and passes its tests.  Once build/PARROT_REVISION 
+contained "39599 1.3.0".  As always, test to make sure Rakudo
+still builds and passes its tests.  Once build/PARROT_REVISION
 has been set to the Parrot release, it must not be changed until
 after the Rakudo release.  In other words, we want each
 monthly release of Rakudo to be able to be built using
@@ -96,8 +97,8 @@ the immediately prior release of Parrot.
 
 =item 3.
 
-The short period following the Parrot release until the 
-Rakudo release is generally intended for fixing bugs, 
+The short period following the Parrot release until the
+Rakudo release is generally intended for fixing bugs,
 updating documentation, and so on.
 
 =item 4.
@@ -187,7 +188,7 @@ Tag the release by its release month ("MMMM-YY") and its code name.
 =item 12.
 
 Upload the release tarball to github's download area at
-L<http://github.com/rakudo/rakudo/downloads>.  
+L<http://github.com/rakudo/rakudo/downloads>.
 
 =item 13.