Line edits

Author: mcasperson

_includes/pe_vs_devops.html

@@ -22,10 +22,11 @@ <h2>What is DevOps Not?</h2>
             href="https://oc.to/r2TWX0">https://oc.to/r2TWX0</a>), where generative cultures high
     in trust and low in blame exhibit higher performance.</p>
 
-<p>These definitions show us that the processes and cultural foundations that support and improve the delivery of
-    features, reduce defects, and reduce the time to resolve issues are all the responsibility of DevOps teams.</p>
+<p>So the DevOps lifecycle makes DevOps teams responsible for tooling and processes, Westrum's organizational
+    cultures makes them responsible for all human interactions, and the DORA metrics makes them responsible for all
+    measurable outcomes.</p>
 
-<p>And these are just two of the more popular interpretations of DevOps. One of the great successes of the DevOps
+<p>And these are just three of the more popular perspectives on DevOps. One of the great successes of the DevOps
     movement is that it encourages new perspectives on the metrics, processes, ideals, and cultural underpinnings of the
     field.</p>
 
@@ -37,7 +38,7 @@ <h2>What is DevOps Not?</h2>
 <p>The term DevOps has become almost unfalsifiable, but this is quite by
     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 encourage creative problem solving. The ideal DevOps team is self-sufficient, with the ability, willingness,
+    to 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