From 424ab2a0242487ecbb109d97dc62a90efffaeb78 Mon Sep 17 00:00:00 2001
From: Ross Campbell <41117279+Ro5s@users.noreply.github.com>
Date: Tue, 26 May 2020 12:39:54 -0400
Subject: [PATCH] Update SafeERC20.sol (#2246)

tweak intro dev comment to reflect more typical use case, wrapping an `IERC20` reference for a deposit contract using others' ERC-20 tokens. I might be mistaken ~ but typically SafeERC20 won't be used in conjunction with ERC20 for OZ token deployments?
---
 contracts/token/ERC20/SafeERC20.sol | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contracts/token/ERC20/SafeERC20.sol b/contracts/token/ERC20/SafeERC20.sol
index bf6238f06..a815e3a3c 100644
--- a/contracts/token/ERC20/SafeERC20.sol
+++ b/contracts/token/ERC20/SafeERC20.sol
@@ -12,7 +12,7 @@ import "../../utils/Address.sol";
  * contract returns false). Tokens that return no value (and instead revert or
  * throw on failure) are also supported, non-reverting calls are assumed to be
  * successful.
- * To use this library you can add a `using SafeERC20 for ERC20;` statement to your contract,
+ * To use this library you can add a `using SafeERC20 for IERC20;` statement to your contract,
  * which allows you to call the safe operations as `token.safeTransfer(...)`, etc.
  */
 library SafeERC20 {