documentation updates

as-apply-alarms/README.md

@@ -1,5 +1,5 @@
 # Introduction:
-as-apply-alarms was created to easily apply alarms to anywhere from one to a number of Amazon Auto Scaling Groups. The tool applies alarms for CPU Utilization. as-apply-alarms will run "out of the box" however the intent is rather to provide a template (and the logic) for managing multiple Auto Scaling Group's alarms.
+as-apply-alarms was created to easily apply alarms to one or more Auto Scaling Groups. The tool applies alarms for CPU Utilization. as-apply-alarms will run "out of the box" however the intent is rather to provide a template (and the logic) for managing multiple Auto Scaling Group's alarms.
 # Directions For Use:
 ## Example of Use:
     as-apply-alarms -d auto-scaling-group-name -t name-of-sns-topic

as-update-launch-config/README.md

@@ -1,5 +1,5 @@
 # Introduction:
-as-update-launch-config was created to easily modify the EC2 Instance Type of an Auto Scaling Group's Launch Configuration File. The most typical use case is to change the size of instance used by an Auto Scaling Group, although as-update-launch-config can also be used to update the storage type, user-data or AMI used by a Launch Config (and hence, an Auto Scaling Group).
+as-update-launch-config was created to modify an Auto Scaling Group's Launch Configuration. The most typical use case is to change the size of instance used by an Auto Scaling Group, although as-update-launch-config can also be used to update the storage type, user-data or AMI used by a Launch Config (and hence, an Auto Scaling Group).
 # Directions For Use:
 ## Example of Use:
     as-update-launch-config -a my-scaling-group -i m1.small -u /home/cjohnson/web-server-user-data.txt

ec2-automate-backup/README.md

@@ -1,5 +1,5 @@
 # Introduction:
-ec2-automate-backup was created to provide easy backup/snapshot functionality for EC2 EBS volumes. Common uses would include the following:
+ec2-automate-backup was created to provide easy backup/snapshot functionality for multiple EC2 EBS volumes. Common uses would include the following:
 * run ec2-automate-backup with a list of volumes for which a snapshot is desired (example: `ec2-automate-backup.sh -v "vol-6d6a0527 vol-636a0112"`)
 * run ec2-automate-backup with a list of volumes for which a snapshot is desired and allow the created snapshots to be deleted after 31 days (example: `ec2-automate-backup.sh -v "vol-6d6a0527 vol-636a0112" -k 31`)
 * run ec2-automate-backup using cron to produce a daily backup (example: `"0 0 * * 0 ec2-user /home/ec2-user/ec2-automate-backup.sh -v "vol-6d6a0527 vol-636a0112" > /home/ec2-user/ec2-automate-backup_`date +"%Y%m%d"`.log"`)

iam-keyfind/README.md

@@ -1,5 +1,5 @@
 # Introduction:
-iam-keyfind was created to either list all Access Keys used by IAM users or by finding a particular IAM key.
+iam-keyfind was created to either list all Access Keys belonging to IAM accounts or find a particular IAM key.
 # Directions For Use:
 ## Example of Use, List Mode:
     iam-keyfind.sh

rds-apply-alarms/README.md

@@ -1,5 +1,5 @@
 # Introduction:
-rds-apply-alarms was created to easily apply alarms to anywhere from one to a number of Amazon RDS instances. The tool applies alarms for CPU Utilization, Feeable Memory, Swap Usage and Free Storage Space. rds-apply-alarms will run "out of the box", however the intent is rather to provide a template (and the logic) for managing multiple RDS instance's alarms.
+rds-apply-alarms was created to easily apply alarms to one or more Amazon RDS instances. The tool applies alarms for CPU Utilization, Feeable Memory, Swap Usage and Free Storage Space. rds-apply-alarms will run "out of the box", however the intent is rather to provide a template (and the logic) for managing multiple RDS instance's alarms.
 # Directions For Use:
 ## Example of Use:
     rds-apply-alarms -d rds-instance-name -t name-of-sns-topic

route53-migrate-zone/README.md

@@ -1,5 +1,5 @@
 # Introduction:
-route53-migrate-zone was created to provide an easy method of migrating Route53 zones to new zones or to new AWS accounts. There are three use cases, detailed below:
+route53-migrate-zone was created to provide a method of migrating a Route53 zone to a new zone or to a new AWS account. There are three use cases, detailed below:
 * Migrate one domain (source.com) to a new domain (destintion.com)
 * Migrate one domain (domain.com) to the same domain in a new account (domain.com)
 * Migrate one domain (source.com) to a new domain in a new account (destination.com)