aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorchriseth <chris@ethereum.org>2017-03-23 03:56:17 +0800
committerGitHub <noreply@github.com>2017-03-23 03:56:17 +0800
commit74d7c513895d28c9746f09d802069809030f2b97 (patch)
treed9cc11eed3e56c2958087bf9f3d1207626cc00e8
parentd626876310c6c4d134b97b847d199dd78d3c5bea (diff)
parent602ad1e60589afea65bbd33ff68605610aa88901 (diff)
downloaddexon-solidity-74d7c513895d28c9746f09d802069809030f2b97.tar.gz
dexon-solidity-74d7c513895d28c9746f09d802069809030f2b97.tar.zst
dexon-solidity-74d7c513895d28c9746f09d802069809030f2b97.zip
Merge pull request #1814 from abrahamsangha/fix-typo-intro-smart-contracts
small fixes
-rw-r--r--docs/introduction-to-smart-contracts.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/introduction-to-smart-contracts.rst b/docs/introduction-to-smart-contracts.rst
index f02447cf..9001a08c 100644
--- a/docs/introduction-to-smart-contracts.rst
+++ b/docs/introduction-to-smart-contracts.rst
@@ -146,7 +146,7 @@ single account.
The line ``event Sent(address from, address to, uint amount);`` declares
a so-called "event" which is fired in the last line of the function
-``send``. User interfaces (as well as server appliances of course) can
+``send``. User interfaces (as well as server applications of course) can
listen for those events being fired on the blockchain without much
cost. As soon as it is fired, the listener will also receive the
arguments ``from``, ``to`` and ``amount``, which makes it easy to track
@@ -161,7 +161,7 @@ transactions. In order to listen for this event, you would use ::
"Sender: " + Coin.balances.call(result.args.from) +
"Receiver: " + Coin.balances.call(result.args.to));
}
- }
+ })
Note how the automatically generated function ``balances`` is called from
the user interface.