Applying renamings to documentation comments

[Skyge]

Glad to see have a new release version, and I am trying to use the latest version right now, but I am confused about this comments: To use this library you can add a using SafeERC20 for IERC20; statement to your contract,
Should it be using SafeERC20Upgradeable for IERC20Upgradeable;

[frangio]

Hi @Skyge. Yes, indeed. While the code is converted automatically, the documentation comments are kept the same. It would be difficult for us to do that automatically, but we may be able to work something out for the docs site.

[frangio]

As explained in Using with Upgrades:

The package replicates the structure of the main OpenZeppelin Contracts package, but every file and contract has the suffix Upgradeable.

[stefek99]

Thank you very much for renaming the package!

• OpenZeppelin/openzeppelin-contracts
• OpenZeppelin/openzeppelin-contracts-upgradeable - logical, upgradeable

"ethereum package" was totally unintuitive

import "@openzeppelin/contracts-ethereum-package/contracts/presets/ERC20PresetMinterPauser.sol";

[frangio]

Closing in favor of #105.