diff --git a/docs/FAQ.html b/docs/FAQ.html
index 3ada460..6b60272 100644
--- a/docs/FAQ.html
+++ b/docs/FAQ.html
@@ -10,6 +10,45 @@
 
 <!--=====================================================================-->
 <h2>
+<a name="license">Licenses</a>
+</h2>
+<!--=====================================================================-->
+
+<dl compact>
+	<dt> <b>Why are the LLVM source code and the front-end distributed
+	under different licenses?</b>
+	<dd>
+	The C/C++ front-ends are based on GCC and must be distributed under
+	the GPL.  Our aim is to distribute LLVM source code are a <em>much
+	less restrictive</em> license, in particular one that does not
+	compel users who distribute tools based on modifying the source to
+	redistribute the modified source code as well.
+
+	<dt><b>Does the Illinois Open Source License really qualify 
+	  as an "open source" license?</b>
+	<dd>The 
+	<a href="http://www.opensource.org/licenses/UoI-NCSA.php">
+        UI Open Source License</a> is certified by the
+	Open Source Initiative (OSI).
+
+	<dt> <b>Can I modify LLVM source code and redistribute the modified
+	  source?</b>
+	<dd>
+	Yes.  The modified source distribution must retain notice both the
+	copyright notice and follow the three bulletted conditions listed in
+	the <a href="releases/1.0/LICENSE.txt">LLVM license</a>.
+
+	<dt> <b>Can I modify LLVM source code and redistribute binaries or
+	  other tools based on it, without redistributing the source.
+	<dd>
+	Yes, this is why we distribute LLVM under a less restrictive license
+	than GPL, as explained in the first question above.
+	<p>
+</dl>
+<hr>
+
+<!--=====================================================================-->
+<h2>
 <a name="source">Source Code</a>
 </h2>
 <!--=====================================================================-->