diff options
| author | chriseth <chris@ethereum.org> | 2018-05-23 16:06:13 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-05-23 16:06:13 +0800 |
| commit | 18c651b7d39ec5808ce29431aee4e0a90aa1e24f (patch) | |
| tree | 99c33410b8110e4baa8e3b9c1cf1d5a3bcaa3e2e | |
| parent | 849b1bd59c8ad22f9fb32dcd65d57edc5d349d00 (diff) | |
| parent | ef1464a13c32fef6148c9305ed2b1fbf834049bd (diff) | |
| download | dexon-solidity-18c651b7d39ec5808ce29431aee4e0a90aa1e24f.tar.gz dexon-solidity-18c651b7d39ec5808ce29431aee4e0a90aa1e24f.tar.zst dexon-solidity-18c651b7d39ec5808ce29431aee4e0a90aa1e24f.zip | |
Merge pull request #4175 from FlashSheridan/patch-1
Minor changes to make the English more idiomatic
| -rw-r--r-- | docs/introduction-to-smart-contracts.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/introduction-to-smart-contracts.rst b/docs/introduction-to-smart-contracts.rst index d1789c44..71f9bd8e 100644 --- a/docs/introduction-to-smart-contracts.rst +++ b/docs/introduction-to-smart-contracts.rst @@ -33,7 +33,7 @@ Storage The first line simply tells that the source code is written for Solidity version 0.4.0 or anything newer that does not break functionality (up to, but not including, version 0.5.0). This is to ensure that the -contract does not suddenly behave differently with a new compiler version. The keyword ``pragma`` is called that way because, in general, +contract does not suddenly behave differently with a new compiler version. The keyword ``pragma`` is called that because, in general, pragmas are instructions for the compiler about how to treat the source code (e.g. `pragma once <https://en.wikipedia.org/wiki/Pragma_once>`_). @@ -62,7 +62,7 @@ so that only you can alter the number. the ASCII character set. It is possible to store UTF-8 encoded data in string variables. .. warning:: - Be careful with using Unicode text as similarly looking (or even identical) characters can + Be careful with using Unicode text, as similar looking (or even identical) characters can have different code points and as such will be encoded as a different byte array. .. index:: ! subcurrency @@ -75,7 +75,7 @@ cryptocurrency. It is possible to generate coins out of thin air, but only the person that created the contract will be able to do that (it is trivial to implement a different issuance scheme). Furthermore, anyone can send coins to each other without any need for -registering with username and password - all you need is an Ethereum keypair. +registering with username and password — all you need is an Ethereum keypair. :: @@ -88,7 +88,7 @@ registering with username and password - all you need is an Ethereum keypair. address public minter; mapping (address => uint) public balances; - // Events allow light clients to react on + // Events allow light clients to react to // changes efficiently. event Sent(address from, address to, uint amount); |