From: Aankhen Date: Sat, 5 May 2007 06:49:55 +0000 (+0000) Subject: Moose::Policy: X-Git-Tag: 0_04~7 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=bae6d4c347ee9329ba96744f33fc1784eb85fcc2;p=gitmo%2FMoose-Policy.git Moose::Policy: * fixed a few typos. --- diff --git a/lib/Moose/Policy.pm b/lib/Moose/Policy.pm index 87851d6..1ca2179 100644 --- a/lib/Moose/Policy.pm +++ b/lib/Moose/Policy.pm @@ -88,7 +88,7 @@ implement a number of customizations and restrictions on a particular Moose class. For instance, L enforces that all -specified Moose classes can only use single inheritence. It does this +specified Moose classes can only use single inheritance. It does this by trapping the call to C on the metaclass and only allowing you to assign a single superclass. @@ -112,11 +112,11 @@ custom metaclass before Moose has set it's default metaclass. In fact, if you try to set a Moose::Policy and there is a C method available, not only will kittens die, but your program will too. -=head2 Policys are class scoped +=head2 Policies are class scoped -You must repeat the policy for each class you want to us it. It is B +You must repeat the policy for each class you want to use it. It is B inherited. This may change in the future, probably it will be a Moose::Policy -itself to allow Moose policys to be inherited. +itself to allow Moose policies to be inherited. =head1 THE POLICY @@ -163,7 +163,7 @@ some random thoughts on that, in no particular order. Roles are an excellent way to combine sets of behaviors together into one, and custom metaclasses are actually better composed by roles then by inheritence. The ideal situation is that this module will provide a set of roles which can be -used to compose you meta-policy with relative ease. +used to compose your meta-policy with relative ease. =back