brace/bracket cleanup

doc/Language/pod.pod6

@@ -115,10 +115,10 @@ Declarator blocks differ from the others by not having a specific type,
 instead they are attached to some source code.
 
 Declarator blocks are introduced by a special comment: either C<#|> or C<#=>,
-which must be immediately followed by either a space or an opening curly bracket.
+which must be immediately followed by either a space or an opening curly brace.
 If followed by a space, the block is terminated by the end of line;
-if followed by one or more opening curly brackets, the block is terminated by the matching
-sequence of closing curly brackets.
+if followed by one or more opening curly braces, the block is terminated by the matching
+sequence of closing curly braces.
 
 Blocks starting with C<#|> are attached to the code after them,
 and blocks starting with C<#=> are attached to the code before them.

doc/Language/syntax.pod6

@@ -196,10 +196,10 @@ That says why we do what we do below.
 say "No more";
 =end code
 
-Brackets inside the comment can be nested, so in C<#`{ a { b } c }>, the comment
-goes until the very end of the string. You may also use more complex
-brackets/braces, such as C<#`{{ double-curly-brace }}>, which might help
-disambiguate from nested brackets/braces. You can embed these comments in
+Curly braces inside the comment can be nested, so in C<#`{ a { b } c }>, the comment
+goes until the very end of the string. You may also use multiple curly
+braces, such as C<#`{{ double-curly-brace }}>, which might help
+disambiguate from nested delimiters. You can embed these comments in
 expressions, as long as you don't insert them in the middle of keywords or
 identifiers.
 
@@ -837,7 +837,7 @@ rules.
 
 Several packages may be declared in a single file. However, you can declare a C<unit> package
 at the start of the file (preceded only by comments or C<use> statements), and the
-rest of the file will be taken as being the body of the package. In this case, the curl brackets are not required.
+rest of the file will be taken as being the body of the package. In this case, the curly braces are not required.
 
 =begin code :solo
 unit module M;