Change .perl to .raku in more files.

Author: Prince213

doc/Language/classtut.pod6

@@ -829,13 +829,13 @@ C<GeekCook>.
 
 The call C<$o.^name> tells us the type of C<$o>: in this case C<Programmer>.
 
-C<$o.perl> returns a string that can be executed as Perl code, and
-reproduces the original object C<$o>. While this does not work perfectly in
+C<$obj.perl> (C<$obj.raku>) returns a string that can be executed as Raku code,
+and reproduces the original object C<$o>. While this does not work perfectly in
 all cases, it is very useful for debugging simple objects.
 N<For example, closures cannot easily be reproduced this way; if you
 don't know what a closure is don't worry. Also current implementations have
 problems with dumping cyclic data structures this way, but they are expected
-to be handled correctly by C<.perl> at some point.>
+to be handled correctly by C<$obj.perl> (C<$obj.raku>) at some point.>
 X<|^methods>
 C<$o.^methods(:local)> produces a list of L<Method|/type/Method>s that can be
 called on C<$o>. The C<:local> named argument limits the returned methods to
@@ -856,7 +856,7 @@ unsurprisingly returns the class name.
 Introspection is very useful for debugging and for learning the language
 and new libraries. When a function or method returns an object you don't
 know about, by finding its type with C<.^name>, seeing a construction recipe
-for it with C<.perl>, and so on, you'll get a good idea of what its return
+for it with C<.raku>, and so on, you'll get a good idea of what its return
 value is. With C<.^methods>, you can learn what you can do with the class.
 
 But there are other applications too. For instance, a routine that serializes

doc/Language/iterating.pod6

@@ -31,7 +31,7 @@ class DNA does Iterable {
 };
 
 my @longer-chain =  DNA.new('ACGTACGTT');
-say @longer-chain.perl;
+say @longer-chain.raku;
 # OUTPUT: «[("A", "C", "G"), ("T", "A", "C"), ("G", "T", "T")]␤»
 
 say  @longer-chain».join("").join("|"); #OUTPUT: «ACG|TAC|GTT␤»