docs

assets/custom-types/remote-route53/README.md

@@ -21,7 +21,7 @@ These steps need to be performed for each domain that you want to manage from ot
 
 1. You will need access to change IAM policies and roles in the Route53 account that is managing the domain ("Hosted Zone" in AWS terminology).  You will also want to look up the hosted zone ID for the domain.
 2. Authenticate to the **Route 53 account.**
-3. From the `assets/custom-types/remote-route53` directory, run `./create-zone-admin.sh <zone-id-to-manage>`. If you've already setup another domain in this account, it will add this domain to the role.
+3. From the `assets/custom-types/remote-route53` directory, run `./create-zone-admin.sh <zone-id-to-manage>`. The zone ID is a alphanumeric code, not the actual domain name.  If you've already setup another domain in this account, it will add this domain to the role.
 4. The ARN of the role will be used as the "DestinationRole" parameter to the Cloud Formation resource, regardless of what account you are using to run the template.
 5. If you are adding an additional domain but have already setup all the accounts and regions per the instructions below, you do not need to repeat these steps.  They will pick up the new domain on the existing role.
 
@@ -31,15 +31,15 @@ These steps need to be performed for each domain that you want to manage from ot
 These steps need to be performed for each account where you want to run CloudFormation templates that use this function (the "CF Account").
 
 1. You will need access to change IAM policies and roles in both the Route53 account and the "CF Account".  You will also need permissions to create Lambda functions and SNS topics in the CF account.
-2. Authenticate to the **CF account.**  Choose a region that has Lambda support.  us-east-1 is recommended, since that is where the AWS Route 53 endpoints live, but you can use any supported region.
+2. Authenticate to the **CF account.**  Choose a region that has Lambda support.  `us-east-1` is recommended, since that is where the AWS Route 53 endpoints live, but you can use any supported region.
 3. Run `./deploy.sh` to create the Lambda function and the appropriate execution role.
 4. Look at the output from the script above and note the command it asks you to run (`./add-zone-admin-trust <role-name>`).
 5. Authenticate to the **Route 53 account.**
 6. Run the command from step 4.  This will grant the function permissions to assume the Route 53 role created earlier.
 
 ## Per AWS region/account combination setup:
 
-These steps need to be performed for **each** region in **each** account where you want to run CloudFormation templates that use this function (the "CF Account").  This does not to be run for the region where you uploaded the Lambda function above, as it created an SNS topic for that region. For example, if you uploaded the Lambda function to us-east-1, you would not need to run this for us-east-1.  But if you will create  stacks in us-west-1 under this account, you would need to create an SNS topic in us-west-1.  
+These steps need to be performed for **each** region in **each** account where you want to run CloudFormation templates that use this function (the "CF Account").  This does not to be run for the region where you uploaded the Lambda function above, as it created an SNS topic for that region. For example, if you uploaded the Lambda function to `us-east-1`, you would not need to run this for `us-east-1`.  But if you will create  stacks in `us-west-1` under this account, you would need to create an SNS topic in `us-west-1`.  
 
 1. You will need access to change Lambda function permissions and create SNS topics in the CF account.
 2. Authenticate to the **CF account.**