From 5638df00b00888e6505ce2fa6571b4851e15159b Mon Sep 17 00:00:00 2001
From: Steve Bratt <steve@thinkabit.com>
Date: Wed, 18 Sep 2024 16:26:39 -0400
Subject: [PATCH] Update getting_started.html.erb

---
 source/playbook/getting_started.html.erb | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/source/playbook/getting_started.html.erb b/source/playbook/getting_started.html.erb
index 9f3696f..052df7e 100644
--- a/source/playbook/getting_started.html.erb
+++ b/source/playbook/getting_started.html.erb
@@ -39,16 +39,16 @@ theme: playbook
         <br>            
         <li><b>Which Use Cases will the specialty work on first?</b>
           <ul>
-            <li>Use Cases help prioritize effort into manageable segments that attract key Use Case Champions and critical Community members.</li>
-            <li>Each Use Case includes a specific health IT or process challenge that (a) attracts more participants into the Community, (b) defines, validates, and/or motivates improvements to underlying workflows, data requirements, and data standards, and (c) motivates demand, adoption, and value. Ideally, data are collected and shared using the same standard which can expand with and support multiple Use Cases.</li>
-            <li>Use Case selection in CodeX typically look for easier (not easy) Use Cases and solutions for which demonstrations could be delivered the soonest, and around which Champions and other stakeholders could align. Use Cases can grow in scope and complexity over time.</li>
+            <li>Use Cases help prioritize effort into manageable segments.</li>
+            <li>Each Use Case includes a scoped health IT or process challenge that (a) defines, validates, and/or motivates improvements to underlying workflows, data requirements, and data standards, (b) attracts more needed participants and skillsets into the Community, and (c) motivates demand, adoption, and value. Ideally, data are collected and shared using the same standard which can expand with and support multiple Use Cases.</li>
+            <li>First Use Cases selected in CodeX typically start with easier (not easy) problems and solutions for which demonstrations could be delivered the soonest, and around which Champions and other stakeholders can align. Use Cases can grow in scope and complexity over time.</li>
             <li>(Key Playbook Tracks: <%= link_to("Community Building", "community.html") %>, <%= link_to("Use Cases & Planning", "use_cases_planning.html") %>)</li>
           </ul>
         </li>
         <br>            
         <li><b>What's the strategy for adoption of standards-based solutions?</b>
           <ul>
-            <li>Each Use Case needs a pragmatic approach that envisions how the resulting solution will be adopted in the ecosystem and improve care and/or reduce burden.</li>
+            <li>Each Use Case needs a pragmatic vision for how the resulting solution will be adopted in the ecosystem and improve care and/or reduce burden.</li>
             <li>Engagement of future users who require (e.g., gov’t agencies) and/or demand (e.g., customers) vendors to implement solutions has proved invaluable in CodeX.</li>
             <li>(Key Playbook Tracks: <%= link_to("Community Building", "community.html") %>, <%= link_to("Use Cases & Planning", "use_cases_planning.html") %>, <%= link_to("Adoption & Value", "adoption.html") %>)</li>
           </ul>
@@ -56,9 +56,9 @@ theme: playbook
         <br>            
         <li><b>Are the necessary resources available to start the first Use Case(s) and deliver success?</b>
           <ul>
-            <li>Starting Use Cases and demonstrating solutions require specific types of organizations, Champions, skillsets, and often financing – at the right times.</li>
-            <li>Resource requirements are typically less clear at the start, but become clearer as work ramps up.</li>
-            <li>Use Case scope and timelines can often be scaled to available resources and still be successful. </li>
+            <li>Launching Use Cases and demonstrating solutions require specific types of organizations, Champions, skillsets, and often financing – at the right times.</li>
+            <li>Resource needs are often less clear at the start, but become increasingly clear as work if planned and accelerated.</li>
+            <li>Use Case scope and timelines can be scaled to available resources and still be successful. </li>
             <li>In CodeX, initial, rapid, promising Use Case results - generally from the easiest early phases of a Use Case - helped attract and justify involvement of new organizations, gather the needed skillsets, and secured funding.</li>
             <li>(Key Playbook Tracks: <%= link_to("Community Building", "community.html") %>, <%= link_to("Use Cases & Planning", "use_cases_planning.html") %>)</li>
           </ul>