Minor fix to README: numbered bullets.

README.md

@@ -59,22 +59,22 @@ Managing your own EC2 instance "manually" will use certificates issued by [Let's
   - Choose an instance of type _Ubuntu Server_ (e.g.: `ami-a8d2d7ce`).
   - Set its `clientid` tag appropriately.
   - Pick a preconfigured [Security Group](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) that opens HTTP (:80/tcp), HTTPS (:443/tcp) and SSH (:22/tcp).
-- Create the DNS record for `<client id>.orca-solution.com` pointing to the right instance (use an [Elastic IP](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html)).
-- Set the [expected environment variables](#environment-variables):
+2. Create the DNS record for `<client id>.orca-solution.com` pointing to the right instance (use an [Elastic IP](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html)).
+3. Set the [expected environment variables](#environment-variables):
   - Edit the `/ec2-ubuntu/orca.conf.tmpl`
   - Upload it as `<client id>.conf` in the `orca-clients` S3 bucket (`arn:aws:s3:::orca-clients`).
-- Upload the setup code to the EC2 instance **or use the alternative** and **skip to step 6**
+4. Upload the setup code to the EC2 instance **or use the alternative** and **skip to step 6**
 ```shell-script
 tar -zcvf setup.tar.gz *.{conf,sh}
 scp -i /path/to/pem setup.tar.gz ubuntu@<ip>:/home/ubuntu
 ```
-- Connect onto the instance via SSH for the last step **or use the alternative** and **skip to step 6**
+5. Connect onto the instance via SSH for the last step **or use the alternative** and **skip to step 6**
 > **IMPORTANT:** Ensure the DNS records have properly propagated before continuing.
 ```shell-script
 tar -zxvf setup.tar.gz
 ./setup.sh
 ```
-- **Alternatively** (and _preferably_), if and only if you have skipped steps 4 and 5, download and run the deployment script on the fly:
+6. **Alternatively** (and _preferably_), if and only if you have skipped steps 4 and 5, download and run the deployment script on the fly:
 > **IMPORTANT:** Ensure the DNS records have properly propagated before continuing.
 ```shell-script
 curl -s https://raw.githubusercontent.com/ccjmne/orca-deploy/master/ec2-ubuntu/utils/deploy.sh | bash

ec2-ubuntu/README.md

@@ -13,22 +13,22 @@ Managing your own EC2 instance "manually" will use certificates issued by [Let's
   - Choose an instance of type _Ubuntu Server_ (e.g.: `ami-a8d2d7ce`).
   - Set its `clientid` tag appropriately.
   - Pick a preconfigured [Security Group](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) that opens HTTP (:80/tcp), HTTPS (:443/tcp) and SSH (:22/tcp).
-- Create the DNS record for `<client id>.orca-solution.com` pointing to the right instance (use an [Elastic IP](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html)).
-- Set the [expected environment variables](#environment-variables):
+2. Create the DNS record for `<client id>.orca-solution.com` pointing to the right instance (use an [Elastic IP](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html)).
+3. Set the [expected environment variables](#environment-variables):
   - Edit the `/ec2-ubuntu/orca.conf.tmpl`
   - Upload it as `<client id>.conf` in the `orca-clients` S3 bucket (`arn:aws:s3:::orca-clients`).
-- Upload the setup code to the EC2 instance **or use the alternative** and **skip to step 6**
+4. Upload the setup code to the EC2 instance **or use the alternative** and **skip to step 6**
 ```shell-script
 tar -zcvf setup.tar.gz *.{conf,sh}
 scp -i /path/to/pem setup.tar.gz ubuntu@<ip>:/home/ubuntu
 ```
-- Connect onto the instance via SSH for the last step **or use the alternative** and **skip to step 6**
+5. Connect onto the instance via SSH for the last step **or use the alternative** and **skip to step 6**
 > **IMPORTANT:** Ensure the DNS records have properly propagated before continuing.
 ```shell-script
 tar -zxvf setup.tar.gz
 ./setup.sh
 ```
-- **Alternatively** (and _preferably_), if and only if you have skipped steps 4 and 5, download and run the deployment script on the fly:
+6. **Alternatively** (and _preferably_), if and only if you have skipped steps 4 and 5, download and run the deployment script on the fly:
 > **IMPORTANT:** Ensure the DNS records have properly propagated before continuing.
 ```shell-script
 curl -s https://raw.githubusercontent.com/ccjmne/orca-deploy/master/ec2-ubuntu/utils/deploy.sh | bash