Add 2 side questions, add intended final image, delete unnecessary inline quizzes

Author: elPiablo

pages/lessons/projects/1.mdx

@@ -18,6 +18,20 @@ smart contract on either Jupiter, or Earth, and although you may be grounded to
 the latter, you are going to deploy yours on a **blockchain**. Not a real
 blockchain, well not at first. Hang on!
 
+
+
+<SideDrawer buttonText="wee Q" title="7i7o Rocks">
+    <Question question="question-1" />
+</SideDrawer>
+<br/>
+
+<SideDrawer buttonText="ano'wee Q for the road" title="John n Maeve rock too">
+    <Question question="question-2" />
+</SideDrawer>
+<br/>
+<br/>
+And now let's check if we were right :)
+
 <SideDrawer buttonText="A what chain?!!">
 A blockchain has quite a few layers to let function, but it basically gives us a place to do computation, and store information. So in one sense it functions as a database. Think about this. To get access to all of the information on a traditional database you need permission from a higher authority, right? Access to information on a public blockchain is permission**less**. Not only can we read the information on it, but anyone can also write information to it. And that’s where we come in and get this all started with our *smart contract*. And what is also different to a traditional database is that once the information goes onto this blockchain, it stays there forever, and ever, and ever….thanks to cryptography!!
 
@@ -124,6 +138,18 @@ benefits to this decentralised model as we’ll continue to see.
 
 </SideDrawer>
 
+## What are we going to do?
+By the end of this lesson we’ll have learned a lot. A simple breakdown of the steps to get there is:
+- Set up our work environment
+- Create a Smart Contract
+- Learn basic Solidity concepts
+- Define variables
+- Create a function
+- Learn about events on the blockchain
+- Deploy our Smart Contract in Remix
+- At the end of the project, we’re really going to test your knowledge with a quiz, so take in whatever you can. 
+- We might even have some questions along the way for fun to expand your already amazing mind!!
+
 ## Let’s get this party started!
 
 We’re going to write a smart contract, which is going to be a “Web3
@@ -554,32 +580,6 @@ in future lessons, so no worries!
 
 </SideDrawer>
 
-We should ask the learner to sum up what they have learned. Some checkpoint
-questions:
-
-Addresses: Apart from a user wallet, what else uses a blockchain (Ethereum)
-address?
-
-Events: How many parameters can we have in an event?
-
-Searching the chain: What can we use to find a past event?
-
-Transactions: Ethereum uses something for transaction fees. What’s it called?
-
-Logs: Where do the values for event parameters get stored?
-
-Versions: What is the use of the **pragma solidity** statement in our smart
-contract?
-
-State variables: Do state variables stay permanently on the blockchain?
-
-Visibility: Can a view function modify the state of the blockchain?
-
-Use cases of smart contract: What can we use a smart contract for?
-
-see the Comment in the very last line of this lesson under ‘Now, please go ahead
-and hop in the forum/discord to tell us: what is your future in web3?’
-
 ## Compile & Deploy
 
 Now that we have written our smart contract in full, we can compile it and
@@ -704,30 +704,13 @@ If you look closely, inside the “logs” part, our smart contract predicted a
 What if you try out setting the message to `gm` and look at the logs again. Can
 you see the magical spell that is being cast here?
 
-![Wizard Wooshing on Successful Lesson](/assets/lessons/1/img_10.png)
+{/* ![Wizard Wooshing on Successful Lesson](/assets/lessons/1/img_10.png) */}
+![Genie Girl holds Ethereum Crystal Ball](/assets/lessons/1/img_11.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!
 
-Apart from a user wallet, what else uses a blockchain (Ethereum) address?
-
-How many parameters can we have in an event?
-
-What can we use to find a past event?
-
-Ethereum uses something for transaction fees. What’s it called?
-
-Where do the values for event parameters get stored?
-
-What is the use of the **pragma solidity** statement in our smart contract?
-
-Do state variables stay permanently on the blockchain?
-
-Can a view function modify the state of the blockchain?
-
-What can we use a smart contract for?
-
-<Quiz quiz="quiz-lesson-1a"/>
+<Quiz quiz="quiz-1"/>
 
-**Now, go to the community in Discord to share your new Open Sourcerer
-powers**......and find the answers too!!!
+Now, go to the community in **developerdao.peeranha.io** to share your new Open Sourcerer
+powers!

public/assets/lessons/1/img_11.png

@@ -1,15 +1,11 @@
 {
-  "question": "Which of these properties does Ethereum have?",
+  "question": "True or False: In order to access and information to a public blockchain you need to have permission from the owner",
   "options": [
     {
-      "answer": "Permissioned"
+      "answer": "True"
     },
     {
-      "answer": "Trustless",
-      "correct": true
-    },
-    {
-      "answer": "Decentralized",
+      "answer": "False",
       "correct": true
     }
   ]

utils/questions/question-1.json

@@ -0,0 +1,12 @@
+{
+  "question": "Which statement is true?",
+  "options": [
+    {
+      "answer": "It’s important to test your code rigorously because once deployed it resides on the Blockchain forever",
+      "correct": true
+    },
+    {
+      "answer": "The great thing about the blockchain is if you need to make corrections to buggy code you can just upload fixes which will automatically overwrite previous versions seamlessly"
+    }
+  ]
+}

utils/questions/question-2.json

@@ -0,0 +1,16 @@
+{
+  "question": "Which of these properties does Ethereum have?",
+  "options": [
+    {
+      "answer": "Permissioned"
+    },
+    {
+      "answer": "Trustless",
+      "correct": true
+    },
+    {
+      "answer": "Decentralized",
+      "correct": true
+    }
+  ]
+}