line edits

Author: mcasperson

_includes/pe_vs_devops.html

@@ -96,7 +96,7 @@ <h2>What is Platform Engineering?</h2>
     teams demonstrates that architectural decisions are centrally defined and can be implemented on demand.</p>
 
 <p>
-    Common artifacts exposed by an IDP include:
+    Common artifacts generated by an IDP include:
 </p>
 <ul>
     <li>Software project templates</li>
@@ -112,12 +112,12 @@ <h2>What is Platform Engineering?</h2>
 <h2>Conclusion</h2>
 
 <p>DevOps is arguably the best philosophy we have to build high performing teams to deliver technical solutions. But
-    just because DevOps can build great teams, there is no guarantee that it will.</p>
+    just because DevOps can be used as teh foundation for great teams, there is no guarantee that it will.</p>
 
 <p>Platform engineering is an acknowledgment that common problems are best solved 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,
-    best practices, and business knowledge is codified and able to be implemented at scale throughout DevOps teams. This
+    best practices, and business knowledge is codified and able to be implemented at scale throughout DevOps teams. A
     one-to-many relationship between an IDP and DevOps processes is a clear sign that you are doing platform engineering
     right.</p>