diff --git a/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html b/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html
index 1ad10ccd64d8012800a811121970da2ece17a973..c70e7874e04d16a49cc4a9a97ef145e47d143f8c 100644
--- a/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html
+++ b/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html
@@ -162,6 +162,7 @@ Code, and for which (at least some) source code for which is provided.
     obligations and allow them to keep certain code in their kernel
     proprietary?</dt>
 
+    <dd>
     <p>Many in the media have talked about the possibility that VMware might
     use some so-called &ldquo;shim layer&rdquo; between Linux code and
     VMware's proprietary code.  While, for decades, there has been much talk of
@@ -177,7 +178,7 @@ Code, and for which (at least some) source code for which is provided.
     code in their own kernel, and evidence seems to indicate the work as a
     whole was developed by modifying Linux code in tandem with
     modifications to &ldquo;vmkernel&rdquo; in a tightly coupled manner.</p>
-
+    </dd>
     <dt>Can you give a <em>specific</em> example, with code, showing how
     VMware combined Linux source code with their binary-only components?</dt>
 
@@ -410,6 +411,8 @@ at <code>bin/vmtar</code> inside
             Software Foundation</a></li>
         <li><a href="https://samba.org/samba/news/announcements/2015-03-06_vmware_lawsuit.html">The
             Samba Team</a></li>
+        <li><a href="http://sourceforge.net/p/swig/news/2015/03/defending-the-gpl/">The
+        SWIG Project</a></li>
         <li><a href="https://plus.google.com/104877287288155269055/posts/cHgyreA76yY">Dave Airlie, Linux Developer</a></li>
         <li><a href="https://twitter.com/mjg59/status/573530001758294016">Matthew Garrett, Linux Developer</a></li>
         <li><a href="/news/2015/mar/05/vmware-lawsuit/#glikely">Grant Likely, Linux Kernel Engineer</a></li>