(no commit message)

diff --git a/why_a_libresoc.mdwn b/why_a_libresoc.mdwn
index bdbf564b0c63e17ae12784581185c2af178e306c..29cdb0c61316fa908c095e1f57d3461f40bb8f28 100644 (file)
--- a/why_a_libresoc.mdwn
+++ b/why_a_libresoc.mdwn
@@ -4,7 +4,9 @@ Its quite hard to guarantee that performant processors (think pipelined, out-of-
 
 There are entire [dissertations](http://www.kroening.com/diss/diss-kroe.pdf) dedicated to the subject matter of merely functionally verifying a pipeline (this doesn’t even consider out of order execution).
 
-Given the fact that performant bug-free processors no longer exist [1][2], how can you trust your processor [3]? The next best thing is to have access to a processor’s design files. Not only have access to them, you must have the freedom to study, improve them, run the test suites and be able to improve those too.  Not only that, you and everyone who has a stake in the success needs to be entirely free from NDAs and other restrictions which prevent and prohibit communication.
+Given the fact that performant bug-free processors no longer exist [1][2], how can you trust your processor [3]? The next best thing is to have access to a processor’s design files. Not only have access to them, you must have the freedom to study, improve them, run the test suites and be able to improve those too.
+
+Not only that, you and everyone who has a stake in the success needs to be entirely free from NDAs and other restrictions which prevent and prohibit communication.  An example: although you yourself might not have the technical capability to review our SoC, you can always find a third party to pay wjo can.  However if the source code was under NDA, do you think that would be practical to consider?
 
 *Collaboration, not competition*.