   signals (atoms, reactions, etc), NOT values. This argument exists for
   historical reasons and is borderline deprecated these days.
 
-  Example Usage:
-  --------------
-
-    (subscribe [:items])
-    (subscribe [:items \"blue\" :small])
-    (subscribe [:items {:colour \"blue\"  :size :small}])
-
+### Example Usage:
+   
+   ```clj
+   (subscribe [:items])
+   (subscribe [:items \"blue\" :small])
+   (subscribe [:items {:colour \"blue\"  :size :small}])
+   ```
+  
   Note: for any given call to `subscribe` there must have been a previous call
   to `reg-sub`, registering the query handler (function) for the `query-id` given.
 
-  Hint
-  ----
+  ### Hint
 
   When used in a view function BE SURE to `deref` the returned value.
   In fact, to avoid any mistakes, some prefer to define:
-
-     (def <sub  (comp deref re-frame.core/subscribe))
+   
+  ```clj
+  (def <sub  (comp deref re-frame.core/subscribe))
+  ```
 
   And then, within their views, they call  `(<sub [:items :small])` rather
   than using `subscribe` directly.
 
-  De-duplication
-  --------------
+  ### De-duplication
 
   Two, or more, concurrent subscriptions for the same query will source reactive
   updates from the one executing handler.

     3. in a unit test where immediate, synchronous processing is useful.

   Usage:
   
     (dispatch-sync [:sing :falsetto 634])
  "
  [event-v]
  (router/dispatch-sync event-v))

  value is ignored.

  Example Use
  First, registration ... associate `:effect2` with a handler.
 
  ```clj
  (reg-fx
     :effect2
     (fn [value]
        ... do something side-effect-y))
  ```
   
  Then, later, if an event handler were to return this effects map ...

  {...
