Fix typo (#327)

docs/_docs/tip-1-nodeBlocks.md

@@ -88,7 +88,7 @@ collectionNode:nodeBlockForItemAtIndexPath:
 </div>
 
 
-We reccommend that you use nodeBlocks. Using the nodeBlock method allows table and collections to request blocks for each cell node, and execute them **concurrently** across multiple threads, which allows us to **parallelize the allocation costs** (in addition to layout measurement). 
+We recommend that you use nodeBlocks. Using the nodeBlock method allows table and collections to request blocks for each cell node, and execute them **concurrently** across multiple threads, which allows us to **parallelize the allocation costs** (in addition to layout measurement). 
 
 This leaves our main thread more free to handle touch events and other time sensitive work, keeping our user's taps happy and responsive. 
 
@@ -130,4 +130,4 @@ Note that it is okay to use the indexPath if it is used strictly for its integer
 
 ## Do not return nil from a nodeBlock
 
-Just as when UIKit requests a cell, returning `nil` will crash the app, so it is important to ensure a valid ASCellNode is returned for either the node or nodeBlock method. Your code should ensure that at least a blank ASCellNode is returned, but ideally the number of items reported to the collection would prevent the method from being called when there is no data to display. 
+Just as when UIKit requests a cell, returning `nil` will crash the app, so it is important to ensure a valid ASCellNode is returned for either the node or nodeBlock method. Your code should ensure that at least a blank ASCellNode is returned, but ideally the number of items reported to the collection would prevent the method from being called when there is no data to display.