line edits

Author: mcasperson

_includes/pe_vs_devops.html

@@ -111,12 +111,12 @@ <h2>What is Platform Engineering?</h2>
 
 <p>Consider a world where we had no notion of a CI server. DevOps teams still have the requirement to build and test
     their
-    code, which would likely lead to situations where every developer build their code locally, nominated a
-    "builder" with the authority to produce golden artifacts, or maybe go a step further and implement a rudimentary
+    code, which would likely lead to situations where every developer built their code locally, nominated a
+    "builder" with the authority to produce golden artifacts, or maybe teams go a step further and implement a rudimentary
     centralized solution with cron jobs.
 </p>
 
-<p>Now imagine adding a second DevOps team. They too need a solution for building their code. There are 4 ways
+<p>Now imagine adding a second DevOps team. They, too, need a solution for building their code. There are 4 ways
     common requirements like this will be addressed:
 </p>
 
@@ -127,7 +127,7 @@ <h2>What is Platform Engineering?</h2>
     <li>It will be addressed with a common solution</li>
 </ul>
 
-<p>It is easy to see that common solutions to common requirements is the only sustainable path for growing
+<p>It is easy to see that common solutions to common requirements are the only sustainable path for growing
     DevOps teams.
 </p>
 
@@ -145,7 +145,7 @@ <h2>What is Platform Engineering?</h2>
     Kohsuke's DevEx.</p>
 
 <p>While CI servers are a solved problem (at least from the point
-    of view of an average DevOps team), environments with multiple DevOps teams working side by side will no doubt
+    of most DevOps team), environments with multiple DevOps teams working side by side will no doubt
     have many more common requirements. Addressing these common requirements with artifacts generated by your IDP
     is the goal of a platform team.
 </p>