Skip to content
Browse files

Fix spelling in rakefile.rdoc

  • Loading branch information...
1 parent 0e555e3 commit d459276f620dcbf55f03e1e183e62af593858d63 @chrisk chrisk committed Oct 19, 2009
Showing with 12 additions and 12 deletions.
  1. +12 −12 doc/rakefile.rdoc
View
24 doc/rakefile.rdoc
@@ -45,7 +45,7 @@ following ...
Actions are defined by passing a block to the +task+ method. Any Ruby
code can be placed in the block. The block may reference the task
-object via the block paramter..
+object via the block parameter.
task :name => [:prereq1, :prereq2] do |t|
# actions (may reference t)
@@ -119,14 +119,14 @@ Rake allows parallel execution of prerequisites using the following syntax:
end
In this example, +copy_files+ is a normal rake task. Its actions are
-executed whereever all of its prerequisites are done. The big
+executed whenever all of its prerequisites are done. The big
difference is that the prerequisites (+copy_src+, +copy_bin+ and
+copy_doc+) are executed in parallel. Each of the prerequisites are
run in their own Ruby thread, possibly allowing faster overall runtime.
=== Secondary Prerequisites
-If any of the primary prerequites of a multitask have common secondary
+If any of the primary prerequisites of a multitask have common secondary
prerequisites, all of the primary/parallel prerequisites will wait
until the common prerequisites have been run.
@@ -196,7 +196,7 @@ or
RELEASE_VERSION rake release
will work. Environment variable names must either match the task
-parameter exactly, or match an all uppcase version of the task
+parameter exactly, or match an all-uppercase version of the task
parameter.
=== Tasks that Expect Parameters
@@ -211,10 +211,10 @@ declared as:
task :name, [:first_name, :last_name]
The first argument is still the name of the task (:name in this case).
-The next to argumements are the names of the parameters expected by
+The next two arguments are the names of the parameters expected by
:name in an array (:first_name and :last_name in the example).
-To access the values of the paramters, the block defining the task
+To access the values of the parameters, the block defining the task
behaviour can now accept a second parameter:
task :name, [:first_name, :last_name] do |t, args|
@@ -259,9 +259,9 @@ dependencies. That format is still supported for compatibility, but
is not recommended for use. The older format may be dropped in future
versions of rake.
-== Accessing Task Programatically
+== Accessing Task Programmatically
-Sometimes it is useful to manipulate tasks programatically in a
+Sometimes it is useful to manipulate tasks programmatically in a
Rakefile. To find a task object, use the <tt>:[]</tt> operator on the
<tt>Rake::Task</tt>.
@@ -435,7 +435,7 @@ common for task names to begin to clash. For example, if you might
have a main program and a set of sample programs built by a single
Rakefile. By placing the tasks related to the main program in one
namespace, and the tasks for building the sample programs in a
-different namespace, the task names will not will not interfer with
+different namespace, the task names will not will not interfere with
each other.
For example:
@@ -531,17 +531,17 @@ Or give it a glob pattern:
== Odds and Ends
-=== do/end verses { }
+=== do/end versus { }
Blocks may be specified with either a +do+/+end+ pair, or with curly
braces in Ruby. We _strongly_ recommend using +do+/+end+ to specify the
actions for tasks and rules. Because the rakefile idiom tends to
-leave off parenthesis on the task/file/rule methods, unusual
+leave off parentheses on the task/file/rule methods, unusual
ambiguities can arise when using curly braces.
For example, suppose that the method +object_files+ returns a list of
object files in a project. Now we use +object_files+ as the
-prerequistes in a rule specified with actions in curly braces.
+prerequisites in a rule specified with actions in curly braces.
# DON'T DO THIS!
file "prog" => object_files {

0 comments on commit d459276

Please sign in to comment.
Something went wrong with that request. Please try again.