HTCondorWiki: Condor Error Data Structure

-{section: Condor Error data structure}
-I am on an awareness campaign for the Condor Error stack. It is the
-most important data structure in Condor, and most people don't even know
+{section: HTCondor Error data structure}
+I am on an awareness campaign for the HTCondor Error stack. It is the
+most important data structure in HTCondor, and most people don't even know
 it exists.
 
 The error stack is sort of like an exception. The error stack object is
@@ -12,7 +12,7 @@
 The "error" itself is a tuple of three values:
 =<subsystem, error code, error text>=
 
-subsystem should be obvious. The error code is unique in Condor, and the
+subsystem should be obvious. The error code is unique in HTCondor, and the
 text is a free-form string that was tacked when the error was generated.
 
 The error codes are defined in =condor_includes/condor_error_codes.h=
@@ -93,7 +93,7 @@
 
 	results = zot(i, errstack);
 	if(i > 9) {
-		errstack->push("EXAMPLE", BAR_ARG_TOO_BIG, "Condor cannot handle double digits!");
+		errstack->push("EXAMPLE", BAR_ARG_TOO_BIG, "HTCondor cannot handle double digits!");
 		return false;
 	}
 	return results;
@@ -102,7 +102,7 @@
 bool zot(int i, CondorError* errstack) {
 
 	if( (i % 2) == 1) {
-		errstack->push("EXAMPLE", ZOT_ARG_ODD, "Condor cannot handle odd numbers!");
+		errstack->push("EXAMPLE", ZOT_ARG_ODD, "HTCondor cannot handle odd numbers!");
 		return false;
 	}
 	return true;