Edited (after Kobo test read)

Signed-off-by: Jens Oliver Meiert <[email protected]>

Author: j9t

manuscript/acknowledgments.md

@@ -3,4 +3,4 @@
 
 With special thanks to [Tony Ruscoe](http://ruscoe.net/) and Kirsty MacRae for reviewing this book, and to Markus Käding for initial feedback on the cover design.
 
-Thanks, too, to Jurriaan Topper and [Jad Joubran](https://jadjoubran.io/) for suggestions for improvements.
+Thanks, too, to Jurriaan Topper and [Jad Joubran](https://jadjoubran.io/) for feedback.

manuscript/book.md

@@ -14,4 +14,4 @@ Contact +1-754-400-0999 or [email protected] for more information.
 
 Follow [Frontend Dogma on Mastodon](https://mas.to/@frontenddogma).
 
-[1.4.34]
+[1.5.0]

manuscript/intro.md

@@ -1,13 +1,13 @@
 {sample: true}
 # Introduction
 
-We live in exciting times; indeed politically, and in the context of this book, technologically. The times are exciting because there has never been a greater wealth of web technologies, tools, and resources to build ever more appealing and performant web sites and web apps.
+We live in exciting times; indeed politically, and in the context of this book, technologically. The times are exciting because there has never been a greater wealth of web technologies, tools, and resources to build ever more appealing and performant websites and apps.
 
 The times are also exciting because they are challenging. They are challenging because the wealth of technologies, tools, and resources has led to complexity and confusion.
 
 We can think of the confusion in terms of focus. Precisely, lack of focus, for with all the options we have it has become less apparent what we best pay attention to. This includes what we should do in the first place, and how we should work with what we have at our disposal. It relates to the sites and apps we build, to the frameworks and libraries we use, and—here we get back to why you’re holding this book in your hands—to the code and CSS we write.
 
-In this book we’ll look at ways to improve our CSS. We’ll go over why that generally matters, and why each method matters. We’ll also talk about what doesn’t matter so much. For example, processors. Much of that will have to do with quality as well as craft. Both I deem important, no less of an idea of web development would I wish to promote. How to best _automate_ such optimization is a great question, but first we need to understand what to optimize for exactly—and though it’s encouraged to automate as much as possible, whether optimization is to be done manually or automatically is not a concern of this book.
+In this book we’ll look at ways to improve our CSS. We’ll go over why that generally matters, and why each method matters. We’ll also talk about what doesn’t matter so much. For example, preprocessors. Much of that will have to do with quality as well as craft. Both I find important, no less of an idea of web development would I wish to promote. How to best _automate_ such optimization is a great question, but first we need to understand what to optimize for exactly—and though it’s encouraged to automate as much as possible, whether optimization is to be done manually or automatically is not a concern of this book.
 
 ## Why Optimization Is Important
 
@@ -25,12 +25,12 @@ Optimization has a touch of perfectionism, but it’s truly a means and not an e
 
 On the pages that follow, I won’t cover _all_ things relating to CSS development these days. The reason for this is simple: Not all of this relates to _optimization_. And so one thing I won’t cover are CSS preprocessors. Personally, I’ve sided with [Roger Johansson](https://www.456bereastreet.com/archive/201603/why_i_dont_use_css_preprocessors/) and outlined [reasons for not using preprocessors](https://meiert.com/en/blog/no-css-preprocessors/). The little there is to optimize through them is already going to be covered in other ways: for example, through repeat emphasis on coding and formatting standards.
 
-On top of that, I regard it useful to stay close to core technologies and not get distracted by abstractions. In the short run, we may benefit from knowing how to work with abstractions; in the long run, we get greater rewards from knowing the underlying technologies. Therefore, we’ll focus on standard CSS rather than preprocessors, like Sass, Less, or Stylus. And when we look at other CSS tools, we won’t discuss optimization of the use of these tools, their workflows, or how to improve the tools themselves, either.
+On top of that, I deem it useful to stay close to core technologies and not get distracted by abstractions. In the short run, we may benefit from knowing how to work with abstractions; in the long run, we get greater rewards from knowing the underlying technologies. Therefore, we’ll focus on standard CSS rather than preprocessors, like Sass, Less, or Stylus. And when we look at other CSS tools, we won’t discuss optimization of the use of these tools, their workflows, or how to improve the tools themselves, either.
 
 C> ⁂
 
 The code in this book follows [Google’s HTML/CSS style guide](https://google.github.io/styleguide/htmlcssguide.html). (For an introduction to coding guidelines and commentary on the Google style guide, see [_The Little Book of HTML/CSS Coding Guidelines_](https://www.oreilly.com/library/view/the-little-book/9781492048459/).)
 
-Before we begin, this is a self-published book made with little extra help. If you find mistakes in it, you have all reason to blame me, the author—but also an opportunity to help make the book a little better as a contributor (who are all acknowledged unless chosen otherwise). Please [file an issue](https://github.com/frontenddogma/css-optimization-basics/issues/new) for problems you find, or [submit a pull request](https://github.com/frontenddogma/css-optimization-basics/pulls) for specific fixes and suggestions. If you bought the book [through Leanpub](https://leanpub.com/css-optimization-basics) or [Google Play Books](https://play.google.com/store/books/details/Jens_Oliver_Meiert_CSS_Optimization_Basics?id=xgTfDwAAQBAJ) you should get updates containing your and other people’s fixes automatically. (Otherwise, there’s always [the original source](https://github.com/frontenddogma/css-optimization-basics).)
+Before we begin, this is a self-published book made with little extra help. You can blame me, the author, for mistakes—but you also have an opportunity to help make the book a little better. Please [file an issue](https://github.com/frontenddogma/css-optimization-basics/issues/new) for problems you find, or [submit a pull request](https://github.com/frontenddogma/css-optimization-basics/pulls) for specific fixes and suggestions. If you bought the book from [Leanpub](https://leanpub.com/css-optimization-basics) or [Google Play Books](https://play.google.com/store/books/details/Jens_Oliver_Meiert_CSS_Optimization_Basics?id=xgTfDwAAQBAJ), you should get updates containing your and other people’s fixes automatically. (Otherwise, there’s always [the original source](https://github.com/frontenddogma/css-optimization-basics).)
 
 Thank you for your support.

manuscript/mindsets.md

@@ -16,7 +16,7 @@ Knowing our goals and needs is important because it’s difficult to meet a goal
 
 ## Stay in the Present
 
-Without becoming self-helpish or philosophical, another useful mindset is to [stay in the present](https://meiert.com/en/blog/develop-for-what-is/), to stay in the now. This means both a keen eye to get rid of everything (documentation, design patterns, code snippets, libraries, &c.) that we don’t need and use anymore (“Know Your Needs”), as well as not to bother coding something that we don’t know is needed _with certainty_.
+Without becoming philosophical, another useful mindset is to [stay in the present](https://meiert.com/en/blog/develop-for-what-is/), to stay in the now. This means both a keen eye to get rid of everything (documentation, design patterns, code snippets, libraries, &c.) that we don’t need and use anymore (“Know Your Needs”), as well as not to bother coding something that we don’t know is needed _with certainty_.
 
 This mindset matters because it keeps our code base and our documentation clean, and hence contributes to our focus (“Do One Thing Really, Really Well,” “Keep It Simple”).
 
@@ -26,7 +26,7 @@ The idea to keep it simple has a lazy touch, yet requires a high level of skill.
 
 As such, keeping things simple requires that we thoroughly understand our field—the core technologies, first and foremost, but everything in between and to the sides as well. And it means economy of motion, because we don’t want to engage in something we don’t need to do.
 
-As a mindset, keeping it simple is truly grandiose, and you may not want to pick up a book on minimalism but rather one about focus—one of my recommendations is Gary Keller’s [_The One Thing_](https://www.the1thing.com/).
+As a mindset, keeping it simple is truly grandiose. To dive deeper, you may not need to start with a book on simplicity or minimalism, but rather one about focus—my recommendation is Gary Keller’s [_The One Thing_](https://www.the1thing.com/).
 
 ## Automate