line edits

Author: mcasperson

_includes/pe_vs_devops.html

@@ -139,7 +139,10 @@ <h2>What is Platform Engineering?</h2>
         his code before he did an actual commit to the repository, to be sure all was well. Once his teammates saw 
         what he was doing, they all wanted to use Jenkins.</p>
 
-    <p>Thus a common solution to a common requirement was born. While CI servers are a solved problem (at least from the point
+    <p>Thus a common solution to a common requirement was born. It is also no coincidence that Jenkins was born to improve
+        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
         have many more common requirements. Addressing these common requirements with artifacts generated by your IDP
         is the goal of a platform team.
@@ -166,7 +169,7 @@ <h2>Conclusion</h2>
     inconsistent solutions at best and eventually creates an unsustainable environment. This in turn leads to
     frustration and poor DevEx.</p>
 
-<p>Platform engineering is an acknowledgment that common problems are best solved with common solutions, and that
+<p>Platform engineering is an acknowledgment that common problems are best addressed with common solutions, and that
     solving common problems is one of the most effective methods for improving DevEx.</p>
 
 <p>By delivering DevEx as a Service, platform teams are responsible for an IDP that ensures architectural decisions,