diff --git a/.obsidian/workspace.json b/.obsidian/workspace.json
index 4fd86fd..d8ce4e5 100644
--- a/.obsidian/workspace.json
+++ b/.obsidian/workspace.json
@@ -35,8 +35,7 @@
               "title": "Initial Questions"
             }
           }
-        ],
-        "currentTab": 1
+        ]
       }
     ],
     "direction": "vertical"
@@ -214,10 +213,10 @@
       "omnisearch:Omnisearch": false
     }
   },
-  "active": "2768622d9c36a711",
+  "active": "fcc28e70ad8acbd2",
   "lastOpenFiles": [
-    "Software Engineering/Meeting.md",
     "Software Engineering/Initial Questions.md",
+    "Software Engineering/Meeting.md",
     "Software Engineering/TA Meeting 1.md",
     "Extracurricular/Misc/Plan.md",
     "Extracurricular/Misc/Proposed Routine Plan.canvas",
diff --git a/Software Engineering/Initial Questions.md b/Software Engineering/Initial Questions.md
index 1adfd41..ba2613c 100644
--- a/Software Engineering/Initial Questions.md	
+++ b/Software Engineering/Initial Questions.md	
@@ -10,7 +10,7 @@
 > It's possible to catch up to speed in a couple of months
 - Can you explain the process by which a smart contract's safety properties will be validated formally?
 - Are there any existing case studies or example proofs we might refer to for a better understanding of the expected output?
-> 
+> > You will be linked to existing projects
 - Define the contract verification criteria
 ### Project scope clarifications
 - Among the seven smart contracts being verified, which ones do you expect us to work on, and why those?