Update sge.md

Author: DilumAluthge

Diff for: docs/sge.md

@@ -1,18 +1,11 @@
-# Sun Grid Engine (SGE) via qrsh
+# Sun Grid Engine (SGE)
 
 > [!WARNING]
 > The SGE functionality is not currently being maintained.
 >
 > We are currently seeking a new maintainer for the SGE functionality. If you are an active user of SGE and are interested in being a maintainer, please open a GitHub issue - say that you are interested in being a maintainer for the SGE functionality.
 
-`SGEManager` uses SGE's `qsub` command to launch workers, which communicate the
-TCP/IP host:port info back to the master via the filesystem.  On filesystems
-that are tuned to make heavy use of caching to increase throughput, launching
-Julia workers can frequently timeout waiting for the standard output files to appear.
-In this case, it's better to use the `QRSHManager`, which uses SGE's `qrsh`
-command to bypass the filesystem and captures STDOUT directly.
-
-## SGE - a simple interactive example
+## SGE via `qsub`: Use `ClusterManagers.addprocs_sge` (or `ClusterManagers.SGEManager`)
 
 ```julia
 julia> using ClusterManagers
@@ -66,3 +59,12 @@ julia>  From worker 26: lum-7-2.local
 julia> rmprocs(workers())
 Task (done)
 ```
+
+## SGE via `qrsh`: Use `ClusterManagers.addprocs_qrsh` (or `ClusterManagers.QRSHManager`)
+
+`SGEManager` uses SGE's `qsub` command to launch workers, which communicate the
+TCP/IP host:port info back to the master via the filesystem.  On filesystems
+that are tuned to make heavy use of caching to increase throughput, launching
+Julia workers can frequently timeout waiting for the standard output files to appear.
+In this case, it's better to use the `QRSHManager`, which uses SGE's `qrsh`
+command to bypass the filesystem and captures STDOUT directly.