more consistent descriptions for write_chunk usage

mojolicious · Mar 23, 2015 · b9ae65b · b9ae65b
1 parent 79b2c10
commit b9ae65b
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 8 deletions.
diff --git a/lib/Mojo/IOLoop.pm b/lib/Mojo/IOLoop.pm
@@ -62,12 +62,7 @@ sub client {
       $self->$cb(undef, $stream);
     }
   );
-  $client->on(
-    error => sub {
-      $self->_remove($id);
-      $self->$cb(pop, undef);
-    }
-  );
+  $client->on(error => sub { $self->_remove($id); $self->$cb(pop, undef) });
   $client->connect(@_);
 
   return $id;

diff --git a/lib/Mojolicious/Guides/Rendering.pod b/lib/Mojolicious/Guides/Rendering.pod
@@ -1295,8 +1295,8 @@ speed up preloading of referenced images and stylesheets.
   app->start;
 
 The optional drain callback ensures that all previous chunks have been written
-before processing continues. An empty chunk or call to
-L<Mojolicious::Controller/"finish"> marks the end of the stream.
+before processing continues. To end the stream you can call
+L<Mojolicious::Controller/"finish"> or write an empty chunk of data.
 
   HTTP/1.1 200 OK
   Connection: keep-alive