Finish fourth mini-quiz, + add some humour

Author: elPiablo

pages/lessons/projects/4.mdx

@@ -437,6 +437,7 @@ into a new `describe` section.
 
 Where exactly do we add this `describe` block?
 
+{/* I think we could do this more cleanly with the following // commented line and its explanation */}
 Currently the end of our `tier-nft.test.js` looks like this, with just one
 additional comment line I added that says
 `// this is where existing describe section ends`:
@@ -460,6 +461,7 @@ additional comment line I added that says
 Our new `describe` section shown below will replace that line that says
 `// this is where existing describe section ends`.
 
+{/* The sentence in the callout below is a bit messy. Could do with an update */}
 <Callout emoji="💡" size="md" variant="info">
   Make sure you keep that last line `})` which is the very end of the block of
   code that holds **all** of the `describe` blocks you're adding in this whole
@@ -605,7 +607,7 @@ of additional highlights:
   breaks our rule of one expect per test, but as long as the test is kept
   simple, we can choose what makes sense for what we're trying to test.
 
-<SideDrawer buttonText="Checkpoint Questions" title="Mint and Withdraw">
+<SideDrawer buttonText="Checkpoint Questions" title="Cross-checking Logic from Tests to Contract">
       <Question question="lesson-4/4-mint-withdraw/Q1" />
       <Question question="lesson-4/4-mint-withdraw/Q2" />
       <Question question="lesson-4/4-mint-withdraw/Q3" />

utils/questions/lesson-4/4-mint-withdraw/Q1.json

@@ -2,11 +2,13 @@
   "question": "Syntax errors: is your final '})' syntax matching the opening 'describe('TierNFT', function () {' every time you add new tests?",
   "options": [
     {
-      "answer": "Yes",
-      "correct": true
+      "answer": "Yes"
     },
     {
-      "answer": "No? It's easy to run into errors with the smallest things. We all do it. Take your time to read the error messages."
+      "answer": "No? It's easy to run into syntax errors with the smallest things. We all do it. Take your time to read the error messages."
+    },
+    {
+      "answer": "There is no right or wrong option with this question.....it's just a gentle reminder :-)"
     }
   ]
 }

utils/questions/lesson-4/4-mint-withdraw/Q4.json

@@ -2,14 +2,14 @@
   "question": "In the 'withdraw()' tests, why is the line 'await contract.connect(otherUser).withdraw()' used?",
   "options": [
     {
-      "answer": "To ensure the contract owner can withdraw the entire contract balance."
+      "answer": "To ensure the 'otherUser' can withdraw the entire contract balance."
     },
     {
-      "answer": "To verify that the 'withdraw()' function updates the contract balance correctly.",
-      "correct": true
+      "answer": "To verify that the 'withdraw()' function updates other balances for the user correctly."
     },
     {
-      "answer": "To check if the contract is functioning correctly for non-owner users."
+      "answer": "To check if the contract is working correctly for verified callers of the function.",
+      "correct": true
     },
     {
       "answer": "To confirm the contract has sufficient funds before withdrawing."

utils/questions/lesson-4/4-mint-withdraw/Q5.json

@@ -1,22 +1,18 @@
 {
-  "question": "",
+  "question": "The '.provider.getBalance(contract.getAddress())).to.equal()' lines in the tests:",
   "options": [
     {
-      "answer": "",
-      "correct": true
+      "answer": "verify the contract owner can provide an airdrop to an equal number of addresses."
     },
     {
-      "answer": ""
+      "answer": "check the contract balance to be greater than zero."
     },
     {
-      "answer": "",
+      "answer": "ensure the contract balance is updated correctly after a function call.",
       "correct": true
     },
     {
-      "answer": ""
-    },
-    {
-      "answer": ""
+      "answer": "confirm that the contract has sufficient funds before proceeding with the test."
     }
   ]
 }