Description: POD spelling retreived -> retrieved unecessary -> unnecessary retreive -> -retrieve Bug: https://rt.cpan.org/Ticket/Display?id=95565 Forwarded: https://rt.cpan.org/Ticket/Display?id=95565 Author: Damyan Ivanov Reviewed-by: gregor herrmann Last-Update: 2024-10-28 --- a/lib/Catalyst/Authentication/Credential/Password.pm +++ b/lib/Catalyst/Authentication/Credential/Password.pm @@ -176,7 +176,7 @@ 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 @@ -812,7 +812,7 @@ 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 @@ =item id( ) The C 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 routine as C $user-Eid> so you should ensure that your store's C can cope with that.