diff --git a/.gitignore b/.gitignore
index 5dc31d0..e4ff0d0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,4 +3,5 @@ _build
 .Rproj.user
 .Rproj
 .env
-*.mo
\ No newline at end of file
+*.mo
+venv
diff --git a/instructors/instructor-notes.md b/instructors/instructor-notes.md
index bd7db82..33a5af9 100644
--- a/instructors/instructor-notes.md
+++ b/instructors/instructor-notes.md
@@ -177,28 +177,35 @@ Remove administrator privileges on the hub by opening a [2i2c support ticket](ht
 
 ## Tasklist
 
-**One week before the workshop**
-    
+### One week before the workshop
+
 - [ ] Copy the CodiMD template, remove the episode section content and set editing rights to *Freely*
 - [ ] Copy feedback form templates and check access permissions
 - [ ] Set up a Slack channel, or equivalent
 - [ ] Schedule the videoconferencing calls for Part One and Part Two
 - [ ] Email learners one week before the workshop
-- [ ] Share a calendar invitation for Part One and Part Two with links to the videoconference call, CodiMD document and Slack channel
+  - [ ] Share a calendar invitation for Part One and Part Two with links to the videoconference call, CodiMD document and Slack channel
 - [ ] Prepare the Community Showcase Hub
   - [ ] Add learners to GitHub team **and** grant them Owner status
   - [ ] Grant *Admin* privileges to learners on the Community Showcase Hub
 
-**During the workshop**
-- [ ] Consider recording your workshop so that learners can refer back to this for later viewing
-    
-**After Part One**
-    
+### Deliver Part One
+
+- [ ] Host Part One of the workshop
+  - [ ] Remember to record the workshop so that learners can refer back to this for later viewing
+
+### After Part One
+
 - [ ] Populate the CodiMD for the self-guided study
-    
-**After Part Two**
 
-- [ ] Email learners two days after the workshop to complete feedback
+### Deliver Part Two
+
+- [ ] Host Part Two of the workshop
+  - [ ] Remember to record the workshop so that learners can refer back to this for later viewing
+
+### After Part Two**
+
+- [ ] Email learners two days after the workshop to complete feedback and follow-up on micro-grant status (if applicable)
 - [ ] Restore the Community Showcase Hub
   - [ ] Remove Owner status from the GitHub team
   - [ ] Remove *Admin* privileges from learners on the Community Showcase Hub
diff --git a/learners/reference.md b/learners/reference.md
index bf2d65a..2ce283d 100644
--- a/learners/reference.md
+++ b/learners/reference.md
@@ -25,7 +25,6 @@
 (glossary)=
 ## Glossary
 
-
 (glossary:cpu)=
 CPU
 : Central Processing Unit – executes computational work. The number of CPU cores needed for a job depends on how scalable the computational work is, the type and amount of work to be processed.
@@ -48,4 +47,3 @@ JupyterHub
 (glossary:ram)=
 RAM
 : Random Access Memory – a computer's "short-term memory". The amount of RAM needed for a job depends on the size of the data structures to be processed.
-
diff --git a/learners/setup.md b/learners/setup.md
index 9490088..71048a0 100644
--- a/learners/setup.md
+++ b/learners/setup.md
@@ -4,14 +4,14 @@
 
 Before joining the training, participants should be able to:
 
-- Access the 2i2c [Community Showcase Hub](https://showcase.2i2c.cloud) using their GitHub account
+- Access the 2i2c [Community Showcase Hub](https://showcase.2i2c.cloud) using their GitHub account (or use their own community hub)
 - Know basic Git, such as pushing and pulling to a remote GitHub repository
-- Find the shared collaborative note-taking document
+- Find the shared collaborative note-taking document, e.g. CodiMD
 - Access the Slack Channel for asynchronous support
 - Use a web browser and video conferencing, e.g. Zoom
 - Read the [2i2c Code of Conduct](https://compass.2i2c.org/code-of-conduct/).
 
-If you have trouble with any of these steps, please contact the training instructor. 
+If you have trouble with any of these steps, please contact the training instructor.
 
 :::{tip}
 If you need a refresher on the fundamentals of Git, then check out: