Skip to content

Commit a9a60dc

Browse files
authored
Merge pull request #156 from losMacos/lesson-2-fixes
Fixes some links in lesson 2
2 parents 2c42fb6 + 415e196 commit a9a60dc

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

lessons/projects/2.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ comfortable with another package manager, feel free to use it.
7575

7676
<ContentCallout emoji='💡' size='md' variant='info'>
7777
To install `npm` on your system, please follow the instructions on
78-
[this link](/lessons/install-npm).
78+
[this link](/lessons/fundamentals/install-npm).
7979
</ContentCallout>
8080

8181
Let’s create and `cd` into our D_D Academy projects folder, and create a
@@ -202,7 +202,7 @@ npm install @openzeppelin/contracts
202202
<ContentCallout emoji='💡' size='md' variant='info'>
203203
Open Zeppelin developed a lot of standard contracts that are super powerful,
204204
widely used and fully tested and audited. Read more about them
205-
[here](/lessons/open_zeppelin).
205+
[here](/lessons/fundamentals/open_zeppelin).
206206
</ContentCallout>
207207

208208
## Let’s start coding!
@@ -235,13 +235,13 @@ contract ProjectNFT {
235235
```
236236

237237
If you’ve been through our
238-
[first project](/lessons/1), you’ll remember the first lines defines our
238+
[first project](/lessons/projects/1), you’ll remember the first lines defines our
239239
copyright license, the second one defines the solidity version we are going to
240240
be using for this contract and the last two lines are how we declare a smart
241241
contract in solidity.
242242

243243
With an empty project, now we can start adding what we need to create our
244-
awesome NFT collection. In particular, [ERC721](/lessons/token-standards) (the
244+
awesome NFT collection. In particular, [ERC721](/lessons/fundamentals/token-standards) (the
245245
formal specification to follow for NFTs) have a lot of requirements to meet
246246
(they should have a numbered ID, functions to transfer them, approve others as
247247
delegates to transfer them, etc).
@@ -382,7 +382,7 @@ OpenZeppelin ERC721 contract provides us a way to create unique URIs from the
382382
IDs of the NFTs. It gives a way to define a base path for a web address and just
383383
attaches the token ID at the end of it. So, if you wanted, you could upload your
384384
NFT info (we'll look at how we store that later) to any web address, say
385-
[www.my-site.com/my-nft-collection](http://www.my-site.com/my-nft-collection/)
385+
`www.my-site.com/my-nft-collection`
386386
and number each info file with the corresponding ID (1, 2, 3, 4…).
387387

388388
We are not going to limit the size of our collection for this project.
@@ -850,7 +850,7 @@ Just go to [Goerli Etherscan](https://goerli.etherscan.io/) (or
850850
[Opensea](https://testnets.opensea.io/)) and search for the address of our
851851
deployed contract.
852852

853-
You can view my links as an example on ~~[Etherscan](https://goerli.etherscan.io/address/0x76A9332DbBB0c497Eca36C2E4370227fff3C058f)~~
853+
You can view my links as an example on [Etherscan](https://goerli.etherscan.io/address/0x76A9332DbBB0c497Eca36C2E4370227fff3C058f)
854854
and [Opensea](https://testnets.opensea.io/collection/soc)
855855

856856
![opensea.png](/assets/lessons/2/img_20.png)

0 commit comments

Comments
 (0)