Various README updates

documentation/composeAndExecute.md

@@ -1,6 +1,6 @@
 # composeAndExecute
 The `composeAndExecute` command is used to compose and execute over an arbitrary set of custom transformers.
-This is accomplished by generating a Go pluggin which allows the `vulcanizedb` binary to link to external transformers, so
+This is accomplished by generating a Go plugin which allows the `vulcanizedb` binary to link to external transformers, so
 long as they abide by one of the standard [interfaces](../staging/libraries/shared/transformer).
 
 Additionally, there are separate `compose` and `execute` commands to allow pre-building and linking to a pre-built .so file.

documentation/sync.md

@@ -1,22 +1,35 @@
 # Syncing commands
-These commands are used to sync raw Ethereum data into Postgres.
+These commands are used to sync raw Ethereum data into Postgres, with varying levels of data granularity.
 
 ## headerSync
-Syncs VulcanizeDB with the configured Ethereum node, populating only block headers.
-This command is useful when you want a minimal baseline from which to track targeted data on the blockchain (e.g. individual smart contract storage values or event logs).
-1. Start Ethereum node
+Syncs block headers from a running Ethereum node into the VulcanizeDB table `headers`.
+- Queries the Ethereum node using RPC calls.
+- Validates headers from the last 15 blocks to ensure that data is up to date.
+- Useful when you want a minimal baseline from which to track targeted data on the blockchain (e.g. individual smart contract storage values or event logs).
+
+##### Usage
+1. Start Ethereum node.
 1. In a separate terminal start VulcanizeDB:
-    - `./vulcanizedb headerSync --config <config.toml> --starting-block-number <block-number>`
-    
+`./vulcanizedb headerSync --config <config.toml> --starting-block-number <block-number>`
+
 ## sync
-Syncs VulcanizeDB with the configured Ethereum node, populating blocks, transactions, receipts, and logs.
-This command is useful when you want to maintain a broad cache of what's happening on the blockchain.
-1. Start Ethereum node (**if fast syncing your Ethereum node, wait for initial sync to finish**)
+Syncs blocks, transactions, receipts and logs from a running Ethereum node into VulcanizeDB tables named
+`blocks`, `uncles`, `full_sync_transactions`, `full_sync_receipts` and `logs`. 
+- Queries the Ethereum node using RPC calls.
+- Validates headers from the last 15 blocks to ensure that data is up to date.
+- Useful when you want to maintain a broad cache of what's happening on the blockchain.
+
+##### Usage
+1. Start Ethereum node (**if fast syncing your Ethereum node, wait for initial sync to finish**).
 1. In a separate terminal start VulcanizeDB:
-    - `./vulcanizedb sync --config <config.toml> --starting-block-number <block-number>`
+`./vulcanizedb sync --config <config.toml> --starting-block-number <block-number>`
 
 ## coldImport
-Sync VulcanizeDB from the LevelDB underlying a Geth node.
+Syncs VulcanizeDB from Geth's underlying LevelDB datastore and persists Ethereum blocks, 
+transactions, receipts and logs into VulcanizeDB tables named `blocks`, `uncles`, 
+`full_sync_transactions`, `full_sync_receipts` and `logs` respectively.
+
+##### Usage
 1. Assure node is not running, and that it has synced to the desired block height.
 1. Start vulcanize_db
    - `./vulcanizedb coldImport --config <config.toml>`