Update README.md

jicowan · jicowan · commit 7a1ee9d133dd · 2016-03-26T13:53:01.000-04:00
diff --git a/README.md b/README.md
@@ -178,9 +178,9 @@ In this step, you create a new DHCP options set and set the domain to be that of
 
 In this step, you launch an EC2 instance and verify that the function executed successfully.
 
-As mentioned previously, the Lambda function looks for the ZONE or CNAME tags associated with the EC2 instance.  If you specify these tags when you launch the instance, you have to include a _trailing dot_.  In this example, the ZONE tag would be set to “ddnslambda.com.” and the CNAME tag could be set to “test.ddnslambda.com.”.
+As mentioned previously, the Lambda function looks for the ZONE or CNAME tags associated with the EC2 instance.  If you specify these tags when you launch the instance, you have to include a _trailing dot_.  In this example, the ZONE tag would be set to “ddnslambda.com**.**” and the CNAME tag could be set to “test.ddnslambda.com**.**”.
 
-Because you updated the DHCP options set in this example, the Lambda function uses the specified zone when it creates the Route 53 DNS resource records.  You can use the ZONE tag to override this behavior if you wanted the function to update a different hosted zone, for example.
+Because you updated the DHCP options set in this example, the Lambda function uses the specified zone when it creates the Route 53 DNS resource records.  You can use the ZONE tag to override this behavior if you wanted the function to update a different hosted zone.
 
 In this example, you launch an EC2 instance into the private subnet of the VPC.  Because you updated the domain value of the DHCP options set to be that of the private hosted zone, the Lambda function creates the DNS resource records in the Route 53 zone file. 
 
@@ -190,7 +190,7 @@ _Launching the EC2 instance_
 
 2) In **Step 3: Configure Instance Details**, for **Network**, select the VPC.  For **Subnet**, select the private subnet.  Choose **Review and Launch**.
 
-3) (Optional)  If you would like to update a different private hosted zone than the one you associated with the VPC, specify the ZONE tag in this step.  You can also specify the CNAME tag if you would like the function to create a CNAME resource record in the associated zone.
+3) (Optional) If you would like to update a different private hosted zone than the one you associated with the VPC, specify the ZONE tag in this step.  You can also specify the CNAME tag if you would like the function to create a CNAME resource record in the associated zone.
 
 Choose **Edit tags** in the **Step 7: Review Instance Launch**.
 
