@@ -37,7 +37,7 @@ type constraint may change in this case.
37
37
= head2 Type Objects
38
38
39
39
To test if an object is a type object, test for definedness and check for
40
- identity between the object and it's C < .WHAT > pseudo-method. Note that the
40
+ identity between the object and its C < .WHAT > pseudo-method. Note that the
41
41
method C < .defined > can be overloaded and may provide false information.
42
42
43
43
my $a = Int;
@@ -366,7 +366,7 @@ Defined as:
366
366
multi sub trait_mod:<is>(Mu:U $child, Mu:U $parent)
367
367
368
368
The L < trait|/type/Sub#Traits > X < C < is > |is (inheritance)> accepts a type object to be
369
- added as a parent class of a class in it's definition. To allow multiple
369
+ added as a parent class of a class in its definition. To allow multiple
370
370
inheritance the trait can be applied more then once. Adding parents to a class
371
371
will import their methods into the target class. If the same method name occurs
372
372
in multiple parents, the first added parent will win.
@@ -574,7 +574,7 @@ Default parameters can be provided.
574
574
= head3 Roles as Types
575
575
576
576
Roles can be used as type constraints wherever a type is expected. If a role is
577
- mixed in with C < does > or C < but > , it's type-object is added to the type-object
577
+ mixed in with C < does > or C < but > , its type-object is added to the type-object
578
578
list of the object in question. If a role is used instead of a class (using
579
579
autopunning), the roles type-object is added to the inheritance chain.
580
580
0 commit comments