Fix for being dyslexic

Author: neil-sproston

modules/README.md

@@ -24,7 +24,7 @@ However we are actively using this system for the following asset types:
 
 #### Backup
 1. Each individual resource has its own CMK (Customer Managed encryption Key) which encrypts the resources data while at rest.
-2. On a regular basis a snapshot is taken off that resource and placed in the the Local AWS Vault as a recovery point (a.k.a. a backup) which encrypts it data with its own CMK.
+2. On a regular basis a snapshot is taken off that resource and placed in the Local AWS Vault as a recovery point (a.k.a. a backup) which encrypts it data with its own CMK.
 3. Once a local recovery point is in place in the local AWS Vault an AWS Backup "Copy Job" is automatically kicked off to make a copy of the recovery point into the Locked Remote Vault in the "Backup" AWS account.
 4. When the recovery point is placed in the Locked AWS Vault it re-encrypts the recovery point with its own CMK. At this time a lifecycle policy is assigned to the recovery point in the Locked Remote AWS Vault
 4. The recovery point can not be removed by ANYONE (including AWS support and the root user) until such time as the lifecycle expires the recovery point. See: https://docs.aws.amazon.com/aws-backup/latest/devguide/vault-lock.html

modules/backup/README.md

@@ -6,7 +6,7 @@ This is a simple module to create a AWS Backup vault, KMS keys, Plans and automa
 
 The vault module should be ran first in the remote AWS account.
 
-**WARNING** Once a snaphshot has been placed intothe remote locked vault it can not be removed until the
+**WARNING** Once a snaphshot has been placed into the remote locked vault it can not be removed until the
  lifecycle duration has been exceeded.
 
 ## Module parameters
@@ -19,14 +19,14 @@ The vault module should be ran first in the remote AWS account.
 | local_lifecycle  | Lifecycle for local copies, in days                      | number | -                   |
 | remote_lifecycle | Lifecycle for remote copies, in days                     | number | -                   |
 | backup_schedule  | The schedule to run backups, in AWS CRON format          | string | cron(15 11 ? * * *) |
-| use_env          | Wether to backup by environmrnt ot ALL assets in account | bool   | false               |
+| use_env          | Wether to backup by environmrnt or ALL assets in account | bool   | false               |
 | environment      | The environment name to select assets from               | string | -                   |
 
 
 ## Sample usage
 
 This snippet creates a backup vault and plan for RSS prod. The AWS account number "123456789012" and ARN
- is the locked vault created by the vault module in a seperate AWS account.
+ is the locked vault created by the vault module in a separate AWS account.
 
 Local copies of the snapshots are held for 7 days and remote "tamper-proof" copies for 90 days. The backup
  runs at 11:15 every day and backs up all assets in the prod environment (as defined by the Environment tag)