Update implied separator rule explanation in syntax.rakudoc

Clarify the implied separator rule for lines ending in the closing curly brace of a block or hash literal.

Author: raiph

doc/Language/syntax.rakudoc

@@ -102,15 +102,20 @@ if True {
 say "world"
 =end code
 
-=head2 Implied separator rule (for statements ending in blocks)
+=head2 Implied separator rule
 
-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, and below.
+If the last code on a line (excluding an end of line comment) is the
+closing curly brace of either a block or a hash constructor literal,
+and it can be syntactically validly interpreted as the end of a
+statement, then a trailing semicolon is optional (and is typically
+omitted).
+
+For example, you don't need to write a semicolon after assigning a
+curly braced literal hash to a variable, or after an C<if> statement
+block as seen above and below.
 
 =begin code
+my $hash = { :foo, :bar }
 if True { say "Hello" }
 say "world";
 =end code
@@ -124,8 +129,9 @@ if True { say "Hello" }; say "world";
 =end code
 
 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.
+control statements, that could end with a bare block or curly brace
+hash literal. For example, in combination with the colon C<:> syntax
+for method calls.
 
 =begin code
 my @names = <Foo Bar Baz>;