aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlex Beregszaszi <alex@rtfs.hu>2017-07-27 00:00:01 +0800
committerGitHub <noreply@github.com>2017-07-27 00:00:01 +0800
commita605e4eb957f65ab172015bd4f03ee56445a9f91 (patch)
treecf5b5e7dfc8c2752695d50c0d1c5a2c22ccb0f5d
parent925569bfa32c6eb1c024e0d860f550119235cd81 (diff)
parent927f01c6d927734ce3ec62c15878745179961ae3 (diff)
downloaddexon-solidity-a605e4eb957f65ab172015bd4f03ee56445a9f91.tar
dexon-solidity-a605e4eb957f65ab172015bd4f03ee56445a9f91.tar.gz
dexon-solidity-a605e4eb957f65ab172015bd4f03ee56445a9f91.tar.bz2
dexon-solidity-a605e4eb957f65ab172015bd4f03ee56445a9f91.tar.lz
dexon-solidity-a605e4eb957f65ab172015bd4f03ee56445a9f91.tar.xz
dexon-solidity-a605e4eb957f65ab172015bd4f03ee56445a9f91.tar.zst
dexon-solidity-a605e4eb957f65ab172015bd4f03ee56445a9f91.zip
Merge pull request #2639 from ethereum/grammar
Fix grammar
-rw-r--r--docs/control-structures.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/control-structures.rst b/docs/control-structures.rst
index a2fae0b3..a7af69f5 100644
--- a/docs/control-structures.rst
+++ b/docs/control-structures.rst
@@ -383,7 +383,7 @@ state in the current call (and all its sub-calls) and also flag an error to the
The convenience functions ``assert`` and ``require`` can be used to check for conditions and throw an exception
if the condition is not met. The ``assert`` function should only be used to test for internal errors, and to check invariants.
The ``require`` function should be used to ensure valid conditions, such as inputs, or contract state variables are met, or to validate return values from calls to external contracts.
-If used properly, analysis tools can evaluate your contract to identify the conditions and function calls which will reach a failing ``assert``. Properly functioning code should never it is reach a failing assert statement, if this happens there is a bug in your contract which you should fix.
+If used properly, analysis tools can evaluate your contract to identify the conditions and function calls which will reach a failing ``assert``. Properly functioning code should never reach a failing assert statement; if this happens there is a bug in your contract which you should fix.
There are two other ways to trigger exceptions: The ``revert`` function can be used to flag an error and
revert the current call. In the future it might be possible to also include details about the error