@@ -256,7 +256,7 @@ delegates to transfer them, etc).
256
256
</SideDrawer >
257
257
258
258
All of it is pretty much for our project, but luckily OpenZeppelin has developed
259
- a lot of contracts that implements these standards and more, they are widely
259
+ a lot of contracts that implement these standards and more, they are widely
260
260
used and audited and, the thing we love about them, they are open-source and we
261
261
can use them to leverage our learning process. With that in our heads, we are
262
262
going to use them inside our contract.
@@ -401,7 +401,7 @@ So, to let our inherited contract know where our NFTs will be stored, we have to
401
401
you look into OpenZeppelin's documentation. There’s a good reason for
402
402
everything. Well, lots of things. And this is one of them!
403
403
404
- Here's the modifications we will add and i 'll explain them below:
404
+ Here's the modifications we will add and I 'll explain them below:
405
405
406
406
``` solidity
407
407
// SPDX-License-Identifier: MIT
@@ -506,7 +506,7 @@ collection to have as NFTs. Each of them will have as a minimum a “name”,
506
506
507
507
As you see in the example, under “image” we have a link to a file on the web,
508
508
which we will refer to as Web2. So, if this website were to go down, our NFTs
509
- would loose their images, showing us the limitations of the centralization of
509
+ would lose their images, showing us the limitations of the centralization of
510
510
web2 data storage.
511
511
512
512
![ nft.pepe.jpeg] ( /assets/lessons/2/img_11.jpeg )
@@ -518,7 +518,7 @@ going to have to go to the moon…
518
518
519
519
Literally.
520
520
521
- There are many services that lets us store files in a decentralized manner. We
521
+ There are many services that let us store files in a decentralized manner. We
522
522
are using the one called IPFS. Inter-Planetary File System. Yep, no joke.
523
523
524
524
![ ipfs.jpeg] ( /assets/lessons/2/img_12.jpeg )
@@ -540,7 +540,7 @@ To ease our path into the IPFS network, services for *pinning* content (e.g.
540
540
Pinata) offer paid and free tiers that ensure that the files we upload are
541
541
* pinned* in IPFS.
542
542
543
- So, go ahead and grab yourself a free pinata account in this
543
+ So, go ahead and grab yourself a free pinata account at this
544
544
[ link] ( https://www.pinata.cloud/ ) .
545
545
546
546
One of the peculiarities of IPFS is that files, or better called ‘content’, are
@@ -828,7 +828,7 @@ password (the one you use to open it, NOT your seed phrase). It also shows you a
828
828
notice so you know that you are entering the danger zone. Confirm and you'll be
829
829
able to copy your private key. Paste it in to our ` hardhat.config.js `
830
830
831
- Please, if your are already a developer and you plan to use git to store your
831
+ Please, if you are already a developer and you plan to use git to store your
832
832
project, don't store your ` hardhat.config.js ` on it, because you will have your
833
833
private key there.
834
834
@@ -852,7 +852,7 @@ This is the output i got in my console:
852
852
![ deploy.rinkeby.png] ( /assets/lessons/2/img_19.png )
853
853
854
854
Remember we are deploying to the actual blockchain, a testnet, but a blockchain
855
- none the less .
855
+ nonetheless .
856
856
857
857
Now that we have run the deploy script, delete the private key and the RPC API
858
858
key from ` hardhat.config.js ` to minimize the handling of the wallet. In the next
@@ -869,4 +869,4 @@ and [Opensea](https://testnets.opensea.io/collection/d-d-academy)
869
869
![ opensea.png] ( /assets/lessons/2/img_20.png )
870
870
871
871
And that's it! You have created your own NFT collection from scratch! What a
872
- super star !!
872
+ superstar !!
0 commit comments