minor edits

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

diff --git a/www/comparison.html b/www/comparison.html
index bfb01f3290ac45da8674e503295db4051fd58bd6..df79d6ec4baf041a6572765d200684da23e05495 100644 (file)
--- a/www/comparison.html
+++ b/www/comparison.html
@@ -54,8 +54,8 @@
         difficult to use as an API and integrate into other tools (e.g. an IDE).\r
         Its historic design and <a \r
         href="http://gcc.gnu.org/ml/gcc/2007-11/msg00460.html">current</a>\r
-        <a href="http://gcc.gnu.org/ml/gcc/2004-12/msg00888.html">policy</a> was\r
-        intended to make it difficult to decouple the front-end from\r
+        <a href="http://gcc.gnu.org/ml/gcc/2004-12/msg00888.html">policy</a> \r
+        makes it difficult to decouple the front-end from\r
         the rest of the compiler. Clang is designed as an API from its\r
         inception.</li>\r
     <li>Various GCC design decisions make it very difficult to reuse: its build\r
@@ -79,9 +79,9 @@
     <li>The diagnostics produced by GCC are acceptable, but are often confusing\r
         and it does not support <a \r
         href="features.html#expressivediags">expressive diagnostics</a>.</li>\r
-    <li>GCC is licensed under the GPL license, which makes it difficult to use\r
-        for projects that do not themselves want to be GPL.  clang uses a BSD\r
-        license.</li>\r
+    <li>GCC is licensed under the GPL license.  clang uses a BSD license, which\r
+        allows it to be used by projects that do not themselves want to be\r
+        GPL.</li>\r
     </ul>\r
 \r
     <!--=====================================================================-->\r