diff --git a/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html b/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html
index c70e7874e04d16a49cc4a9a97ef145e47d143f8c..b418dff76e98e84d75bbf65a9062955c40aad190 100644
--- a/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html
+++ b/www/conservancy/static/linux-compliance/vmware-lawsuit-faq.html
@@ -70,7 +70,8 @@
   usual, friendly, and non-confrontational way.  Nevertheless, VMware
   immediately referred Conservancy to VMware's outside legal counsel in the
   USA, and Conservancy negotiated with VMware's legal counsel throughout
-  late 2011, 2012 and 2013.  We exchanged and reviewed CCS candidates, and
+  late 2011, 2012 and 2013.  We exchanged and reviewed
+  <a title="Complete, Corresponding Source" href="https://copyleft.org/guide/comprehensive-gpl-guidech6.html#x9-470005.2.1">CCS</a> candidates, and
   admittedly, VMware made substantial and good efforts toward compliance on
   BusyBox.  However, VMware still refused to fix a few minor and one major
   compliance problem that we discovered during the process.  Namely, there