From: Chris Lattner <sabre@nondot.org>
Date: Mon, 10 Dec 2007 08:21:12 +0000 (+0000)
Subject: fixes, thanks to Nico Weber
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0d1638ee36bcc76c0f944ba8c1d878956d570ede;p=clang

fixes, thanks to Nico Weber


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

diff --git a/www/comparison.html b/www/comparison.html
index 78261b7cce..aa11b5fa2e 100644
--- a/www/comparison.html
+++ b/www/comparison.html
@@ -62,7 +62,7 @@
     <ul>
     <li>The Clang ASTs and design are intended to be <a 
         href="features.html#simplecode">easily understandable</a> by
-        anyone who is familiar with the languages involved and who have a basic
+        anyone who is familiar with the languages involved and who has a basic
         understanding of how a compiler works.  GCC has a very old codebase
         which presents a steep learning curve to new developers.</li>
     <li>Clang is designed as an API from its inception, allowing it to be reused
@@ -173,10 +173,10 @@
     
     <ul>
     <li>PCC dates from the 1970's and has been dormant for most of that time.
-        The clang + llvm community are very active.</li>
+        The clang + llvm communities are very active.</li>
     <li>PCC doesn't support C99, Objective-C, and doesn't aim to support
         C++.</li>
-    <li>PCC's code generation is very limited compared to LLVM, it produces very
+    <li>PCC's code generation is very limited compared to LLVM.  It produces very
         inefficient code and does not support many important targets.</li>
     <li>Like Elsa, PCC's does not have an integrated preprocessor, making it
         extremely difficult to use it for source analysis tools.</li>