Merge pull request #129 from yardenshoham/patch-3

Fix rendering of "JSON Data APIs vs JSON REST APIs" title

book/CH05_htmxPatterns.adoc

@@ -336,7 +336,7 @@ In the interest of keeping our application simple, we are going to omit that mor
 
 We have updated the client-side code (if HTML can be considered code) so it now issues a `DELETE` request to the appropriate
 URL, but we still have some work to do.  Since we updated both the route and the HTTP method we are using, we are going to
-need to update the server-side implementation as well to handle this new HTTP Request.
+need to update the server-side implementation as well to handle this new HTTP request.
 
 .The original server-side code for deleting a contact
 [source, python]

book/CH08_TricksOfThehtmxMasters.adoc

@@ -276,6 +276,7 @@ both buttons in a `div` and eliminate the redundant `hx-target` specification by
 Here is our updated code:
 
 (((hx-sync, example)))
+
 .Syncing two buttons
 [source, html]
 ----

book/CH10_JSONDataAPIs.adoc

@@ -128,6 +128,7 @@ Note that by splitting these two APIs apart, you reduce the pressure to constant
 This is the key advantage of splitting your Data API from your Hypermedia API.
 
 ((("REST API")))
+
 .JSON Data APIs vs JSON "`REST`" APIs
 ****
 Unfortunately, today, for historical reasons, what we are calling JSON Data APIs are often referred to as