Slight additional editing for clarity and correctness

doc/Language/tables.pod6

@@ -86,10 +86,10 @@ of the table.  For example,
 =end table
 =end code
 
-5. For tables with many rows and no multi-line content, blank line row
-separators are fine.  However, with one or more rows with multi-line
-content, it is easier to ensure proper results by using a visible row
-separator line between every content row.
+5. For tables with many rows and no multi-line content, using no row
+separators is fine.  However, with one or more rows with multi-line
+content, it is easier to ensure proper results by using a row
+separator line (visible or invisible) between every content row.
 
 =head1 Good Tables
 
@@ -195,7 +195,7 @@ Following are examples of invalid (Bad) tables, and they should
 trigger an unhandled exception during parsing.  They are taken from
 tests used in the table-pod-fix project mentioned above.  After
 acceptance of the project's code into the Rakudo source, they will be
-added to the current C<Specification Tests>.  Note they may not trigge
+added to the current C<Specification Tests>.  Note they may not trigger
 an exception at the moment, but they will after the project's code is
 integrated.