Merge pull request #28 from booleancoercion/master

Fixed a typo

src/2_a_mental_model_for_futures.md

@@ -1,12 +1,12 @@
 # A mental model of how Futures and runtimes work
 
 The main goal in this part is to build a high level
-mental model of how the different pieces we read about in the previos chapter
+mental model of how the different pieces we read about in the previous chapter
 works toghether. I hope this will make it easier to understand what we just read
 about in the previous chapter and also explain why we take a deep dive into topics
 like trait objects and generators in the next few chapters.
 
-This is not the only way to model this since we're making assumtions on runtime
+This is not the only way to model this since we're making assumptions on runtime
 specifics that can vary a great deal, but it's the way I found it easiest to
 build upon. Finally, please note that the code itself is "pseudo-rust" due to
 the need for brevity and clarity.
@@ -72,4 +72,4 @@ this chapter._
 </a>
 <a href="./assets/slides/Slide19.PNG" target="_blank">
  <img src="./assets/slides/Slide19.PNG" alt="slide19"/>
-</a>
+</a>

src/3_waker_context.md

@@ -3,7 +3,7 @@
 > **Overview:**
 >
 > - Understand how the Waker object is constructed
-> - Learn how the runtime know when a leaf-future can resume
+> - Learn how the runtime knows when a leaf-future can resume
 > - Learn the basics of dynamic dispatch and trait objects
 >
 > The `Waker` type is described as part of [RFC#2592][rfc2592].