- fixing titles

Author: JKHeadley

website/blog/2018-06-26-How-To-Build-Powerful-APIs-Blazingly-Fast-With-Nodejs.md

@@ -37,7 +37,8 @@ Are any of these good reasons to write weak code? Of course not, but they exist
 
 > you’re in for a wild ride
 
-The Story
+# The Story
+
 For the past several years I’ve been working as a web developer for the software consultancy [Scal.io](http://scal.io/). During this time I’ve had the pleasure of learning Node.js and working on multiple apps all serving RESTful APIs. At first everything seemed great. I mean, just google [any tutorial](https://www.google.com/search?q=how+to+build+node+api&oq=how+to+build+node+api&aqs=chrome..69i57.5240j0j9&sourceid=chrome&ie=UTF-8) for building a RESTful API with Node.js. You’ll find tons of articles and videos on how to have your own server up and running in minutes.
 
 Wow! This stuff is easy! (I thought) At least at first…
@@ -57,7 +58,8 @@ After working on several projects together, a [buddy of mine](https://github.com
 
 I knew we were on to something…
 
-The Journey
+# The Journey
+
 Soon after we completed that project I started looking into how we could take what we had created and make a useful tool out of it. The original solution worked well, but it was [tightly coupled](https://www.agiletestingframework.com/devops-journey/transformation/tightly-coupled-code/) to the project and still lacked a good amount of functionality. I spent days brainstorming and re-writing code. After what seemed like a huge amount of effort, I finally had a [workable solution](https://hackernoon.com/the-problem-with-apis-331f08f7a39c). However (like most beginnings)…it was pretty embarrassing.
 
 The tool worked, but it existed as a framework that you had to clone directly from GitHub (eww). The developer was forced to design their project around the framework and it still lacked a lot of functionality, even compared to our original solution.
@@ -83,7 +85,7 @@ I always believed in the core concept of the project but it was exciting to have
 
 The more it improved the more I felt we had really tapped into a goldmine for RESTful API development. The resulting code was consistent, robust, and easy to follow (standards…yay!). Not only that, but what previously took days or weeks to develop now could be done in just a few hours!
 
-The Result
+# The Result
 
 <p align="center"><img width="367" height="298" src="https://cdn-images-1.medium.com/max/800/1*fpvgfJJX0LjR74xVMZ3oUQ.png" alt="serious"></a></p>