HTCondorWiki: Creating Condor Pools At Amazon

-One approach to using cloud resources to run HTCondor jobs is to use the =condor_annex= tool to expand an existing pool onto the cloud (see HowToUseCondorAnnexWithOnDemandInstances).  Another approach, documented here, is to create a new HTCondor pool entirely in the cloud.  The HTCondor team maintains an AWS Marketplace entry to help simplify the process.  These instructions assume you already have an AWS account and some experience using HTCondor; it will also help to have some experience using AWS and SSH.  You will also need an EC2 key pair; if you don't already have one, see section 5.
+One approach to using cloud resources to run HTCondor jobs is to use the =condor_annex= tool to expand an existing pool onto the cloud (see HowToUseCondorAnnexWithOnDemandInstances).  Another approach, documented here, is to create a new HTCondor pool entirely in the cloud.  The HTCondor team maintains an AWS Marketplace entry to help simplify the process.  These instructions assume you already have an AWS account and some experience using HTCondor; it will also help to have some experience using AWS and SSH.  You will also need an EC2 key pair; if you don't already have one, see section 5.1.
 
 Although this approach doesn't allow jobs already in a queue to run on cloud resources, it has the advantage that all file-transfer between the queue and the execute nodes occurs within the cloud, which could lead to substantial performance improvements and cost reductions.
 
@@ -16,7 +16,8 @@
 4: Clean Up
 4:: The Cloud Resources
 4:: The Head Node
-5: Appendix: Obtain an EC2 Key Pair
+5: Appendix
+5:: Obtain an EC2 Key Pair
 
 {section: 1 Start a Head Node}
 
@@ -157,7 +158,9 @@
 
 ----
 
-{section: 5 Obtain an EC2 Key Pair}
+{section: 5 Appendix}
+
+{subsection: 5.1 Obtain a Key Pair}
 
 You need an EC2 key pair in order to connect (SSH) to your head node.