From c3307e2418290768486d7acf87b87b5eba61d83e Mon Sep 17 00:00:00 2001
From: Chris Lattner <sabre@nondot.org>
Date: Mon, 10 Dec 2007 08:21:12 +0000
Subject: [PATCH] fixes, thanks to Nico Weber

llvm-svn: 44789
---
 clang/www/comparison.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/clang/www/comparison.html b/clang/www/comparison.html
index 78261b7cce6b..aa11b5fa2e25 100644
--- a/clang/www/comparison.html
+++ b/clang/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>