From 51191d315209093ccac061e08becd01c23f02fc9 Mon Sep 17 00:00:00 2001 From: Francisco Giordano Date: Mon, 2 Oct 2023 17:43:51 -0300 Subject: [PATCH] Fix typos (cherry picked from commit b4a9c47e9bebc9bb9aef0a07338abcd5d3ea2744) --- SECURITY.md | 2 +- contracts/mocks/token/ERC20ForceApproveMock.sol | 2 +- docs/modules/ROOT/pages/erc4626.adoc | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index 4d6ff96ed..e9a5148ec 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -39,4 +39,4 @@ Note as well that the Solidity language itself only guarantees security updates ## Legal -Smart contracts are a nascent techology and carry a high level of technical risk and uncertainty. OpenZeppelin Contracts is made available under the MIT License, which disclaims all warranties in relation to the project and which limits the liability of those that contribute and maintain the project, including OpenZeppelin. Your use of the project is also governed by the terms found at www.openzeppelin.com/tos (the "Terms"). As set out in the Terms, you are solely responsible for any use of OpenZeppelin Contracts and you assume all risks associated with any such use. This Security Policy in no way evidences or represents an on-going duty by any contributor, including OpenZeppelin, to correct any flaws or alert you to all or any of the potential risks of utilizing the project. +Smart contracts are a nascent technology and carry a high level of technical risk and uncertainty. OpenZeppelin Contracts is made available under the MIT License, which disclaims all warranties in relation to the project and which limits the liability of those that contribute and maintain the project, including OpenZeppelin. Your use of the project is also governed by the terms found at www.openzeppelin.com/tos (the "Terms"). As set out in the Terms, you are solely responsible for any use of OpenZeppelin Contracts and you assume all risks associated with any such use. This Security Policy in no way evidences or represents an on-going duty by any contributor, including OpenZeppelin, to correct any flaws or alert you to all or any of the potential risks of utilizing the project. diff --git a/contracts/mocks/token/ERC20ForceApproveMock.sol b/contracts/mocks/token/ERC20ForceApproveMock.sol index 9fbca9727..36c0f574d 100644 --- a/contracts/mocks/token/ERC20ForceApproveMock.sol +++ b/contracts/mocks/token/ERC20ForceApproveMock.sol @@ -4,7 +4,7 @@ pragma solidity ^0.8.20; import {ERC20} from "../../token/ERC20/ERC20.sol"; -// contract that replicate USDT (0xdac17f958d2ee523a2206206994597c13d831ec7) approval beavior +// contract that replicate USDT (0xdac17f958d2ee523a2206206994597c13d831ec7) approval behavior abstract contract ERC20ForceApproveMock is ERC20 { function approve(address spender, uint256 amount) public virtual override returns (bool) { require(amount == 0 || allowance(msg.sender, spender) == 0, "USDT approval failure"); diff --git a/docs/modules/ROOT/pages/erc4626.adoc b/docs/modules/ROOT/pages/erc4626.adoc index 43ec3ebb9..c42426add 100644 --- a/docs/modules/ROOT/pages/erc4626.adoc +++ b/docs/modules/ROOT/pages/erc4626.adoc @@ -23,7 +23,7 @@ When plotted in log-log scale, the rate is defined similarly, but appears differ image::erc4626-rate-loglog.png[Exchange rates in logarithmic scale] -In such a reprentation, widely different rates can be clearly visible in the same graph. This wouldn't be the case in linear scale. +In such a representation, widely different rates can be clearly visible in the same graph. This wouldn't be the case in linear scale. image::erc4626-rate-loglogext.png[More exchange rates in logarithmic scale]