review fixes

documentation/composeAndExecute.md

@@ -12,7 +12,13 @@ Storage Transformers
     
 Event Transformers   
    * [Guide](../../staging/libraries/shared/factories/event/README.md)
-   * [Example](https://github.com/vulcanize/ens_transformers)
+   * [Example 1](https://github.com/vulcanize/ens_transformers/tree/master/transformers/registar)
+   * [Example 2](https://github.com/vulcanize/ens_transformers/tree/master/transformers/registry)
+   * [Example 3](https://github.com/vulcanize/ens_transformers/tree/master/transformers/resolver)
+
+Contract Transformers
+   * [Example 1](https://github.com/vulcanize/account_transformers)
+   * [Example 2](https://github.com/vulcanize/ens_transformers/tree/master/transformers/domain_records)
 
 ## Preparing transformers to work as a plugin for composeAndExecute
 To plug in an external transformer we need to:
@@ -24,7 +30,7 @@ or [ContractTransformerInitializer](../../staging/libraries/shared/transformer/c
 [storage](../../staging/libraries/shared/watcher/storage_watcher.go#L53),
 or [contract](../../staging/libraries/shared/watcher/contract_watcher.go#L68) watcher execution modes
 3. Create db migrations to run against vulcanizeDB so that we can store the transformer output
-    * Do not `goose fix` the transformer migrations   
+    * Do not `goose fix` the transformer migrations, this is to ensure they are always ran after the core vulcanizedb migrations which are kept in their fixed form
     * Specify migration locations for each transformer in the config with the `exporter.transformer.migrations` fields
     * If the base vDB migrations occupy this path as well, they need to be in their `goose fix`ed form
     as they are [here](../../staging/db/migrations)

documentation/docker.md

@@ -1,22 +0,0 @@
-# Start full environment in docker by single command
-
-## Geth Rinkeby
-
-make command        | description
-------------------- | ----------------
-rinkeby_env_up      | start geth, postgres and rolling migrations, after migrations done starting vulcanizedb container
-rinkeby_env_deploy  | build and run vulcanizedb container in rinkeby environment
-rinkeby_env_migrate | build and run rinkeby env migrations
-rinkeby_env_down    | stop and remove all rinkeby env containers
-
-Success run of the VulcanizeDB container require full geth state sync,
-attach to geth console and check sync state:
-
-```bash
-$ docker exec -it rinkeby_vulcanizedb_geth geth --rinkeby attach
-...
-> eth.syncing
-false
-```
-
-If you have full rinkeby chaindata you can move it to `rinkeby_vulcanizedb_geth_data` docker volume to skip long wait of sync.