From: Reid Spencer <rspencer@reidspencer.com>
Date: Tue, 10 Aug 2004 16:38:18 +0000 (+0000)
Subject: Fixed some spellos and grammaros.
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=d8473378febba85e8b7b72311de08f4ddcc1bf5a;p=oota-llvm.git

Fixed some spellos and grammaros.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@15610 91177308-0d34-0410-b5e6-96231b3b80d8
---

diff --git a/docs/CommandLine.html b/docs/CommandLine.html
index 73533750191..aea3ec843c0 100644
--- a/docs/CommandLine.html
+++ b/docs/CommandLine.html
@@ -458,10 +458,10 @@ things it doesn't know about, like enums or '<tt>int*</tt>'s?</p>
 
 <p>The answer is that it uses a table driven generic parser (unless you specify
 your own parser, as described in the <a href="#extensionguide">Extension
-Guide</a>).  This parser maps literal strings to whatever type is required, are
+Guide</a>).  This parser maps literal strings to whatever type is required, and
 requires you to tell it what this mapping should be.</p>
 
-<p>Lets say that we would like to add four optimizations levels to our
+<p>Lets say that we would like to add four optimization levels to our
 optimizer, using the standard flags "<tt>-g</tt>", "<tt>-O0</tt>",
 "<tt>-O1</tt>", and "<tt>-O2</tt>".  We could easily implement this with boolean
 options like above, but there are several problems with this strategy:</p>