From b734bf3fa558b5afaa443c56c4deddcd857f5aef Mon Sep 17 00:00:00 2001 From: Francisco Giordano Date: Wed, 15 Apr 2020 13:33:24 -0300 Subject: [PATCH] Tweak wording in ERC20Snapshot docs --- contracts/token/ERC20/ERC20Snapshot.sol | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/contracts/token/ERC20/ERC20Snapshot.sol b/contracts/token/ERC20/ERC20Snapshot.sol index cd256002a..55d12b2a4 100644 --- a/contracts/token/ERC20/ERC20Snapshot.sol +++ b/contracts/token/ERC20/ERC20Snapshot.sol @@ -60,13 +60,13 @@ abstract contract ERC20Snapshot is ERC20 { * * Emits a {Snapshot} event that contains the same id. * - * {_snapshot} is `internal`: you must decide how to expose it externally. This can be done both by - * guarding it with a system such as {AccessControl}, or by leaving it open to the public. + * {_snapshot} is `internal` and you have to decide how to expose it externally. It's usage may be restricted to a + * set of accounts, for example using {AccessControl}, or it may be open to the public. * * [WARNING] * ==== * While an open way of calling {_snapshot} is required for certain trust minimization mechanisms such as forking, - * you must consider that it can potentially be used by attackers in two ways. + * you must consider that it can potentially be used by attackers in two ways. * * First, it can be used to increase the cost of retrieval of values from snapshots, although it will grow * logarithmically thus rendering this attack ineffective in the long term. Second, it can be used to target