Book - Projects - Fix typo.

book/projects/project_roadmap.md

@@ -1,6 +1,6 @@
 # Project Roadmap
 
-Each project will progress through these stages: 
+Each project will progress through these stages:
 
 ```{image} ../img/project-timeline.png
 :alt: flowchart of typical hackweek project timelines
@@ -36,15 +36,15 @@ We facilitate a project team formation session at the end of the first day of th
 ## **Teamwork**
 
 * kick-off meeting focuses on hearing from each team member:
-    * What are your unique learning goals? 
+    * What are your unique learning goals?
     * How do you work best? What level of group interaction works for you?
     * What skills and background are you most excited to share with the team?
     * When are you available to meet?
-* set up team computing infrastructure on Slack and GitHub ([Project Initiallization](project_initialization)) 
+* set up team computing infrastructure on Slack and GitHub ([Project Initialization](project_initialization))
 * project work begins and teams have regular check-ins to chart progress
 * project outputs are recorded in a GitHub repository
 
-## **Presentations** 
+## **Presentations**
 
 * each team has 15 minutes to share what was learned, what challenges arose, what might be worth trying next
 * individual contributions to the group effort are recognized and celebrated
@@ -54,7 +54,7 @@ We facilitate a project team formation session at the end of the first day of th
 * We aspire to keep projects going after the hackweek! This is an optional (ideal) outcome of hackweek project work.
 * Project leads/helpers will transition to longer-term engagement via mentorship role (optional/with support).
 * Additional people join a growing Community of Practice (for example, centered on a community software library).
-* software, research results are packaged and shared/published. 
+* software, research results are packaged and shared/published.