<strong> to <emphasis> (xmllint)

git-svn-id: http://svn.osgeo.org/postgis/trunk@9452 b70326c6-7e19-0410-871a-916f4a2858ee

diff --git a/doc/faq.xml b/doc/faq.xml
index a9548298a4068d2812c902353e5554be4081debc..8caa185f9699c04dd79b3c901c1db16f9563b305 100644 (file)
--- a/doc/faq.xml
+++ b/doc/faq.xml
@@ -367,10 +367,10 @@ WHERE ST_DWithin(geocolumn, 'POINT(1000 1000)', 100.0);</programlisting>
 
       <answer>
         <para>Almost certainly not. As an example, consider Oracle database running on Linux. Linux is GPL, Oracle is not, does Oracle running on Linux have to be distributed using the GPL? No. So your software can use a PostgreSQL/PostGIS database as much as it wants and be under any license you like.</para>
-                               <para>The only exception would be if you made changes to the PostGIS source code, and distributed your changed version of PostGIS. In that case you would have to share the code of your changed PostGIS (but not the code of applications running on top of it). Even in this limited case, you would still only have to distribute source code to people you distributed binaries to. The GPL does not require that you <strong>publish</strong> your source code, only that you share it with people you give binaries to.</para>
+                               <para>The only exception would be if you made changes to the PostGIS source code, and distributed your changed version of PostGIS. In that case you would have to share the code of your changed PostGIS (but not the code of applications running on top of it). Even in this limited case, you would still only have to distribute source code to people you distributed binaries to. The GPL does not require that you <emphasis>publish</emphasis> your source code, only that you share it with people you give binaries to.</para>
       </answer>
     </qandaentry>
 
   </qandaset>
 
-</chapter>
\ No newline at end of file
+</chapter>