aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorchriseth <chris@ethereum.org>2017-10-16 20:29:40 +0800
committerGitHub <noreply@github.com>2017-10-16 20:29:40 +0800
commitc2fab07ccdf9000023dd9373d9072d44dcdd93d7 (patch)
tree371599ff569c324dc4f00b37db3217f0b4d06698
parentdbc8655b363d4023c987ccfea2db371cc0213200 (diff)
parent550653300b5deca3a26631eb883da68d72458bd6 (diff)
downloaddexon-solidity-c2fab07ccdf9000023dd9373d9072d44dcdd93d7.tar.gz
dexon-solidity-c2fab07ccdf9000023dd9373d9072d44dcdd93d7.tar.zst
dexon-solidity-c2fab07ccdf9000023dd9373d9072d44dcdd93d7.zip
Merge pull request #3087 from Casinelli/develop
Update abi-spec.rst
-rw-r--r--docs/abi-spec.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/abi-spec.rst b/docs/abi-spec.rst
index 0361458f..43757d24 100644
--- a/docs/abi-spec.rst
+++ b/docs/abi-spec.rst
@@ -279,7 +279,7 @@ Events
Events are an abstraction of the Ethereum logging/event-watching protocol. Log entries provide the contract's address, a series of up to four topics and some arbitrary length binary data. Events leverage the existing function ABI in order to interpret this (together with an interface spec) as a properly typed structure.
-Given an event name and series of event parameters, we split them into two sub-series: those which are indexed and those which are not. Those which are indexed, which may number up to 3, are used alongside the Keccak hash of the event signature to form the topics of the log entry. Those which as not indexed form the byte array of the event.
+Given an event name and series of event parameters, we split them into two sub-series: those which are indexed and those which are not. Those which are indexed, which may number up to 3, are used alongside the Keccak hash of the event signature to form the topics of the log entry. Those which are not indexed form the byte array of the event.
In effect, a log entry using this ABI is described as: