<p>The second one is
<a href="http://en.wikipedia.org/wiki/Coverity">Coverity</a> which is
a source code checker. It is able to process the source of a program
-and find problems in the logic. It started out as the Stanford
-Checker and became well known when it was used to find bugs in the
-Linux kernel. It is now a commercial tool and the company behind it
-is running <a href="http://www.scan.coverity.com/">a community
-service</a> for the free software community, where a lot of free
-software projects get their source checked for free. Several thousand
-defects have been found and fixed so far. It can find errors like
-'lock L taken in file X line N is never released if exiting in line
-M', or 'the code in file Y lines O-P can never be executed'. The
-projects included in the community service project have managed to get
-rid of a lot of reliability problems thanks to Coverity.</p>
+and find problems in the logic without running the program. It
+started out as the Stanford Checker and became well known when it was
+used to find bugs in the Linux kernel. It is now a commercial tool
+and the company behind it is running
+<a href="http://www.scan.coverity.com/">a community service</a> for the
+free software community, where a lot of free software projects get
+their source checked for free. Several thousand defects have been
+found and fixed so far. It can find errors like 'lock L taken in file
+X line N is never released if exiting in line M', or 'the code in file
+Y lines O to P can never be executed'. The projects included in the
+community service project have managed to get rid of a lot of
+reliability problems thanks to Coverity.</p>
<p>I believe tools like this, that are able to automatically find
errors in the source, are vital to improve the quality of software and