Minor punctuation and grammatical fixes to Preface and History. (#61)

* Minor punctuation and grammatical fixes to Preface and History.

* Spelling, wording, and punctuation fixes

---------

Co-authored-by: Clint Herron <hanclinto@gmail.com>
Co-authored-by: Hendrik Kleinwaechter <hendrik.kleinwaechter@gmail.com>

book/intro/preface.tex

@@ -8,7 +8,7 @@ It was a white fluffy sandwich bread, and she made it within one to two hours us
 Being a bit more experienced, I now realize it's
 ideal to wait a little while before cutting into your bread, but back then,
 we kids couldn't wait. Mom would cut for us a few slices straight from the oven, and we would
-immediately proceed to pour butter or jam on each slice. Within minutes, 1kg of
+immediately proceed to pour butter or jam on each slice. Within minutes, 1 kg of
 flour would be consumed. Bread became an integral part of my weekly food.
 
 I was lucky that my parents could afford a yearly ski trip to
@@ -34,7 +34,7 @@ For the first time, I was faced with shopping for my own bread. It was never
 on my mind to actually start baking it for myself. I would just buy 
 a good loaf while shopping at the supermarket. My favorite variety
 was a Schwarzbrot, Korn an Korn. It’s a very dark and hearty rye bread
-with added berries and sunflower seeds. Being a little naive,
+with added berries and sunflower seeds. Being a little naïve,
 I'd never before examined the packaging of what I was buying. One day, that
 changed.
 
@@ -62,7 +62,7 @@ steps to follow. The baking instructions and temperatures were all different, to
 Meanwhile, having completed my studies, I started work as an engineer.
 We engineers are faced with many challenges. The compiler or runtime is
 always screaming at you with errors, and it's your job to figure out how to fix them.
-It can take hours, sometimes days just to fix a simple problem. If you want
+It can take hours, sometimes days, just to fix a simple problem. If you want
 to become a software engineer, you have to develop a certain ``never-give-up'' attitude.
 
 When writing code, software engineers often need to use a set of pre-made routines. These routines have been
@@ -79,20 +79,20 @@ bug. That is when the developer must dig deeper to see the 'what' and the 'why'
 the framework is doing. You will need to read other engineer's source code, and you will be forced
 to understand {\it why} things are happening.
 
-Being unhappy with what I was baking, my engineering mindset took over and I had
+Being unhappy with what I was baking, my engineering mindset took over, and I had
 to do my own deep dive to understand what was going on. Much to my surprise, however,
 none of the recipes I'd encountered would tell me {\it why} I should use amount X
 of water and amount Y of flour, or {\it why} exactly I should use fresh yeast over dry yeast. Why
 should I slap my dough while kneading it on the counter? Why is a standmixer
 better than kneading by hand?  Why should I let the dough sit for this long?
 Why is steaming the dough during baking important? Do I really need to
-get myself an expensive dutch oven to bake bread?
+get myself an expensive Dutch oven to bake bread?
 
 The problem compounded when I started reading about sourdough. It all sounded like black
 magic. Why were some sourdoughs made from fruits, while others were made from flour?
 Why should one recipe use wheat while another used rye or spelt? How often should the
 sourdough be fed? The questions I had then could have filled 20 pages. I was confused,
-but became even more determined to learn how decent bread should be made at home.
+but I became even more determined to learn how decent bread should be made at home.
 
 The feedback I received from friends helped me to improve with each
 iteration of homemade bread. Compared to coding, where you sometimes have to wait months
@@ -150,7 +150,7 @@ I have developed similar algorithms myself as a software engineer.
 I've since decided to take some time off from the algorithm cycle to work on something more
 long term and meaningful. My mission has always been to share my knowledge with as many people
 in the world as possible. That's also why my content has been provided in English rather than
-German. After discussing with members of the community, I figured that writing a book could
+German. After discussions with members of the community, I figured that writing a book could
 help me achieve that goal. Most of the books that exist today are collections of recipes. My
 idea, however, is to provide you with a deeper foundation of knowledge that you can use to
 follow other recipes.
@@ -162,7 +162,7 @@ and more. It should provide a detailed understanding as to why certain steps are
 and how to adapt then when things go wrong while making bread.
 
 It is my desire for this knowledge to be accessible to everyone around the world, regardless
-of budget, and as such, do not want to charge for the book. That's why I've decided to make
+of budget, and as such, I do not want to charge for the book. That's why I've decided to make
 it open source and have asked the community to support my work financially via my ko-fi page
 (https://ko-fi.com/thebreadcode). The community's feedback has been amazing so far, and
 I've already raised much more money than initially expected.