round of quiz cleanup and nitpicks

Author: wolovim

pages/lessons/projects/4.mdx

@@ -66,7 +66,7 @@ it's an important tool to ensuring your contract will work as expected.
 
 ### Setting up our project dependencies
 If you have an existing project from your previous work on the TierNFT lesson,
-you have all the Hardhat dependencies installed. {/* @wolovim , would we need to comment out the deployment script if we were to use that 'already set up' project? I mean, would that script give us bother each time we ran the tests in this lesson? */} Otherwise let's create a new Hardhat project and copy in the contract which
+you have all the Hardhat dependencies installed. Otherwise let's create a new Hardhat project and copy in the contract which
 we'll be testing. To create a new project, please refer to _Lesson 3 - Tier NFTs_ and search for
 the “First things first 👷‍♂️" section to get your project going. Follow the steps
 until "Let’s start coding”, then open up your code editor. If you are using VSCode, type `code .` in your terminal to open VSCode. After running through that section you'll have a working Hardhat project for the

utils/questions/lesson-4/1-intro/Q1.json

@@ -2,14 +2,14 @@
   "question": "Choose the reasons for using automated tests:",
   "options": [
     {
-      "answer": "Give us insurance if we upgrade code later ",
+      "answer": "Warns of regressions if we upgrade code later",
       "correct": true
     },
     {
       "answer": "So we don’t have to use manual tests"
     },
     {
-      "answer": "Give us the chance to utilise code modularly",
+      "answer": "Build confidence in each component of our code",
       "correct": true
     },
     {

utils/questions/lesson-4/1-intro/Q2.json

@@ -1,14 +1,14 @@
 {
-  "question": "What is the role of a Testnet in smart contract development?",
+  "question": "What is the role of a testnet in smart contract development?",
   "options": [
     {
       "answer": "It helps to deploy smart contracts to the Ethereum mainnet."
     },
     {
-      "answer": "To airdrop free Ether to devs because testing gets the eco-system a good name."
+      "answer": "To airdrop free Ether to devs, because testing gives the ecosystem a good name."
     },
     {
-      "answer": "It's used to interact with smart contracts using that real Ether."
+      "answer": "It's used to interact with smart contracts using real Ether."
     },
     {
       "answer": "It's a network that is used for testing smart contracts.",

utils/questions/lesson-4/1-intro/Q4.json

@@ -2,17 +2,17 @@
   "question": "When writing unit tests for a smart contract, what should we be testing?",
   "options": [
     {
-      "answer": "Functionality that only involves external contracts."
+      "answer": "Functionality that only involves external contracts"
     },
     {
-      "answer": "Only private functions that aren't externally accessible."
+      "answer": "Only private functions that aren't externally accessible"
     },
     {
-      "answer": "All functions and possible edge cases that the contract may encounter.",
+      "answer": "All functions and possible edge cases that the contract may encounter",
       "correct": true
     },
     {
-      "answer": "Just the constructor function to ensure the contract gets deployed properly."
+      "answer": "Just the constructor function to ensure the contract gets deployed properly"
     }
   ]
 }

utils/questions/lesson-4/1-intro/Q5.json

@@ -2,7 +2,7 @@
   "question": "What do you imagine one of the first steps is in this lesson?",
   "options": [
     {
-      "answer": "To add your private key to the .gitignore file!"
+      "answer": "To add your private key to the .gitignore file"
     },
     {
       "answer": "To harmonise Solidity versions across the project",

utils/questions/lesson-4/2-get-set-up/Q5.json

@@ -5,14 +5,14 @@
       "answer": "Testing the mint() function, because if the network is down, we won't see the tokens on a marketplace"
     },
     {
-      "answer": "Testing constructor() because it inherits from another contract"
+      "answer": "Testing constructor(), because it inherits from another contract"
     },
     {
-      "answer": "Testing tokenURI() because the SVG file is in the contract and not in a separate .json file",
+      "answer": "Testing tokenURI(), because the SVG file is in the contract and not in a separate .json file",
       "correct": true
     },
     {
-      "answer": "Testing withdraw() because it involves more than one party for a transaction"
+      "answer": "Testing withdraw(), because it involves more than one party for a transaction"
     }
   ]
 }

utils/questions/lesson-4/3-general-concepts/Q2.json

@@ -2,10 +2,7 @@
   "question": "Why is it essential to ensure that tests fail before they pass?",
   "options": [
     {
-      "answer": "To verify that the test environment is set up correctly."
-    },
-    {
-      "answer": "To identify potential bugs in the smart contract code.",
+      "answer": "To verify that the test environment is configured correctly.",
       "correct": true
     },
     {
@@ -15,7 +12,7 @@
       "answer": "To confirm that the contract owner can withdraw funds."
     },
     {
-      "answer": "To verify that the test is correctly checking the expected result.",
+      "answer": "To confirm that your contract is actually being interacted with.",
       "correct": true
     }
   ]

utils/quizzes/lesson-4-quiz.json

@@ -5,17 +5,17 @@
       "question": "Choose those which automated testing of smart contracts can help achieve?",
       "options": [
         {
-          "answer": "Faster development and deployment process."
+          "answer": "Faster deployment process"
         },
         {
-          "answer": "Finding every possible bug and vulnerability."
+          "answer": "Finding every possible bug and vulnerability"
         },
         {
-          "answer": "Improving the overall code quality.",
+          "answer": "Improving the overall code quality",
           "correct": true
         },
         {
-          "answer": "Ensuring the smart contract is free of errors.",
+          "answer": "Ensuring the smart contract is free of errors",
           "correct": true
         }
       ]
@@ -24,31 +24,31 @@
       "question": "Which testing approach is recommended for ensuring a secure smart contract?",
       "options": [
         {
-          "answer": "Only manual testing with thorough code review."
+          "answer": "Only manual testing with thorough code review"
         },
         {
-          "answer": "Automated testing using unit tests exclusively."
+          "answer": "Automated testing using unit tests exclusively"
         },
         {
-          "answer": "A combination of manual testing, automated testing, and code auditing.",
+          "answer": "A combination of manual testing, automated testing, and code auditing",
           "correct": true
         },
         {
-          "answer": "Skipping testing to expedite the deployment process."
+          "answer": "Skipping testing to expedite the deployment process"
         }
       ]
     },
     {
       "question": "Which three variables did we define with the 'let' keyword to use in our test suite?",
       "options": [
         {
-          "answer": "tokenTier, tierID, onlyOwner."
+          "answer": "tokenTier, tierID, onlyOwner"
         },
         {
-          "answer": "symbol, collection, provider."
+          "answer": "symbol, collection, provider"
         },
         {
-          "answer": "otherUser, contract, owner.",
+          "answer": "otherUser, contract, owner",
           "correct": true
         }
       ]
@@ -166,7 +166,7 @@
           "answer": "To decrease the number of transactions"
         },
         {
-          "answer": "To ensure the correctness and reliability of the smart contract's behavior.",
+          "answer": "To improve the correctness and reliability of all the smart contract's behavior",
           "correct": true
         },
         {
@@ -196,10 +196,11 @@
       "question": "Why is it essential to ensure that tests fail before they pass?",
       "options": [
         {
-          "answer": "To verify that the test environment is set up correctly."
+          "answer": "To verify that the test environment is configured correctly.",
+          "correct": true
         },
         {
-          "answer": "To identify potential bugs in the smart contract code.",
+          "answer": "To confirm that your contract is actually being interacted with.",
           "correct": true
         },
         {