diff --git a/tiddlywiki/tiddlers/content/Coursework.tid b/tiddlywiki/tiddlers/content/Coursework.tid
index 2c38146..ca4dc7f 100644
--- a/tiddlywiki/tiddlers/content/Coursework.tid
+++ b/tiddlywiki/tiddlers/content/Coursework.tid
@@ -4,6 +4,8 @@
title: Coursework
type: text/vnd.tiddlywiki
+
''NOTE'': Please reload this document in your web browser to ensure that you are looking at the latest version, and not an older version that your browser has cached.
+
! Labs
<$list filter="[tag[lab]!tag[hidden]sort[title]]">
diff --git a/tiddlywiki/tiddlers/content/labs/lab02/_Labs_02_Clone the Repository.md b/tiddlywiki/tiddlers/content/labs/lab02/_Labs_02_Clone the Repository.md
index 1b3ab17..233a1af 100644
--- a/tiddlywiki/tiddlers/content/labs/lab02/_Labs_02_Clone the Repository.md
+++ b/tiddlywiki/tiddlers/content/labs/lab02/_Labs_02_Clone the Repository.md
@@ -8,7 +8,7 @@
If asked for a master password at this point (or any later point), it is 'password' (without the speech marks).
-1. Switch to the GitBucket *quick setup* page in your web browser, and copy one of the *origin* URLs for your repository from the page. It will start with \code{https://} and end with \code{.git}.
+1. Switch to the GitBucket *quick setup* page in your web browser, and copy one of the *origin* URLs for your repository from the page. It will start with `https://` and end with `.git`.
1. Paste the URL into the *Repository URL* box in NetBeans.
diff --git a/tiddlywiki/tiddlers/content/labs/lab02/_Labs_02_Issue Driven Development.tid b/tiddlywiki/tiddlers/content/labs/lab02/_Labs_02_Issue Driven Development.tid
index 1fd8dce..6f7d204 100644
--- a/tiddlywiki/tiddlers/content/labs/lab02/_Labs_02_Issue Driven Development.tid
+++ b/tiddlywiki/tiddlers/content/labs/lab02/_Labs_02_Issue Driven Development.tid
@@ -5,7 +5,7 @@
title: /Labs/02/Issue Driven Development
type: text/x-markdown
-We have mentioned //issue driven development// a few times. This is the idea of using an issue management system as a 'to do list' to drive your development. Issues help you to give your commits more context and make it easier for yourself and other developers to find the code for a particular feature or bug. Issues also help to form part of the documentation for the system, particularly since developers can add comments to issues to elaborate on decisions or provide clarification for problems and bugs.
+We have mentioned *issue driven development* a few times. This is the idea of using an issue management system as a 'to do list' to drive your development. Issues help you to give your commits more context and make it easier for yourself and other developers to find the code for a particular feature or bug. Issues also help to form part of the documentation for the system, particularly since developers can add comments to issues to elaborate on decisions or provide clarification for problems and bugs.
Using issues is also a good way of ensuring that your commits make sense --- work on a single issue and then commit before starting on the next issue. If you do this then your commit history will be focused around your issues, and assuming your issues are based on features, bugs, and other logical work units (which they should be), then your commit history will make sense.
diff --git a/tiddlywiki/tiddlers/system/editing/$__ou_editing_TableOfContents.tid b/tiddlywiki/tiddlers/system/editing/$__ou_editing_TableOfContents.tid
index 0702fdf..a775a58 100644
--- a/tiddlywiki/tiddlers/system/editing/$__ou_editing_TableOfContents.tid
+++ b/tiddlywiki/tiddlers/system/editing/$__ou_editing_TableOfContents.tid
@@ -7,12 +7,12 @@
!! Contents
-<$list filter="[tag!tag[hidden]!tag[lab]sortan[section]]">
+<$list filter="[tag!tag[hidden]!tag[lab]!tag[image]sortan[section]]">
<$set name="strippedTitle" filter="[all[current]split[/]last[]]">
<$link>{{!!section}}. <>$link>
$set>
$list>
-
<>
+
<>
$set>
\ No newline at end of file