HTCondorWiki: Using Condor Annex On Chtc

 (AnnexName =?= "MyFirstAnnex" || IsCHTC)
 {endverbatim}
 
-If the phrase "add the following clause" didn't make a lot of sense to you,
+If the phrase "add the following clause" didn't make a lot of sense to you, the new =requirements= line should like the following, except replacing the text =<old-requirements>= with everything to the right of the equals sign in the original requirements line.
 
 {verbatim}
-requirements = (AnnexName =?= "MyFirstAnnex" || IsCHTC) && (OpSysMajorVer isnt defined || OpSysMajorVer == 6)
+requirements = (<old-requirements>) && (AnnexName =?= "MyFirstAnnex" || IsCHTC)
 {endverbatim}
 
-Once you've gotten one job running, you may want to add additional resources to your annex.  While repeating the command from section 3 will add another instance to the "MyFirstAnnex" annex, for simplicity we recommend using another name.  (Using an existing name updates the lease for all instances in the annex, existing and new; but only new instances will respect the new max idle time.  If you've used the name of your annex in your job requirements, this might be worth the trouble.)
+...
 
+{verbatim}
+(OpSysMajorVer isnt defined || OpSysMajorVer == 6)
+{endverbatim}
 
+...
 
 {subsection: 4.2 Modify an Idle Job}