add changes 😯

chapter10/chapter10.md

@@ -325,7 +325,7 @@ When things go south (e.g., memory leaks, overloads, crashes), there are two thi
 Monitoring
 ----------
 
-<span id="monitor" class="anchor"></span>When going to production, software and development operations engineers need a way to get current status quickly. Having a dashboard or just an end point that spits out JSON-formatted properties is a good idea, including properties such as the following:
+<span id="monitor" class="anchor"></span>When going to production, software and development operations engineers need a way to get current status quickly. Having a dashboard or just an endpoint that spits out JSON-formatted properties is a good idea, including properties such as the following:
 
 -   `memoryUsage`: memory usage information
 -   `uptime`: number of seconds the Node.js process is running

chapter2/chapter2.md

@@ -906,3 +906,5 @@ Nothing fancy so far, but it's worth pointing out that it took us just a few
 # Summary
 
 In this chapter we learned what Express.js is and how it works. We also explored different ways to install it and use its scaffolding (command-line tool) to generate apps. We went through the Blog example with a high-level overview (traditional vs. REST API approaches), and proceeded with creating the project file, folders, and the simple Hello World example, which serves as a foundation for the book's main project: the Blog app. And then lastly, we touched on a few topics such as settings, a typical request process, routes, AJAX versus server side, Pug, templates, and middleware.
+
+In the next chapter we'll examine an important aspect of modern web development and software engineering: test-driven development. We look at the Mocha module and write some tests for Blog in true TDD/BDD style. In addition, the next chapter deals with adding a database to Blog routes to populate these templates, and shows you how to turn them into working HTML pages!