documentation tweaks

mojolicious · Mar 15, 2014 · d0cb3af · d0cb3af
1 parent aa01906
commit d0cb3af
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 10 deletions.
diff --git a/lib/Mojolicious/Controller.pm b/lib/Mojolicious/Controller.pm
@@ -843,8 +843,8 @@ timeout, which usually defaults to C<15> seconds.
   $c          = $c->session(foo => 'bar');
 
 Persistent data storage for the next few requests, all session data gets
-serialized with L<Mojo::JSON> and stored C<Base64> encoded in C<HMAC-SHA1>
-signed cookies. Note that cookies usually have a 4096 byte limit, depending on
+serialized with L<Mojo::JSON> and stored Base64 encoded in HMAC-SHA1 signed
+cookies. Note that cookies usually have a 4096 byte limit, depending on
 browser.
 
   # Manipulate session
@@ -869,7 +869,7 @@ browser.
   $c         = $c->signed_cookie(foo => 'bar', {path => '/'});
 
 Access signed request cookie values and create new signed response cookies.
-Cookies failing C<HMAC-SHA1> signature verification will be automatically
+Cookies failing HMAC-SHA1 signature verification will be automatically
 discarded.
 
 =head2 stash

diff --git a/lib/Mojolicious/Guides/Growing.pod b/lib/Mojolicious/Guides/Growing.pod
@@ -113,8 +113,8 @@ ids were exchanged between browser and web server in the form of cookies.
   Set-Cookie: session=hmac-sha1(base64(json($session)))
 
 In L<Mojolicious> however we are taking this concept one step further by
-storing everything C<JSON> serialized and C<Base64> encoded in C<HMAC-SHA1>
-signed cookies, which is more compatible with the REST philosophy and reduces
+storing everything JSON serialized and Base64 encoded in HMAC-SHA1 signed
+cookies, which is more compatible with the REST philosophy and reduces
 infrastructure requirements.
 
 =head2 Test Driven Development
@@ -357,7 +357,7 @@ L<Mojolicious/"secrets">.
 
   app->secrets(['Mojolicious rocks']);
 
-This passphrase is used by the C<HMAC-SHA1> algorithm to make signed cookies
+This passphrase is used by the HMAC-SHA1 algorithm to make signed cookies
 secure and can be changed at any time to invalidate all existing sessions.
 
   $self->session(user => 'sri');
@@ -381,7 +381,7 @@ method L<Mojolicious::Controller/"flash">.
   $self->redirect_to('goodbye');
 
 Just remember that all session data gets serialized with L<Mojo::JSON> and
-stored in C<HMAC-SHA1> signed cookies, which usually have a 4096 byte limit,
+stored in HMAC-SHA1 signed cookies, which usually have a 4096 byte limit,
 depending on browser.
 
 =head2 Final prototype

diff --git a/lib/Mojolicious/Sessions.pm b/lib/Mojolicious/Sessions.pm
@@ -77,9 +77,9 @@ Mojolicious::Sessions - Signed cookie based session manager
 =head1 DESCRIPTION
 
 L<Mojolicious::Sessions> manages simple signed cookie based sessions for
-L<Mojolicious>. All data gets serialized with L<Mojo::JSON> and stored
-C<Base64> encoded on the client-side, but is protected from unwanted changes
-with a C<HMAC-SHA1> signature.
+L<Mojolicious>. All data gets serialized with L<Mojo::JSON> and stored Base64
+encoded on the client-side, but is protected from unwanted changes with a
+HMAC-SHA1 signature.
 
 =head1 ATTRIBUTES