fix a few typos (closes #802)

mojolicious · May 30, 2015 · 5a00d9e · 5a00d9e
1 parent 4ea1fa4
commit 5a00d9e
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 9 deletions.
diff --git a/Changes b/Changes
@@ -1,5 +1,5 @@
 
-6.12  2015-05-27
+6.12  2015-05-30
   - Added TO_JSON method to Mojo::Collection. (wttw)
 
 6.11  2015-05-16

diff --git a/lib/Mojolicious/Guides/Cookbook.pod b/lib/Mojolicious/Guides/Cookbook.pod
@@ -212,7 +212,7 @@ C<mod_proxy>, the configuration looks quite similar to the Nginx one above.
 =head2 Apache/CGI
 
 C<CGI> is supported out of the box and your L<Mojolicious> application will
-automatically detect that it is executed as a C<CGI> script. It's use in
+automatically detect that it is executed as a C<CGI> script. Its use in
 production environments is discouraged though, because as a result of how
 C<CGI> works, it is very slow and many web servers are making it exceptionally
 hard to configure properly.
@@ -452,7 +452,7 @@ nested closures that often result from continuation-passing style.
 
 =head2 Timers
 
-Another primary feature of the event loop are timers, which are created with
+Timers, another primary feature of the event loop, are created with
 L<Mojo::IOLoop/"timer"> and can for example be used to delay rendering of a
 response, and unlike C<sleep>, won't block any other requests that might be
 processed concurrently.

diff --git a/lib/Mojolicious/Guides/Rendering.pod b/lib/Mojolicious/Guides/Rendering.pod
@@ -443,10 +443,10 @@ L<Mojolicious::Plugin::DefaultHelpers/"accepts">.
 
 By now you've probably already encountered the built-in 404 (Not Found) and 500
 (Server Error) pages, that get rendered automatically when you make a mistake.
-Those are fallbacks for when your own exception handling fails, but especially
-during development they can also be a great help, you can render them manually
-with the helpers L<Mojolicious::Plugin::DefaultHelpers/"reply-E<gt>exception">
-and L<Mojolicious::Plugin::DefaultHelpers/"reply-E<gt>not_found">.
+Those are fallbacks for when your own exception handling fails, which can be
+especially helpful during development. You can also render them manually with
+the helpers L<Mojolicious::Plugin::DefaultHelpers/"reply-E<gt>exception"> and
+L<Mojolicious::Plugin::DefaultHelpers/"reply-E<gt>not_found">.
 
   use Mojolicious::Lite;
   use Scalar::Util 'looks_like_number';
@@ -1128,8 +1128,8 @@ applications, plugins make that very simple.
 
   1;
 
-The C<register> method will be called when you load the plugin and to add your
-helper to the application you can use L<Mojolicious/"helper">.
+The C<register> method will be called when you load the plugin. And to add your
+helper to the application, you can use L<Mojolicious/"helper">.
 
   use Mojolicious::Lite;