clarify that the advantages of the BSD license apply to when you incorporate clang...

patch by Jonathan Sauer.

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

diff --git a/www/features.html b/www/features.html
index d55391a34fb48af7ff44a3c4eaa6e7b172a55fd6..2d3191e685c41321a11ed4e611b1230a7a5baab3 100644 (file)
--- a/www/features.html
+++ b/www/features.html
@@ -329,13 +329,15 @@ specifically designed and built to capture this information.
 <!--=======================================================================-->
 
 <p>We actively intend for clang (and LLVM as a whole) to be used for
-commercial projects, and the BSD license is the simplest way to allow this.  We
-feel that the license encourages contributors to pick up the source and work
-with it, and believe that those individuals and organizations will contribute
-back their work if they do not want to have to maintain a fork forever (which is
-time consuming and expensive when merges are involved).  Further, nobody makes
-money on compilers these days, but many people need them to get bigger goals
-accomplished: it makes sense for everyone to work together.</p>
+commercial projects, not only as a stand-alone compiler but also as a library
+embedded inside a proprietary application.  The BSD license is the simplest way
+to allow this.  We feel that the license encourages contributors to pick up the
+source and work with it, and believe that those individuals and organizations
+will contribute back their work if they do not want to have to maintain a fork
+forever (which is time consuming and expensive when merges are involved).
+Further, nobody makes money on compilers these days, but many people need them
+to get bigger goals accomplished: it makes sense for everyone to work
+together.</p>
 
 <p>For more information about the LLVM/clang license, please see the <a 
 href="http://llvm.org/docs/DeveloperPolicy.html#license">LLVM License