fix docs

cname/README.md

@@ -16,9 +16,9 @@ You will need to either fix the domain name (zone) or request the VPC have acces
 all zones where DNS entries are permitted are already associated with the appropriate VPCs.  Under normal conditions,
 you will want to use the `var.vpc_domain_name` (from the shared parent VPC), or from a `data` resource (see [example](#using-dhcp-options-data-resource)).
 
-It uses a default TTL of 900.
+The record(s) created use a default TTL of 900.  You may change this with the `ttl` option.
 
-It also creates what we call a heritage record. This is an indication of _what_ thing created the record, and when.  It is added by
+This also creates what we call a heritage record. This is an indication of _what_ thing created the record, and when.  It is added by
 the dynamic route53 Lambdas for EC2 instances, and within this module, it uses its own details.
 
 The record looks like:

cname/main.tf

@@ -17,9 +17,9 @@
 * all zones where DNS entries are permitted are already associated with the appropriate VPCs.  Under normal conditions,
 * you will want to use the `var.vpc_domain_name` (from the shared parent VPC), or from a `data` resource (see [example](#using-dhcp-options-data-resource)).
 * 
-* It uses a default TTL of 900.
+* The record(s) created use a default TTL of 900.  You may change this with the `ttl` option.
 * 
-* It also creates what we call a heritage record. This is an indication of _what_ thing created the record, and when.  It is added by
+* This also creates what we call a heritage record. This is an indication of _what_ thing created the record, and when.  It is added by
 * the dynamic route53 Lambdas for EC2 instances, and within this module, it uses its own details.
 * 
 * The record looks like: