Update DAE-Trouble-Shooting.md

Author: FreddieAkeroyd

doc/specific_iocs/dae/DAE-Trouble-Shooting.md

@@ -466,7 +466,7 @@ Hopefully there is either only one `eventsYYYYY.tmp` file, or the most recent on
 
 For info, the `eventsYYYYY.tmp` file is the NeXus HDF5 file being written as the run goes along, and the `run_YYYYY` folder is the raw events read from the electronics. The `.tmp` is renamed to `.nxs` during an END is nothing has gone wrong, otherwise raw events can be replayed from `run_YYYYY` to create a NeXus file from scratch       
 
-If the run number comes back incorrectly (like as `000001`) then it means `c:\data\recovery.run` has been corrupted. There are backup weekday copies in c:\data e.g. `recovery.run_Thu` so you can pick one to copy to `recovery.run` however note that this may include an old run number so after restarting you may need to reset the run number (see on this page) 
+If the run number comes back incorrectly (like as `000001`) then it means `c:\data\recovery.run` has been corrupted. There are backup weekday copies in c:\data e.g. `recovery.run_Thu` so you can pick one to copy to `recovery.run` however note that this may include an old run number so after restarting you may need to reset the run number (see on this page). Looking at file sizes of `recovery.run_*` to see which looks to be the most recent good one.  
 
 If after the above you get SQLite/selogger database errors in the isisicp log, then stop isisdae/isisicp and delete `c:\data\selog.*` (`.sq3`, `.sq3-shm`, and `.sh3-wal` files)