Merge branch 'main' of https://github.com/OctopusSolutionsEngineering/PlatformEngineeringBook

Author: mcasperson

_includes/pe_vs_devops.html

@@ -31,9 +31,9 @@ <h2>What is DevOps Not?</h2>
     the question “What is DevOps not?”</p>
 
 <p>There is no satisfying answer to that question. The term DevOps has become almost unfalsifiable, but this is quite by
-    design. DevOps has unashamedly sought to break down the silos that previously separated teams responsible for
+    design. DevOps has unashamedly sought to break down silos and absorb responsibilities that previously separated teams
     creating and delivering technical solutions, while simultaneously building a culture of psychological safety to
-    empower teams to deliver creative solutions. The ideal DevOps team is self-sufficient, with the ability,
+    encourage creative problem solving. The ideal DevOps team is self-sufficient, with the ability,
     willingness, confidence, and responsibility to tackle any and every problem.</p>
 
 <p>But for every ideal DevOps team thriving on the responsibility of owning their own destiny, there is another team slowly
@@ -95,6 +95,20 @@ <h2>What is Platform Engineering?</h2>
     implemented platform engineering. This one-to-many relationship between an IDP and the processes used by DevOps
     teams demonstrates that architectural decisions are centrally defined and can be implemented on demand.</p>
 
+<p>
+    Common artifacts exposed by an IDP include:
+</p>
+<ul>
+    <li>Software project templates</li>
+    <li>CI/CD pipelines templates</li>
+    <li>IaC templates</li>
+    <li>Scripts to configure local development environments</li>
+    <li>Document and presentation templates</li>
+    <li>Dashboard templates</li>
+    <li>Checklists for starting new projects</li>
+    <li>Reference architectures</li>
+</ul>
+
 <h2>Conclusion</h2>
 
 <p>DevOps is arguably the best philosophy we have to build high performing teams to deliver technical solutions. But