Promote "hard to violate" to the Definition

Author: chadwhitacre

README.md

@@ -19,8 +19,6 @@ you're using BUSL we will need to review your license more closely since BUSL
 can have highly variable implementations.
 
 For **licenses**, we're still working out specifics but we intend to be fairly
-stringent in order to avoid license proliferation. Of course your license must
-meet the [Fair Source Definition](https://fair.io/about/). It must also not put
-an undue burden on the user to monitor their compliance with your license (any
-compliance checks should be built into your software itself). It should also be
-adopted at more than one company, at least.
+stringent in order to avoid license proliferation. Uour license must meet the
+[Fair Source Definition](https://fair.io/about/), and it should be adopted at
+more than one company, at least.

src/pages/about.astro

@@ -48,6 +48,7 @@ const heroData = {
             to protect the producer’s business model; and
           </li>
           <li>undergoes delayed Open Source publication (DOSP).</li>
+          <li>does not put an undue burden on the user to monitor their compliance.</li>
         </ol>
         <div>
           <p class="pb-[1.5rem]">
@@ -100,6 +101,13 @@ const heroData = {
             Will this be meaningful in practice? Again, time will tell.
           </p>
 
+          <p>
+            The fourth point is that Fair Source software must not put an undue
+            burden on the user to monitor their compliance with the license.
+            For the most part, compliance checks should be built into the software
+            itself. It should be difficult to violate the license terms.
+          </p>
+
           <h3>Why Fair Source?</h3>
 
           <p class="pb-[1.5rem]">