Skip to content

Commit f1554ea

Browse files
author
Ikko Ashimine
authored
Fix typo in security/index.md
maximium -> maximum
1 parent 0949d36 commit f1554ea

File tree

1 file changed

+1
-1
lines changed
  • src/content/developers/docs/smart-contracts/security

1 file changed

+1
-1
lines changed

src/content/developers/docs/smart-contracts/security/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ As mentioned, anyone can call public functions in your smart contract once it is
4646

4747
**`require()`**: `require` are defined at the start of functions and ensures predefined conditions are met before the called function is executed. A `require` statement can be used to validate user inputs, check state variables, or authenticate the identity of the calling account before progressing with a function.
4848

49-
**`assert()`**: `assert()` is used to detect internal errors and check for violations of “invariants” in your code. An invariant is a logical assertion about a contract’s state that should hold true for all function executions. An example invariant is the maximium total supply or balance of a token contract. Using `assert()` ensures that your contract never reaches a vulnerable state, and if it does, all changes to state variables are rolled back.
49+
**`assert()`**: `assert()` is used to detect internal errors and check for violations of “invariants” in your code. An invariant is a logical assertion about a contract’s state that should hold true for all function executions. An example invariant is the maximum total supply or balance of a token contract. Using `assert()` ensures that your contract never reaches a vulnerable state, and if it does, all changes to state variables are rolled back.
5050

5151
**`revert()`**: `revert()` can be used in an if-else statement that triggers an exception if the required condition is not satisfied. The sample contract below uses `revert()` to guard the execution of functions:
5252

0 commit comments

Comments
 (0)