Update nGEM-detector.md

Capitalised instrument name.

Author: davidkeymer

doc/specific_iocs/other/nGEM-detector.md

@@ -1,6 +1,6 @@
 # nGEM Detector
 
-The nGEM detector is a portable detector that connects via a private ethernet connection to vendor software running on a laptop. It is often used on INES. Detector group will normally set up the laptop with the vendor software, on Ines this is installed to `c:\users\ines_mgr\documents\ngem` or `c:\nGEM-software` and a program `ngemapp.exe` is left running.
+The nGEM detector is a portable detector that connects via a private ethernet connection to vendor software running on a laptop. It is often used on INES. Detector group will normally set up the laptop with the vendor software, on INES this is installed to `c:\users\ines_mgr\documents\ngem` or `c:\nGEM-software` and a program `ngemapp.exe` is left running.
 
 Ibex support is via the NGEM IOC, which is installed and run on the laptop. It could in principle run on the NDX computer and talk to the `ngemapp.exe` program over the network, but the IOC needs to move files off the laptop to a locally attached USB hard drive after collection ends so it is more convenient to run on the laptop rather than the NDX. The IOC connects to localhost port 61000 by default, this would only need to be changed (via a macro) if the IOC was not running on the laptop. This port number is the same as passed to the `ngemapp.exe` program running in a separate window, it is the "UI Port" of the ngem software. The nGEM detector itself is network based and will be in a local 192.168 local address attached to the laptop, ibex does not need to be aware of this as it talks to the nGEM server program and does not need to directly communicate with the detector hardware.   
 
@@ -34,4 +34,4 @@ If the detector is moved to another instrument with the same laptop then:
 
 * If the NGEM vendor software is restarted, the IOC on the laptop will need to be restarted. Kill the running ioc cmd window and then run runIOC.bat shortcut on desktop
 * Make sure the NGEM IOC isn't running in two places with the same PV prefix, currently this means the IOC should be **running only on the laptop and not on the associated NDX computer** (NGEM is listed in the start/stop IOCs menu so can get started accidentally). If there are two IOCs running, you will have issues starting/stopping collection and probably see "multiple PV warning" if you use a command line tool
-* the program will rename the datafile to include the run number currently used on the instrument. If this is not happening, it could be an issue with the epics external gateway on the NDX computer (`GWEXT`) - check if e.g. for INES `caget IN:INES:DAE:RUNNUMBER` works when run from a computer separate to the NDX, if it doesn't then try locating and terminating the `gateway.exe` for the external gateway (procServ will automatically restart it). If that doesn't work, you may need to restart ibex server on the NDX             
+* the program will rename the datafile to include the run number currently used on the instrument. If this is not happening, it could be an issue with the epics external gateway on the NDX computer (`GWEXT`) - check if e.g. for INES `caget IN:INES:DAE:RUNNUMBER` works when run from a computer separate to the NDX, if it doesn't then try locating and terminating the `gateway.exe` for the external gateway (procServ will automatically restart it). If that doesn't work, you may need to restart ibex server on the NDX