anchor.diff:  
   <% note do %>
   
  -This is a note. It tells you notey things. Notey things are auxiliary information for something that has already came before.
  +This is a note. It tells you notey things. Notey things are auxiliary information for something that we just learned about.
   
   For example, if we had been discussing oxen and how we might burden them with tasks, then a note might inform you that oxen only work under optimal weather conditions; including but not limited to an oxygen rich environment.
   
  -This information would be important if for example, you intended to operate your oxen on a frozen moon. An ox would not do well on a frozen moon and you'd be better off enslaving some other species more suited to the moon's environment. Taking an ox with you would be ill advised in this scenario.
  +This information would be important if for example, you intended to operate your oxen on a frozen moon. An ox would not do well on a frozen moon and you'd be better off enslaving some other species more suited to said moon's environment. Taking an ox with you would be ill advised in this scenario.
   
   <% end %>
   
  
positive.code: 
  This book started out like most development books, with a cuss word or two. I couldn't get my helpers where I wanted them. I cant remember where I wanted them, I just remember I wanted them somewhere they didn't want to go. Because helpers are blocks and blocks unlike procs, stay where they are. All I wanted was to include my helpers from a module like a sane rational developer gosh damn asfgjdhdh... sorry, I'm getting off track.
  
  I did the easy thing. I duplicated code. I copied my helpers to all the places I needed them. The solution was ugly and felt wrong, but it worked.
  
  I committed the code, finished the project, and went on with my life. But I still wondered: why in the world were helpers not modules?
  
  Like most developers I don't learn the internals of my tools until I encounter a problem. Until I spend hours cussing and nights stressing over bugs I don't know how to fix. Until GitHub issues and StackOverflow become my last hopes. Until I get so fed up that I finally `git clone` and read the code.
  
  This book covers what I learned about the frameworks ruby developers use every day. From the awkwardness of BodyProxy to the wonderful simplicity of Rack's call. From Sinatra to Rails and every Rack app in-between.
  
  You will learn the insides of Rack, the specification nearly all ruby frameworks conform to. You will learn how Sinatra gets all its methods into a single file and how Rails get its into so many. You will learn how middleware works and learn why streaming with Rack is hacky. You will learn how to write middleware and raw MVC apps without any framework. Ultimately, you will learn enough to build your own framework.
  
  This is a book for every developer that has ever _been hurt_ by a lack of understanding of Rack. Every developer that burnt themselves with Sinatra, Rails or _other_
  
  - For every cuss word, pain point, confusion, and broken site.
  - For every time you didn't take the time to save time.
  
negative.code: end
  ```
  
  At important points in the book there will be links to GitHub commits or branches. You can use them to keep your progress in sync with the book. They look like this:
  
  <%= commit    'yahweh/universe', '1',      'The Beginning of Everything. A commit Link' %>
  <%= gh_branch 'yahweh/universe', 'master', 'The Beginning of Everything. A branch link' %>
  