Externally source all references

diff --git a/README.md b/README.md
index 70b5ea9f0a859fc0372a792a41298d91388fc1de..df0c301febfd810dbe21b92f6b3f37431b29b541 100644 (file)
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@ a [CM-5 monitor](https://dfarq.homeip.net/tandy-cm-5-monitor/) using the
 [Tandy Graphics Adapter display standard](
 https://en.wikipedia.org/wiki/Tandy_Graphics_Adapter).
 
-![A Pico 2 hooked up to my monitor.](reference/cm5.jpeg "My current setup")
+![A Pico 2 hooked up to my monitor.](assets/cm5.jpeg "My current setup")
 
 ## Building
 
@@ -25,10 +25,11 @@ The resulting `tga.uf2` file can be copied to the Pico 2.
 
 ## Troubleshooting
 
-Given the lack of [documentation](reference/cm5.pdf) (or, more likely, my lack
-of understanding it) I can only *assume* the CM-5 monitor operates at a 5V TTL
-level. This would of course be an issue since the Pico operates at 3.3V and
-would explain why I was unable to test the code simply by plugging the Pico
-directly into the monitor. It would seem we need a way of boosting the TTL level
-of the Pico---perhaps with some special IC---before we're able to test the PIO
-code.
+Given the lack of
+[documentation](https://www.manualslib.com/manual/3309783/Tandy-Cm-5.html) (or,
+more likely, my lack of understanding it) I can only *assume* the CM-5 monitor
+operates at a 5V TTL level. This would of course be an issue since the Pico
+operates at 3.3V and would explain why I was unable to test the code simply by
+plugging the Pico directly into the monitor. It would seem we need a way of
+boosting the TTL level of the Pico---perhaps with some special IC---before we're
+able to test the PIO code.

diff --git a/reference/cm5.jpeg b/assets/cm5.jpeg
similarity index 100%
rename from reference/cm5.jpeg
rename to assets/cm5.jpeg

diff --git a/reference/cm5.pdf b/reference/cm5.pdf
deleted file mode 100644 (file)
index f968bea..0000000
Binary files a/reference/cm5.pdf and /dev/null differ