diff --git a/1-Setup.md b/1-Setup.md
index 19333ba88019727e9103473f26790a1a0356881d..80c799746b63f835d116e7d21cbe257dd5fe115f 100644
--- a/1-Setup.md
+++ b/1-Setup.md
@@ -1,5 +1,7 @@
 # [IOC Deployment and Troubleshooting](README.md)
 
+Link to [the outline](instructions#outline)
+
 ## 1 Setup
 
 ### 1.1 Configure Environment Variables
diff --git a/2-IOC-deployment.md b/2-IOC-deployment.md
index f072d084db3b00bb07b2dec53d24d71f70bb0297..d8187f7bff9897253d8070ce6122b700e033882c 100644
--- a/2-IOC-deployment.md
+++ b/2-IOC-deployment.md
@@ -1,5 +1,7 @@
 # [IOC Deployment and Troubleshooting](README.md)
 
+Link to the [previous section](1-Setup.md#1-setup)
+
 ## 2 Deploy a new IOC
 
 ### 2.1 Clone xxx
diff --git a/3-Add-simulated-motors.md b/3-Add-simulated-motors.md
index add397f9bce9ecbc16c1716bd546153518bbb36d..cdc5847273053db914f3d275bf3a52b9c8906ac4 100644
--- a/3-Add-simulated-motors.md
+++ b/3-Add-simulated-motors.md
@@ -1,5 +1,7 @@
 # [IOC Deployment and Troubleshooting](README.md)
 
+Link to the [previous section](2-IOC-deployment.md#2-deploy-a-new-ioc)
+
 ## 3 Add simulated motors to the IOC
 
 IOCs based on xxx already include support for simulated motors by default, so only the IOC's run-time config needs to be modified to add simulated motors.
diff --git a/4-Deploy-motorVMC.md b/4-Deploy-motorVMC.md
index 59946111a32cc194852d4d6e9c78241cd47713c8..85f5f099d11604bf295eec925635f52c398dfedd 100644
--- a/4-Deploy-motorVMC.md
+++ b/4-Deploy-motorVMC.md
@@ -1,5 +1,7 @@
 # [IOC Deployment and Troubleshooting](README.md)
 
+Link to the [previous section](3-Add-simulated-motors.md#3-add-simulated-motors-to-the-ioc)
+
 ## 4 Deploy the motorVMC (Virtual Motor Controller) module
 
 A Virtual Motor Controller (VMC) has a number of advantages over simulated motors for EPICS trainings:
diff --git a/5-Add-virtual-motors.md b/5-Add-virtual-motors.md
index fa87525205c6f64e2cec5df19023bc97beaefb47..dd4a533e66cacd1c912a6798bc1fd73923144865 100644
--- a/5-Add-virtual-motors.md
+++ b/5-Add-virtual-motors.md
@@ -1,5 +1,7 @@
 # [IOC Deployment and Troubleshooting](README.md)
 
+Link to the [previous section](4-Deploy-motorVMC.md#4-deploy-the-motorvmc-virtual-motor-controller-module)
+
 ## 5 Add virtual motors to the IOC
 
 ### 5.1 Add motorVMC to the IOC's RELEASE file
diff --git a/6-asyn-troubleshooting.md b/6-asyn-troubleshooting.md
index a5657d0dcb0fad31de9b11246cde5f743dd178c4..0a2eef28bec11e8739db71896ec63fb486b8909d 100644
--- a/6-asyn-troubleshooting.md
+++ b/6-asyn-troubleshooting.md
@@ -1,5 +1,7 @@
 # [IOC Deployment and Troubleshooting](README.md)
 
+Link to the [previous section](5-Add-virtual-motors.md#5-add-virtual-motors-to-the-ioc)
+
 ## 6 asyn troubleshooting
 
 The EPICS asyn module provides a [trace facility](https://htmlpreview.github.io/?https://github.com/epics-modules/asyn/blob/master/documentation/asynDriver.html#asynTrace) that allows communication between an IOC and a controller to be displayed or logged.