code

Author: arthurfiorette

README.md

@@ -59,9 +59,7 @@ On the other hand, the `catch {}` block **is** genuine control flow, making its
 
 > a person or thing that is excluded from a general statement or does not follow a rule.
 
-Since `catch` is explicitly handling exceptions, it makes sense to encapsulate exception-handling logic in a block that separates it from the normal program flow.
-
-<br />
+Since `catch` is explicitly handling exceptions, it makes sense to encapsulate exception-handling logic in a block that separates it. Following the same line of thought, there is no logical reason to also encapsulate the non-exceptional flow in a block.
 
 Consider a simple function like this:
 
@@ -76,8 +74,6 @@ function getPostInfo(session, postSlug, cache, db) {
 }
 ```
 
-<br />
-
 But **production code is rarely this clean**. Error handling quickly forces a messier structure:
 
 ```js
@@ -118,8 +114,6 @@ The `try` blocks didn't provide much value beyond introducing unnecessary nestin
 
 Instead, using the proposed `try` operator simplifies the function:
 
-<br />
-
 ```js
 function getPostInfo(session, postId, cache, db) {
   const [userOk, userErr, user] = try cache.getUser(session.userId)