This document is associated w/ ticket #1095.
 
-This document details the initial requirements of Condor's High Frequency Computing (HFC) effort.  The goal of Condor HFC is to effectively manage and obtain high-throughput of short (less than one second) jobs, or tasks.
+This document details the initial requirements of HTCondor's High Frequency Computing (HFC) effort.  The goal of HTCondor HFC is to effectively manage and obtain high-throughput of short (less than one second) jobs, or tasks.
 
 Note what is presented here are the requirements for a 1.0 release, the smallest possible useful release; in the interest of a quick, successful initial implementation, we want to minimize feature creep.  Furthermore, note that this document discusses just the requirements for this work, purposefully tries to avoid mentioning any particular implementation.
 
-Three fundamental abstractions encompass Condor HFC: _tasks_, _schedulers_, and _workers_.  Requirements for these three appears below, followed by more general requirements.
+Three fundamental abstractions encompass HTCondor HFC: _tasks_, _schedulers_, and _workers_.  Requirements for these three appears below, followed by more general requirements.
 
 {section: Task Requirements}
 
@@ -116,7 +116,7 @@
 
 {subsection: Reliability Requirements}
 
-In order to get substantially better performance than vanilla Condor jobs, we need to relax the reliability constraints that Condor normally maintains.
+In order to get substantially better performance than vanilla HTCondor jobs, we need to relax the reliability constraints that HTCondor normally maintains.
 
 Task submission shall be atomic.  That is, after the client submits to the scheduler, and receives a positive acknowledgment, all tasks in the batch are under control of the scheduler.  It will impossible for the scheduler to get a truncated task or a truncated batch of tasks.  If the client fails to receive the ack, it should resend the batch with the same guid.
 
@@ -124,7 +124,7 @@
 
 {subsection: Delivery Requirements}
 
-All code will be merged into the mainline Condor, and generally available to Condor users under Condor's normal licensing and distribution terms.
+All code will be merged into the mainline HTCondor, and generally available to HTCondor users under HTCondor's normal licensing and distribution terms.
 
 {subsection: Platform Requirements}