{section: 1. Advertise the GPU}
 
-The availability of GPU resources must be advertised in the machine's ClassAd, in order for jobs that need GPUs to be matched with machines that have GPUs.
-
-As of HTCondor 8.2 (actually 8.1.6), you can detect and advertise GPUs by adding a single line to the configuration file on your STARTD.
+The availability of GPU resources must be advertised in the machine's ClassAd, in order for jobs that need GPUs to be matched with machines that have GPUs. As of HTCondor version 8.2.0 (actually 8.1.6), the detection and advertisement of GPUs is automated by adding a single line representing a metaknob to the configuration of the execute node.
 
    use feature : GPUs
 
-You can advertise additional attributes of the GPUs by also setting
+Advertise additional attributes of the GPUs by also setting
 
    GPU_DISCOVERY_EXTRA = -extra
 
-The =feature:GPUs= metaknob (above) will invoke the _condor_gpu_discovery_ tool
-to populate a custom resource identified by 'GPUs' in the following way.
+The =feature:GPUs= metaknob will invoke the _condor_gpu_discovery_ tool
+to generate and populate the machine ClassAd for a custom resource identified by the =GPUs= tag within ClassAd attribute names.
 
-The HTCondor _condor_gpu_discovery_ tool is designed to assist in detecting GPUs and in providing configuration details that help to set up the advertisement of GPU information.
+The HTCondor _condor_gpu_discovery_ tool is designed to assist in detecting GPUs and in providing details that help to set up the advertisement of GPU information.
 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 this mechanism is used to define a resource. These examples use the resource type name =GPUs=. These resource type names are case insensitive, but all characters within the name are significant,
+HTCondor has a general mechanism for declaring user-defined slot resources. GPUs are a user-defined slot resource, so this same mechanism is used to define a resource. Use of the metaknob always uses the resource type name =GPUs=. This resource type name is case insensitive, but all characters within the name are significant,
 so be consistent.
 
 Define =GPUs= as a custom resource by adding the following definitions to the configuration of the execute node.