Update README.md

Author: pazams

src/pages/error-handling/README.md

@@ -7,6 +7,7 @@ Both languages pass errors as regular values. Also, both languages leverage flow
 Despite the similarity claimed above, the languages differ on how and when errors are handled:
 
 **JS**
+
 In JS, the way to propagate an error is determined by the synchronous or asynchronous nature of the function.
 If a function is synchronous, then it should use `throw` when an error occurs, and the caller should use `try/catch` blocks.
 
@@ -15,6 +16,7 @@ Otherwise, an asynchronous function should propagate the error by passing it as
 Note the `async/await` mechanism, which is in draft, will consolidate both worlds by having asynchronous errors being handled inside `try/catch` blocks.
 
 **Go**
+
 In Go on the other hand, the way to propagate an error is determined by the degree of severity with context of the whole application.
 
 For example, for a web-server application, if errors occur in a request handling code path, they should not crash the entire server.  Therefore, these errors should be returned as a last argument to the caller.