Update README.md

Fixed typo.

Author: EthanRBrown

README.md

@@ -4,7 +4,7 @@ This is the companion repository to [Web Development With Node and Express, 1st
 
 ## IMPORTANT: New Structure
 
-The first version of the book attempted to treat the repo as a linear development effort.  That is, it attempted to mirror the progress a reader might make as he or she went through the book...or the progress a real development effort might take.  This approach was well-intentioned, but turned out to cause more problems than it solved.  After strugglign with those problems, I realized that compromises had to be made to reflect the reality of this repo (including the amount of time I have to maintain this repo).  Instead of a linear commit history with tags for each chapter, each chapter now lives in its own directory (including an "alternate ending" chapter, `ch-08-jquery-file-upload`).  Tags now represent "versions".  The nice thing about versions is that the version of the book you're reading can be correlated to the version of the repository.  For example, if your book says to use version 1.5, you can checkout tag 1.5, and feel confident that the code will mirror what you're reading.
+The first version of the book attempted to treat the repo as a linear development effort.  That is, it attempted to mirror the progress a reader might make as he or she went through the book...or the progress a real development effort might take.  This approach was well-intentioned, but turned out to cause more problems than it solved.  After struggling with those problems, I realized that compromises had to be made to reflect the reality of this repo (including the amount of time I have to maintain this repo).  Instead of a linear commit history with tags for each chapter, each chapter now lives in its own directory (including an "alternate ending" chapter, `ch-08-jquery-file-upload`).  Tags now represent "versions".  The nice thing about versions is that the version of the book you're reading can be correlated to the version of the repository.  For example, if your book says to use version 1.5, you can checkout tag 1.5, and feel confident that the code will mirror what you're reading.
 
 Benefits of this approach: