diff --git a/source/playbook/index.html.erb b/source/playbook/index.html.erb
index 138162d..5a65d16 100644
--- a/source/playbook/index.html.erb
+++ b/source/playbook/index.html.erb
@@ -46,7 +46,7 @@ To get the most out of the Playbook, it would be helpful for leaders to have or
         <figcaption>Waterfall diagram of a notional timeline for implementing the five Playbook tracks, showing that they are related and overlapping.</figcaption>
       </figure>
       
-      <p>A brief descripion of each track with a link to the more detailed page for each:  
+      <p>A brief description of each track with a link to the more detailed page for each:  
       <ol class="section-list">
         <li><%= link_to("Community Building", "community.html") %>: Community starts with leadership from committed "Champions" who have broad reach, a grasp of key challenges and potential Use Cases, and the ability to grow the Community with skilled and active participants. A fair and sustainable Governance framework must be established. Certain organizations and skills may be needed only at certain points with one or more tracks. </li>
         <li><%= link_to("Use Cases & Planning", "use_cases_planning.html") %>: The Community must prioritize well-scoped projects that address key challenges, offer new work and data flows, and scope the needed data standards. They must organize and schedule Use Case work all the way through to adoption and measuring value, and secure the resources (organizations, Champions, people/skills) needed to succeed. Specific Use Cases attract additional subsets of each specialty.</li>