diff options
| author | Skiral Inc <skiralinc@gmail.com> | 2017-07-27 07:17:43 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-07-27 07:17:43 +0800 |
| commit | 7f7927fd1d1b33394f46ebf11ab32187f7472136 (patch) | |
| tree | 7fd406c51710cc02d71b2a279ed8a68435d381ec | |
| parent | a605e4eb957f65ab172015bd4f03ee56445a9f91 (diff) | |
| download | dexon-solidity-7f7927fd1d1b33394f46ebf11ab32187f7472136.tar.gz dexon-solidity-7f7927fd1d1b33394f46ebf11ab32187f7472136.tar.zst dexon-solidity-7f7927fd1d1b33394f46ebf11ab32187f7472136.zip | |
fix misspell
| -rw-r--r-- | docs/security-considerations.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/security-considerations.rst b/docs/security-considerations.rst index 658c12b2..9efc5721 100644 --- a/docs/security-considerations.rst +++ b/docs/security-considerations.rst @@ -14,7 +14,7 @@ the source code is often available. Of course you always have to consider how much is at stake: You can compare a smart contract with a web service that is open to the -public (and thus, also to malicous actors) and perhaps even open source. +public (and thus, also to malicious actors) and perhaps even open source. If you only store your grocery list on that web service, you might not have to take too much care, but if you manage your bank account using that web service, you should be more careful. |