small grammar and punctuation fixes

Author: wolovim

pages/lessons/projects/3.mdx

@@ -24,12 +24,11 @@ title="Lesson 3: Tier NFTs"
 discussionUrl="https://developerdao.peeranha.io/discussions"
 />
 ## About this lesson
-PART 1
 
-Welcome to this tutorial, where you will learn how to create tiered NFTs using Solidity smart contracts and expand the capabilities of your NFT projects. This tutorial builds upon the knowledge gained from our previous *Getting Started with Smart Contract Development* and *Build a Basic NFT* lessons. If you haven't already, we recommend you complete them to familiarise yourself with the fundamentals of Solidity and the concepts we will be building upon in this lesson. 
+Welcome to this tutorial, where you will learn how to create tiered NFTs using Solidity smart contracts and expand the capabilities of your NFT projects. This tutorial builds upon the knowledge gained from our previous **Getting Started with Smart Contract Development** and **Build a Basic NFT** lessons. If you haven't already, we recommend you complete them to familiarise yourself with the fundamentals of Solidity and the concepts we will be building upon in this lesson.
 
 
-Throughout this tutorial, we will provide you with checkpoint questions to test your previous knowledge, predict upcoming steps in the lesson, and allow you to gauge how well you are soaking up the new content. Be sure to check out all the side-drawers for a deeper dive into the concepts, as there will be a quiz at the end of the lesson. We estimage between one and six hours to complete the lesson, depending on your previous experience and your need to learn new ideas. Remember to take regular breaks and enjoy the process of development. We even have a pomodoro timer ⌛ in the menu header to help you pace yourself and remind you to 'touch some grass' and appreciate nature's contribution to our well-being. 🌱
+Throughout this tutorial, we will provide you with checkpoint questions to test your previous knowledge, predict upcoming steps in the lesson, and allow you to gauge how well you are soaking up the new content. Be sure to check out all the side-drawers for a deeper dive into the concepts, as there will be a quiz at the end of the lesson. We estimate between one and six hours to complete the lesson, depending on your previous experience and your need to learn new ideas. Remember to take regular breaks and enjoy the process of development. We even have a pomodoro timer ⌛ in the menu header to help you pace yourself and remind you to "touch grass" and appreciate nature's contribution to our well-being. 🌱
 
 ## What are we building?
 {/* INTRO AND CONTENTS */}
@@ -58,7 +57,7 @@ Now that we have set the stage, it's time to dive into the exciting world of tie
 - Writing and deploying a Solidity smart contract
 - Creating tiered NFTs with varying levels of rarity and attributes
 - Write scripts for deployment
-- Exploring additional functionalities and possibilities with tiered NFTs ..... in the smart contract!
+- Exploring additional functionalities and possibilities with tiered NFTs ... in the smart contract!
 - Showcasing and trading your tiered NFTs on a public marketplace
 
 ### Developer tooling
@@ -305,7 +304,7 @@ Now we need to modify the mint function with logic that can access the three NFT
 
 The mint function selects tiers based on the amount of native token it receives stored in `msg.value`. 
 
-The `require` statement is a simple and powerful built-in function of Solidity you'll be using a lot in the future. It checks if the 1st parameter is true or false. On true, it does nothing, allowing execution to continue normally, but on false it throws an exception that reverts everything we modified in the transaction. In our case, if we send the function zero token value, it will **revert** with a "Not enough value for the minimum Tier" message, and stop executing. Otherwise we can select the tier we want..... as long as we can afford it! 
+The `require` statement is a simple and powerful built-in function of Solidity you'll be using a lot in the future. It checks if the 1st parameter is true or false. On true, it does nothing, allowing execution to continue normally, but on false it throws an exception that reverts everything we modified in the transaction. In our case, if we send the function zero token value, it will **revert** with a "Not enough value for the minimum Tier" message, and stop executing. Otherwise we can select the tier we want... as long as we can afford it!
 
 We already have two `uint256` variables declared. You might wonder which is the *key* and which the *value* inside the `tokenTier` mapping? See if you can track through the code and find out.
 
@@ -661,7 +660,7 @@ contract TierNFT is ERC721 {
 
 ### Where are all our funds?  Let's add a withdraw Function!
 
-We need to find a way to actually withdraw any funds our contract generates, otherwise they'll get stuck **in the contract** .... that **we** created! Let's import `Ownable.sol`, to get those permissions, so that only **we** can withdraw those funds, and not anyone else. Clever, eh?
+We need to find a way to actually withdraw any funds our contract generates, otherwise they'll get stuck **in the contract** ... that **we** created! Let's import `Ownable.sol`, to get those permissions, so that only **we** can withdraw those funds, and not anyone else. Clever, eh?
 
 ```solidity
 // Place this next to the other imports at the top:
@@ -930,7 +929,7 @@ For your wallet's private key, the most sensitive data of the project, you need
 notice so you know that you are entering the *danger zone*. Confirm and you'll be able to copy your private key. Add your private key into the `.env` file like so:
 
 ```bash
-PRIVATE_KEY=f8abc629b....
+PRIVATE_KEY=f8abc629b...
 ```
 
 <Callout emoji='💡' size='md' variant='info'>
@@ -952,7 +951,7 @@ configuration files, which may need uploaded to a project's repo.
 
 Remember to always **protect your private keys, and your recovery seed phrases** to keep your wallet safe and **unwanted guests out**.
 
-### It’s Time . . . .
+### It’s Time . . .
 
 We will deploy our smart contract by using this command: