@@ -31,9 +31,9 @@ and Event signatures for a given smart contract. Along with [Names](/data-model/
3131use of ABIs goes a very long way towards making your Ethereum data much more understandable.
3232
3333Similar to names of addresses, ABI files are not available on-chain which means they must be
34- acquired somewhere. Unfortunately, the Ethereum community has not yet understand that Etherscan
34+ acquired somewhere. Unfortunately, the Ethereum community has not yet understood that Etherscan
3535is not a good place to store this very important information. For this reason, TrueBlocks uses
36- Etherscan to acquire ABI files and therefor one needs to get an Etherscan API key to use this
36+ Etherscan to acquire ABI files and therefore one needs to get an Etherscan API key to use this
3737function.
3838
3939The following commands produce and manage Abis:
@@ -96,9 +96,9 @@ Functions consist of the following fields:
9696
9797Parameters are a constituent part of a [ Function or Event] ( /data-model/accounts/#function ) . The
9898parameters of a function are each individual value passed into the function. Along with the
99- function's name, the parameters types (once canonicalized) are used to create a function's four
99+ function's name, the parameter types (once canonicalized) are used to create a function's four
100100byte signature (or an event's 32-byte signature). Parameters are important to TrueBlocks because
101- we use them as part of the ABI decoding and the ` --articulate ` process to conver the blockchain's
101+ we use them as part of the ABI decoding and the ` --articulate ` process to convert the blockchain's
102102bytes into human-readable text.
103103
104104The following commands produce and manage Parameters:
0 commit comments