Skip to content

Commit 98a678a

Browse files
authored
docs: cheatcode typos (#2845)
1 parent 6b3db2a commit 98a678a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/dev/cheatcodes.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ The concept of cheat codes and cheat code inspector is very simple.
3838

3939
In solidity cheat codes are calls to a specific address, the cheat code handler address:
4040

41-
`keccak(`address(bytes20(uint160(uint256(keccak256('hevm cheat code')))))`)`: 0x7109709ECfa91a80626fF3989D68f67F5b1DD12D
41+
`keccak(address(bytes20(uint160(uint256(keccak256('hevm cheat code'))))))`: 0x7109709ECfa91a80626fF3989D68f67F5b1DD12D
4242

4343
which can be initialized like `Cheats constant cheats = Cheats(0x7109709ECfa91a80626fF3989D68f67F5b1DD12D);`, when
4444
inheriting from `forge-std/Test.sol` it can be accessed via `vm.<cheatcode>` directly.
@@ -83,7 +83,7 @@ essentially a large `match` over the decoded `HEVMCalls` which serves as the imp
8383

8484
## Adding a new cheat code
8585

86-
This process consists of 3 steps:
86+
This process consists of 4 steps:
8787

8888
1. add the function signature to the `abigen!` macro so a new `HEVMCalls` variant is generated
8989
2. implement the cheat code handler

0 commit comments

Comments
 (0)