Skip to content

Commit 687f654

Browse files
authored
Fix: typos
Fix: typos
1 parent 130447f commit 687f654

File tree

1 file changed

+8
-8
lines changed
  • pages/lessons/projects

1 file changed

+8
-8
lines changed

pages/lessons/projects/2.mdx

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -256,7 +256,7 @@ delegates to transfer them, etc).
256256
</SideDrawer>
257257

258258
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
260260
used and audited and, the thing we love about them, they are open-source and we
261261
can use them to leverage our learning process. With that in our heads, we are
262262
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
401401
you look into OpenZeppelin's documentation. There’s a good reason for
402402
everything. Well, lots of things. And this is one of them!
403403

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:
405405

406406
```solidity
407407
// SPDX-License-Identifier: MIT
@@ -506,7 +506,7 @@ collection to have as NFTs. Each of them will have as a minimum a “name”,
506506

507507
As you see in the example, under “image” we have a link to a file on the web,
508508
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
510510
web2 data storage.
511511

512512
![nft.pepe.jpeg](/assets/lessons/2/img_11.jpeg)
@@ -518,7 +518,7 @@ going to have to go to the moon…
518518

519519
Literally.
520520

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
522522
are using the one called IPFS. Inter-Planetary File System. Yep, no joke.
523523

524524
![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.
540540
Pinata) offer paid and free tiers that ensure that the files we upload are
541541
*pinned* in IPFS.
542542

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
544544
[link](https://www.pinata.cloud/).
545545

546546
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
828828
notice so you know that you are entering the danger zone. Confirm and you'll be
829829
able to copy your private key. Paste it in to our `hardhat.config.js`
830830

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
832832
project, don't store your `hardhat.config.js` on it, because you will have your
833833
private key there.
834834

@@ -852,7 +852,7 @@ This is the output i got in my console:
852852
![deploy.rinkeby.png](/assets/lessons/2/img_19.png)
853853

854854
Remember we are deploying to the actual blockchain, a testnet, but a blockchain
855-
none the less.
855+
nonetheless.
856856

857857
Now that we have run the deploy script, delete the private key and the RPC API
858858
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)
869869
![opensea.png](/assets/lessons/2/img_20.png)
870870

871871
And that's it! You have created your own NFT collection from scratch! What a
872-
super star!!
872+
superstar!!

0 commit comments

Comments
 (0)