Updated JSON RPC Error Codes Improvement Proposal (markdown)

Author: Neurone

JSON-RPC-Error-Codes-Improvement-Proposal.md

@@ -41,7 +41,7 @@ They will be contained in the `data` field of the RPC error message as follows:
     message: 'Execution error',
     data: [{
         code: 102,
-        message: 'Innsufficient gas'
+        message: 'Insufficient gas'
     },
     {
         code: 103,
@@ -53,7 +53,7 @@ They will be contained in the `data` field of the RPC error message as follows:
 | Code    | Possible Return message | Description |
 | --------|-------------------------|-------------|
 |100 | X doesn't exist    | Should be used when something which should be there is not found. (Doesn't apply to eth_getTransactionBy* and eth_getBlock*. They return a success with value `null`)
-|101 | Requires ether         | Should be used for actions which require somethin else, e.g. gas or a value.
+|101 | Requires ether         | Should be used for actions which require something else, e.g. gas or a value.
 |102 | Gas too low           | Should be used when a to low value of gas was given.
 |103 | Gas limit exceeded   | Should be used when a limit is exceeded, e.g. for the gas limit in a block.
 |104 | Rejected           | Should be used when an action was rejected, e.g. because of its content (too long contract code, containing wrong characters ?, should differ from `-32602` - Invalid params).
@@ -64,5 +64,5 @@ They will be contained in the `data` field of the RPC error message as follows:
 
 | Code    | Possible Return message | Description |
 | --------|-------------------------|-------------|
-|106 | Timeout            | Should be used when an action timedout.
+|106 | Timeout            | Should be used when an action timed out.
 |107 | Conflict           | Should be used when an action conflicts with another (ongoing?) action.