diff --git a/docs/assets/capability-myths-demolished.pdf b/docs/assets/capability-myths-demolished.pdf
new file mode 100755
index 00000000..c6cf968b
Binary files /dev/null and b/docs/assets/capability-myths-demolished.pdf differ
diff --git a/docs/object-capabilities/object-capabilities.md b/docs/object-capabilities/object-capabilities.md
index b4b02216..224a8552 100644
--- a/docs/object-capabilities/object-capabilities.md
+++ b/docs/object-capabilities/object-capabilities.md
@@ -26,7 +26,7 @@ Instead of having permissions lists, access control lists, or other forms of sec
 
 There's a great paper on how the object-capability model works, and it's pretty easy reading:
 
-[Capability Myths Demolished](http://srl.cs.jhu.edu/pubs/SRL2003-02.pdf)
+[Capability Myths Demolished](/assets/capability-myths-demolished.pdf)
 
 ## Capabilities and concurrency