diff --git a/README.md b/README.md
index d5c0ab7..263ce96 100644
--- a/README.md
+++ b/README.md
@@ -43,7 +43,7 @@
 "snap" we're always looking for. David Kachel has a very good
 commentary on this:
 
-[The Primacy Of Local Contrast](http://davidkachel.com/wpNewDK/wp-content/uploads/2019/05/PrimacyOfLocalContrast.pdf)
+[http://davidkachel.com/wpNewDK/wp-content/uploads/2019/05/PrimacyOfLocalContrast.pdf](http://davidkachel.com/wpNewDK/wp-content/uploads/2019/05/PrimacyOfLocalContrast.pdf)
 
 For example, I recently shot a scene in which the darkest shadows were
 on Zone III, and the brightest highlights (snow) were well into Zone
@@ -98,7 +98,7 @@
 For those of you with a technical bent, I highly recommend a careful
 reading of this explanation of film behavior by David Kachel:
 
-[How Film Works](http://davidkachel.com/wpNewDK/wp-content/uploads/2019/05/HowFilmWorks.pdf)
+[http://davidkachel.com/wpNewDK/wp-content/uploads/2019/05/HowFilmWorks.pdf](http://davidkachel.com/wpNewDK/wp-content/uploads/2019/05/HowFilmWorks.pdf)
 
 Normally, we don't notice this because *we agitate regularly* thereby
 replenishing the supply for fresh developer everywhere, most
@@ -210,7 +210,7 @@
   temperature-sensitive timer to keep temperature considerations out
   of mind in the darkroom.  You can find the details here:
 
-  [Devtimer](https://gitbucket.tundraware.com/tundra/devtimer)
+  [https://gitbucket.tundraware.com/tundra/devtimer](https://gitbucket.tundraware.com/tundra/devtimer)
 
   This is certainly not a requirement and you can do ordinary
   time/temperature corrections as usual in your own work.