--- Coro/Coro.pm	2011/05/12 23:55:39	1.297
+++ Coro/Coro.pm	2011/08/03 14:52:18	1.304
@@ -18,7 +18,6 @@
   cede; # and again
   
   # use locking
-  use Coro::Semaphore;
   my $lock = new Coro::Semaphore;
   my $locked;
   
@@ -345,7 +344,7 @@
 our $main;    # main coro
 our $current; # current coro
 
-our $VERSION = 5.372;
+our $VERSION = 6.04;
 
 our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub rouse_cb rouse_wait);
 our %EXPORT_TAGS = (
@@ -769,7 +768,7 @@
 This is a rather brutal way to free a coro, with some limitations - if
 the thread is inside a C callback that doesn't expect to be canceled,
 bad things can happen, or if the cancelled thread insists on running
-complicated cleanup handlers that rely on it'S thread context, things will
+complicated cleanup handlers that rely on its thread context, things will
 not work.
 
 Any cleanup code being run (e.g. from C<guard> blocks) will be run without