 
   ### Data merge
 
-  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
+  Untangled will automatically merge (and normalize) the result of loads into the application client database.
+  Untangled overrides the built-in Om shallow merge to a merge that has a number of extension that are useful for
   simple application reasoning:
 
   #### 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:
+  this causes a different problem. Let's say you have two UI components (with the same Ident) that ask for similar information:
 
   Component A asks for [:a]
   Component A2 asks for [:a :b]


  ### Load vs. Load-Action

  Both `load-field` and `load-data` will call `om/transact!` under the hood, targeting untangled's built-in `untangled/load`
  mutation, which is responsible for sending your request to the server. By contrast, `load-field-action` and `load-data-action`,
  **do not** call `om/transact!`, and are used to initialize a load inside of one of your custom client-side mutations.

  Let's look at an example of a standard load. Say you want to load a list of people from the server:


  - `without`: A set of keywords that should be (recursively) removed from `query`
  - `refresh`: A vector of keywords that should cause re-rendering after the load.
  - `parallel`: True or false. If true, bypasses the sequential network queue
  - `target`: A key path where the result should be move to when the load is complete.
  - `marker`: True or false. If true, places a loading marker in place of the first top-level key in the query,
    of in place of the given database object if `ident` and `field` are set (e.g. by `load-field`)

  For most direct use-cases you'll probably skip using the `load-field` specific parameters. You can read
  the source of `load-field` if you'd like to simulate it by hand.

  For example:

  ```
  (load-data reconciler [:prop])
  ```

  is a simple helper that is ultimately identical to:

  ```
  (om/transact! reconciler '[(untangled/load {:query [:prop]}) :ui/loading-data])
  ```

  (the follow-on read is to ensure load markers update).

  #### Getting a Remote Value after a Mutation

