diff options
| author | Cryptomental <cryptomental.com@gmail.com> | 2018-07-10 15:17:33 +0800 |
|---|---|---|
| committer | Cryptomental <cryptomental.com@gmail.com> | 2018-07-11 04:57:59 +0800 |
| commit | eb92d5f760995aef4c79fcaa3f8c2437718ffc7f (patch) | |
| tree | cef370944f927172225a767a472afe75a626a349 /docs/frequently-asked-questions.rst | |
| parent | d454cec1bd8c95d0ab850a199bf9696dcebe14a5 (diff) | |
| download | dexon-solidity-eb92d5f760995aef4c79fcaa3f8c2437718ffc7f.tar.gz dexon-solidity-eb92d5f760995aef4c79fcaa3f8c2437718ffc7f.tar.zst dexon-solidity-eb92d5f760995aef4c79fcaa3f8c2437718ffc7f.zip | |
docs: Fix typos.
Used codespell and manual fixes.
Refs: #4442
Diffstat (limited to 'docs/frequently-asked-questions.rst')
| -rw-r--r-- | docs/frequently-asked-questions.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/frequently-asked-questions.rst b/docs/frequently-asked-questions.rst index 75693bdd..e64849ea 100644 --- a/docs/frequently-asked-questions.rst +++ b/docs/frequently-asked-questions.rst @@ -69,7 +69,7 @@ Can you return an array or a ``string`` from a solidity function call? Yes. See `array_receiver_and_returner.sol <https://github.com/fivedogit/solidity-baby-steps/blob/master/contracts/60_array_receiver_and_returner.sol>`_. What is problematic, though, is returning any variably-sized data (e.g. a -variably-sized array like ``uint[]``) from a fuction **called from within Solidity**. +variably-sized array like ``uint[]``) from a function **called from within Solidity**. This is a limitation of the EVM and will be solved with the next protocol update. Returning variably-sized data as part of an external transaction or call is fine. @@ -260,7 +260,7 @@ The third one is the stack, which is used to hold small local variables. It is almost free to use, but can only hold a limited amount of values. For almost all types, you cannot specify where they should be stored, because -they are copied everytime they are used. +they are copied every time they are used. The types where the so-called storage location is important are structs and arrays. If you e.g. pass such variables in function calls, their |