1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
|
Description: POD spelling
retreived -> retrieved
unecessary -> unnecessary
retreive -> -retrieve
Author: Damyan Ivanov <dmn@debian.org>
Forwarded: https://rt.cpan.org/Ticket/Display?id=95565
--- a/lib/Catalyst/Authentication/Credential/Password.pm
+++ b/lib/Catalyst/Authentication/Credential/Password.pm
@@ -175,7 +175,7 @@ be sure to use that same field name when
This sets the password type. Often passwords are stored in crypted or hashed
formats. In order for the password module to verify the plaintext password
-passed in, it must be told what format the password will be in when it is retreived
+passed in, it must be told what format the password will be in when it is retrieved
from the user object. The supported options are:
=over 8
--- a/lib/Catalyst/Plugin/Authentication.pm
+++ b/lib/Catalyst/Plugin/Authentication.pm
@@ -814,7 +814,7 @@ However, even if use_session is disabled
object will be auto-vivified and session Cookies will be sent in the headers. To
prevent accidental session creation, check if a session already exists with
if ($c->sessionid) { ... }. If the session doesn't exist, then don't place
-anything in the session to prevent an unecessary session from being created.
+anything in the session to prevent an unnecessary session from being created.
=item default_realm
--- a/lib/Catalyst/Plugin/Authentication/Internals.pod
+++ b/lib/Catalyst/Plugin/Authentication/Internals.pod
@@ -308,7 +308,7 @@ should experience no problems.
=item id( )
The C<id()> method should return a unique id (scalar) that can be used to
-retreive this user from the store. Often this will be provided to the store's
+retrieve this user from the store. Often this will be provided to the store's
C<find_user()> routine as C<id =E<gt> $user-E<gt>id> so you should ensure that your
store's C<find_user()> can cope with that.
|