diff --git a/Unit_testing/check_minimum_requirement.php b/Unit_testing/check_minimum_requirement.php
index cd31486..6571c1b 100644
--- a/Unit_testing/check_minimum_requirement.php
+++ b/Unit_testing/check_minimum_requirement.php
@@ -37,7 +37,15 @@
 
 <hr />
 
-<p class="blackboard grey-light result">Your results may take a few seconds to appear below. If your schema passes all the tests then you have met the minimum requirement for Assignment 1 and are guaranteed to score at least 50%. Your final submission will be marked using an extended version of this schema checking tool. If you are unsure about anything in the report, please contact one of the teaching staff.</p>
+<div class="blackboard grey-light result">
+
+<p>Your results may take a few seconds to appear below. If your schema passes all the tests then you have met the minimum requirement for Assignment 1 and should score at least 50%. Your final submission will be marked using an extended version of this schema checking tool.</p>
+
+<p>Note that the <em>first</em> sentence of any failure message is the most important one. The second sentence is generated by the software framework this tool is built on and may sometimes be a bit obscure. For example, if a table or column is missing or mis-named, you will see something like “Failed asserting that 0 matches expected 1.” This can safely be ignored. More subtly, suppose you declare a column of type <code>NUMBER</code> with no length, when a maximum length is specified. Oracle’s <code>NUMBER</code> data type defaults to a length of 38 digits, so failure messages will refer to the value “38”. Again, this can be ignored.</p>
+
+<p>If you are unsure about anything in the report, please contact one of the teaching staff.</p>
+
+</div>
 
 <div style="border: 2px solid grey; width: 50%; padding: 1em 4em 1em 4em;">