Update getting_started.html.erb

Addes line breaks between questions sections.

source/playbook/getting_started.html.erb

@@ -14,38 +14,38 @@ theme: playbook
 
     <p>MITRE has found that the following are the most important initial qustions that should be asked and largely answered before starting a data standards, implementation, and deployment initiative within a new specialty. These questions purposely do not have a one-to-one corresponse with the tracks covered in subsequent sections of the Playbook. However, these are specific questions related to one more more tracks that must be addressed before or very early in the process of starting such a major project.</p>
     <ul class="action-list">
-
+<br>    
      <li><b>Who are the community champions that will drive success?</b>
         <ul>
           <li>Champions are the most important key to the steps below. Champions understand needs, reach large constituencies, and mobilize resources.</li>
           <li>Leading medical professional societies and Government organizations have been the successful CodeX Champions.</li>
           <li>Must commit to the approach, to leading a project that grows in complexity and participation, and to helping to find skills and funding.</li>
         </ul>
      </li>
-
+<br>            
       <li><b>Do Champions and other leading organizations agree on a Governance framework?</b>
         <ul>
           <li>Good Governance facilitates communications, decision making, project management, and resource distribution.</li>
           <li>Must be lightweight, with focus on providing infrastructure, starting use cases, adjudicating concerns, and applying funding to projects (sparingly).</li>
           <li>The CodeX HL7 FHIR Accelerator serves this purpose for Use Cases around cancer (mCODE standard), cardiovascular disease, and genomics, so far. Other governance schemes are possible but would require more effort to startup and engage across specialties.</li>
         </ul>
       </li>
-
+<br>            
       <li><b>What are the first handful of Use Cases that will be worked on?</b>
         <ul>
           <li>Use Cases help prioritize effort into manageable segments that attract key 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 and standards, and (c) motivates demand, adoption, and value. Data are collected and shared using the same standard for multiple use cases.</li>
           <li>Initial CodeX Use Cases often start with “lower-bar” problems around which many stakeholders can align (2b). Use Cases can grow in scope over time.</li>
         </ul>
       </li>
-
+<br>            
       <li><b>What is your plan for adoption and, ultimately, providing value in the health ecosystem?</b>
         <ul>
           <li>Each Use Case needs a pragmatic approach that envisions how the resulting solution will 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>
         </ul>
       </li>
-
+<br>            
       <li><b>Do you have the resources need to start the Use Case and deliver success?</b>
         <ul>
           <li>Starting Use Cases and demonstrating solutions require specific types of organizations, skillsets, and often financing – at the right times.</li>