Skip to content

Commit 4a98475

Browse files
Daulox92arr00
andauthored
Update Crowdsales Link (#5746)
Co-authored-by: Arr00 <13561405+arr00@users.noreply.github.com>
1 parent f27019d commit 4a98475

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ To keep your system secure, you should **always** use the installed code as-is,
6868
The guides in the [documentation site](https://docs.openzeppelin.com/contracts) will teach about different concepts, and how to use the related contracts that OpenZeppelin Contracts provides:
6969

7070
* [Access Control](https://docs.openzeppelin.com/contracts/access-control): decide who can perform each of the actions on your system.
71-
* [Tokens](https://docs.openzeppelin.com/contracts/tokens): create tradeable assets or collectives, and distribute them via [Crowdsales](https://docs.openzeppelin.com/contracts/crowdsales).
71+
* [Tokens](https://docs.openzeppelin.com/contracts/tokens): create tradeable assets or collectives.
7272
* [Utilities](https://docs.openzeppelin.com/contracts/utilities): generic useful tools including non-overflowing math, signature verification, and trustless paying systems.
7373

7474
The [full API](https://docs.openzeppelin.com/contracts/api/token/ERC20) is also thoroughly documented, and serves as a great reference when developing your smart contract application. You can also ask for help or follow Contracts' development in the [community forum](https://forum.openzeppelin.com).

0 commit comments

Comments
 (0)