{section: 4 Run Jobs on Your Resources}
 
-It shouldn't take more than a few minutes from when your new resources join the pool for your test job to start running.  The test job sleeps for ten minutes to make it easier to catch in the running state; you don't need to wait for it to finish before testing one of your own jobs.
+It shouldn't take more than a few minutes from when your new resources join the pool for your test job to start running.  The test job sleeps for ten minutes to make it easier to catch in the running state; you don't need to wait for the test job to finish before testing one of your own jobs.
 
 You can make use of the annex resources for your own jobs in two ways: by modifying an existing submit file or by editing jobs already in the queue.
 
 {subsection: 4.1 Change a Submit File}
 
-Be sure to make a copy of your submit file before you start changing it. ;)
+Be sure to make a backup copy of your submit file before you start changing your submit file. ;)
 
 You will need to add the following lines to the submit file (before the queue statement):
 {verbatim}
@@ -201,7 +201,7 @@
 
 (This tautology will prevent CHTC's submit nodes from adding a requirement that =OpSysMajorVer= be 6 or 7.)
 
-If the old requirements _do_ mention =OpSysMajorVer=, they most likely include a clause of the following form:
+If the old requirements _do_ mention =OpSysMajorVer=, the old requirements most likely include a clause of the following form:
 
 {verbatim}
 OpSysMajorVer == 6
@@ -217,7 +217,7 @@
 
 {subsection: 4.2 Modify an Idle Job}
 
-If you want a job that's already in the queue to run on your AWS resources, you can use the =condor_qedit= command to make changes much like the ones you would if you were changing a submit file.  However, to make sure your job doesn't flock to someplace you don't want it to go, you'll need to modify the =requirements= before you set =MayUseAWS= and =WantFlocking=.
+If you want a job that's already in the queue to run on your AWS resources, you can use the =condor_qedit= command to make changes much like the ones you would if you were changing a submit file.  However, to make sure your job doesn't flock somewhere you don't want your job to go, you'll need to modify the =requirements= before you set =MayUseAWS= and =WantFlocking=.
 
 For these examples, we'll assume your job's ID is 100234.5.