-HTCondor can help manage GPUs (graphics processing units) in your pool of execute nodes, allocating them as resources to jobs, which can use them using an API such as {link:http://www.khronos.org/opencl/ OpenCL} or {link:http://www.nvidia.com/object/cuda_home_new.html CUDA}.
+HTCondor can help manage the allocation of GPUs (graphics processing units) to jobs within a pool of execute nodes, where HTCondor considers the GPUs as resources to jobs. The jobs can use the GPUs using an API such as {link:http://www.khronos.org/opencl/ OpenCL} or {link:http://www.nvidia.com/object/cuda_home_new.html CUDA}.
 
-The techniques described here depend on HTCondor version 8.1.4 or later. Those using an earlier version of HTCondor must upgrade. Those that cannot upgrade for some reason may try an older, less flexible technique as
+The techniques described here depend on HTCondor version 8.1.4 or a later version. Those with less current versions may try an older, less flexible technique as
 described at HowToManageGpusInSeriesSeven.
 
 The general technique to manage GPUs is:
 
 1: Advertise the GPU: configure HTCondor so that execute nodes include information about available GPUs in their machine ClassAd.
-2: Job requests a GPU: jobs identify their request for a GPU and specify any further Requirements to acquire a suitable GPU
+2: Job requests a GPU: jobs identify their request for a GPU and specify any further specific requirements of the GPU, in order to acquire a suitable GPU
 3: Identify the GPU: Jobs modify their arguments or environment to learn which GPU they may use.
 
 {section: Advertise the GPU}
 
 The HTCondor =condor_gpu_discovery= tool is designed to assist in detecting GPUs and in configuring HTCondor to advertise GPU information.
-This tool detects CUDA and OpenCL devices, and outputs a list of GPU identifiers for all detected devices.
+This tool detects CUDA and OpenCL devices, and it outputs a list of GPU identifiers for all detected devices.
 
 HTCondor has a general mechanism for declaring user-defined slot resources. GPUs are a user-defined slot resource, so use this mechanism to define a resource called 'GPUs'. This resource type name, 'GPUs,' is case insensitive, but you must be consistent about the plural. HTCondor considers 'GPU' to be a different resource type than 'GPUs'.  We recommend the use of 'GPUs' for GPU custom resources.
 
@@ -67,7 +67,7 @@
 
 {section: Job requests a GPU}
 
-User jobs that require a GPU must specify this requirement.  In a job's submit file, it might do something as simple as
+User jobs that require a GPU must specify this requirement.  In a job's submit description file, it might do something as simple as
 
 {code}
 Request_GPUs = 1