Fix linking errors from #171

Author: miketaylr

index.html

@@ -338,14 +338,14 @@ <h2>NEL policies</h2>
 
       <p>
       A <a>NEL policy</a> is <dfn>stale</dfn> if the <a>duration from</a> its
-      <a>creation</a> to the <a>current wall time</a> is greater than 172800
-      seconds (48 hours).
+      <a>creation</a> to the [=environment settings object/current wall time=]
+      is greater than 172800 seconds (48 hours).
       </p>
 
       <p>
       A <a>NEL policy</a> is <dfn>expired</dfn> if the <a>duration from</a> its
-      <a>creation</a> to the <a>current wall time</a> is greater than its
-      <a>ttl</a> (in seconds).
+      <a>creation</a> to the [=environment settings object/current wall time=]
+      is greater than its <a>ttl</a> (in seconds).
       </p>
     </section>
 
@@ -695,7 +695,7 @@ <h2>Process policy headers</h2>
             <dd>the value of <var>item</var>'s <a>max_age</a> member</dd>
 
             <dt><a>creation</a></dt>
-            <dd>the <a>current wall time</a></dd>
+            <dd>the [=environment settings object/current wall time=]</dd>
 
             <dt><a>successful sampling rate</a></dt>
             <dd>
@@ -1902,7 +1902,7 @@ <h2>Privacy Considerations</h2>
       NEL report only contains information available from DNS itself.  This
       prevents <a>servers</a> from abusing NEL to collect more information about
       their users than they already have access to. Note that NEL reports will
-      include a web site's public IP address in the <a>report body</a>'s
+      include a web site's public IP address in the [=report/body|report body=]'s
       <code>server_ip</code> field, which may not always be known to the service
       which generates the NEL header, for example if it is behind a load
       balancer or other transparent MitM proxy.