Address feedback

Author: mkurz

app/views/getInvolved.scala.html

@@ -22,7 +22,7 @@ <h1>How you can help</h1>
                 <h3 class="opencollective">Donate to our Open Collective</h3>
                 <a href="//opencollective.com/playframework#section-contributors">35+ backers</a>
                 <p>
-                    Play uses <a href="//opencollective.com/playframework">Open Collective</a> to gather money to pay contributors and to cover project expenses, open and transparently.
+                    Play uses <a href="//opencollective.com/playframework">Open Collective</a> to collect donations from sponsors. These funds are used to pay contributors and cover project costs, openly and transparently.
                     Individuals and companies alike can support Play financially by <a href="@routes.Application.sponsors()">becoming backers or premium sponsors</a>.
                 </p>
 

app/views/sponsors.scala.html

@@ -16,7 +16,7 @@ <h1>Why sponsor Play?</h1>
             </p>
             <p>
                 Your donation will help the project stay live and grow successfully.
-                If you have an interest that contributors care and look after the project, maintain and push it forward, please go to <a href="//opencollective.com/playframework">our Open Collective page</a> to become a backer or a premium sponsor.
+                If you are interested in helping us maintain a vibrant community of contributors to improve and support the Play Framework, please go to <a href="//opencollective.com/playframework">our Open Collective page</a> to become a backer or a premium sponsor.
             </p>
             <div class="donate-button">
                 <a href="//opencollective.com/playframework">Donate to our Collective</a>
@@ -69,7 +69,7 @@ <h2>Who is responsible?</h2>
                 <h2>What will the project do with the money?</h2>
                 <p>
                     Open Collective is a public and fully transparent plattform, so you have <a href="//opencollective.com/playframework/transactions">full insight into the projects financials</a>.
-                    Anyone can <a href="//opencollective.com/playframework/expenses/new">file an expense</a>, which however needs to be approved by Play's Open Collective admins to get it reimbursed.
+                    Anyone can <a href="//opencollective.com/playframework/expenses/new">file an expense</a>, which needs to be approved by Play's Open Collective admins to get it reimbursed.
                 </p>
                 <p>The money will be used to cover following project costs:</p>
                 <ul>
@@ -96,7 +96,7 @@ <h2>What are the next steps?<br/></h2>
                 <ul>
                     <li>
                         <b>Security fixes</b><br/>
-                        Until now, when a security problem was reported, the Play team tried to fix it as soon as possible and usually released a new minor Play version containing a fix shortly afterwards. We plan to continue with this practise.
+                        Until now, when a security problem was reported, the Play team tried to fix it as soon as possible and usually released a new minor Play version containing a fix shortly afterwards. We plan to continue with this practice.
                     </li>
                     <li>
                         <b>Support of the latest version of JVM</b><br/>
@@ -105,7 +105,7 @@ <h2>What are the next steps?<br/></h2>
                     <li>
                         <b>Support of the latest versions of sbt</b><br/>
                         That is our priority as well. In spring this year we made Play work with sbt 1.4+ (See <a href="//github.com/playframework/playframework/pull/10648">#10648</a>, <a href="//github.com/playframework/playframework/pull/10711">#10711</a> and <a href="//github.com/playframework/playframework/pull/10655">#10655</a>. Adjustment in Play's code were needed because sbt 1.4 shipped with some internal changes (by adopting an internal "virtual filesystem") that made it incompatible with Play.<br/>
-                        Long story short: We will definitely support new sbt versions soon after they got released.
+                        Long story short: We will definitely support new sbt versions soon after they are released.
                     </li>
                     <li>
                         <b>Support of the latest versions of Scala</b><br/>