merge changes

Author: 0xChin

pages/lessons/projects/1.mdx

@@ -297,7 +297,7 @@ contract WAGMI {
     <Callout emoji='💡' size='md' variant='info'>
     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.
     </Callout>
- 
+
     #### Which visibility should I use ?
 
     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?
 ![Wizard Wooshing on Successful Lesson](/assets/lessons/1/img_10.png)
 
 Before you go ahead and tell us: **what your future in web3 is,** have a check
-on what you didn’t know a little while ago, and what you know now! *
+on what you didn’t know a little while ago, and what you know now! \*
 
 Apart from a user wallet, what else uses a blockchain (Ethereum) address?
 
@@ -726,4 +726,4 @@ Can a view function modify the state of the blockchain?
 What can we use a smart contract for?
 
 **Now, go to the community in Discord to share your new Open Sourcerer
-powers**......and find the answers too!!!
+powers**......and find the answers too!!!