Checks content on Pod6 tables

Only some changes here and there, but it checks the item on "more well-defined pod tables" in #2632, since it seemt to have been written after that.

Author: JJ

doc/Language/pod.pod6

@@ -774,7 +774,7 @@ perl6 --doc=Markdown input.pod6 > output.md
 
 =head2 Text
 
-In order to generate Text from Pod, you can use the default
+In order to generate text from Pod, you can use the default
 C<Pod::To::Text> module.
 
 Using the terminal, run the following command:

doc/Language/tables.pod6

@@ -4,10 +4,10 @@
 
 =SUBTITLE The good, the bad and the ugly
 
-The official specification for Perl 6 POD tables is located in the
+The official specification for Pod 6 tables is located in the
 Documentation specification here:
 L<Tables|https://raw.githubusercontent.com/perl6/specs/master/S26-documentation.pod>.
-Although Pod 6 specifications are not completely handled properly yet,
+Although Pod 6 specifications are not completely and properly handled yet,
 several projects are ongoing to correct the situation; one such
 project is ensuring the proper handling of Pod 6 tables.
 
@@ -38,11 +38,13 @@ V<'|'>, and V<'='>.
 
 5. Leading and trailing row-separator lines generate a warning.
 
-6. Formatting blocks in table cells currently are ignored and treated as plain text.
+6. Formatting blocks in table cells are currently ignored and treated as
+plain text.
 
 HINT: During development, use of the environment variable C<RAKUDO_POD6_TABLE_DEBUG>
-will show you how Rakudo interprets your pod tables before they are passed
-to renderers such as B<Pod::To::HTML>, B<Pod::To::Text>, and B<Pod::To::Markdown>.
+will show you how Rakudo interprets your Pod tables before they are passed
+to renderers such as C<Pod::To::HTML>, C<Pod::To::Text>, and
+C<Pod::To::Markdown>.
 
 =head1 Best practices