correct image floats

2 files changed, 2 insertions, 2 deletions

diff --git a/report/esoteric_project_report.pdf b/report/esoteric_project_report.pdf
index a044f70..ed7c08c 100644
--- a/report/esoteric_project_report.pdf
+++ b/report/esoteric_project_report.pdf
diff --git a/report/esoteric_project_report.tex b/report/esoteric_project_report.tex
index 7c77a80..09b22ff 100644
--- a/report/esoteric_project_report.tex
+++ b/report/esoteric_project_report.tex
@@ -448,6 +448,8 @@ The use of actual source files in testing meant that compiler and program behavi
 Logical testing using test harnesses was particularly thorough, ensuring that the parser was able to handle comparing integers, as well as real numbers. 
 In addition, extensive logical testing for the AND and OR operators was carried out to ensure that there were no bugs from the position of particular variables being evaluated. 
 In other words, the software was tested so that the order of variables in a logical test did not matter, for example A AND B is equivalent to B AND A (see appendix for examples of this).
+Various different mathematical, conditional and logical tests were used to test the functionality of the implemented code. 
+These tests, combined with example code, allowed our compiler system to be checked in a real world scenario, and thus solidify the testing done in earlier sprints.
 Below are some examples of output testing harnesses, run through the IDE program.
 
 \begin{figure}[!htb]
@@ -464,8 +466,6 @@ Below are some examples of output testing harnesses, run through the IDE program
 	\label{test_harness_two}	
 \end{figure}
 
-As can be seen from the above screenshots, various different mathematical, conditional and logical tests were used to test the functionality of the implemented code. 
-These tests, combined with example code, allowed our compiler system to be checked in a real world scenario, and thus solidify the testing done in earlier sprints.
 
 
 \chapter{Discussion, conclusion and future work}