DOCS: Fix many spelling errors (#471)

docs/_functions/domain/A.md

@@ -10,7 +10,7 @@ A adds an A record To a domain. The name should be the relative label for the re
 
 The address should be an ip address, either a string, or a numeric value obtained via [IP](#IP).
 
-Modifers can be any number of [record modifiers](#record-modifiers) or json objects, which will be merged into the record's metadata.
+Modifiers can be any number of [record modifiers](#record-modifiers) or json objects, which will be merged into the record's metadata.
 
 {% include startExample.html %}
 {% highlight js %}

docs/_functions/domain/AAAA.md

@@ -8,9 +8,9 @@ parameters:
 
 AAAA adds an AAAA record To a domain. The name should be the relative label for the record. Use `@` for the domain apex.
 
-The address should be an ipv6 address as a string.
+The address should be an IPv6 address as a string.
 
-Modifers can be any number of [record modifiers](#record-modifiers) or json objects, which will be merged into the record's metadata.
+Modifiers can be any number of [record modifiers](#record-modifiers) or json objects, which will be merged into the record's metadata.
 
 {% include startExample.html %}
 {% highlight js %}

docs/_functions/domain/ALIAS.md

@@ -6,7 +6,7 @@ parameters:
   - modifiers...
 ---
 
-ALIAS is a virtual record type that points a record at another record. It is analagous to a CNAME, but is usually resolved at request-time and served as an A record. Unlike CNAMEs, ALIAS records can be used at the zone apex (`@`)
+ALIAS is a virtual record type that points a record at another record. It is analogous to a CNAME, but is usually resolved at request-time and served as an A record. Unlike CNAMEs, ALIAS records can be used at the zone apex (`@`)
 
 Different providers handle ALIAS records differently, and many do not support it at all. Attempting to use ALIAS records with a DNS provider type that does not support them will result in an error.
 

docs/_functions/domain/CAA.md

@@ -11,7 +11,7 @@ CAA adds a CAA record to a domain. The name should be the relative label for the
 
 Tag can be one of "issue", "issuewild" or "iodef".
 
-Value is a string. The format of the contents is different depending on the tag.  DNSControl will handle any escaping or quoting required, similer to TXT records.  For example use `CAA("@", "issue", "letsencrypt.org")` rather than `CAA("@", "issue", "\"letsencrypt.org\"")`.
+Value is a string. The format of the contents is different depending on the tag.  DNSControl will handle any escaping or quoting required, similar to TXT records.  For example use `CAA("@", "issue", "letsencrypt.org")` rather than `CAA("@", "issue", "\"letsencrypt.org\"")`.
 
 Flags are controlled by modifier.:
 

docs/_functions/domain/DnsProvider.md

@@ -5,7 +5,7 @@ parameters:
   - nsCount
 ---
 
-DnsProvider indicates that the specifid provider should be used to manage
+DnsProvider indicates that the specified provider should be used to manage
 records for this domain. The name must match the name used with [NewDnsProvider](#NewDnsProvider).
 
 The nsCount parameter determines how the nameservers will be managed from this provider.

docs/_functions/domain/IGNORE.md

@@ -5,7 +5,7 @@ name: IGNORE
 IGNORE can be used to ignore some records presents in zone.
 All records (independently of their type) of that name will be completely ignored.
 
-IGNORE is like NO_PURGE except it acts only on some specific records intead of the whole zone.
+IGNORE is like NO_PURGE except it acts only on some specific records instead of the whole zone.
 
 IGNORE is generally used in very specific situations:
 

docs/_functions/domain/PTR.md

@@ -81,5 +81,5 @@ D(REV('2001:db8:302::/48'), REGISTRAR, DnsProvider(BIND),
 {% include endExample.html %}
 
 In the future we plan on adding a flag to `A()` which will insert
-the correct PTR() record if the approprate `.arpa` domain has been
+the correct PTR() record if the appropriate `.arpa` domain has been
 defined.

docs/_functions/domain/R53_ALIAS.md

@@ -6,7 +6,7 @@ parameters:
   - ZONE_ID modifier
 ---
 
-R53_ALIAS is a Route53 specific virtual record type that points a record at either another record or an AWS entity (like a Cloudfront distribution, an ELB, etc...). It is analagous to a CNAME, but is usually resolved at request-time and served as an A record. Unlike CNAMEs, ALIAS records can be used at the zone apex (`@`)
+R53_ALIAS is a Route53 specific virtual record type that points a record at either another record or an AWS entity (like a Cloudfront distribution, an ELB, etc...). It is analogous to a CNAME, but is usually resolved at request-time and served as an A record. Unlike CNAMEs, ALIAS records can be used at the zone apex (`@`)
 
 Unlike the regular ALIAS directive, R53_ALIAS is only supported on Route53. Attempting to use R53_ALIAS on another provider than Route53 will result in an error.
 
@@ -16,7 +16,7 @@ Target should be a string representing the target. If it is a single label we wi
 
 The Target can be any of:
 
-* _CloudFront distribution_: in this case specify the domain name that CloudFront assigned whenyou created your distribution (note that your CloudFront distribution must include an alternante domain name that matches the record you're adding)
+* _CloudFront distribution_: in this case specify the domain name that CloudFront assigned when you created your distribution (note that your CloudFront distribution must include an alternate domain name that matches the record you're adding)
 * _Elastic Beanstalk environment_: specify the CNAME attribute for the environment. The environment must have a regionalized domain name. To get the CNAME, you can use either the [AWS Console](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customdomains.html), [AWS Elastic Beanstalk API](http://docs.aws.amazon.com/elasticbeanstalk/latest/api/API_DescribeEnvironments.html), or the [AWS CLI](http://docs.aws.amazon.com/cli/latest/reference/elasticbeanstalk/describe-environments.html).
 * _ELB load balancer_: specify the DNS name that is associated with the load balancer. To get the DNS name you can use either the AWS Console (on the EC2 page, choose Load Balancers, select the right one, choose the description tab), [ELB API](http://docs.aws.amazon.com/elasticloadbalancing/latest/APIReference/API_DescribeLoadBalancers.html), the [AWS ELB CLI](http://docs.aws.amazon.com/cli/latest/reference/elb/describe-load-balancers.html), or the [AWS ELBv2 CLI](http://docs.aws.amazon.com/cli/latest/reference/elbv2/describe-load-balancers.html).
 * _S3 bucket_ (configured as website): specify the domain name of the Amazon S3 website endpoint in which you configured the bucket (for instance s3-website-us-east-2.amazonaws.com). For the available values refer to the [Amazon S3 Website Endpoints](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region).

docs/_functions/domain/TXT.md

@@ -20,7 +20,7 @@ Each string is a JavaScript string (quoted using single or double
 quotes).  The (somewhat complex) quoting rules of the DNS protocol
 will be done for you.
 
-Modifers can be any number of [record modifiers](#record-modifiers) or json objects, which will be merged into the record's metadata.
+Modifiers can be any number of [record modifiers](#record-modifiers) or json objects, which will be merged into the record's metadata.
 
 {% include startExample.html %}
 {% highlight js %}

docs/_functions/global/D.md

@@ -14,7 +14,7 @@ Modifier arguments are processed according to type as follows:
 
 - A function argument will be called with the domain object as it's only argument. Most of the [built-in modifier functions](#domain-modifiers) return such functions.
 - An object argument will be merged into the domain's metadata collection.
-- An array arument will have all of it's members evaluated recursively. This allows you to combine multiple common records or modifiers into a variable that can
+- An array argument will have all of it's members evaluated recursively. This allows you to combine multiple common records or modifiers into a variable that can
    be used like a macro in multiple domains.
 
 {% include startExample.html %}

docs/_functions/global/NewDnsProvider.md

@@ -8,7 +8,7 @@ return: string
 ---
 
 NewDnsProvider registers a new DNS Service Provider. The name can be any string value you would like to use.
-The type must match a valid dns provider type identifer (see [provider page.]({{site.github.url}}/provider-list))
+The type must match a valid dns provider type identifier (see [provider page.]({{site.github.url}}/provider-list))
 
 Metadata is an optional object, that will only be used by certain providers. See [individual provider docs]({{site.github.url}}/provider-list) for specific details.
 

docs/_functions/global/NewRegistrar.md

@@ -8,7 +8,7 @@ return: string
 ---
 
 NewRegistrar registers a registrar provider. The name can be any string value you would like to use.
-The type must match a valid registar provider type identifer (see [provider page.]({{site.github.url}}/provider-list))
+The type must match a valid registrar provider type identifier (see [provider page.]({{site.github.url}}/provider-list))
 
 Metadata is an optional object, that will only be used by certain providers. See [individual provider docs]({{site.github.url}}/provider-list) for specific details.
 

docs/_functions/global/REV.md

@@ -51,5 +51,5 @@ D(REV('2001:db8:302::/48'), REGISTRAR, DnsProvider(BIND),
 {% include endExample.html %}
 
 In the future we plan on adding a flag to `A()` which will insert
-the correct PTR() record if the approprate `D(REV()` domain (i.e. `.arpa` domain) has been
+the correct PTR() record if the appropriate `D(REV()` domain (i.e. `.arpa` domain) has been
 defined.