diff --git a/run-pihole/README.md b/run-pihole/README.md
index b60bd05..2615425 100644
--- a/run-pihole/README.md
+++ b/run-pihole/README.md
@@ -5,20 +5,20 @@
 2. Persists through reboots and firmware updates.
 
 ### Requirements
-1. You have setup the on boot script described in this repo (https://github.com/boostchicken/udmpro-utilities/tree/master/on-boot-script)
+1. You have setup the on boot script described [here](https://github.com/boostchicken/udmpro-utilities/tree/master/on-boot-script)
 2. PiHole persists through firmware updates. The on-boot script does not.  If you update your FM setup on-boot again and everything should work.
 
 ### Customization
-* Feel free to change 20-dns.conflist to change the IP address of the container. Make sure to update all ip references and the iptables rules in on_boot.sh.  The IP address can be anywhere from x.x.x.3 to x.x.x.254. .1 is reserved for the gateway and .2 is reserved for the macvlan bridge.
-* If you don't want to use vlan5, just replace br5 with br(vlanid) in on_boot.sh and 20-dns.conflist, also update all the ips accordingly
+* Feel free to change [20-dns.conflist](https://github.com/boostchicken/udm-utilities/blob/master/run-pihole/udm-files/20-dns.conflist) to change the IP address of the container. Make sure to update all ip references and the iptables rules in [on_boot.sh](https://github.com/boostchicken/udm-utilities/blob/master/run-pihole/udm-files/on_boot.sh).  The IP address can be anywhere from x.x.x.3 to x.x.x.254. .1 is reserved for the gateway and .2 is reserved for the macvlan bridge.
+* If you don't want to use vlan5, just replace br5 with br(vlanid) in [on_boot.sh](https://github.com/boostchicken/udm-utilities/blob/master/run-pihole/udm-files/on_boot.sh) and [20-dns.conflist](https://github.com/boostchicken/udm-utilities/blob/master/run-pihole/udm-files/20-dns.conflist), also update all the ips accordingly
 
 ### Steps
-1. On your controller, make a Corporate network with no DHCP server and give it a vlan.  All examples assume vlan 5.
-2. Install the CNI plugins with install-cni-plugins.sh
-3. Copy udm-files/20-dns.conflist to /mnt/data/podman/cni (or a place of your choosing and update on_boot.sh symlink).  This will create your podman macvlan network
-3. Update your on_boot.sh to include the commands in udm-files/on_boot.sh.  You can leave out the iptables rules if you don't want to DNAT all DNS calls to your PiHole
-4. Execute on_boot.sh
-5. Run the pihole docker container, be sure to make the directories for your persistent pihole configuration.  They are mounted as volumes in the command below.
+1. On your controller, make a Corporate network with no DHCP server and give it a vlan. For this example we are using vlan 5.
+2. Install the CNI plugins with by executing [install-cni-plugins.sh](https://github.com/boostchicken/udm-utilities/blob/master/run-pihole/install-cni-plugins.sh) on your UDM
+3. Copy [20-dns.conflist](https://github.com/boostchicken/udm-utilities/blob/master/run-pihole/udm-files/20-dns.conflist) to /mnt/data/podman/cni (or a place of your choosing and update [on_boot.sh](https://github.com/boostchicken/udm-utilities/blob/master/run-pihole/udm-files/on_boot.sh) symlink).  This will create your podman macvlan network
+4. Update your on_boot.sh to include the commands in [on_boot.sh](https://github.com/boostchicken/udm-utilities/blob/master/run-pihole/udm-files/on_boot.sh).  You can leave out the iptables rules if you don't want to DNAT all DNS calls to your PiHole
+5. Execute on_boot.sh
+6. Run the pihole docker container, be sure to make the directories for your persistent pihole configuration.  They are mounted as volumes in the command below.
 
 ```
  podman run -d --network dns \
@@ -34,9 +34,9 @@
     pihole/pihole:latest
 ```
 
-6. Set pihole password
+7. Set pihole password
 ```
 podman exec -it pihole pihole -a -p YOURNEWPASSHERE
 ```
-6. Update your DNS Servers to 10.0.5.3 (or your custom ip) in all your DHCP configs.
-7. Access the pihole like you would normally.
+8. Update your DNS Servers to 10.0.5.3 (or your custom ip) in all your DHCP configs.
+9. Access the pihole like you would normally.