aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authora4nkit <aktjha@gmail.com>2018-06-13 15:20:32 +0800
committera4nkit <aktjha@gmail.com>2018-06-13 15:20:32 +0800
commitf79efb8dbfc20c36e83000e664df3be326a534d0 (patch)
treeb580fc632dce55d8f353258c7a91be93ae701265
parent62b05d415765d8ca31dad7001a4a49648845aa7e (diff)
downloaddexon-solidity-f79efb8dbfc20c36e83000e664df3be326a534d0.tar.gz
dexon-solidity-f79efb8dbfc20c36e83000e664df3be326a534d0.tar.zst
dexon-solidity-f79efb8dbfc20c36e83000e664df3be326a534d0.zip
fix typo
-rw-r--r--docs/contributing.rst2
-rw-r--r--docs/miscellaneous.rst2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/contributing.rst b/docs/contributing.rst
index 6717a8b9..b95cff1a 100644
--- a/docs/contributing.rst
+++ b/docs/contributing.rst
@@ -111,7 +111,7 @@ Example: ``./test/libsolidity/syntaxTests/double_stateVariable_declaration.sol``
A syntax test must contain at least the contract under test itself, followed by the seperator ``----``. The additional comments above are used to describe the
expected compiler errors or warnings. This section can be empty in case that the contract should compile without any errors or warnings.
-In the above example, the state variable ``variable`` was declared twice, which is not allowed. This will result in a ``DeclarationError`` stating that the identifer was already declared.
+In the above example, the state variable ``variable`` was declared twice, which is not allowed. This will result in a ``DeclarationError`` stating that the identifier was already declared.
The tool that is being used for those tests is called ``isoltest`` and can be found under ``./test/tools/``. It is an interactive tool which allows
editing of failing contracts using your prefered text editor. Let's try to break this test by removing the second declaration of ``variable``:
diff --git a/docs/miscellaneous.rst b/docs/miscellaneous.rst
index 0d49c3df..108d4c96 100644
--- a/docs/miscellaneous.rst
+++ b/docs/miscellaneous.rst
@@ -190,7 +190,7 @@ important for static analysis tools that operate on bytecode level and
for displaying the current position in the source code inside a debugger
or for breakpoint handling.
-Both kinds of source mappings use integer indentifiers to refer to source files.
+Both kinds of source mappings use integer identifiers to refer to source files.
These are regular array indices into a list of source files usually called
``"sourceList"``, which is part of the combined-json and the output of
the json / npm compiler.