DOCS: Mostly styling and links (#2178)

Co-authored-by: Tom Limoncelli <tal@whatexit.org>

documentation/functions/global/DOMAIN_ELSEWHERE.md

@@ -40,6 +40,6 @@ D("example.com", REG_NAMEDOTCOM,
 {% endcode %}
 
 {% hint style="info" %}
-**NOTE**: The `NO_PURGE` is used out of abundance of caution but since no
+**NOTE**: The [`NO_PURGE`](../domain/NO_PURGE.md) is used out of abundance of caution but since no
 `DnsProvider()` statements exist, no updates would be performed.
 {% endhint %}

documentation/functions/global/DOMAIN_ELSEWHERE_AUTO.md

@@ -44,5 +44,5 @@ D("example.com", REG_NAMEDOTCOM,
 {% endcode %}
 
 {% hint style="info" %}
-**NOTE**: The `NO_PURGE` is used to prevent DNSControl from changing the records.
+**NOTE**: The [`NO_PURGE`](../domain/NO_PURGE.md) is used to prevent DNSControl from changing the records.
 {% endhint %}

documentation/functions/global/D_EXTEND.md

@@ -9,13 +9,13 @@ parameter_types:
 ---
 
 `D_EXTEND` adds records (and metadata) to a domain previously defined
-by `D()`. It can also be used to add subdomain records (and metadata)
+by [`D()`](D.md). It can also be used to add subdomain records (and metadata)
 to a previously defined domain.
 
 The first argument is a domain name. If it exactly matches a
-previously defined domain, `D_EXTEND()` behaves the same as `D()`,
+previously defined domain, `D_EXTEND()` behaves the same as [`D()`](D.md),
 simply adding records as if they had been specified in the original
-`D()`.
+[`D()`](D.md).
 
 If the domain name does not match an existing domain, but could be a
 (non-delegated) subdomain of an existing domain, the new records (and
@@ -24,12 +24,12 @@ names (labels), and targets (as appropriate). See the examples below.
 
 Matching the domain name to previously-defined domains is done using a
 `longest match` algorithm.  If `domain.tld` and `sub.domain.tld` are
-defined as separate domains via separate `D()` statements, then
+defined as separate domains via separate [`D()`](D.md) statements, then
 `D_EXTEND('sub.sub.domain.tld', ...)` would match `sub.domain.tld`,
 not `domain.tld`.
 
 Some operators only act on an apex domain (e.g.
-`CF_REDIRECT` and `CF_TEMP_REDIRECT`). Using them
+[`CF_REDIRECT`](../domain/CF_REDIRECT.md) and [`CF_TEMP_REDIRECT`](../domain/CF_TEMP_REDIRECT.md)). Using them
 in a `D_EXTEND` subdomain may not be what you expect.
 
 {% code title="dnsconfig.js" %}
@@ -83,7 +83,7 @@ ProTips: `D_EXTEND()` permits you to create very complex and
 sophisticated configurations, but you shouldn't. Be nice to the next
 person that edits the file, who may not be as expert as yourself.
 Enhance readability by putting any `D_EXTEND()` statements immediately
-after the original `D()`, like in above example.  Avoid the temptation
+after the original [`D()`](D.md), like in above example.  Avoid the temptation
 to obscure the addition of records to existing domains with randomly
 placed `D_EXTEND()` statements. Don't build up a domain using loops of
 `D_EXTEND()` statements. You'll be glad you didn't.

documentation/functions/global/REV.md

@@ -10,7 +10,7 @@ ts_return: string
 `REV` returns the reverse lookup domain for an IP network. For
 example `REV('1.2.3.0/24')` returns `3.2.1.in-addr.arpa.` and
 `REV('2001:db8:302::/48)` returns `2.0.3.0.8.b.d.0.1.0.0.2.ip6.arpa.`.
-This is used in `D()` functions to create reverse DNS lookup zones.
+This is used in [`D()`](D.md) functions to create reverse DNS lookup zones.
 
 This is a convenience function. You could specify `D('3.2.1.in-addr.arpa',
 ...` if you like to do things manually but why would you risk making
@@ -51,6 +51,6 @@ D(REV('2001:db8:302::/48'), REGISTRAR, DnsProvider(BIND),
 ```
 {% endcode %}
 
-In the future we plan on adding a flag to `A()` which will insert
-the correct PTR() record if the appropriate `D(REV()` domain (i.e. `.arpa` domain) has been
+In the future we plan on adding a flag to [`A()`](../domain/A.md)which will insert
+the correct PTR() record in the appropriate `D(REV())` domain (i.e. `.arpa` domain) has been
 defined.