write and write_chunk are not actually response specific

mojolicious · Mar 21, 2015 · f5e772e · f5e772e
1 parent 6abe3f7
commit f5e772e
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/lib/Mojo/Content.pm b/lib/Mojo/Content.pm
@@ -584,7 +584,7 @@ Size of content already received from message in bytes.
 
 Write dynamic content non-blocking, the optional drain callback will be invoked
 once all data has been written. Calling this method without a chunk of data
-will finalize the response headers and allow for dynamic content to be written
+will finalize the L</"headers"> and allow for dynamic content to be written
 later. You can write an empty chunk of data at any time to end the stream.
 
   # Make sure previous chunk of data has been written before continuing
@@ -605,9 +605,9 @@ later. You can write an empty chunk of data at any time to end the stream.
 
 Write dynamic content non-blocking with C<chunked> transfer encoding, the
 optional drain callback will be invoked once all data has been written. Calling
-this method without a chunk of data will finalize the response headers and
-allow for dynamic content to be written later. You can write an empty chunk of
-data at any time to end the stream.
+this method without a chunk of data will finalize the L</"headers"> and allow
+for dynamic content to be written later. You can write an empty chunk of data
+at any time to end the stream.
 
   # Make sure previous chunk of data has been written before continuing
   $content->write_chunk('He' => sub {