From 242a8c2bdf42db4193fb9e6df9d73cb0baef70c2 Mon Sep 17 00:00:00 2001
From: Jake <jworth@prevailhs.com>
Date: Wed, 14 May 2014 14:49:28 -0500
Subject: [PATCH] Fix some typos

---
 doc/command_line_usage.rdoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/command_line_usage.rdoc b/doc/command_line_usage.rdoc
index 4d13370ec..105d6c8e9 100644
--- a/doc/command_line_usage.rdoc
+++ b/doc/command_line_usage.rdoc
@@ -20,7 +20,7 @@ Options are:
     tracing details). The _output_ parameter is optional, but if
     specified it controls where the backtrace output is sent. If
     _output_ is <tt>stdout</tt>, then backtrace output is directed to
-    stardard output. If _output_ is <tt>stderr</tt>, or if it is
+    standard output. If _output_ is <tt>stderr</tt>, or if it is
     missing, then the backtrace output is sent to standard error.
 
 [<tt>--comments</tt>]
@@ -49,7 +49,7 @@ Options are:
 
 [<tt>--jobs</tt> _number_  (-j)]
 
-    Specifies the maximun number of concurrent threads allowed. Rake
+    Specifies the maximum number of concurrent threads allowed. Rake
     will allocate threads as needed up to this maximum number.
 
     If omitted, Rake will attempt to estimate the number of CPUs on
@@ -135,7 +135,7 @@ Options are:
     Turn on invoke/execute tracing. Also enable full backtrace on
     errors. The _output_ parameter is optional, but if specified it
     controls where the trace output is sent. If _output_ is
-    <tt>stdout</tt>, then trace output is directed to stardard output.
+    <tt>stdout</tt>, then trace output is directed to standard output.
     If _output_ is <tt>stderr</tt>, or if it is missing, then trace
     output is sent to standard error.