Permalink
Browse files

[docs] Misspellings caught by ispell

  • Loading branch information...
1 parent c41bcd7 commit 44f0ec0cd95b0fb257946dc7dd9c33aefc7ff882 @kyleha kyleha committed Aug 13, 2010
Showing with 4 additions and 4 deletions.
  1. +1 −1 docs/S11-Modules-proposal.pod
  2. +3 −3 docs/guide_to_setting.pod
View
2 docs/S11-Modules-proposal.pod
@@ -109,7 +109,7 @@ Consider the example "use Foo::Bar:ver<1.2.3>:auth<baz>"
Rakudo * will look for files matching Foo/Bar.pm and Foo/Bar.*.pm from
every starting point listed in @*INC. Rakudo will then open each file
in turn and partially (how?) parse the content to extract the first :ver
-and :auth values, building a list of the results. Cacheing will
+and :auth values, building a list of the results. Caching will
probably be added soon after the initial implementation works, in order to
reduce the obvious overheads.
View
6 docs/guide_to_setting.pod
@@ -40,7 +40,7 @@ especially if they follow these guidelines:
=over
-=item Think of lazyness
+=item Think of laziness
At some point in the hopefully not-so-distant future Lists will become
lazy by default. So you should try to avoid anything that forces eager
@@ -50,7 +50,7 @@ This is bad:
while $i < self.elems { ... }
-Better use a C<for> loop, which will respect lazyness
+Better use a C<for> loop, which will respect laziness
for self.list { ... }
@@ -85,7 +85,7 @@ All built-in methods or subroutines should be declared as C<multi>.
If a method doesn't take any arguments, give it an explicit empty
signature C<()>. That's very different from omitting the signature
-alltogether (which would be an implicit caatch-all signature).
+altogether (which would be an implicit catch-all signature).
=item Use implicit return at the end of routines

0 comments on commit 44f0ec0

Please sign in to comment.