diff --git a/developer-guide/30-Development/02-development-on-Raspberry-Pi.md b/developer-guide/30-Development/02-development-on-Raspberry-Pi.md
index 59cfbb39..ac669015 100644
--- a/developer-guide/30-Development/02-development-on-Raspberry-Pi.md
+++ b/developer-guide/30-Development/02-development-on-Raspberry-Pi.md
@@ -9,7 +9,7 @@ If you have a Raspberry Pi available, you can quickly boot up a near-exact envir
 
 1. Install the Pioreactor software on to a microSD card by following the instructions [here](/user-guide/software-set-up).
 2. Power the Raspberry Pi. Since there's no HAT hardware, there won't be a blue blinking LED. The Raspberry Pi will still connect to the network you provided in the setup.
-3. SSH into the Raspberry Pi. [Instructions on how to SSH in](http://localhost:3001/user-guide/accessing-raspberry-pi).
+3. SSH into the Raspberry Pi. [Instructions on how to SSH in](/user-guide/accessing-raspberry-pi).
     - You should also be able to visit http://pioreactor.local
 4. Once SSH'ed in, we need to add some "mocking" packages. Enter the following:
     - `sudo pip3 install fake-rpi`
diff --git a/user-guide/03-Extending your Pioreactor/01-cluster-management/01-create-cluster.md b/user-guide/03-Extending your Pioreactor/01-cluster-management/01-create-cluster.md
index 619de56c..09f17314 100644
--- a/user-guide/03-Extending your Pioreactor/01-cluster-management/01-create-cluster.md	
+++ b/user-guide/03-Extending your Pioreactor/01-cluster-management/01-create-cluster.md	
@@ -56,7 +56,7 @@ When you have multiple Pioreactors, you can nominate one to be the leader, and r
 
 #### Cluster, and leader is _not_ a worker
 
-You can also choose not to have the leader be a worker. This is useful if you have a spare Raspberry Pi without the Pioreactor hardware, or the number of Pioreactors grows large and you wish to keep one out of the inventory to focus on being a leader only. We provide custom images for this [here](http://localhost:3001/user-guide/software-set-up#id-like-to-have-the-leader-not-be-a-worker-and-only-a-standalone-leader-can-i-do-that).
+You can also choose not to have the leader be a worker. This is useful if you have a spare Raspberry Pi without the Pioreactor hardware, or the number of Pioreactors grows large and you wish to keep one out of the inventory to focus on being a leader only. We provide custom images for this [here](/user-guide/software-set-up#id-like-to-have-the-leader-not-be-a-worker-and-only-a-standalone-leader-can-i-do-that).
 
 ![leader not worker](/img/user-guide/leader_cluster.png)
 
diff --git a/user-guide/03-Extending your Pioreactor/07-using-pumps.md b/user-guide/03-Extending your Pioreactor/07-using-pumps.md
index 127ee626..742ff2f5 100644
--- a/user-guide/03-Extending your Pioreactor/07-using-pumps.md	
+++ b/user-guide/03-Extending your Pioreactor/07-using-pumps.md	
@@ -120,7 +120,7 @@ Before attaching to media, waste, or vials for your experiments, you can spray t
 
 ### Running pumps from the web interface
 
-See documentation on [how to run pumps manually from the UI](http://localhost:3001/user-guide/manual-dosing-leds#dosing).
+See documentation on [how to run pumps manually from the UI](/user-guide/manual-dosing-leds#dosing).
 
 ### Running pumps from the command line