fix: minor typos (#141)

README.md

@@ -20,7 +20,7 @@ We are specifically interested if you find one of the following:
 - typos
 - grammatical errors
 - factual errors
-- poor explanations that are unaccessible for beginners
+- poor explanations that are inaccessible for beginners
 - poor structure within a book section
 
 This list is not exhaustive - if you think that an interesting piece of trivia or a funny joke would add value to this book, don't hesitate to contribute it.

src/chapter1/README.md

@@ -4,6 +4,6 @@
 
 First we will need to go through the basics of the JavaScript language that we will use pretty much everywhere throughout this book. After all the Next.js stack is built on top of it.
 
-You will setup your runtime, learn about variables, data types, operators and control flow. You will also learn how to write functions and how to think _functionally_. Thinking _functionally_ will make you a better software developer and a better person. Isn't that great?
+You will set up your runtime, learn about variables, data types, operators and control flow. You will also learn how to write functions and how to think _functionally_. Thinking _functionally_ will make you a better software developer and a better person. Isn't that great?
 
 Let's dive right in!

src/chapter2/README.md

@@ -6,7 +6,7 @@ Now that we learned the basics of JavaScript, we could theoretically dive right
 However, JavaScript as a language has a central problem—it does not come with type checking.
 For example, there is nothing preventing you from trying to add two objects except the fact that—well—your application will crash and burn.
 
-In general, one the most common error sources are what can be described as type errors: a certain kind of value was used where a different kind of value was expected.
+In general, one of the most common error sources are what can be described as type errors: a certain kind of value was used where a different kind of value was expected.
 This could be due to simple typos, a failure to understand how to use a library correctly, incorrect assumptions about runtime behavior and more.
 
 The goal of TypeScript is to provide static type checking for JavaScript programs—in other words, TypeScript provides you with tooling that runs before your code is executed (static) and ensures that the types of the program are correct (type checking).

src/chapter4/README.md

@@ -7,6 +7,6 @@ So far we've introduced the programming language that will power our project (Ty
 But our users don't really care about the code we write nor the theory we know—they care about their _data_.
 After all, the primary purpose of web applications is to ingest and show interesting data to the user.
 
-Of course, it would be really bad if after every page refresh that data would be lost—therefore we need a way to store data _persistenly_ which is where _relational databases_ and the SQL language come into play.
+Of course, it would be really bad if after every page refresh that data would be lost—therefore we need a way to store data _persistently_ which is where _relational databases_ and the SQL language come into play.
 
 This chapter will introduce these concepts.

src/chapter5/README.md

@@ -2,7 +2,7 @@
 
 <div style="text-align: right"> <i> I hate Drizzle <br> — From Drizzles' official marketing page </i> </div>
 
-Drizzle is a ORM (object relational mapping) framework written in TypeScript.
+Drizzle is an ORM (object relational mapping) framework written in TypeScript.
 ORM frameworks allow you to convert data between regular (TypeScript) objects and SQL rows.
 
 Basically, instead of writing SQL queries directly and then laboriously translating the results between TypeScript objects and SQL rows, you let the ORM do the translation for you.

src/chapter7/README.md

@@ -1,6 +1,6 @@
 # Chapter 7: Adding Spice with React
 
-<div style="text-align: right"> <i> What's a React developer's favorite place to hang out? <br> The State Park. <br> - From "1000 programming dad-jokes" </i> </div>
+<div style="text-align: right"> <i> What's a React developer's favorite place to hang out? <br> The State Park. <br> — From "1000 programming dad-jokes" </i> </div>
 
 In this chapter we will create a simple (website) client using React.
 This client will allow us to add and delete tasks, where each task will have a title and a description.

src/chapter8/README.md

@@ -1,6 +1,6 @@
 # Chapter 8: Moving to the Server with Next.js
 
-<div style="text-align: right"> <i> Why did the Next.js developer order the steak? <br> Because he wanted a full-steak experience. <br> - From "1000 programming dad-jokes" </i> </div>
+<div style="text-align: right"> <i> Why did the Next.js developer order the steak? <br> Because he wanted a full-steak experience. <br> — From "1000 programming dad-jokes" </i> </div>
 
 Now that you have a rough overview of React, we want to move to the server.
 Next.js is a React-based framework for building full-stack applications.

src/chapter9/README.md

@@ -1,8 +1,8 @@
 # Chapter 9: Becoming Pretty with Tailwind CSS
 
-<div style="text-align: right"> <i> I feel like an idiot for not using Tailwind CSS until now. <br> - Ryan Florence </i> </div>
+<div style="text-align: right"> <i> I feel like an idiot for not using Tailwind CSS until now. <br> — Ryan Florence </i> </div>
 
-So far, our pages are functional, but they're not pretty to look.
+So far, our pages are functional, but they're not pretty to look at.
 
 CSS (short for Cascading Style Sheets) is a special language that is used for specifying the styling of an HTML document.
-We won't use CSS directly, but rather Tailwind CSS - a utility-first CSS framework that greatly simplifies the styling process.
+We won't use CSS directly, but rather Tailwind CSS—a utility-first CSS framework that greatly simplifies the styling process.

src/introduction.md

@@ -2,11 +2,11 @@
 
 <div style="text-align: right"> <i>No one reads introductions anyway.<br> — Sun Tzu</i></div>
 
-Long gone are the times when JavaScript was just a scripting language to add simple interactive behaviour to websites. The ECMAScript 2015 standard significantly improved the usability of the language. Excellent UI libraries like React allow you to write straightforward declarative code which massively simplifies building user interfaces. Thanks to Node.js you can write JavaScript on the server. Next.js empowers you to write complex APIs very quickly and PostgreSQL provides a relational database that fits right in with the other tools. The Next.js stack therefore allows you to quickly develop complex applications using just one language - JavaScript (with optional type hints via TypeScript).
+Long gone are the times when JavaScript was just a scripting language to add simple interactive behaviour to websites. The ECMAScript 2015 standard significantly improved the usability of the language. Excellent UI libraries like React allow you to write straightforward declarative code which massively simplifies building user interfaces. Thanks to Node.js you can write JavaScript on the server. Next.js empowers you to write complex APIs very quickly and PostgreSQL provides a relational database that fits right in with the other tools. The Next.js stack therefore allows you to quickly develop complex applications using just one language—JavaScript (with optional type hints via TypeScript).
 
-This book serves as an introduction to the Next.js stack. However you don't learn software development by _just_ reading books, you learn it by creating projects. We will therefore not bombard you with useless language trivia for hundreds of pages. If you care about that, go read the standard - it's _pretty comprehensive_. Instead we will create a real software project - an application for managing tasks called **easy-opus** (get it?). We will begin with nothing more than an empty project directory and the _will to learn_. We will end with a useful piece of software that allows us to create tasks, assign tasks to different users, update their statuses and much more.
+This book serves as an introduction to the Next.js stack. However you don't learn software development by _just_ reading books, you learn it by creating projects. We will therefore not bombard you with useless language trivia for hundreds of pages. If you care about that, go read the standard—it's _pretty comprehensive_. Instead we will create a real software project—an application for managing tasks called **easy-opus** (get it?). We will begin with nothing more than an empty project directory and the _will to learn_. We will end with a useful piece of software that allows us to create tasks, assign tasks to different users, update their statuses and much more.
 
-This book is therefore _inherently practical_ - unlike some other literature we will not dwell much on theoretical considerations. On the other hand, purely practical concerns are first-class citizens here (for example there is an entire chapter devoted to hosting your application). This doesn't mean that _theory bad, practice good_. It simply means that the approach for _this particular book_ is heavily geared towards completing a real software project.
+This book is therefore _inherently practical_—unlike some other literature we will not dwell much on theoretical considerations. On the other hand, purely practical concerns are first-class citizens here (for example there is an entire chapter devoted to hosting your application). This doesn't mean that _theory bad, practice good_. It simply means that the approach for _this particular book_ is heavily geared towards completing a real software project.
 
 This book is therefore also _not_ about becoming *yet another JavaScript guru*™ (there are already too many of them). It's about writing a useful product. It is fundamentally about **getting things done**. The Next.js stack is really just a tool we use to get things done.