Skip to content

Commit

Permalink
pod cleanup
Browse files Browse the repository at this point in the history
  • Loading branch information
kraih committed Aug 20, 2011
1 parent c829562 commit bf5631e
Show file tree
Hide file tree
Showing 5 changed files with 8 additions and 8 deletions.
4 changes: 2 additions & 2 deletions lib/Mojolicious/Controller.pm
Expand Up @@ -876,7 +876,7 @@ will not be encoded.
$c->render_exception('Oops!');
$c->render_exception(Mojo::Exception->new('Oops!'));
Render the exception template C<exception.${mode}.html.$handler> or
Render the exception template C<exception.$mode.html.$handler> or
C<exception.html.$handler> and set the response status code to C<500>.
=head2 C<render_json>
Expand All @@ -902,7 +902,7 @@ Disable auto rendering, especially for long polling this can be quite useful.
$c->render_not_found;
$c->render_not_found($resource);
Render the not found template C<not_found.${mode}.html.$handler> or
Render the not found template C<not_found.$mode.html.$handler> or
C<not_found.html.$handler> and set the response status code to C<404>.
=head2 C<render_partial>
Expand Down
6 changes: 3 additions & 3 deletions lib/Mojolicious/Guides/Rendering.pod
Expand Up @@ -611,9 +611,9 @@ to C<CPAN>.
While the built-in C<exception> and C<not_found> templates are very useful
during development, you most likely want to show your users something more
related to your application in production.
That's why L<Mojolicious> will always try to render
C<exception.${mode}.html.*> or C<not_found.${mode}.html.*> before falling
back to the built-in default templates.
That's why L<Mojolicious> will always try to render C<exception.$mode.html.*>
or C<not_found.$mode.html.*> before falling back to the built-in default
templates.

@@ exception.production.html.ep
<!doctype html><html>
Expand Down
2 changes: 1 addition & 1 deletion lib/Mojolicious/Lite.pm
Expand Up @@ -759,7 +759,7 @@ L<Mojolicious> mode, default will be C<development>.
=head2 Logging
L<Mojo::Log> messages will be automatically written to C<STDERR> or a
C<log/${mode}.log> file if a C<log> directory exists.
C<log/$mode.log> file if a C<log> directory exists.
$ mkdir log
Expand Down
2 changes: 1 addition & 1 deletion lib/Mojolicious/Plugin/Config.pm
Expand Up @@ -133,7 +133,7 @@ Mojolicious::Plugin::Config - Perlish Configuration Plugin
L<Mojolicious::Plugin::Config> is a Perl-ish configuration plugin.
The application object can be accessed via the C<app> helper.
You can extend the normal config file C<myapp.conf> with C<mode> specific
ones like C<myapp.${mode}.conf>.
ones like C<myapp.$mode.conf>.
=head1 OPTIONS
Expand Down
2 changes: 1 addition & 1 deletion lib/Mojolicious/Plugin/JSONConfig.pm
Expand Up @@ -88,7 +88,7 @@ L<Mojolicious::Plugin::JSONConfig> is a JSON configuration plugin that
preprocesses it's input with L<Mojo::Template>.
The application object can be accessed via C<$app> or the C<app> helper.
You can extend the normal config file C<myapp.json> with C<mode> specific
ones like C<myapp.${mode}.json>.
ones like C<myapp.$mode.json>.
=head1 OPTIONS
Expand Down

0 comments on commit bf5631e

Please sign in to comment.