From 87d4a1e3b1af8faaa71a6f14a2c76f7b4ee62dfd Mon Sep 17 00:00:00 2001 From: snoppy Date: Mon, 27 May 2024 11:25:44 +0800 Subject: [PATCH] chore: fix typos Signed-off-by: snoppy --- .../lib/reference/lib/forge-std/src/interfaces/IERC4626.sol | 2 +- .../lib/openzeppelin-contracts/lib/forge-std/src/Script.sol | 2 +- .../lib/openzeppelin-contracts/lib/forge-std/src/Vm.sol | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/contracts/lib/reference/lib/forge-std/src/interfaces/IERC4626.sol b/contracts/lib/reference/lib/forge-std/src/interfaces/IERC4626.sol index bfe3a11..c1aa39c 100644 --- a/contracts/lib/reference/lib/forge-std/src/interfaces/IERC4626.sol +++ b/contracts/lib/reference/lib/forge-std/src/interfaces/IERC4626.sol @@ -161,7 +161,7 @@ interface IERC4626 is IERC20 { /// - MUST NOT revert. function maxRedeem(address owner) external view returns (uint256 maxShares); - /// @notice Allows an on-chain or off-chain user to simulate the effects of their redeemption at the current block, + /// @notice Allows an on-chain or off-chain user to simulate the effects of their redemption at the current block, /// given current on-chain conditions. /// @dev /// - MUST return as close to and no more than the exact amount of assets that would be withdrawn in a redeem call diff --git a/contracts/lib/reference/lib/openzeppelin-contracts/lib/forge-std/src/Script.sol b/contracts/lib/reference/lib/openzeppelin-contracts/lib/forge-std/src/Script.sol index f4b7efa..e588598 100644 --- a/contracts/lib/reference/lib/openzeppelin-contracts/lib/forge-std/src/Script.sol +++ b/contracts/lib/reference/lib/openzeppelin-contracts/lib/forge-std/src/Script.sol @@ -13,7 +13,7 @@ abstract contract Script { Vm public constant vm = Vm(VM_ADDRESS); /// @dev Compute the address a contract will be deployed at for a given deployer address and nonce - /// @notice adapated from Solmate implementation (https://github.com/transmissions11/solmate/blob/main/src/utils/LibRLP.sol) + /// @notice adapted from Solmate implementation (https://github.com/transmissions11/solmate/blob/main/src/utils/LibRLP.sol) function computeCreateAddress(address deployer, uint256 nonce) internal pure returns (address) { // The integer zero is treated as an empty byte string, and as a result it only has a length prefix, 0x80, computed via 0x80 + 0. // A one byte integer uses its own value as its length prefix, there is no additional "0x80 + length" prefix that comes before it. diff --git a/contracts/lib/reference/lib/openzeppelin-contracts/lib/forge-std/src/Vm.sol b/contracts/lib/reference/lib/openzeppelin-contracts/lib/forge-std/src/Vm.sol index f204cf0..8cab8f6 100644 --- a/contracts/lib/reference/lib/openzeppelin-contracts/lib/forge-std/src/Vm.sol +++ b/contracts/lib/reference/lib/openzeppelin-contracts/lib/forge-std/src/Vm.sol @@ -217,7 +217,7 @@ interface Vm { // ---- // In case the returned value is a JSON object, it's encoded as a ABI-encoded tuple. As JSON objects // don't have the notion of ordered, but tuples do, they JSON object is encoded with it's fields ordered in - // ALPHABETICAL ordser. That means that in order to succesfully decode the tuple, we need to define a tuple that + // ALPHABETICAL ordser. That means that in order to successfully decode the tuple, we need to define a tuple that // encodes the fields in the same order, which is alphabetical. In the case of Solidity structs, they are encoded // as tuples, with the attributes in the order in which they are defined. // For example: json = { 'a': 1, 'b': 0xa4tb......3xs}