systemd-process-supervision.md

@@ -30,13 +30,11 @@ That would then start the `rts-module@h1lsc.service` to load the kernel module,
 
 The DAQD components are managed directly with systemd via `systemctl`.  Here are the various available services.
 
-
-
- * [`rts-daqd.service`](support/systemd/rts-daqd.service): the main DAQD service
- * `rts-local_dc.service`: the local data concentrator
- * `rts-nds.service`: back-end NDS1 data source
- * `rts-edc.service`: stand-alone EPICS data recorder 
- * `rts-run_number.service`: run number server
+ * [`rts-daqd.service`](https://git.ligo.org/cds/advligorts/-/blob/master/support/systemd/rts-daqd@.service): the main DAQD service
+ * [`rts-local_dc.service`](https://git.ligo.org/cds/advligorts/-/blob/master/support/systemd/rts-local_dc@.service): the local data concentrator
+ * [`rts-nds.service`](https://git.ligo.org/cds/advligorts/-/blob/master/support/systemd/rts-nds@.service): back-end NDS1 data source
+ * [`rts-edc.service`](https://git.ligo.org/cds/advligorts/-/blob/master/support/systemd/rts-edc@.service): stand-alone EPICS data recorder 
+ * [`rts-run_number.service`](https://git.ligo.org/cds/advligorts/-/blob/master/support/systemd/rts-run_number@.service): run number server
 
 The services are controlled via `systemctl`:
 ```shell