Start by creating a new AWS account, or logging into your existing account.  You may prefer to do the former, since _condor_annex_ is still experimental.  For the same reason, _condor_annex_ presently assumes that it has almost unlimited privileges.  (In the future, there will be a high-privilege one-time set-up, and the end user will run _condor_annex_ with a low-privilege AWS user (or role).)  You may want to create a(n IAM) user with "Admin" privileges, instead.
 
-You may have noticed a lot of information missing from the command-line above.  _condor_annex_ does all of its AWS work through the 'aws' command-line tool, which has a configuration file containing the access key and secret key for a given AWS account (or user or role).  If, like above, the command-line is incomplete, _condor_annex_ will look up the missing information in the AWS.  This allows you (the annex administrator) to update and maintain the defaults without having to distribute files to your end users.
+You may have noticed a lot of information missing from the command-line above.  _condor_annex_ does all of its AWS work through the 'aws' command-line tool, which has a configuration file containing the access key and secret key for a given AWS account (or user or role).  If, like above, the command-line is incomplete, _condor_annex_ will look up the missing information in the 'aws' tool's account.  This allows you (the annex administrator) to update and maintain the defaults without having to distribute files to your end users.
 
 The four default things you can set in the account are:
 
 1: An SSH keypair.  _condor_annex_ will use the one named "HTCondorAnnex".
 2: A VPC.  _condor_annex_ will use the one whose "name" tag is "HTCondorAnnex".
 3: VPC subnets.  _condor_annex_ will use the ones whose "name" tag is "HTCondorAnnex".
-4: Launch configurations.  _condor_annex- will us the ones named "HTCondorAnnex-1" through "HTCondorAnnex-8".
+4: Launch configurations.  _condor_annex_ will use the ones named "HTCondorAnnex-1" through "HTCondorAnnex-8".
 
 To speed your quick start, we provide the following Amazon Linux AMIs with HTCondor 8.4.2 pre-installed:
 
@@ -52,11 +52,15 @@
 
 The launch configurations need only the instance type, the AMI ID, and the spot price, if any.  Additional specifications are presently ignored.
 
-Once you've used the web console to create all of these objects, you'll need to install and configure the 'aws' command-line tool.  You don't need to set a default region, although if you don't, you'll need to specify one on the _condor_annex_ command-line.  Something along the lines of "yum install python-pip; pip install awscli" will usually get the job done.
+Once you've used the web console to create all of these objects, you'll need to install and configure the 'aws' command-line tool.  You don't need to set a default region, but _condor_annex_ defaults to 'us-east-1'.  Something along the lines of "yum install python-pip; pip install awscli" will usually get the tool installed.  To configure, run 'aws configure'.
 
 {subsubsection: HTCondor}
 
-_condor_annex_ assumes that it is run from a shell with a live HTCondor installation.  In particular, the security configuration should be pool password, more or less as follows:
+_condor_annex_ assumes that it is run from a shell with a live HTCondor installation.  This means that the HTCondor binaries are in the PATH and that the environment variable CONDOR_CONFIG points to an HTCondor configuration file.  That configuration file should include lines like the ones below, since _condor_annex_ assumes that pool password security is used (so that it knows what security token(s) to propagate).  The easiest way to accomplish this may be to create a personal condor; this also has the virtue of isolating your real pool from _condor_annex_ while you test it.  See
+
+https://htcondor-wiki.cs.wisc.edu/index.cgi/wiki?p=CreatingPersonalHtcondor
+
+for more information about installing a personal condor.
 
 {verbatim}
 SEC_CLIENT_AUTHENTICATION_METHODS = FS, PASSWORD
@@ -66,11 +70,7 @@
 ALLOW_WRITE = condor_pool@*/* $(FULL_HOSTNAME) $(IP_ADDRESS)
 {endverbatim}
 
-The manual has information on how to generate 'password_file'.  See
-
-https://htcondor-wiki.cs.wisc.edu/index.cgi/wiki?p=CreatingPersonalHtcondor
-
-for more information about installing a personal condor.  See also
+The manual has information on how to generate 'password_file'.  See also
 
 https://htcondor-wiki.cs.wisc.edu/index.cgi/wiki?p=HowToEnablePoolPassword