REflow and clarification

Author: JJ

doc/Language/traps.pod6

@@ -1595,12 +1595,14 @@ method TOP ($/ is copy) { my $foo = ~$/; my $v = $foo ~~ /foo/;  }
 
 =head2 Using certain names for rules/token/regexes
 
-Grammars are classes.
+Grammars are actually a type of classes.
 
     grammar G {};
     say G.^mro; # OUTPUT: «((G) (Grammar) (Match) (Capture) (Cool) (Any) (Mu))␤»
 
-C<^mro> prints the class hierarchy of this empty grammar, showing all the superclasses. And these superclasses have their very own methods. Defining a method in that grammar might clash with the ones inhabiting the class hierarchy:
+C<^mro> prints the class hierarchy of this empty grammar, showing all the
+superclasses. And these superclasses have their very own methods. Defining a
+method in that grammar might clash with the ones inhabiting the class hierarchy:
 
 =begin code :skit-test<throws exception>
 grammar g {
@@ -1613,9 +1615,18 @@ say g.parse('defined');
 # /tmp/dZ3evir0pb line 1␤  in block <unit> at /tmp/dZ3evir0pb line 1␤␤»
 =end code
 
-C«item» seems innocuous enough, but it is a L<C<sub> defined in class C<Mu>|/routine/item>. The message is a bit cryptic and totally unrelated to that fact, but that is why this is listed as a trap. In general, all subs defined in any part of the hierarchy are going to cause problems; some methods will too. For instance, C<CREATE>, C<take> and C<defined> (which are defined in L<Mu>). In general, multi methods and simple methods will not have any problem, but it might not be a good practice to use them as rule names.
-
-Also avoid L<phasers|/language/objects#Object_Construction> for rule/token/regex names: C<TWEAK>, C<BUILD>, C<BUILD-ALL> will throw another kind of exception if you do that: C<Cannot find method 'match': no method cache and no .^find_method>, once again only slightly related to what is actually going on.
+C«item» seems innocuous enough, but it is a L<C<sub> defined in class
+C<Mu>|/routine/item>. The message is a bit cryptic and totally unrelated to that
+fact, but that is why this is listed as a trap. In general, all subs defined in
+any part of the hierarchy are going to cause problems; some methods will too.
+For instance, C<CREATE>, C<take> and C<defined> (which are defined in L<Mu>). In
+general, multi methods and simple methods will not have any problem, but it
+might not be a good practice to use them as rule names.
+
+Also avoid L<phasers|/language/objects#Object_Construction> for rule/token/regex
+names: C<TWEAK>, C<BUILD>, C<BUILD-ALL> will throw another kind of exception if
+you do that: C<Cannot find method 'match': no method cache and no
+.^find_method>, once again only slightly related to what is actually going on.
 
 =head1 Unfortunate generalization