PR:

Submitted by:
Reviewed by:	-doc
Approved by:	bmah
Obtained from:
MFC after:

Clarify "what are goals" question.  Since this is the closest thing
FreeBSD has to a mission statement, it has been extensively reviewed
on -doc and revised a few times before commit, so I'm making quite an
extensive commit message.

-only one goal is listed, so don't use plural "goals."  That goal does
have several sub-components, but it's one primary goal.

-use URLs instead of file links, so people who are browsing docs
locally can use the link.

-add an extra question on BSD license here, since we're discussing it
anyway.  bmah said (paraphrased): he would have probably split it into
a separate commit, but approved as submitted.  Will do so in the
future.

en_US.ISO8859-1/books/faq/book.sgml

@@ -100,11 +100,11 @@
 
       <qandaentry>
         <question id="FreeBSD-goals">
-          <para>What are the goals of FreeBSD?</para>
+          <para>What is the goal of the FreeBSD Project?</para>
         </question>
 
         <answer>
-          <para>The goals of the FreeBSD Project are to provide software
+          <para>The goal of the FreeBSD Project is to provide software
             that may be used for any purpose and without strings attached.
             Many of us have a significant investment in the code (and
             project) and would certainly not mind a little financial
@@ -117,20 +117,46 @@
             Software and one that we enthusiastically support.</para>
 
           <para>That code in our source tree which falls under the <ulink
-            url="../../../../copyright/COPYING">GNU General Public
+            url="http://www.FreeBSD.org/copyright/COPYING">GNU General Public
               License (GPL)</ulink> or <ulink
-            url="../../../../copyright/COPYING.LIB">GNU Library
+            url="http://www.FreeBSD.org/copyright/COPYING.LIB">GNU Library
               General Public License (LGPL)</ulink> comes with slightly more
             strings attached, though at least on the side of enforced access
             rather than the usual opposite.  Due to the additional complexities
             that can evolve in the commercial use of GPL software, we do,
             however, endeavor to replace such software with submissions under
             the more relaxed <ulink
-            url="../../../../copyright/freebsd-license.html">
+            url="http://www.FreeBSD.org/copyright/freebsd-license.html">
               FreeBSD copyright</ulink> whenever possible.</para>
         </answer>
       </qandaentry>
 
+      <qandaentry>
+        <question id="bsd-license-restrictions">
+          <para>Does the FreeBSD license have any restrictions?</para>
+        </question>
+
+        <answer>
+          <para>Yes.  Those restrictions do not control how you use
+            the code, merely how you treat the FreeBSD Project itself.
+            If you have serious license concerns, read the actual
+            <ulink
+            url="http://www.FreeBSD.org/copyright/freebsd-license.html">
+            license</ulink>.  For the simply curious, the license can
+            be summarized like this.</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>Don't claim that you wrote this.</para>
+            </listitem>
+
+            <listitem>
+              <para>Don't sue us if it breaks.</para>
+            </listitem>
+          </itemizedlist>
+        </answer>
+      </qandaentry>
+
       <qandaentry>
         <question id="why-called-FreeBSD">
           <para>Why is it called FreeBSD?</para>