Small POD and typographical fixes

Raku · Apr 4, 2015 · 5da63dc · 5da63dc
1 parent 8e1c6ee
commit 5da63dc
Show file tree

Hide file tree

Showing 6 changed files with 11 additions and 8 deletions.
diff --git a/S02-bits.pod b/S02-bits.pod
@@ -297,7 +297,7 @@ backslashing conventions in surrounding cultures.  Hence you must write an
 explicit whitespace match some other way, such as with quotes or with a
 C<\x20> or C<\c32> escape.  On the other hand, while an unspace can start
 with C<\#> in normal code, C<\#> within a regex is specifically allowed, and
-is not taken as unspace, but matches a literal U+0023, NUMBER SIGN.  (Within
+is not taken as unspace, but matches a literal C<U+0023> (NUMBER SIGN).  (Within
 a character class, you may also escape whitespace with a backslash; the
 restriction on unspace applies only at the normal pattern-matching level.)
 

diff --git a/S03-operators.pod b/S03-operators.pod
@@ -1110,7 +1110,7 @@ C<< infix:<~> >>, string/buffer concatenation
 
 =item *
 
-C<< infix:<&> >>, all() operator
+C<< infix:<&> >>, C<all()> operator
 
     $a & $b & $c ...
 
@@ -1136,7 +1136,7 @@ tests don't pass.  This cannot be guaranteed by:
 
 =item *
 
-C<< infix:<|> >>, any() operator
+C<< infix:<|> >>, C<any()> operator
 
     $a | $b | $c ...
 
@@ -1159,7 +1159,7 @@ of safety:
 
 =item *
 
-C<< infix:<^> >>, one() operator
+C<< infix:<^> >>, C<one()> operator
 
     $a ^ $b ^ $c ...
 

diff --git a/S05-regex.pod b/S05-regex.pod
@@ -2221,7 +2221,7 @@ defined as any of:
     U+2028  LINE SEPARATOR
     U+2029  PARAGRAPH SEPARATOR
 
-Note that U+000D CARRIAGE RETURN (CR) is considered vertical whitespace despite
+Note that C<U+000D> (CARRIAGE RETURN) is considered vertical whitespace despite
 the fact that it only moves the "carriage" horizontally.
 
 =item *

diff --git a/S19-commandline.pod b/S19-commandline.pod
@@ -588,14 +588,17 @@ I don't have a solution, but perhaps pass a closure that evaluates to an Int?
 This should try to use whatever option does the same thing to a new
 filehandle when S16 is further developed.
 
-=for consideration
+=begin consideration
+
 [probably a setter method on $*IN of some sort?  --law]
 
 Sandboxing? maybe -r
 
 Env var? maybe -E.
 Could be posed in terms of substituting a different setting.
 
+=end consideration
+
 =head1 AUTHORS
 
     Jerry Gay <jerry.gay@rakudoconsulting.com>

diff --git a/S28-special-names.pod b/S28-special-names.pod
@@ -2,7 +2,7 @@
 
 =head1 TITLE
 
- [DRAFT] Synopsis 28 - Special Names [DRAFT]
+[DRAFT] Synopsis 28 - Special Names [DRAFT]
 
 =head1 VERSION
 

diff --git a/S29-functions.pod b/S29-functions.pod
@@ -4,7 +4,7 @@
 
 Synopsis 29: Builtin Functions
 
-=head1 Version
+=head1 VERSION
 
     Created: 12 Mar 2005