Mention the new .raku method

Author: MasterDuke17

doc/Language/faq.pod6

@@ -308,8 +308,9 @@ X<|Data::Dumper (FAQ)>
 Typical options are to use the L<say|/routine/say> routine that uses
 the L<gist|/routine/gist> method which gives the "gist" of the object being
 dumped. More detailed output can be obtained by calling the
-L<perl|/routine/perl> method that typically returns an object's representation
-in L<EVAL|/routine/EVAL>-able code.
+L<perl|/routine/perl> method (soon to be deprecated in favor of C<$obj.raku>,
+available since the Rakudo 2019.11 release) that typically returns an object's
+representation in L<EVAL|/routine/EVAL>-able code.
 
 If you're using the L<rakudo|https://rakudo.org> implementation, you can use
 the L«rakudo-specific C<dd> routine|/programs/01-debugging#Dumper_function_dd»
@@ -677,8 +678,8 @@ about the object deemed unimportant to understanding the essence of the object.
 
 Or phrased differently, C<$obj.Str> gives a string representation,
 C<$obj.gist> provides a short summary of that object suitable for
-fast recognition by a human, and C<$obj.perl> gives a Rakuish representation
-from which the object could be re-created.
+fast recognition by a human, and C<$obj.perl> (C<$obj.raku>) gives a Rakuish
+representation from which the object could be re-created.
 
 For example, when the C<Str> method is invoked on a type object, also known
 as an "undefined value", the type is stringified to an empty string
@@ -694,8 +695,8 @@ say $x;         # OUTPUT: «(Date)␤»
 
 If you'd like to show a debugging version of an object, it is probably better
 to use the L«rakudo-specific C<dd> routine|/programs/01-debugging#Dumper_function_dd».
-It essentially does a C<$obj.perl> and shows that on STDERR rather than STDOUT,
-so it won't interfere with any "normal" output of your program.
+It essentially does a C<$obj.perl> (C<$obj.raku>) and shows that on STDERR rather than
+STDOUT, so it won't interfere with any "normal" output of your program.
 
 In short, C<say> is optimized for casual human interpretation, C<dd> is optimized
 for casual debugging output and C<print> and C<put> are more generally suitable