update PPC id, and minor Markdown fixes

Author: book

ppcs/ppc0026-enhanced-regex-xx.md

@@ -3,7 +3,7 @@
 ## Preamble
 
     Author:  Karl Williamson <[email protected]>
-    ID:      KHW-0001
+    ID:      0026
     Status:  Draft
 
 ## Abstract
@@ -32,7 +32,7 @@ fixes that.
 ## Specification
 
 I propose adding a new opt-in feature.  Call it, for now, "feature
-enhanced_re_xx".  Within its scope, the /xx modifier would change things so
+`enhanced_re_xx`".  Within its scope, the /xx modifier would change things so
 that inside a bracketed character class [...], any vertical space would be
 treated as a blank, essentially ignored.  Any unescaped '#' would begin a
 comment that ends at the end of the line.
@@ -45,25 +45,31 @@ would be raised.
 
 And an unescaped '#' within a comment would raise a warning.  So
 
+```
  $a[$i] =~ qr/ [ a-z         # We need to match the lowercase alphabetics
                  ! @ # . *   # And certain punctuation
                  0-9         # And the digits (which can only occur in $a[0])
                ]
              /xx;
+```
 
 would warn.
 
 It might be that an unescaped '#' that isn't of the form \s+#\s+ should
 warn to catch things like if the above example's second line were just
 
+```
  !@#.*
+```
 
 Also, any comments inside [...] would check for an unescaped ']' on the same
 line after a '#', and raise a warning if found.  So, something like
 
+```
  $a[$i] =~ qr/ [ a-z  # . * ]
                [ A-Z ]
              /xx;
+```
 
 would warn.  Either escape the '#' or the ']' to suppress it, depending on what
 your intent was.