more links to commands

mojolicious · Jan 30, 2014 · af12908 · af12908
1 parent faac71b
commit af12908
Show file tree

Hide file tree

Showing 4 changed files with 14 additions and 12 deletions.
diff --git a/lib/Mojolicious/Guides/Cookbook.pod b/lib/Mojolicious/Guides/Cookbook.pod
@@ -1043,9 +1043,9 @@ be able to work standalone as well as inside an already running event loop.
 =head2 Command line
 
 Don't you hate checking huge HTML files from the command line? Thanks to the
-C<mojo get> command that is about to change. You can just pick the parts that
-actually matter with the CSS selectors from L<Mojo::DOM> and JSON Pointers
-from L<Mojo::JSON::Pointer>.
+command L<Mojolicious::Command::get> that is about to change. You can just
+pick the parts that actually matter with the CSS selectors from L<Mojo::DOM>
+and JSON Pointers from L<Mojo::JSON::Pointer>.
 
   $ mojo get http://mojolicio.us 'head > title'
 
@@ -1142,8 +1142,9 @@ namespace.
 =head2 Running code against your application
 
 Ever thought about running a quick one-liner against your L<Mojolicious>
-application to test something? Thanks to the C<eval> command you can do just
-that, the application object itself can be accessed via C<app>.
+application to test something? Thanks to the command
+L<Mojolicious::Command::eval> you can do just that, the application object
+itself can be accessed via C<app>.
 
   $ mojo generate lite_app myapp.pl
   $ ./myapp.pl eval 'say for @{app->static->paths}'

diff --git a/lib/Mojolicious/Guides/Rendering.pod b/lib/Mojolicious/Guides/Rendering.pod
@@ -1026,7 +1026,7 @@ that a response has been generated.
 
 =head2 Post-processing dynamic content
 
-While post-processing tasks are generally very easy with hook
+While post-processing tasks are generally very easy with the hook
 L<Mojolicious/"after_dispatch">, for content generated by the renderer it is a
 lot more efficient to use L<Mojolicious/"after_render">.
 
@@ -1131,9 +1131,9 @@ section of your application, similar to templates.
 
 Templates stored in files get preferred over files from the C<DATA> section,
 this allows you to include a default set of templates in your application that
-the user can later customize. The C<inflate> command will write all templates
-and static files from the C<DATA> section into actual files in the
-C<templates> and C<public> directories.
+the user can later customize. The command L<Mojolicious::Command::inflate>
+will write all templates and static files from the C<DATA> section into actual
+files in the C<templates> and C<public> directories.
 
   $ ./myapp.pl inflate
 

diff --git a/lib/Mojolicious/Guides/Routing.pod b/lib/Mojolicious/Guides/Routing.pod
@@ -767,8 +767,9 @@ out for quicksand!
 
 =head2 Introspection
 
-The C<routes> command can be used from the command line to list all available
-routes together with name and underlying regular expressions.
+The command L<Mojolicious::Command::routes> can be used from the command line
+to list all available routes together with name and underlying regular
+expressions.
 
   $ ./myapp.pl routes -v
   /foo/:name  GET   fooname  ^/foo/([^/\.]+))(?:\.([^/]+)$)?

diff --git a/lib/Mojolicious/Lite.pm b/lib/Mojolicious/Lite.pm
@@ -993,7 +993,7 @@ L<Test::Mojo>.
 
   done_testing();
 
-Run all unit tests with the C<test> command.
+Run all unit tests with the command L<Mojolicious::Command::test>.
 
   $ ./myapp.pl test
   $ ./myapp.pl test -v