diff --git a/doc/Extensions/Distributed-Poller.md b/doc/Extensions/Distributed-Poller.md
index e6c3e2c9dd..2d9ebedf77 100644
--- a/doc/Extensions/Distributed-Poller.md
+++ b/doc/Extensions/Distributed-Poller.md
@@ -31,7 +31,7 @@ $config['distributed_poller_memcached_port'] = '11211';
Below is an example setup based on a real deployment which at the time of writing covers over 2,500 devices and 50,000 ports. The setup is running within an Openstack environment with some commodity ha
rdware for remote pollers. Here's a diagram of how you can scale LibreNMS out:
-![Example Setup](http://www.librenms.org/img/librenms-distributed-diagram.png)
+![Example Setup](http://docs.librenms.org/img/librenms-distributed-diagram.png)
###Architecture
How you setup the distribution is entirely up to you, you can choose to host the majority of the required services on a single virtual machine or server and then a poller to actually query the devices being monitored all the way through to having a dedicated server for each of the individual roles. Below are notes on what you need to consider both from the software layer but also connectivity.
diff --git a/doc/Extensions/Varnish.md b/doc/Extensions/Varnish.md
index 15c3acc879..98fda2adf6 100644
--- a/doc/Extensions/Varnish.md
+++ b/doc/Extensions/Varnish.md
@@ -7,7 +7,7 @@ Varnish is caching software that sits logically between an HTTP client and an HT
#####