about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2015-07-13 20:46:27 -0700
committerKartik K. Agaram <vc@akkartik.com>2015-07-13 20:46:27 -0700
commitfaf0429b687561dc3d01adf0ff75cef630ba0f6c (patch)
tree94938e79489e420e17aa79e9678b09f5b6046b03
parentd855af1fba7868a4cbee848d316f6394a8e1d4a0 (diff)
downloadmu-faf0429b687561dc3d01adf0ff75cef630ba0f6c.tar.gz
1775
-rw-r--r--Readme.md4
-rw-r--r--html/chessboard-test.pngbin0 -> 11099 bytes
-rw-r--r--html/factorial-test.pngbin0 -> 8499 bytes
3 files changed, 2 insertions, 2 deletions
diff --git a/Readme.md b/Readme.md
index 0c69fd83..91218f85 100644
--- a/Readme.md
+++ b/Readme.md
@@ -122,7 +122,7 @@ You can also run its unit tests:
 
 Here's what one of the tests inside `factorial.mu` looks like:
 
-![test example](http://i.imgur.com/SiQv9gn.png)
+![test example](html/factorial-test.png)
 
 Every test conceptually spins up a really lightweight virtual machine, so you
 can do things like check the value of specific locations in memory. You can
@@ -130,7 +130,7 @@ also print to screen and check that the screen contains what you expect at the
 end of a test. For example, `chessboard.mu` checks the initial position of a
 game of chess (delimiting the edges of the screen with periods):
 
-![screen test](http://i.imgur.com/ufopuF8.png)
+![screen test](html/chessboard-test.png)
 
 Similarly you can fake the keyboard to pretend someone typed something:
 
diff --git a/html/chessboard-test.png b/html/chessboard-test.png
new file mode 100644
index 00000000..8514cec7
--- /dev/null
+++ b/html/chessboard-test.png
Binary files differdiff --git a/html/factorial-test.png b/html/factorial-test.png
new file mode 100644
index 00000000..02f8ec9c
--- /dev/null
+++ b/html/factorial-test.png
Binary files differ