line edits

Author: mcasperson

_includes/planning.html

@@ -30,7 +30,7 @@ <h2>Building your Platform Team</h2>
     74%.</p>
 
 <p>You can expect a successful platform engineering strategy to work closely with, or incorporate, other specialized roles 
-    such as technicalsupport, technical writers, security, and site reliability. That said, though, generalists will serve 
+    such as DevRel, technical support, technical writers, security, and site reliability. That said, though, generalists will serve 
     your initial platform well by being able to draw on experience from various backgrounds.</p>
 
 <p>The Forbes article “Generalist Vs. Specialist Teams: How To Build A Highly Creative Startup” (https://oc.to/jkdl9C)
@@ -228,28 +228,28 @@ <h2>Feedback</h2>
 </ol>
 
 <p>Remember, though, that high-quality feedback scores require an appropriate sample size. Unless many internal
-    customers use your IDP, you may not be able to source feedback from enough people to generate meaningful scores.</p>
+    customers use your IDP, you may not be able to passively source feedback from enough people to generate meaningful scores.</p>
 
 <p>In the paper “Belief in the Law of Small Numbers”, Kahneman and Tversky define the Law of Small Numbers as the
     mistaken belief that a small sample accurately reflects the probabilities of a population. With small sample sizes,
     those few customers who felt like providing feedback may unduly influence how well you believe all customers
     received your IDP.</p>
 
-<p>The effort spent encouraging your internal customers to supply feedback may be better spent scheduling user
+<p>The effort spent encouraging your internal customers to supply asynchronous feedback may be better spent scheduling user
     interviews after releasing features or on a regular schedule. Compared to most product teams, you have the advantage
     of working side by side with your customers, and it would be a missed opportunity not to take advantage of this.</p>
 
 <p>However, there is still value in offering a real-time feedback mechanism, if only to provide an outlet for frustrated
     customers to signal their displeasure. Just as most product teams would prefer to receive such feedback directly
     rather than second hand via channels like social media, platform teams benefit from the opportunity to resolve these
-    issues directly rather than hear from the CTO that their IDP is not meeting expectations.</p>
+    issues directly rather than hearing from the CTO that their IDP is not meeting expectations.</p>
 
 <p><i>A common pattern I have noticed in many mobile apps is a two-step feedback process. The first question is designed
     to gauge whether the customer would provide a positive or negative rating. Those that indicated they would provide a
     negative rating are redirected to an internal feedback channel, while those providing positive feedback are
     forwarded to the public app store.</i></p>
 
-<p>So while low-touch feedback methods like NPS and CSAT scores may not provide reliable metrics with small sample
+<p>So while passive feedback methods like NPS and CSAT scores may not provide reliable metrics with small sample
     sizes, it is still worth collecting this data. Conversations with customers are where you will find the actual
     value. But offering a way to submit negative feedback provides platform teams the opportunity to quickly resolve, or
     at least understand, points of friction. Meanwhile, any positive feedback is marketing gold, regardless of the