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