Mentioned how to find and view the BalsamIQ wireframe.

README.md

@@ -123,7 +123,10 @@ of features were however dropped because of poor time management. The most
 basic and required features were focused on instead. I also had problems 
 fitting terrain selection into the battle editor page, since this requirement
 was announced *after* the wireframe was created. Thus, the battle editor
-ended up looking differently than the wireframe.
+ended up looking differently than the wireframe. The wireframe can be found
+in the repository, named balsamIQ-wireframe.bmpr and can be opened using
+the website BalsamIQ.com. The wireframe might also be available at:
+https://balsamiq.cloud/shgfqro/pcl4roa/rA609
 
 ### Conclusion
 In the end, this project was a very good way to gain a lot of experience 
@@ -132,4 +135,4 @@ javadoc and unit testing were taught well and gave a very valuable and real
 insight into how it is to actually program larger systems. Although the 
 project was not completely finished to a satisfactory degree, I believe
 I have learned enough, and have the capabilities, to create clean, intuitive,
-and efficient code; given enough time.
\ No newline at end of file
+and efficient code; given enough time.