HTCondorWiki: Nmi Test

-{section: Testing Condor with NMI}
+{section: Testing HTCondor with NMI}
 
-{subsection: Testing a Previous Condor Build}
+{subsection: Testing a Previous HTCondor Build}
 
 If the build you want to test was made from a git tag, you can submit the tests using the same tag:
 
@@ -27,7 +27,7 @@
 
 {section: The following is old documentation that needs to be updated or removed}
 
-{subsection: Using a Workspace Directory to Test a Previous Condor Build}
+{subsection: Using a Workspace Directory to Test a Previous HTCondor Build}
 
 For this scenario, my job_core_max-local-running tests were producing false negatives on random platforms in the nightly build. I wanted to make a fix to the test files and then test my changes against the previous night's build. These instructions will allow you to do that without having to commit any of your changes to CVS.
 
@@ -81,7 +81,7 @@
 --test-src=/space/home/pavlo/V6_7-branch/condor-6.7.15.tar.gz
 {endcode}
 
-{subsection: Using a Workspace Directory to Test a change to the Condor NMI test glue}
+{subsection: Using a Workspace Directory to Test a change to the HTCondor NMI test glue}
 
 Now, we will submit a new test using a previous build result. The *nmi-glue* option is where the system will get the test nmi_glue to run against the build results. Again, make sure that you give the full path to this option (don't just use ./). ALSO, make sure you test your glue changes against a Unix and a Windows platform!!!! Notice the change to --platforms!
 {code}