Index: faq.html
===================================================================
--- faq.html	(revision 15298)
+++ faq.html	(working copy)
@@ -557,8 +557,7 @@
 <![CDATA[-----------------------------------------------------------]]>
 
 <div class="h3" id="more-information" title="more-information">
-<h3>I have other questions.  Where can I get more<a
-name="more-information"> information?</a></h3>
+<h3>I have other questions.  Where can I get more information?</h3>
 
 <p>Please send your questions or concerns to the Subversion Users <a
 href="mailto:users@subversion.tigris.org">mailing list</a>.  Alternatively,
@@ -928,7 +927,7 @@
 of tables and bunch of logfiles (log.*).  Berkeley DB journals all
 changes made to the tables, so that the tables can be recovered to a
 consistent state in case of interruptions (<a
-href="#wedged-repos">more info</a>).</p>
+href="#bdb-recovery">more info</a>).</p>
 
 <p>The logfiles will grow forever, eating up disk space, unless you,
 (as the repository administrator) do something about it.  At any given
@@ -1950,11 +1949,10 @@
 
 <![CDATA[-----------------------------------------------------------]]>
 
-<div class="h3" id="permissions" title="permissions">
-<h3>
-    <a name="stuck-bdb-repos">My repository seems to get stuck all the
-time, giving me errors about needing recovery (DB_RUNRECOVERY).  What
-could be the cause?</a></h3>
+<div class="h3" id="stuck-bdb-repos" title="stuck-bdb-repos">
+<h3>My repository seems to get stuck all the
+time, giving me errors about needing recovery (DB_RUNRECOVERY). What
+could be the cause?</h3>
 
 <p>The BerkeleyDB database in your repository is sensitive to
 interruptions.  If a process accessing the database exits without
@@ -1970,7 +1968,7 @@
 
 <p>For most of these cases, you should run "svnadmin recover", which
 rewinds the repository back to a consistent state; see <a
-href="#wedged-repos">this question</a> for details.  Note that running
+href="#bdb-recovery">this question</a> for details.  Note that running
 out of disk space, combined with frequent checkouts or updates, can
 cause the repository to crash in a way where recovery is not possible
 (so keep backups).</p>
@@ -1989,10 +1987,10 @@
 
 <![CDATA[-----------------------------------------------------------]]>
 
-<div class="h3" id="wedged-repos" title="wedged-repos">
-<h3>
-    <a name="bdb-recovery">Every time I try to access my repository, the
-process just hangs. Is my repository corrupt?</a></h3>
+<div id="wedged-repos"></div>
+<div class="h3" id="bdb-recovery" title="bdb-recovery">
+<h3>Every time I try to access my repository, the
+process just hangs. Is my repository corrupt?</h3>
 
 <p>
 Your repository is not corrupt, nor is your data lost. If your process
@@ -2119,7 +2117,7 @@
 database locks (this does not happen with FSFS repositories).  It
 shouldn't happen in the course of normal operations, but if it does,
 the solution is to run database recovery as described <a
-href="#wedged-repos">here</a>.  If it happens often, you probably need
+href="#bdb-recovery">here</a>.  If it happens often, you probably need
 to raise the default lock parameters (<tt>set_lk_max_locks</tt>,
 <tt>set_lk_max_lockers</tt>, and <tt>set_lk_max_objects</tt>) in the
 db/DB_CONFIG file.  When changing DB_CONFIG in an existing repository,
@@ -2241,7 +2239,7 @@
 <h3>I'm getting errors finding or opening a repository,
     but I know my repository URL is correct.  What's wrong?</h3> 
 
-<p>See <a href="#wedged-repos">this faq.</a></p>
+<p>See <a href="#bdb-recovery">this faq.</a></p>
 
 </div>