diff --git a/index.html b/index.html
index eca9392..6adc1b4 100644
--- a/index.html
+++ b/index.html
@@ -39,7 +39,7 @@ <h2>
             <em>Fair Core</em> is to <a href='https://fair.io' target='_blank' rel='noopener'>Fair Source</a> what <em>Open Core</em> is to <a href='https://opensource.org' target='_blank' rel='noopener'>Open Source</a>.
           </h2>
           <p>
-            A perfect blend of the <a href='https://fsl.software' target='_blank' rel='noopener'>Functional Source License 1.1</a> <em>&</em> the <a href='https://www.elastic.co/licensing/elastic-license' target='_blank' rel='noopener'>Elastic License 2.0</a> balancing developer sustainability <em>&</em> user freedom. Safely share projects with commercial features in <em>a single codebase</em> while eventually contributing to Open Source.
+            A perfect blend of the <a href='https://fsl.software' target='_blank' rel='noopener'>Functional Source License 1.1</a> <em>&</em> the <a href='https://www.elastic.co/licensing/elastic-license' target='_blank' rel='noopener'>Elastic License 2.0</a> balancing developer sustainability <em>&</em> user freedom. Safely share projects with commercial features in <em>a single codebase</em> while eventually contributing it to Open Source.
           </p>
           <h3>
             The <em>pitch</em>
@@ -139,7 +139,7 @@ <h4>
             For projects moving from closed source to Fair Source, the <abbr title='Fair Core License'>FCL</abbr> is advantageous because it doesn't require project reorganization. In Open Core, commercial features need to be extracted and separately licensed or made closed source, causing potential code churn and risk. In contrast, the <abbr title='Fair Core License'>FCL</abbr> allows a project's commercial features to simply be wrapped in a license key check.
           </p>
           <p>
-            Another advantage of the <abbr title='Fair Core License'>FCL</abbr> is that commercial features will eventually become Open Source. In contrast, with an Open Core project, its commercial features will never become Open Source, unless a one-off commercial license is used which eventually contributes to Open Source.
+            Another advantage of the <abbr title='Fair Core License'>FCL</abbr> is that commercial features will eventually become Open Source. In contrast, with an Open Core project, its commercial features will never become Open Source, unless a one-off commercial license is used which eventually contributes it to Open Source.
           </p>
           <p>
             Finally, the <abbr title='Fair Core License'>FCL</abbr> is a non-compete license, unlike Open Core, which typically doesn't restrict on endeavor, though that depends on the commercial license as well.