File tree 1 file changed +2
-2
lines changed
contracts/token/ERC20/extensions
1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -15,7 +15,7 @@ pragma solidity ^0.8.20;
15
15
*
16
16
* There are two important considerations concerning the use of `permit`. The first is that a valid permit signature
17
17
* expresses an allowance, and it should not be assumed to convey additional meaning. In particular, it should not be
18
- * considered as an intention to spend the approval in any specific way. The second is that because permits have
18
+ * considered as an intention to spend the allowance in any specific way. The second is that because permits have
19
19
* built-in replay protection and can be submitted by anyone, they can be frontrun. A protocol that uses permits should
20
20
* take this into consideration and allow a `permit` call to fail. Combining these two aspects, a pattern that may be
21
21
* generally recommended is:
@@ -32,7 +32,7 @@ pragma solidity ^0.8.20;
32
32
* }
33
33
* ```
34
34
*
35
- * Observe that: 1) `msg.sender` is used as the owner, leaving no ambiguity as to the signer intent, 2) the use of
35
+ * Observe that: 1) `msg.sender` is used as the owner, leaving no ambiguity as to the signer intent, and 2) the use of
36
36
* `try/catch` allows the permit to fail and makes the code tolerant to frontrunning. (See also
37
37
* {SafeERC20-safeTransferFrom}).
38
38
*
You can’t perform that action at this time.
0 commit comments