minor markdown fixes for #44 https://youtu.be/E1vXNrN6BbU

Author: nelsonic

README.md

@@ -746,8 +746,8 @@ and corresponding writeup:
 
 ### 11. Todo List!
 
-The _ultimate_ test of whether you _learned/understood_ something is
-applying it to _different_ context to the one you learned in.
+The _ultimate_ test of whether you _learned/understood_ something is <br />
+_applying_ your knowledge to _different_ context from the one you learned in.
 
 Let's "_turn this up to eleven_" and build something "_useful_"!
 
@@ -839,13 +839,13 @@ to build something full-featured and easy/fast to read!!
 [![babel](https://cloud.githubusercontent.com/assets/194400/25772913/72a818f4-326c-11e7-8020-9b5dab715987.png)](https://twitter.com/iamdevloper/status/787969734918668289 "Babel, how to show off that you don't have core ES5 skills.")
 
 If you can build with "ES5" JavaScript: <br />
-a) you side-step the
+**a)** you side-step the
 [_noise_](https://twitter.com/iamdevloper/status/610191865216786432)
 and focus on core skills that **_already_ work everywhere**! <br />
 (_don't worry you can always "top-up" your
 JS knowledge later with ES6, etc!_)<br />
-b) you **don't** need to **waste time** installing
+**b)** you **don't** need to **waste time** installing
 [_**Two Hundred Megabytes**_](https://cloud.githubusercontent.com/assets/194400/13321493/39fcfa30-dbc7-11e5-8b05-f046675f9cb6.png)
 of dependencies just to run a simple project! <br />
-c) You ***save time*** (_for yourself, your team and end-users!_)
+**c)** You ***save time*** (_for yourself, your team and end-users!_)
 because your code is _already_ optimized to run in _any_ browser!

elmish.md

@@ -1,6 +1,6 @@
 # `Elm`(_ish_)
 
-### (How to Build a Front-end Micro-Framework _From Scratch_)
+### (How to Build a Front-end Micro-Framework _From Scratch_)
 
 ![elmlogo-ish](https://user-images.githubusercontent.com/194400/43213139-b70a4c68-902d-11e8-8162-3c7cb56b6360.png)
 <!-- the colors are deliberately "a bit off" to emphasize that
@@ -1510,7 +1510,7 @@ You should see something like this:
 https://stackoverflow.com/questions/2010892/storing-objects-in-html5-localStorage <br />
 + Spec: https://www.w3.org/TR/webstorage/#the-localstorage-attribute
 
-#### Implementation
+#### Implementation
 
 _Given_ that saving and retrieving the Todo List `model` to/from `localStorage`
 uses two "native" DOM API functions, we can _avoid_ writing our own functions
@@ -1637,7 +1637,6 @@ then checkout:
 https://stackoverflow.com/questions/494143/creating-a-new-dom-element-from-an-html-string-using-built-in-dom-methods-or-pro
 
 
-
 ## Notes
 
 <sup>1</sup><small>The reason for calling the micro-framework `Elm`(_ish_)

multiple-counters.md

@@ -23,9 +23,11 @@ see:
 
 
 This "_works_" and "_satisfies_ the _requirement_"
-of having multiple counters on the same "page".
-_However_, it's not a "sustainable" way of "extending" an app for the long term.
-Almost no "_real_" web application uses an `Integer` as the `model`.
+of having multiple counters on the same "page". <br />
+_However_, it's not a "sustainable" way of "extending"
+an app for the long term. <br />
+Almost no "_real_" web application uses an `Integer` as the `model`,
+so the "_complexity_" of the model will be much greater.
 
 We could leave the counter example `model` as an `Integer`
 and move on to the _next_ example (_Todo List_),
@@ -65,7 +67,7 @@ test('Test Update update(0) returns 0 (current state)', function(assert) {
 });
 ```
 This test is still _relevant_ because the Elm Architecture _always_
-returns the `model` _unchanged_ if no `action` is given.
+returns the `model` _unchanged_ if no `action` is given. <br />
 We need to _update_ this test to reflect the change in the `model` signature:
 ```js
 test('update({counters:[0]}) returns {counters:[0]} (current state unmodified)', function(assert) {