HTCondorWiki: Git New Branch Rules

-Below are the rules to be followed for any new branch that you plan to push to Condor's central git repository.
+Below are the rules to be followed for any new branch that you plan to push to HTCondor's central git repository.
 
 {subsection: Naming your branch}
 
@@ -17,9 +17,9 @@
    after XXX. If a number is already there in the old version,
    increment it.
 
-Release branches are made for every release of Condor when we're
+Release branches are made for every release of HTCondor when we're
    almost ready to ship them.  They should be named with the version
-   of Condor they hold, for example: "V6_5_3-branch".  We know that
+   of HTCondor they hold, for example: "V6_5_3-branch".  We know that
    any branch name with a 3-number version like that is a release
    branch for that specific version.
 
@@ -115,7 +115,7 @@
 The version string and pre-release tag can be found in the top level /CMakeLists.txt. Look for these lines:
 
 {code}
-# Condor version info
+# HTCondor version info
 set(VERSION "7.5.6")
 
 # Set PRE_RELEASE to either a string (i.e. "PRE-RELEASE-UWCS") or OFF