diff --git a/benefits.markdown b/benefits.markdown
index 0cdad69..78ec683 100644
--- a/benefits.markdown
+++ b/benefits.markdown
@@ -2,19 +2,19 @@
 layout: page
 title: Benefits of a KDE Project
 ---
-Being part of the international KDE community conveys certain benefits and rights. These include:
+Being part of the international KDE community conveys certain benefits:
 
-* Stand on the shoulders of giants
+* To stand on the shoulders of giants
   * Make use of KDE infrastructure for project hosting
   * Benefit from the experience of the KDE sysadmins
   * Get support from the larger community with development, documentation, translation, testing, bug handling, etc.
   * Use opportunities to integrate with a large ecosystem of end-user products
-  * Create cross-pollination of ideas and innovation through interaction with teams sharing common values
+  * Interact with teams that have common values, leadin to the cross-pollination of ideas and innovations
 * Enjoy representation and support by KDE e.V.
   * Participate in Akademy and other KDE events
-  * Be considered for financial and organizational support
-  * Know that your trademark can be secured
-  * Know that your project's license can be defended via the [Fiduciary Licensing Agreement](http://ev.kde.org/rules/fla.php)
+  * Receive financial and organizational support
+  * Know that your trademarks can be secured
+  * Know that your licensing wishes will be protected via the [Fiduciary Licensing Agreement](http://ev.kde.org/rules/fla.php)
 * Increase your market visibility through the reputation of the KDE community and KDE
   promotion tools such as:
   * pushing project announcements to the Dot and employing other KDE promotion channels
@@ -24,7 +24,7 @@ Being part of the international KDE community conveys certain benefits and right
     for communication on web sites and other channels
 
 <div class="addendum">
-<a href="principles.html">Principles of a KDE Project</a><br/>
+<a href="commitments.html">Commitments of a KDE Project</a><br/>
 <a href="index.html">Back to the manifesto</a>
 </div>
 
diff --git a/commitments.markdown b/commitments.markdown
index b046224..7824919 100644
--- a/commitments.markdown
+++ b/commitments.markdown
@@ -1,27 +1,25 @@
 ---
 layout: page
-title: Principles of a KDE Project
+title: Commitments of a KDE Project
 ---
-The KDE Project designation carries certain principles and requirements:
+The KDE Project designation carries with it certain commitments:
 
 * Support the [KDE Code of Conduct](http://www.kde.org/code-of-conduct/)
 * There is no mandatory Contributor License Agreement
 * Technical requirements
   * The project stays true to established practices common to similar KDE projects
     unless special considerations force it to deviate
-  * Software assets access model
-    * Direct write access to the software assets is granted only to KDE contributor accounts
-    * Direct write access to the software assets is granted to all KDE contributor accounts
+  * All KDE contributor accounts get direct (and universal) write access to the software assets
   * Projects that choose not to host their web services on KDE infrastructure need to provide
     administrative access to the KDE sysadmin team; or, if such access cannot be granted,
     a regular backup of all the code and data used by the web services should be provided to
     the KDE sysadmins (except if the service is not an integral part of the project's workflow,
     community interactions and public image) to ensure continued availability
 * Copyrights, trademarks and patents
-  * [KDE licensing policy](http://techbase.kde.org/Policies/Licensing_Policy) should be respected
-  * KDE branding guidelines should be respected
-  * Trademark continuity – if the authors of the software abandon it or disappear, they agree to transfer the trademark to the next maintainer
-  * Patent License - If the code is covered by patents registered by the project itself, those patents must be licensed freely
+  * [KDE licensing policy](http://techbase.kde.org/Policies/Licensing_Policy) must be respected
+  * KDE branding guidelines are respected
+  * If the authors of the software abandon it or disappear, they agree to transfer the trademark to the next maintainer
+  * If the code is covered by patents registered by the project itself, those patents must be licensed freely
 
 <div class="addendum">
 <a href="benefits.html">Benefits of a KDE Project</a><br/>
diff --git a/index.html b/index.html
index ce3153f..3d2d53a 100644
--- a/index.html
+++ b/index.html
@@ -14,10 +14,10 @@ leadership and decision processes;</div>
 
 <div>
 <span class="value">Free Software</span> to ensure the result of our work
-is available to all people;</div>
+is available to all people for all time;</div>
 
 <div>
-<span class="value">Inclusivity</span> to ensure that people of all origins
+<span class="value">Inclusivity</span> to ensure that all people
 are welcome to join us and participate;</div>
 
 <div>
@@ -37,5 +37,5 @@ items essential to define and stay true to ourselves.</div>
 
 <div class="addendum">From those values we derived the
 <a href="benefits.html">benefits</a> and
-<a href="principles.html">principles</a> of a KDE Project.</div>
+<a href="commitments.html">commitments</a> of a KDE Project.</div>
 </center>
