Author: sunnavy
Date: 2009-09-19 04:41:57 +0200 (Sat, 19 Sep 2009)
New Revision: 28294
Modified:
docs/Perl6/Spec/S02-bits.pod
docs/Perl6/Spec/S03-operators.pod
docs/Perl6/Spec/S04-control.pod
docs/Perl6/Spec/S09-data.pod
docs/Perl6/Spec/S11-modules.pod
docs/Perl6/Spec/S12-objects.pod
docs/Perl6/Spec/S22-package-format.pod
docs/Perl6/Spec/S28-special-names.pod
Log:
typo fix
Modified: docs/Perl6/Spec/S02-bits.pod
===================================================================
--- docs/Perl6/Spec/S02-bits.pod 2009-09-19 00:58:11 UTC (rev 28293)
+++ docs/Perl6/Spec/S02-bits.pod 2009-09-19 02:41:57 UTC (rev 28294)
@@ -2589,7 +2589,7 @@
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
Modified: docs/Perl6/Spec/S03-operators.pod
===================================================================
--- docs/Perl6/Spec/S03-operators.pod 2009-09-19 00:58:11 UTC (rev 28293)
+++ docs/Perl6/Spec/S03-operators.pod 2009-09-19 02:41:57 UTC (rev 28294)
@@ -101,7 +101,7 @@
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
Modified: docs/Perl6/Spec/S04-control.pod
===================================================================
--- docs/Perl6/Spec/S04-control.pod 2009-09-19 00:58:11 UTC (rev 28293)
+++ docs/Perl6/Spec/S04-control.pod 2009-09-19 02:41:57 UTC (rev 28294)
@@ -562,7 +562,7 @@
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
Modified: docs/Perl6/Spec/S09-data.pod
===================================================================
--- docs/Perl6/Spec/S09-data.pod 2009-09-19 00:58:11 UTC (rev 28293)
+++ docs/Perl6/Spec/S09-data.pod 2009-09-19 02:41:57 UTC (rev 28294)
@@ -556,7 +556,7 @@
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
Modified: docs/Perl6/Spec/S11-modules.pod
===================================================================
--- docs/Perl6/Spec/S11-modules.pod 2009-09-19 00:58:11 UTC (rev 28293)
+++ docs/Perl6/Spec/S11-modules.pod 2009-09-19 02:41:57 UTC (rev 28294)
@@ -381,7 +381,7 @@
class Dog:auth<http://www.some.com/~jrandom>:ver<1.2.1>;
class Dog:auth<mailto:jran...@some.com>: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
form:
Modified: docs/Perl6/Spec/S12-objects.pod
===================================================================
--- docs/Perl6/Spec/S12-objects.pod 2009-09-19 00:58:11 UTC (rev 28293)
+++ docs/Perl6/Spec/S12-objects.pod 2009-09-19 02:41:57 UTC (rev 28294)
@@ -752,7 +752,7 @@
$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 @@
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
Modified: docs/Perl6/Spec/S22-package-format.pod
===================================================================
--- docs/Perl6/Spec/S22-package-format.pod 2009-09-19 00:58:11 UTC (rev
28293)
+++ docs/Perl6/Spec/S22-package-format.pod 2009-09-19 02:41:57 UTC (rev
28294)
@@ -87,7 +87,7 @@
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
Modified: docs/Perl6/Spec/S28-special-names.pod
===================================================================
--- docs/Perl6/Spec/S28-special-names.pod 2009-09-19 00:58:11 UTC (rev
28293)
+++ docs/Perl6/Spec/S28-special-names.pod 2009-09-19 02:41:57 UTC (rev
28294)
@@ -45,7 +45,7 @@
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
