 
   ### Data merge
 
-  When the server responds Untangled will merge the result into the application client database. It overrides the built-in Om
+  Untangled will automatically merge the result of loads into the application client database.
+  It overrides the built-in Om
   shallow merge. Untangled's data merge has a number of extension that are useful for
   simple application reasoning:
 
-  1. Merge is a deep merge, but with extra logic
-
-  Untangled merges your response via deep merge, meaning that existing data is not wiped out by default. Unfortunately,
+  #### Deep Merge
+
+  Untangled merges the response via a deep merge, meaning that existing data is not wiped out by default. Unfortunately,
   this causes a different problem. Let's say you have two UI components that ask for similar information:
 
   Component A asks for [:a]

      not asked for alone). This does indicate that your UI is possibly in a state inconsistent with the server, which
      is the reason for the \"avoid this case\" advice.

  ### Normalization

  Normalization is always *on* in Untangled. You are forced to use the default database format. If you've passed an
  atom as initial state then initial state is assumed to be pre-normalized, but normalization will always be on. Loads
  must use real composed queries from the UI for normalization to work (the om `get-query` function adds info to assit
  with normalization).

  Therefore, you almost *never* want to use a hand-written query that has not been placed on a `defui`. It is perfectly
  acceptable to define queries via `defui` to ensure normalization will work, and this will commonly be the case if your
  UI needs to ask for data in a structure different from what you want to run against the server.

  ### Parameterized Reads

  You may add parameters to your remote reads using an optional argument to data fetch:

(ns untangled-tutorial.H-Server-Interactions
  (:require-macros [cljs.test :refer [is]]
                   [untangled-tutorial.tutmacros :refer [untangled-app]])
  (:require [om.next :as om :refer-macros [defui]]
            [om.dom :as dom]
            [devcards.core :as dc :refer-macros [defcard defcard-doc]]
            [untangled.client.mutations :as m]
            [untangled.client.core :as uc]))

; TODO: Explain Om's HATEOS (keyword listing in :keys)
; see: https://github.com/omcljs/om/wiki/Quick-Start-%28om.next%29
