Browse files

typo fix

git-svn-id: c213334d-75ef-0310-aa23-eaa082d1ae64
  • Loading branch information...
1 parent c2db802 commit 023d54beb9ae64355bdf9aa34cc3a6b695e3949b sunnavy committed Sep 19, 2009
Showing with 9 additions and 9 deletions.
  1. +1 −1 S02-bits.pod
  2. +1 −1 S03-operators.pod
  3. +1 −1 S04-control.pod
  4. +1 −1 S09-data.pod
  5. +1 −1 S11-modules.pod
  6. +2 −2 S12-objects.pod
  7. +1 −1 S22-package-format.pod
  8. +1 −1 S28-special-names.pod
2 S02-bits.pod
@@ -2589,7 +2589,7 @@ and the like--see S05.
The C<qw/foo bar/> quote operator now has a bracketed form: C<< <foo bar> >>.
When used as a subscript it performs a slice equivalent to C<{'foo','bar'}>.
-Elsewhere it is equivalent to a parenthesisized list of strings:
+Elsewhere it is equivalent to a parenthesized list of strings:
C<< ('foo','bar') >>. Since parentheses are generally reserved just for
precedence grouping, they merely autointerpolate in list context. Therefore
2 S03-operators.pod
@@ -101,7 +101,7 @@ associativity, but user-defined operators and precedence levels may mix
right and left associative operators at the same precedence level.
If two conflicting operators are used ambiguously in the same
expression, the operators will be considered non-associative with
-respect to each other, and parentheses must be used to disambiguoate.
+respect to each other, and parentheses must be used to disambiguate.
If you don't see your favorite operator above, the following
sections cover all the operators in precedence order. Basic operator
2 S04-control.pod
@@ -562,7 +562,7 @@ or equivalently, using placeholders:
Since C<do> is defined as going in front of a statement, it follows
that it can always be followed by a statement label. This is particularly
-useful for the do-once block, since it is offically a loop and can take
+useful for the do-once block, since it is officially a loop and can take
therefore loop control statements.
=head2 Statement-level bare blocks
2 S09-data.pod
@@ -556,7 +556,7 @@ representing an infinite dimension is necessarily represented lazily.
cartesian product of the key slice dimensions is not guaranteed to
index existing elements in every case. That is, this is not intended
to reflect current combinations of keys in use (use C<:k> for that).
-Note that you have to distingish these two forms:
+Note that you have to distinguish these two forms:
@array[].shape # the integer indices
@array{}.shape # the user-defined indices
2 S11-modules.pod
@@ -381,7 +381,7 @@ For example:
class Dog:auth<>:ver<1.2.1>;
class Dog:auth<>:ver<1.2.1>;
-Since these are somewhat unweildy to look at, we allow a shorthand in
+Since these are somewhat unwieldy to look at, we allow a shorthand in
which a bare subscripty adverb interprets its elements according to their
4 S12-objects.pod
@@ -752,7 +752,7 @@ call C<CREATE> yourself and then pass the resulting candidate to C<.bless>:
$object = $class.bless($candidate, :k1($v1), :k2($v2))
For the built-in default C<CREATE> method, C<P6opaque> is the default
-representation. Other possiblilities are C<P6hash>, C<P5hash>,
+representation. Other possibilities are C<P6hash>, C<P5hash>,
C<P5array>, C<PyDict>, C<Cstruct>, etc.
The C<bless> function automatically calls all appropriate C<BUILD>
@@ -1604,7 +1604,7 @@ Note the difference between:
Day $n where 1 <= * <= 5 # 1..5
The first C<where> is considered dynamic not because of the nature
-of the comparsons but because C<Int> is not finitely enumerable.
+of the comparisons but because C<Int> is not finitely enumerable.
Our C<Weekday> subset type can calculate the set membership at compile
time because it is based on the C<Day> enum, and hence is considered
static despite the use of a C<where>. Had we based C<Weekday> on
2 S22-package-format.pod
@@ -87,7 +87,7 @@ These files are created in step 3 of the C<General Flow>
C<JIB> is a simple 3 letter combination that's not yet 'taken' as
a known extension. It's purposely not perl specific, as there's nothing
-about the C<JIB> specification that's limitin it to perl only.
+about the C<JIB> specification that's limiting it to perl only.
# XXX - Also C<package> is carrying double meaning in P6 as both namespace
and source distribution. Can we remove the former meaning and refer to them
2 S28-special-names.pod
@@ -45,7 +45,7 @@ not modifiable at run time. This does not mean that the variable has the
same value everywhere; for instance, C<$?LINE> is different on every line
of the program.
-The C<$*foo> variables function both as dymamically scoped variables
+The C<$*foo> variables function both as dynamically scoped variables
and as globals. Globalness is relative, in other words. Any dynamic
scope may modify the set of globals visible via the C<$*foo> notation.
Most of the standard globals listed below actually live either in

0 comments on commit 023d54b

Please sign in to comment.