Fix some typo on documentation

docs/FAQs/BestPractice.md

@@ -44,5 +44,5 @@ Originally, it was recommended that events be a vector like this `[:some-event-i
 
 A better practice is to encapsulate the "args" into a single map: `[:some-event-id  {:x arg1 :another arg2}]`
 
-And then to optionally use the `unwrap` middleware on the asspciated event handlers. See [here](http://day8.github.io/re-frame/api-re-frame.core/#unwrap)
+And then to optionally use the `unwrap` middleware on the associated event handlers. See [here](http://day8.github.io/re-frame/api-re-frame.core/#unwrap)
 

docs/FAQs/laggy-input.md

@@ -28,7 +28,7 @@ That `on-change` handler is being called after the user types every character.
   6. That means the text in the box will revert from `state B` to `state A` (the character just typed won't be in the input)
   7. Now if nothing happened till the next animation frame the situation would resolve itself. Because `state B` would be rendered next time because the event which included the 
   new character would have been processed well before then. 
-  6. BUT if the user immediately types another character, the state dispatched will be `State A + new character`. The prevous character typed, 
+  6. BUT if the user immediately types another character, the state dispatched will be `State A + new character`. The previous character typed, 
      which caused A -> B, is now lost. 
 
 Bottom line: with very fast typing, characters can get dropped just before animation-frames.