Make examples compile

doc/Type/Cool.pod6

@@ -708,7 +708,7 @@ number of characters in the string. Please note that on the JVM, you currently g
 codepoints instead of graphemes.
 
     say 'møp'.chars;    # OUTPUT: «3␤»
-    say 'ã̷̠̬̊'.chars      # OUTPUT: «1␤»
+    say 'ã̷̠̬̊'.chars;      # OUTPUT: «1␤»
     say '👨‍👩‍👧‍👦🏿'.chars;      # OUTPUT: «1␤»
 
 X<|Grapheme> X<|NFG>
@@ -726,8 +726,8 @@ there are many other cases when this may happen. Another example is C<\c[ZWJ]>
 You can check C<Grapheme_Cluster_Break> property of a character in
 order to see how it is going to behave:
 
-    say ‘ã̷̠̬̊’.uniprops(‘Grapheme_Cluster_Break’) # OUTPUT: «(Other Extend Extend Extend Extend)␤»
-    say ‘👨‍👩‍👧‍👦🏿’.uniprops(‘Grapheme_Cluster_Break’) # OUTPUT: «(E_Base_GAZ ZWJ E_Base_GAZ ZWJ E_Base_GAZ ZWJ E_Base_GAZ E_Modifier)␤»
+    say ‘ã̷̠̬̊’.uniprops(‘Grapheme_Cluster_Break’); # OUTPUT: «(Other Extend Extend Extend Extend)␤»
+    say ‘👨‍👩‍👧‍👦🏿’.uniprops(‘Grapheme_Cluster_Break’); # OUTPUT: «(E_Base_GAZ ZWJ E_Base_GAZ ZWJ E_Base_GAZ ZWJ E_Base_GAZ E_Modifier)␤»
 
 You can read more about graphemes in the
 L<Unicode Standard|http://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries>,