Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Fix typos.
  • Loading branch information
Util committed Nov 13, 2011
1 parent d2a7270 commit 59b0ea5
Show file tree
Hide file tree
Showing 6 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion S03-operators.pod
Expand Up @@ -2905,7 +2905,7 @@ You do still need them on the left for

since assignment operators are tighter than comma to their left.

"Don't care" positions may be indicated by assigment to the C<*> token.
"Don't care" positions may be indicated by assignment to the C<*> token.
A final C<*> throws away the rest of the list:

($a, *, $c) = 1, 2, 3; # throw away the 2
Expand Down
2 changes: 1 addition & 1 deletion S04-control.pod
Expand Up @@ -1399,7 +1399,7 @@ of these can occur multiple times within the block. So they aren't
really traits, exactly--they add themselves onto a list stored in the
actual trait (except for C<START>, which executes inline). So if you
examine the C<ENTER> trait of a block, you'll find that it's really
a list of phasers rather than a single phaser. In general, initalizing
a list of phasers rather than a single phaser. In general, initializing
phasers execute in order declare, while finalizing phasers execute in
the opposite order.

Expand Down
2 changes: 1 addition & 1 deletion S05-regex.pod
Expand Up @@ -4362,7 +4362,7 @@ or

s[pattern] = qq[replacement]

This is not a normal assigment, since the right side is evaluated each
This is not a normal assignment, since the right side is evaluated each
time the substitution matches (much like the pseudo-assignment to declarators
can happen at strange times). It is therefore treated as a "thunk", that is,
it will be called as a chunk of code that creates a dynamic scope but not a
Expand Down
2 changes: 1 addition & 1 deletion S06-routines.pod
Expand Up @@ -2364,7 +2364,7 @@ readonly properties:
copy True if the parameter has C<is copy> trait
named True if the parameter is to be passed named
named_names List of names a named parameter can be passed as
capture True if the paramater binds the caller's Capture
capture True if the parameter binds the caller's Capture
parcel True if the parameter is too lazy to contextualize
slurpy True if the parameter is slurpy
optional True if the parameter is optional
Expand Down
2 changes: 1 addition & 1 deletion S26-documentation.pod
Expand Up @@ -1573,7 +1573,7 @@ just regular Pod blocks and may appear anywhere within a source file, and as
many times as required.
There is a corresponding variable, C<$=data>, from which each C<=data> block
can be retreived. C<$=data> holds an object that does both the Associative
can be retrieved. C<$=data> holds an object that does both the Associative
and Positional roles.
Each C<=data> block can be given a C<:key> option, to name it. The contents
Expand Down
2 changes: 1 addition & 1 deletion S32-setting-library/IO.pod
Expand Up @@ -71,7 +71,7 @@ X<dir>

Returns a lazy list of file names in the C<$directory>. By default the current
and the parent directory are excluded, which can be controlled with the
C<$test> named paramater. Only items that smart-match against this test are
C<$test> named parameter. Only items that smart-match against this test are
returned.

=item getc
Expand Down

0 comments on commit 59b0ea5

Please sign in to comment.