HTCondorWiki: How To Limit Disk Usage Of Jobs

 {section: How to limit disk usage of jobs}
 
-Known to work with Condor version: 7.0
+Known to work with HTCondor version: 7.0
 
-Condor monitors how much disk space jobs consume in the scratch directory created for the job on the execute machine when the job runs.  This scratch directory is typically only used by jobs which turn on Condor's file transfer mode (should_transfer_files=true).  For such jobs, the scratch directory is the current working directory and they might write their output files into that directory while they are running.
+HTCondor monitors how much disk space jobs consume in the scratch directory created for the job on the execute machine when the job runs.  This scratch directory is typically only used by jobs which turn on HTCondor's file transfer mode (should_transfer_files=true).  For such jobs, the scratch directory is the current working directory and they might write their output files into that directory while they are running.
 
-One problem that can happen is that one job on a multi-cpu system uses up so much space that all other jobs fail due to lack of space.  If the partition containing Condor's EXECUTE directory is shared by other tasks (including perhaps Condor), a full partition could cause additional things to fail as well.
+One problem that can happen is that one job on a multi-cpu system uses up so much space that all other jobs fail due to lack of space.  If the partition containing HTCondor's EXECUTE directory is shared by other tasks (including perhaps HTCondor), a full partition could cause additional things to fail as well.
 
 {subsection: How to preempt (evict) a job that uses too much disk space}
 
@@ -21,7 +21,7 @@
 
 {subsection: How to configure a separate disk partition for each batch slot}
 
-The most effective way to control how much space jobs use is to put the execute directory for each slot on its own disk partition.  Then you don't have to worry about a malformed job consuming massive amounts of disk space before PREEMPT has a chance to operate.  Assuming you have already created the necessary partitions, you can configure Condor to use them like this:
+The most effective way to control how much space jobs use is to put the execute directory for each slot on its own disk partition.  Then you don't have to worry about a malformed job consuming massive amounts of disk space before PREEMPT has a chance to operate.  Assuming you have already created the necessary partitions, you can configure HTCondor to use them like this:
 
 {code}
 SLOT1_EXECUTE = /path/to/execute1