Skip to content

Commit 5da63dc

Browse files
committed
Small POD and typographical fixes
1 parent 8e1c6ee commit 5da63dc

File tree

6 files changed

+11
-8
lines changed

6 files changed

+11
-8
lines changed

S02-bits.pod

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -297,7 +297,7 @@ backslashing conventions in surrounding cultures. Hence you must write an
297297
explicit whitespace match some other way, such as with quotes or with a
298298
C<\x20> or C<\c32> escape. On the other hand, while an unspace can start
299299
with C<\#> in normal code, C<\#> within a regex is specifically allowed, and
300-
is not taken as unspace, but matches a literal U+0023, NUMBER SIGN. (Within
300+
is not taken as unspace, but matches a literal C<U+0023> (NUMBER SIGN). (Within
301301
a character class, you may also escape whitespace with a backslash; the
302302
restriction on unspace applies only at the normal pattern-matching level.)
303303

S03-operators.pod

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1110,7 +1110,7 @@ C<< infix:<~> >>, string/buffer concatenation
11101110

11111111
=item *
11121112

1113-
C<< infix:<&> >>, all() operator
1113+
C<< infix:<&> >>, C<all()> operator
11141114

11151115
$a & $b & $c ...
11161116

@@ -1136,7 +1136,7 @@ tests don't pass. This cannot be guaranteed by:
11361136

11371137
=item *
11381138

1139-
C<< infix:<|> >>, any() operator
1139+
C<< infix:<|> >>, C<any()> operator
11401140

11411141
$a | $b | $c ...
11421142

@@ -1159,7 +1159,7 @@ of safety:
11591159

11601160
=item *
11611161

1162-
C<< infix:<^> >>, one() operator
1162+
C<< infix:<^> >>, C<one()> operator
11631163

11641164
$a ^ $b ^ $c ...
11651165

S05-regex.pod

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2221,7 +2221,7 @@ defined as any of:
22212221
U+2028 LINE SEPARATOR
22222222
U+2029 PARAGRAPH SEPARATOR
22232223

2224-
Note that U+000D CARRIAGE RETURN (CR) is considered vertical whitespace despite
2224+
Note that C<U+000D> (CARRIAGE RETURN) is considered vertical whitespace despite
22252225
the fact that it only moves the "carriage" horizontally.
22262226

22272227
=item *

S19-commandline.pod

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -588,14 +588,17 @@ I don't have a solution, but perhaps pass a closure that evaluates to an Int?
588588
This should try to use whatever option does the same thing to a new
589589
filehandle when S16 is further developed.
590590

591-
=for consideration
591+
=begin consideration
592+
592593
[probably a setter method on $*IN of some sort? --law]
593594

594595
Sandboxing? maybe -r
595596

596597
Env var? maybe -E.
597598
Could be posed in terms of substituting a different setting.
598599

600+
=end consideration
601+
599602
=head1 AUTHORS
600603

601604
Jerry Gay <jerry.gay@rakudoconsulting.com>

S28-special-names.pod

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
=head1 TITLE
44

5-
[DRAFT] Synopsis 28 - Special Names [DRAFT]
5+
[DRAFT] Synopsis 28 - Special Names [DRAFT]
66

77
=head1 VERSION
88

S29-functions.pod

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
Synopsis 29: Builtin Functions
66

7-
=head1 Version
7+
=head1 VERSION
88

99
Created: 12 Mar 2005
1010

0 commit comments

Comments
 (0)