From: Chris Lattner <sabre@nondot.org>
Date: Mon, 10 Dec 2007 02:05:32 +0000 (+0000)
Subject: minor edits
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ff11fa385191408118c3812392b1d899f36cee63;p=clang

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 bfb01f3290..df79d6ec4b 100644
--- 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).
         Its historic design and <a 
         href="http://gcc.gnu.org/ml/gcc/2007-11/msg00460.html">current</a>
-        <a href="http://gcc.gnu.org/ml/gcc/2004-12/msg00888.html">policy</a> was
-        intended to make it difficult to decouple the front-end from
+        <a href="http://gcc.gnu.org/ml/gcc/2004-12/msg00888.html">policy</a> 
+        makes it difficult to decouple the front-end from
         the rest of the compiler. Clang is designed as an API from its
         inception.</li>
     <li>Various GCC design decisions make it very difficult to reuse: its build
@@ -79,9 +79,9 @@
     <li>The diagnostics produced by GCC are acceptable, but are often confusing
         and it does not support <a 
         href="features.html#expressivediags">expressive diagnostics</a>.</li>
-    <li>GCC is licensed under the GPL license, which makes it difficult to use
-        for projects that do not themselves want to be GPL.  clang uses a BSD
-        license.</li>
+    <li>GCC is licensed under the GPL license.  clang uses a BSD license, which
+        allows it to be used by projects that do not themselves want to be
+        GPL.</li>
     </ul>
 
     <!--=====================================================================-->