From 927f01c6d927734ce3ec62c15878745179961ae3 Mon Sep 17 00:00:00 2001 From: Yoichi Hirai Date: Wed, 26 Jul 2017 17:02:06 +0200 Subject: [PATCH] Fix grammar --- docs/control-structures.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/control-structures.rst b/docs/control-structures.rst index a2fae0b36..a7af69f5f 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