diff --git a/concepts/naming.md b/concepts/naming.md
index 535e681..8f56589 100644
--- a/concepts/naming.md
+++ b/concepts/naming.md
@@ -39,7 +39,7 @@
 `a/y/foo/bar`, `mount table a/y` must also be consulted, since it serves
 mounts made below `y`.
 
-![Example namespace](https://cdn.rawgit.com/vanadium/docs/images/namespace-generic.svg)
+![Example namespace](https://cdn.rawgit.com/vanadium/docs/master/images/namespace-generic.svg)
 
 The first element of a name that begins with `/` points to the mount table at
 which to begin the resolution. For example, the name `/ns1.v.io:8101/a` starts
@@ -56,12 +56,12 @@
 that is relative to `ns1.v.io:8101`, its root, and hence can resolve
 `a`, `b`, `c`, `a/y`, and `a/z`.
 
-![The view from Client 1](https://cdn.rawgit.com/vanadium/docs/images/namespace-client1.svg)
+![The view from Client 1](https://cdn.rawgit.com/vanadium/docs/master/images/namespace-client1.svg)
 
 In contrast, process `Client 2` with `ns2.v.io:8102` as its root can
 resolve only `y` and `z`.
 
-![The view from Client 2](https://cdn.rawgit.com/vanadium/docs/images/namespace-client2.svg)
+![The view from Client 2](https://cdn.rawgit.com/vanadium/docs/master/images/namespace-client2.svg)
 
 The advantage of using a relative namespace is that it can define a context.
 For example, for debugging or testing one would set up the namespace to
@@ -85,7 +85,7 @@
 difference with relative names is that we're assuming a "current directory" to
 start from as opposed to providing it in the name.
 
-![The leaves are servers, or empty tables](https://cdn.rawgit.com/vanadium/docs/images/namespace-with-servers.svg)
+![The leaves are servers, or empty tables](https://cdn.rawgit.com/vanadium/docs/master/images/namespace-with-servers.svg)
 
 User-supplied server code that implements RPCs also appears as names in mount
 tables. In the diagram above `Server 1` and `Server 2` provide a server called
diff --git a/designdocs/authentication.md b/designdocs/authentication.md
index 817310a..98feff6 100644
--- a/designdocs/authentication.md
+++ b/designdocs/authentication.md
@@ -44,7 +44,7 @@
 In this implementation, [NaCl/box] is used to establish an [authenticated-encryption]
 channel based on an ECDH key exchange.
 
-![](https://cdn.rawgit.com/vanadium/docs/images/authentication-flow.svg)
+![](https://cdn.rawgit.com/vanadium/docs/master/images/authentication-flow.svg)
 Where:
 - `{foo}k` represents the message `foo` encrypted using the key `k`
 - Channel bindings C1 and C2 at the Client and Server ends respectively are
diff --git a/designdocs/identity-service.md b/designdocs/identity-service.md
index 70fdf00..1a73d97 100644
--- a/designdocs/identity-service.md
+++ b/designdocs/identity-service.md
@@ -90,7 +90,7 @@
 for a blessing from the Vanadium Blessing Service. The following sequence
 diagram lists the network requests involved in this process:
 
-![](https://cdn.rawgit.com/vanadium/docs/images/blessing-flow.svg)
+![](https://cdn.rawgit.com/vanadium/docs/master/images/blessing-flow.svg)
 
 - Solid-line arrows represent HTTPS requests (except one HTTP to localhost).
 - Dotted-line arrows represent Vanadium RPC requests.
diff --git a/tools/vanadium-chrome-extension.md b/tools/vanadium-chrome-extension.md
index e4d03c9..aca6bfe 100644
--- a/tools/vanadium-chrome-extension.md
+++ b/tools/vanadium-chrome-extension.md
@@ -30,7 +30,7 @@
 extension sends messages back to the web app when those calls return, or when
 an external device initiates a call to the JavaScript client.
 
-![Vanadium Chrome extension overview](https://cdn.rawgit.com/vanadium/docs/images/chrome-extension-overview.svg)
+![Vanadium Chrome extension overview](https://cdn.rawgit.com/vanadium/docs/master/images/chrome-extension-overview.svg)
 
 Isolating the Vanadium libraries inside a NaCl plugin has the added benefit
 that no JavaScript web app ever sees any private keys.  All cryptographic
@@ -44,7 +44,7 @@
 
 The following diagram depicts these components and the flow of messages between them.
 
-![Vanadium Chrome extension details](https://cdn.rawgit.com/vanadium/docs/images/chrome-extension-detail.svg)
+![Vanadium Chrome extension details](https://cdn.rawgit.com/vanadium/docs/master/images/chrome-extension-detail.svg)
 
 When a web app makes an RPC to a device using the Vanadium JavaScript library,
 a message is sent to the content script, which then forwards that message to