Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

===================================================================
RCS file: /ftp/cvs/cvsroot/htdocs/docs/current/index.html,v
rcsdiff: /ftp/cvs/cvsroot/htdocs/docs/current/index.html,v: warning: Unknown phrases like `commitid ...;' are present.
retrieving revision 1.60
retrieving revision 1.61
diff -u -p -r1.60 -r1.61
--- htdocs/docs/current/index.html	2018/06/23 21:24:34	1.60
+++ htdocs/docs/current/index.html	2018/06/24 16:13:19	1.61
@@ -145,8 +145,7 @@
 <hr>
 <h3 class="title">Frequently asked questions</h3>
 <h4 class="title">
-<a name="why-track"></a>Why track NetBSD-current? (<a href="#faq">top</a>)
-  </h4>
+<a name="why-track"></a>Why track NetBSD-current?</h4>
 <p>
 The developers of NetBSD have made the current development sources
 available to the public for several reasons.  Overall, providing
@@ -173,8 +172,7 @@ eliminated.
 </p>
 
 <h4 class="title">
-<a name="what-to-do"></a>Things you need to remember (<a href="#faq">top</a>)
-  </h4>
+<a name="what-to-do"></a>Things you need to remember</h4>
 
 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
 <li class="listitem">
@@ -213,8 +211,7 @@ system calls added, but do it anyway; it
 </p>
 
 <h4 class="title">
-<a name="updating-from-snapshot"></a>Updating an existing system from a current snapshot (<a href="#faq">top</a>)
-  </h4>
+<a name="updating-from-snapshot"></a>Updating an existing system from a current snapshot</h4>
 <p>
 <span class="emphasis"><em>Please remember to check <a class="ulink" href="http://ftp.NetBSD.org/pub/NetBSD/NetBSD-current/src/UPDATING" target="_top">src/UPDATING</a>
 for quirks around certain specific changes.</em></span></p>
@@ -415,24 +412,21 @@ and ready to build your own current sour
 </p>
 
 <h4 class="title">
-<a name="downloading"></a>Downloading current source (<a href="#faq">top</a>)
-  </h4>
+<a name="downloading"></a>Downloading current source</h4>
 <p>
 See the <a class="ulink" href="../guide/en/chap-fetch.html" target="_top">Obtaining the sources</a>
 section in the <a class="ulink" href="../guide/en/" target="_top">NetBSD Guide</a>.
 </p>
 
 <h4 class="title">
-<a name="building"></a>Building a release from source (<a href="#faq">top</a>)
-  </h4>
+<a name="building"></a>Building a release from source</h4>
 <p>
 See the <a class="ulink" href="../guide/en/chap-build.html" target="_top">Crosscompiling NetBSD</a>
 section in the <a class="ulink" href="../guide/en/" target="_top">NetBSD Guide</a>.
 </p>
 
 <h4 class="title">
-<a name="updating-from-source"></a>Updating an existing system from source (<a href="#faq">top</a>)
-  </h4>
+<a name="updating-from-source"></a>Updating an existing system from source</h4>
 <p>
 See the <a class="ulink" href="../guide/en/chap-updating.html" target="_top">Updating an existing system
 from sources</a>
@@ -440,8 +434,7 @@ section in the <a class="ulink" href="..
 </p>
 
 <h4 class="title">
-<a name="etcupdate"></a>Updating the configuration and startup files (<a href="#faq">top</a>)
-  </h4>
+<a name="etcupdate"></a>Updating the configuration and startup files</h4>
 <p>
 See the <a class="ulink" href="../guide/en/chap-updating.html#updating-etcupdate" target="_top">More
 details about the updating of configuration and startup files</a>
@@ -449,8 +442,7 @@ section in the <a class="ulink" href="..
 </p>
 
 <h4 class="title">
-<a name="error"></a>What if I get an error? (<a href="#faq">top</a>)
-  </h4>
+<a name="error"></a>What if I get an error?</h4>
 <p>
 
 If you try to build -current, either from a snapshot or an earlier
@@ -479,8 +471,7 @@ If you try to build -current, either fro
 </p>
 
 <h4 class="title">
-<a name="using-anoncvs"></a>Tracking NetBSD-current with anoncvs (<a href="#faq">top</a>)
-  </h4>
+<a name="using-anoncvs"></a>Tracking NetBSD-current with anoncvs</h4>
 <p>
 See the <a class="ulink" href="../guide/en/chap-fetch.html#chap-fetch-cvs" target="_top">Fetching
 by CVS</a>
@@ -548,8 +539,7 @@ directory, and they will be automaticall
 </div>
 
 <h4 class="title">
-<a name="import-merge"></a>Importing and merging sources. (<a href="#faq">top</a>)
-  </h4>
+<a name="import-merge"></a>Importing and merging sources.</h4>
     <p>Sources are imported as follows:</p>
 <pre class="programlisting">$ cvs -d /misc/cvsrep import -I ! -I CVS netbsd netbsd current-<span class="emphasis"><em>date</em></span></pre>
 
@@ -603,8 +593,7 @@ $ cvs -d /misc/cvsrep checkout netbsd
 </pre>
     
 <h4 class="title">
-<a name="tagging"></a>Tagging a successful build (<a href="#faq">top</a>)
-  </h4>
+<a name="tagging"></a>Tagging a successful build</h4>
     <p> If the <a class="ulink" href="#building" target="_top">build</a> completes successfully,
       and produces a working set of binaries,
       it can be useful to tag the working sources.
@@ -683,8 +672,7 @@ close TAG;
 </div>
 
 <h4 class="title">
-<a name="getrepos"></a>Getting the whole repository (<a href="#faq">top</a>)
-  </h4>
+<a name="getrepos"></a>Getting the whole repository</h4>
 <p>
 
 All the procedures described above allow you keeping your own