Cleaning up "Separating statements by semicolons" (#1479)

* Cleaning up "Separating statements by semicolons"

Trying to address #1477

* More explanation, postcircumfix exception

* More concise trailing statement explanation

* removed mention of postcircumfix blocks

Deleting to avoid confusion

Author: molecules

doc/Language/syntax.pod6

@@ -76,35 +76,58 @@ routine argument lists.
 =head2 Separating Statements with Semicolons
 
 A Perl 6 program is a list of statements, separated by semicolons C<;>.
+
+=begin code
+say "Hello";
+say "world";
+=end code
+
 A semicolon after the final statement (or after the final statement inside a
-block) is optional, though it's good form to include it.
+block) is optional.
+
+=begin code
+say "Hello";
+say "world"
+=end code
 
 =begin code
 if True {
-    say "Hello";
+    say "Hello"
 }
-say "world";
+say "world"
 =end code
 
-Both semicolons are optional here, but leaving them out increases the chance
-of syntax errors when adding more lines later.
-
 =head2 Implied Separator Rule (for statements ending in blocks)
 
-Complete statements ending in blocks can omit the trailing semicolon, if no
+Complete statements ending in bare blocks can omit the trailing semicolon, if no
 additional statements on the same line follow the block's closing curly
 brace C<}>. This is called the "implied separator rule". For example, you
-don't need to write a semicolon after an C<if> statement block as seen above.
+don't need to write a semicolon after an C<if> statement block as seen above, and
+below.
+
+=begin code
+if True { say "Hello" }
+say "world";
+=end code
 
-If you want additional statements to trail the block, you do need to include
-a semicolon between the block and the statement.
+However, semicolons are required to separate a block from trailing statements in
+the same line.
 
 =begin code
 if True { say "Hello" }; say "world";
 #                     ^^^ this ; is required
 =end code
 
-However, for a series of blocks that are part of the same C<if>/C<elsif>/C<else> (or similar)
+This implied statement separator rule applies in other ways, besides control
+statements, that could end with a bare block. For example, in combination with
+the colon C<:> syntax for method calls.
+
+=begin code
+my @names = <Foo Bar Baz>;
+my @upper-case-names = @names.map: { .uc }    # OUTPUT: [FOO BAR BAZ]
+=end code
+
+For a series of blocks that are part of the same C<if>/C<elsif>/C<else> (or similar)
 construct, the implied separator rule only applies at the end of the last block of that series.
 These three are equivalent:
 
@@ -125,16 +148,6 @@ else    { say "Goodbye" } # <- no semicolon required because it ends in a block
 say "world";
 =end code
 
-But, remember, this implied statement separator rule applies in other ways that
-statements could end with block. For example, in combination with the colon C<:>
-syntax for method calls:
-
-=begin code
-my @names = <Foo Bar Baz>;
-my @upper-case-names = @names.map: { .uc }
-# [FOO BAR BAZ]
-=end code
-
 =head2 Comments
 
 Comments are parts of the program text only intended for human readers, and