Browse files

fix a few typos

  • Loading branch information...
1 parent d5f5207 commit 069844941129709f58654508bafc0d0fd9e63ba0 @felher felher committed Feb 25, 2012
Showing with 8 additions and 8 deletions.
  1. +2 −2 S02-bits.pod
  2. +1 −1 S07-iterators.pod
  3. +1 −1 S09-data.pod
  4. +1 −1 S10-packages.pod
  5. +1 −1 S12-objects.pod
  6. +2 −2 S32-setting-library/Containers.pod
View
4 S02-bits.pod
@@ -4126,7 +4126,7 @@ for method calls is distinguished from sub calls, it is only unrecognized
sub calls that must be treated specially.
You still must declare your subroutines, but a bareword with an unrecognized
-name is provisionally compiled as a subroutine call, on that assumption that
+name is provisionally compiled as a subroutine call, on the assumption that
such a declaration will occur by the end of the current compilation unit:
foo; # provisional call if neither &foo nor ::foo is defined so far
@@ -4519,7 +4519,7 @@ value without a stringy allomorphism. Put spaces to override that:
<1/2> # a Rat
< 1/2 > # a RatStr
-Or use the the C<«»> form of quotewords, which is always allomorphic:
+Or use the C<«»> form of quotewords, which is always allomorphic:
«1/2» # a RatStr
« 1/2 » # a RatStr
View
2 S07-iterators.pod
@@ -70,7 +70,7 @@ workahead by use of pragmas.
I/O from a file may generally be assumed to be finite, but I/O
from a socket may not. However, since the definition of "finite"
is somewhat dependent on available memory, a file that is too big
-may be reasonably be treated lazily. In any case, there should be no
+may reasonably be treated lazily. In any case, there should be no
profound semantic differences between "mostly lazy" and "mostly eager".
They are primarily just hints to the implementation as to whether
you are likely to want to use all the values in the list. Nothing
View
2 S09-data.pod
@@ -1270,7 +1270,7 @@ autovivification is defined in terms of type objects rather than failure,
it still works under "use fatal".
This table solidifies the intuition that an operation pertaining to some data
-structure causes the type object to autivivify to such an object:
+structure causes the type object to autovivify to such an object:
operation autovivifies to
========= ===============
View
2 S10-packages.pod
@@ -127,7 +127,7 @@ the module is merely used/needed elsewhere.
A declaration of any object of the form C<A::B::c> also creates (if needed)
an empty package C<A>, and an empty package C<B> inside of C<A>, in addition to creating
-C<c> inside of C<B>. Such empty packages may be subsequently be redeclared as any other
+C<c> inside of C<B>. Such empty packages may subsequently be redeclared as any other
package-like object (module, class, etc.), and no redeclaration warning will be issued
for such a redeclaration. If a parent package already exists, no stub package
needs to be created, and no declaration of the form C<A::B::c> has anything
View
2 S12-objects.pod
@@ -1793,7 +1793,7 @@ list, or an equivalent angle bracket list:
=head2 Value Generation
-The values are generated implicitly by default, but may be also be
+The values are generated implicitly by default, but may also be
specified explicitly. If the first value is unspecified, it defaults
to 0. To specify the first value, use pair notation (see below).
View
4 S32-setting-library/Containers.pod
@@ -128,13 +128,13 @@ The following are defined in the C<List> role/class:
multi method new(*@args --> List )
-Constructs an C<List> that can visit all iterable elements of the all the arguments.
+Constructs an C<List> that can visit all iterable elements of all the arguments.
=item list
sub list(*@args --> List )
-Constructs an C<List> that can visit all iterable elements of the all the arguments.
+Constructs an C<List> that can visit all iterable elements of all the arguments.
=item cat

0 comments on commit 0698449

Please sign in to comment.