More Perl 6 to raku changes

+ perl6 to raku in docs/ops.markdown
+ change file extensions in docs/release_guide
+ remove redundant link https://rakudo.perl6.org/downloads/rakudo/ because this link and https://rakudo.org/downloads/rakudo points to same site
+ reflect the change in file extensions .p6 to raku in helper scripts in tools folder in rakudo

docs/ops.markdown

@@ -82,27 +82,27 @@ This desugars to:
 ## p6bool
 * p6bool(Mu $value)
 
-Create a Perl 6 Bool from $value.
+Create a Raku Bool from $value.
 
 ## p6box_i
 * p6box_i(int $value)
 
-Box a native int into a Perl 6 Int.
+Box a native int into a Raku Int.
 
 ## p6box_n
 * p6box_n(num $value)
 
-Box a native num into a Perl 6 Num.
+Box a native num into a Raku Num.
 
 ## p6box_s
 * p6box_s(str $value)
 
-Box a native str into a Perl 6 Str.
+Box a native str into a Raku Str.
 
 ## p6box_u
 * p6box_u(uint $value)
 
-Box a native uint into a Perl 6 UInt.
+Box a native uint into a Raku UInt.
 
 ## p6capturelex
 * p6capturelex(Mu $closure)
@@ -141,7 +141,7 @@ Returns client's language version (`6.<rev>`). See [p6clientcorectx](#p6clientco
 ## p6clientctx
 * p6clientctx()
 
-Returns client's, i.e. the first Perl6 caller from different package, context.
+Returns client's, i.e. the first Raku caller from different package, context.
 
 ## p6configposbindfailover
 * p6configposbindfailover(Mu $type, Mu $failover-type)
@@ -169,7 +169,7 @@ to a _true_ value then lookup is performed only in client's SETTING.
 ## p6init
 * p6init()
 
-Initializes the GlobalContext extensions for Perl 6.
+Initializes the GlobalContext extensions for Raku.
 
 ## p6inpre
 * p6inpre()

docs/rakudo-nqp-and-pod-notes.md

@@ -172,13 +172,13 @@ process for later developers.
 Following is the start of a table to show the grammar tokens that have
 action methods and their resulting `.ast` values.
 
-| Actions method           | `made` (`ast`) value 
+| Actions method           | `made` (`ast`) value
 | ---                      | ---            
-| pod_textcontent          | 
-| pod_block:sym\<delimited> | QAST node [instance of Pod::Heading] 
-| pod_block:sym\<delimited> | QAST node [instance of Pod::Item] 
-| pod_block:sym\<delimited> | QAST node [instance of Pod::Defn] 
-| pod_block:sym\<delimited> | QAST node [instance of Pod::Block::Named] 
+| pod_textcontent          |
+| pod_block:sym\<delimited> | QAST node [instance of Pod::Heading]
+| pod_block:sym\<delimited> | QAST node [instance of Pod::Item]
+| pod_block:sym\<delimited> | QAST node [instance of Pod::Defn]
+| pod_block:sym\<delimited> | QAST node [instance of Pod::Block::Named]
 | pod_content:sym\<block>   | $<pod_block>.ast;
 | pod_content_toplevel     | $<pod_block>.ast
 

docs/release_guide.pod

@@ -35,7 +35,7 @@ Currently there are two tools:
 =item *
 L<Release Sakefile|https://github.com/rakudo/rakudo/blob/master/tools/releasable/Sakefile>
 which is meant to be used together with
-L<Releasable|https://github.com/perl6/whateverable/wiki/Releasable> bot
+L<Releasable|https://github.com/Raku/whateverable/wiki/Releasable> bot
 
 =item *
 L<NeuralAnomaly|https://github.com/zoffixznet/na> bot
@@ -92,13 +92,13 @@ etc. as appropriate.
   git add docs/announce/YYYY.MM.md
   git commit docs
 
-There is a helper script C<tools/create-release-announcement.p6> that
+There is a helper script C<tools/create-release-announcement.raku> that
 will create a basic release announcement for you based on the state
 of the repository and the current date.  Feel free to use it to
 save yourself some time, but please look over its output if you decide
 to use it:
 
-    ./perl6 tools/create-release-announcement.p6 > docs/announce/YYYY.MM.md
+    ./raku tools/create-release-announcement.raku > docs/announce/YYYY.MM.md
 
 =item *
 
@@ -114,7 +114,7 @@ To spot more regressions, it’s a good idea to test the ecosystem and see
 if there are any modules that were working correctly (e.g. passing their
 tests) on the previous release but no longer work on HEAD. One of the
 tools to do that is
-L<Blin|https://github.com/perl6/Blin>.
+L<Blin|https://github.com/Raku/Blin>.
 
 Generally, any kind of breakage in modules is unwanted, but there are
 exceptions. Submit Pull Requests to anything that is affected and file
@@ -140,7 +140,7 @@ Update Rakudo’s leap-second tables:
 
   perl tools/update-tai-utc.pl
 
-If a new leap second has been announced, F<src/core/Rakudo/Internals.pm>
+If a new leap second has been announced, F<src/core.c/Rakudo/Internals.pm6>
 will be modified, so commit the new version. B<Note:> be sure to double
 check the modifications are correct before committing.
 
@@ -172,14 +172,14 @@ new release is significant.
 Include a list of contributors since the last release in the announcement.
 You can get an automatically generated list by running
 
-  ./perl6 tools/contributors.p6
+  ./raku tools/contributors.raku
 
 To obtain all contributors, ensure you have all supporting repositories
 checked out, before running (this can be achieved by building rakudo
 and running a spectest). Please check the result manually for duplicates
-and other errors. Note that you may not be able to run your system perl6
+and other errors. Note that you may not be able to run your system raku
 in a local checkout, you may have to wait until you build in this
-directory and use C<./perl6>.
+directory and use C<./raku>.
 
   git add docs/announce/YYYY.MM.md
   git commit docs
@@ -205,7 +205,7 @@ status). It is also a good idea to look for JVM issues at this point.
 
 Create an NQP release with the same C<YYYY.MM> version number
 as Rakudo. Follow NQP’s
-L<docs/release_guide.pod|https://github.com/perl6/nqp/blob/master/docs/release_guide.pod>
+L<docs/release_guide.pod|https://github.com/Raku/nqp/blob/master/docs/release_guide.pod>
 file to do that.
 
 =item 8.
@@ -245,7 +245,7 @@ Install Inline::Perl5 so stresstest can use it.
 
   git clone https://github.com/ugexe/zef
   export PATH=`pwd`/install/bin:$PATH
-  cd zef; perl6 -Ilib bin/zef install .
+  cd zef; raku -Ilib bin/zef install .
   cd ..
   export PATH=`pwd`/install/share/perl6/site/bin:$PATH
   zef install Inline::Perl5
@@ -331,17 +331,15 @@ Sign the tarball with your PGP key:
 
 =item 18.
 
-Upload the tarball and the signature to L<http://rakudo.org/downloads/rakudo>
-and L<https://rakudo.perl6.org/downloads/rakudo/>:
+Upload the tarball and the signature to L<http://rakudo.org/downloads/rakudo>:
 
   scp rakudo-YYYY.MM.tar.gz rakudo-YYYY.MM.tar.gz.asc \
        rakudo@rakudo.org:public_html/downloads/rakudo/
-  scp rakudo-YYYY.MM.tar.gz rakudo-YYYY.MM.tar.gz.asc \
-       rakudo@www.p6c.org:public_html/downloads/rakudo/
+
 
 If you do not have permissions for that, ask one of (jnthn,
 masak, tadzik, moritz, [Coke], lizmat, timotimo,
- AlexDaniel) on #perl6 or #perl6-dev to do it for you.
+ AlexDaniel) on #raku or #raku-dev to do it for you.
 
 =item 19.