aboutsummaryrefslogtreecommitdiffstats
path: root/docs/frequently-asked-questions.rst
diff options
context:
space:
mode:
authorchriseth <chris@ethereum.org>2018-07-11 17:52:22 +0800
committerGitHub <noreply@github.com>2018-07-11 17:52:22 +0800
commit07910c80cb42a717212cf6b0a4c405eff20e6051 (patch)
tree7ab4a06da70cde7c253a1a0c82ccc085bf76efd5 /docs/frequently-asked-questions.rst
parentd84976dc871a1fdfab233650b989af69e325bf2b (diff)
parent140dbfdbd8f4319d1d02339feea0a8636a3738e5 (diff)
downloaddexon-solidity-07910c80cb42a717212cf6b0a4c405eff20e6051.tar.gz
dexon-solidity-07910c80cb42a717212cf6b0a4c405eff20e6051.tar.zst
dexon-solidity-07910c80cb42a717212cf6b0a4c405eff20e6051.zip
Merge pull request #4462 from cryptomental/feature/add-codespell
Feature/add codespell
Diffstat (limited to 'docs/frequently-asked-questions.rst')
-rw-r--r--docs/frequently-asked-questions.rst4
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