aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Grau <graup@users.noreply.github.com>2016-06-18 05:13:03 +0800
committerGitHub <noreply@github.com>2016-06-18 05:13:03 +0800
commit6aa069403a3c865569d7fb38b99eab95f9ecbce4 (patch)
treeb96c81ea74b2e0e7da31e5386fa6f75b58c7696b
parent371690f027aa681ac6c290e383aded5d38ae75ba (diff)
downloaddexon-solidity-6aa069403a3c865569d7fb38b99eab95f9ecbce4.tar.gz
dexon-solidity-6aa069403a3c865569d7fb38b99eab95f9ecbce4.tar.zst
dexon-solidity-6aa069403a3c865569d7fb38b99eab95f9ecbce4.zip
Fix typo in Libraries section
-rw-r--r--docs/contracts.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/contracts.rst b/docs/contracts.rst
index c94f8d99..bd85d258 100644
--- a/docs/contracts.rst
+++ b/docs/contracts.rst
@@ -742,10 +742,10 @@ only once at a specific address and their code is reused using the ``DELEGATECAL
(``CALLCODE`` until Homestead)
feature of the EVM. This means that if library functions are called, their code
is executed in the context of the calling contract, i.e. ``this`` points to the
-calling contract and especially the storage from the calling contract can be
+calling contract, and especially the storage from the calling contract can be
accessed. As a library is an isolated piece of source code, it can only access
state variables of the calling contract if they are explicitly supplied (it
-would have to way to name them, otherwise).
+would have no way to name them, otherwise).
Libraries can be seen as implicit base contracts of the contracts that use them.
They will not be explicitly visible in the inheritance hierarchy, but calls