docs: Add chapter on control flow (#608)

nodejs · aug2uag · aug2uag · aug2uag · Apr 26, 2020 · aug2uag
diff --git a/src/documentation/0056-node-control-flow/index.md b/src/documentation/0056-node-control-flow/index.md
+section: Getting Started
+---
+
+I'm presenting material that's helped me greatly in the past from [Mixu's Node.js Book](http://book.mixu.net/node/ch7.html).
-I'm presenting material that's helped me greatly in the past from [Mixu's Node.js Book](http://book.mixu.net/node/ch7.html).
+The material in this post has been heavily inspired by [Mixu's Node.js Book chapter 7](http://book.mixu.net/node/ch7.html).
diff --git a/src/documentation/0056-node-control-flow/index.md b/src/documentation/0056-node-control-flow/index.md
+section: Getting Started
+---
+
+The material in this post are heavily inspired by [Mixu's Node.js Book](http://book.mixu.net/node/ch7.html).
-The material in this post are heavily inspired by [Mixu's Node.js Book](http://book.mixu.net/node/ch7.html).
+The material in this post is heavily inspired by [Mixu's Node.js Book](http://book.mixu.net/node/ch7.html).
diff --git a/src/documentation/0056-node-control-flow/index.md b/src/documentation/0056-node-control-flow/index.md
+
+The material in this post are heavily inspired by [Mixu's Node.js Book](http://book.mixu.net/node/ch7.html).
+
+At it's core, JavaScript is designed to be non-blocking on the "main" thread only. Other threads provide the ability to run tasks asynchronously at the cost of control.
-At it's core, JavaScript is designed to be non-blocking on the "main" thread only. Other threads provide the ability to run tasks asynchronously at the cost of control.
+At its core, JavaScript is designed to be non-blocking on the "main" thread only. Other threads provide the ability to run tasks asynchronously at the cost of control.
diff --git a/src/documentation/0056-node-control-flow/index.md b/src/documentation/0056-node-control-flow/index.md
+
+This creates some unique constraints that only a functional style of programming can cure. This is where "callbacks" come in to the picture.
+
+You may find yourself in "callback hell"
	I'm presenting material that's helped me greatly in the past from [Mixu's Node.js Book](http://book.mixu.net/node/ch7.html).
	The material in this post has been heavily inspired by [Mixu's Node.js Book chapter 7](http://book.mixu.net/node/ch7.html).
	The material in this post are heavily inspired by [Mixu's Node.js Book](http://book.mixu.net/node/ch7.html).
	The material in this post is heavily inspired by [Mixu's Node.js Book](http://book.mixu.net/node/ch7.html).

		The material in this post are heavily inspired by [Mixu's Node.js Book](http://book.mixu.net/node/ch7.html).

		At it's core, JavaScript is designed to be non-blocking on the "main" thread only. Other threads provide the ability to run tasks asynchronously at the cost of control.
	At it's core, JavaScript is designed to be non-blocking on the "main" thread only. Other threads provide the ability to run tasks asynchronously at the cost of control.
	At its core, JavaScript is designed to be non-blocking on the "main" thread only. Other threads provide the ability to run tasks asynchronously at the cost of control.

		This creates some unique constraints that only a functional style of programming can cure. This is where "callbacks" come in to the picture.

		You may find yourself in "callback hell"