HTCondorWiki: Using Condor Annex For The First Time

 
 {subsection: Testing}
 
-Give HTCondor a few seconds to spin up and the try a few commands to make sure the basic are working:
+Give HTCondor a few seconds to spin up and the try a few commands to make sure the basics are working.  Your output will vary depending on the time of day, the name of your Linux machine, and its core count, but it should generally be pretty similar to the following.
 
 {term}
 $ condor_q
--- Schedd: submit-3.batlab.org : <128.104.100.22:12258?... @ 02/03/17 13:52:56
-OWNER BATCH_NAME      SUBMITTED   DONE   RUN    IDLE   HOLD  TOTAL JOB_IDS
+- Schedd: submit-3.batlab.org : <127.0.0.1:12815?... @ 02/03/17 13:57:35
+OWNER    BATCH_NAME         SUBMITTED   DONE   RUN    IDLE  TOTAL JOB_IDS
 
 0 jobs; 0 completed, 0 removed, 0 idle, 0 running, 0 held, 0 suspended
 $ condor_status -any
@@ -58,7 +58,7 @@
 
 {file: ~/condor-annex/sleep.submit}
 executable = /bin/sleep
-arguments = 60
+arguments = 600
 queue
 {endfile}
 
@@ -86,7 +86,7 @@
 
 {subsection: Configure public interface}
 
-The default personal Condor uses the loop-back interface, which basically just means it won't talk to anyone other than itself.  For =condor_annex= to work, your personal condor needs to use the Linux machine's public interface.  In most cases, that's as simple as adding the following lines to =~/condor-8.7.0/local/condor_config.local=.
+The default personal Condor uses the "loopback" interface, which basically just means it won't talk to anyone other than itself.  For =condor_annex= to work, your personal condor needs to use the Linux machine's public interface.  In most cases, that's as simple as adding the following lines to =~/condor-8.7.0/local/condor_config.local=.
 
 {file: ~/condor-8.7.0/local/condor_config.local}
 NETWORK_INTERFACE = *