Skip to content

Commit 37e8fd5

Browse files
committed
style: remove formatter upates
1 parent de624c4 commit 37e8fd5

File tree

1 file changed

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

1 file changed

+3
-3
lines changed

pages/lessons/projects/1.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -297,7 +297,7 @@ contract WAGMI {
297297
<Callout emoji='💡' size='md' variant='info'>
298298
While private and internal are not readable or modifiable from other contracts, its values are set on a public blockchain, making its values visible from the outside world.
299299
</Callout>
300-
300+
301301
#### Which visibility should I use ?
302302

303303
A simple answer to this is , start with giving every variable a `private` visibility then as you move further in contract developement modify variables to `internal` visibility as a next step of modification. Try to use `public` visibility as little as possible in order to be gas efficient and making less vulnerabilities in the smart contract.
@@ -705,7 +705,7 @@ you see the magical spell that is being cast here?
705705
![Wizard Wooshing on Successful Lesson](/assets/lessons/1/img_10.png)
706706

707707
Before you go ahead and tell us: **what your future in web3 is,** have a check
708-
on what you didn’t know a little while ago, and what you know now! \*
708+
on what you didn’t know a little while ago, and what you know now! *
709709

710710
Apart from a user wallet, what else uses a blockchain (Ethereum) address?
711711

@@ -726,4 +726,4 @@ Can a view function modify the state of the blockchain?
726726
What can we use a smart contract for?
727727

728728
**Now, go to the community in Discord to share your new Open Sourcerer
729-
powers**......and find the answers too!!!
729+
powers**......and find the answers too!!!

0 commit comments

Comments
 (0)