pod6-> rakudoc updates

Author: coke

writing-docs/CREATING-NEW-DOCS.md

@@ -1,4 +1,4 @@
-### A new (or existing) pod6 document currently must adhere to the following conventions:
+### A new (or existing) rakudoc document currently must adhere to the following conventions:
 
 1. it must be valid Raku pod
 2. the first non-comment or non-empty line must be:

writing-docs/EXAMPLES.md

@@ -8,7 +8,7 @@ documentation with some example.
 Please use code blocks to highlight example code; any indented blocks
 are considered to be code, but you can specify the `=for code` directive, or a
 combination of `=begin code` and `=end code` to better control which
-blocks are considered. The POD6 directives also allow you to set
+blocks are considered. The rakudoc directives also allow you to set
 attributes for a block of code.
 
 When using a `=for code` directive or a `=begin code`/`=end code`
@@ -155,7 +155,7 @@ styles.
 ## Indented text
 
 4-space indented text is formatted as a code block. The indent is *not*
-part of the displayed code. It's not possible to add any POD6
+part of the displayed code. It's not possible to add any rakudoc
 directives on this style.
 
 ## =for code
@@ -167,7 +167,7 @@ is indented.
 ## =begin code / =end code
 
 The enclosed text is treated as code. The indentation level is
-relative to the indentation of the POD6 directives.
+relative to the indentation of the rakudoc directives.
 
 ##  Environment Variables
 

writing-docs/INDEXING.md

@@ -2,7 +2,7 @@
 
 ### Synopsis
 
-A term or a location in a Pod6 document can be indexed so that it is
+A term or a location in a rakudoc document can be indexed so that it is
 possible to create a named reference pointing to it. This can be used
 to generate a reference in the rendered version of the documentation or
 implement search function on the website hosting the rendered documentation.

writing-docs/STYLEGUIDE.md

@@ -222,7 +222,7 @@ spec items are available in.
 
 ## Use of HTML
 
-Generally, Pod6 should be more than enough for any
+Generally, rakudoc should be more than enough for any
 documentation. However, if you need to embed HTML into the
 documentation after thinking about it twice, bear in mind that we support
 the current and previous major releases of Chrome, Firefox, Edge,

writing-docs/TESTING.md

@@ -31,7 +31,7 @@ failing tests and someone will still review it.
 You can run the basic tests against a subset of files with
 
 ```
-$ TEST_FILES="doc/Language/faq.pod6 doc/Type/Complex.pod6" make test
+$ TEST_FILES="doc/Language/faq.rakudoc doc/Type/Complex.rakudoc" make test
 ```
 
 Or against everything that you haven't committed yet:
@@ -57,7 +57,7 @@ $ util/test-modified.sh
 Or to run specific files regardless of their git status:
 
 ```
-$ TEST_FILES="doc/Language/faq.pod6 doc/Type/Complex.pod6" make xtest
+$ TEST_FILES="doc/Language/faq.rakudoc doc/Type/Complex.rakudoc" make xtest
 ```
 
 If you see some tests are skipped (spelling or signature checks), that's fine.