Update hex docs

Author: FreddieAkeroyd

doc/processes/instrument_details/MUX-Instrument-Details.md

@@ -1,4 +1,4 @@
 # MUX
 
 MUX is the name of the system to run the Negative Muon items. It does not use a standard muon DAE, but instead 
-uses the [CAE Hexagon digitisers](/doc/specific_iocs/other/CAEN-Hexagon.md) to acquire data
+uses the [CAE Hexagon digitisers](/specific_iocs/other/CAEN-Hexagon.md) to acquire data

doc/specific_iocs/other/CAEN-Hexagon.md

@@ -4,7 +4,7 @@ The CAEN hexagon is the data acquisition used on MUX. It is currently controlled
 
 Data is published to the usual instrument network archive on `d:`, but to the `autoreduced` subfolder at the moment
 
-The hexagon runs in event mode (which it calls list mode). It is running embedded linux and generates a file locally, this local disk is served via samba and looks like a windows network share. At the end of acquisition the CAEN IOC copies files from the hexagon onto the local computer, runs a script to convert these `.bin` to `.nxs`, then archives both sets of files. The ISISICP also saves a nexus file, but this has suffix `.nxs_se`. The `.nxs` file that is generated contains a link to open the sample environement from `.nxs_se` so both files are needed for analysis.
+The hexagon runs in event mode (which it calls list mode). It is running embedded linux and generates a file locally, this local disk is served via samba and looks like a windows network share. At the end of acquisition the CAEN IOC copies files from the hexagon onto the local computer, runs a script to convert these `.bin` to `.nxs`, then archives both sets of files. The ISISICP also saves a nexus file, but this has suffix `.nxs_se`. The `.nxs` file that is generated contains a link to open the sample environment from `.nxs_se` so both files are needed for analysis.
 
 Scripting uses usual `begin` and `end` commands, however these have local modifications to start the hexagon which in turn starts the simulated ISISDAE/isisicp. Run numbers are synced between hexagon and simulated DAE, the custom dashboard db has been changed to read values from the hexagon not the ISISDAE ioc.
 
@@ -21,4 +21,4 @@ Sometimes the hexagon loses connection with the IOC, this can be due to a hexago
 - try an IOC restart
 - try a hexagon power cycle then an IOC restart
 
-After a hexagon power cycle, a timing register needs to be set on the hexagon using the CAEN MCA2 vendor software to make the event/list mode work properly. The scientists know about this and will do this. 
+After a hexagon power cycle, a timing register needs to be set on the hexagon using the CAEN MCA2 vendor software to make the event/list mode work properly. The scientists know about this and will do this.