feat: leave some commented questions in .mdx for @7i7o

Author: elPiablo

src/pages/lessons/projects/6.mdx

@@ -31,7 +31,7 @@ but let's get our focus on this one first.
 
 We'll have checkpoint questions at stages for testing your
 previous knowledge, predicting next steps in the lesson, and helping you see how you're 
-absorbing the new content. Expect a final quiz,
+absorbing the new content. You can also (soon) expect a final quiz,
 so make sure you're checking out all the side-drawers for a deeper dive of the
 new concepts. To complete the lesson, expect somewhere between one and four
 hours, depending on your previous experience and the need to learn new ideas.
@@ -96,7 +96,7 @@ Some basic functionality that our tokens need to provide are:
 - Approve an amount of tokens from an account to be spent by a third-party
   account
 
-{/**@7i7o it might be cool to have these sentences to open a paragraph before the side-drawer, instead of on line 132
+{/**@7i7o is it cool to have these two sentences here to create paragraph before the side-drawer, instead of where they were originally on line 132 (see below)
  Although I don't know if you want to 'associate' OZ with the actual functions and events you lay out in the side-drawer. */}
 Has someone created a battle-tested library for the standard? Yes. OpenZeppelin, among others, has created an implementation we can inherit to create our own tokens easily. Here is a quick overview of what {/*maybe another word choice for 'what' e.g. 'functionality' or 'the components'*/} a contract needs in order to be called an ERC20 Token
 contract:
@@ -133,8 +133,8 @@ You can check the details in the full EIP-20 titled
 
 ## Let's code, but first...
 
-Before we start hacking away without any structure to follow, what is our
-project's structure and what do we want to achieve? Since we are _BUIDLING_, I'd like to think of our project, or smart contract,
+Before we start hacking away without any structure to follow, what is our actual
+project's structure, and what do we want to achieve? Since we are _BUIDLING_, I'd like to think of our project, or smart contract,
 the same way as we would _roughly_ build a house:
 
     * 1 - Foundations