Update table and column descriptions

schemas/gcp/enriched/contracts.json

@@ -30,7 +30,7 @@
         "name": "block_timestamp",
         "type": "TIMESTAMP",
         "mode": "REQUIRED",
-        "description": "The timestamp for when the block was collated"
+        "description": "Timestamp of the block where this contract was created"
     },
     {
         "name": "block_number",

schemas/gcp/enriched/descriptions/blocks.txt

@@ -1,3 +1,3 @@
 The Ethereum blockchain is composed of a series of blocks.
 This table contains a set of all blocks in the blockchain and their attributes.
-Exported using https://github.com/medvedev1088/ethereum-etl
+Data is exported using https://github.com/medvedev1088/ethereum-etl

schemas/gcp/enriched/descriptions/contracts.txt

@@ -2,4 +2,4 @@ Some transactions create smart contracts from their input bytes, and this smart
 32-byte address.
 This table contains a subset of Ethereum addresses that contain contract byte-code, as well as some basic analysis
 of that byte-code.
-Exported using https://github.com/medvedev1088/ethereum-etl
+Data is exported using https://github.com/medvedev1088/ethereum-etl

schemas/gcp/enriched/descriptions/logs.txt

@@ -1,4 +1,4 @@
 Similar to the token_transfers table, the logs table contains data for smart contract events.
 However, it contains all log data, not only ERC20 token transfers.
 This table is generally useful for reporting on any logged event type on the Ethereum blockchain.
-Exported using https://github.com/medvedev1088/ethereum-etl
+Data is exported using https://github.com/medvedev1088/ethereum-etl

schemas/gcp/enriched/descriptions/token_transfers.txt

@@ -2,4 +2,4 @@ The most popular type of transaction on the Ethereum blockchain invokes a contra
 transfer operation, moving some number of tokens from one 20-byte address to another 20-byte address.
 This table contains the subset of those transactions and has further processed and denormalized the data to make it
 easier to consume for analysis of token transfer events.
-Exported using https://github.com/medvedev1088/ethereum-etl
+Data is exported using https://github.com/medvedev1088/ethereum-etl

schemas/gcp/enriched/descriptions/tokens.txt

@@ -1,2 +1,2 @@
 Token data.
-Exported using https://github.com/medvedev1088/ethereum-etl
+Data is exported using https://github.com/medvedev1088/ethereum-etl

schemas/gcp/enriched/descriptions/transactions.txt

@@ -2,4 +2,4 @@ Each block in the blockchain is composed of zero or more transactions.
 Each transaction has a source address, a target address, an amount of Ether transferred, and an array of input bytes.
 This table contains a set of all transactions from all blocks, and contains a block identifier to get associated
 block-specific information associated with each transaction.
-Exported using https://github.com/medvedev1088/ethereum-etl
+Data is exported using https://github.com/medvedev1088/ethereum-etl

schemas/gcp/enriched/logs.json

@@ -37,7 +37,7 @@
         "name": "block_timestamp",
         "type": "TIMESTAMP",
         "mode": "REQUIRED",
-        "description": "The timestamp for when the block was collated"
+        "description": "Timestamp of the block where this log was in"
     },
     {
         "name": "block_number",

schemas/gcp/enriched/token_transfers.json

@@ -35,7 +35,7 @@
         "name": "block_timestamp",
         "type": "TIMESTAMP",
         "mode": "REQUIRED",
-        "description": "The timestamp for when the block was collated"
+        "description": "Timestamp of the block where this transfer was in"
     },
     {
         "name": "block_number",

schemas/gcp/enriched/transactions.json

@@ -71,13 +71,13 @@
     {
         "name": "receipt_status",
         "type": "INT64",
-        "description": "Either 1 (success) or 0 (failure)"
+        "description": "Either 1 (success) or 0 (failure) (post Byzantium)"
     },
         {
         "name": "block_timestamp",
         "type": "TIMESTAMP",
         "mode": "REQUIRED",
-        "description": "The timestamp for when the block was collated"
+        "description": "Timestamp of the block where this transaction was in"
     },
     {
         "name": "block_number",

schemas/gcp/raw/receipts.json

@@ -44,6 +44,6 @@
     {
         "name": "status",
         "type": "INT64",
-        "description": "Either 1 (success) or 0 (failure)"
+        "description": "Either 1 (success) or 0 (failure) (post Byzantium)"
     }
 ]