From nobody Thu May 15 22:07:38 2025
Delivered-To: importer@patchew.org
Received-SPF: pass (zoho.com: domain of redhat.com designates 209.132.183.28
 as permitted sender) client-ip=209.132.183.28;
 envelope-from=libvir-list-bounces@redhat.com; helo=mx1.redhat.com;
Authentication-Results: mx.zohomail.com;
	spf=pass (zoho.com: domain of redhat.com designates 209.132.183.28 as
 permitted sender)  smtp.mailfrom=libvir-list-bounces@redhat.com
Return-Path: <libvir-list-bounces@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by
 mx.zohomail.com
	with SMTPS id 1501091513849590.736991909652;
 Wed, 26 Jul 2017 10:51:53 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com
 [10.5.11.14])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx1.redhat.com (Postfix) with ESMTPS id 8E7A08B137;
	Wed, 26 Jul 2017 17:51:50 +0000 (UTC)
Received: from colo-mx.corp.redhat.com
 (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 280995D724;
	Wed, 26 Jul 2017 17:51:50 +0000 (UTC)
Received: from lists01.pubmisc.prod.ext.phx2.redhat.com
 (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33])
	by colo-mx.corp.redhat.com (Postfix) with ESMTP id B2A9E4BB79;
	Wed, 26 Jul 2017 17:51:49 +0000 (UTC)
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com
	[10.5.11.16])
	by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP
	id v6QHpT10025503 for <libvir-list@listman.util.phx.redhat.com>;
	Wed, 26 Jul 2017 13:51:30 -0400
Received: by smtp.corp.redhat.com (Postfix)
	id EFC90692B8; Wed, 26 Jul 2017 17:51:29 +0000 (UTC)
Received: from t460.redhat.com (ovpn-116-106.ams2.redhat.com [10.36.116.106])
	by smtp.corp.redhat.com (Postfix) with ESMTP id A5F21692AF;
	Wed, 26 Jul 2017 17:51:24 +0000 (UTC)
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 8E7A08B137
Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com;
 dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com;
 spf=fail smtp.mailfrom=libvir-list-bounces@redhat.com
From: "Daniel P. Berrange" <berrange@redhat.com>
To: libvir-list@redhat.com
Date: Wed, 26 Jul 2017 18:51:04 +0100
Message-Id: <20170726175115.400-2-berrange@redhat.com>
In-Reply-To: <20170726175115.400-1-berrange@redhat.com>
References: <20170726175115.400-1-berrange@redhat.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16
X-loop: libvir-list@redhat.com
Subject: [libvirt] [PATCH 01/12] docs: switch to using 'id' attribute
	instead of 'name' for links
X-BeenThere: libvir-list@redhat.com
X-Mailman-Version: 2.1.12
Precedence: junk
List-Id: Development discussions about the libvirt library & tools
	<libvir-list.redhat.com>
List-Unsubscribe: <https://www.redhat.com/mailman/options/libvir-list>,
	<mailto:libvir-list-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/libvir-list>
List-Post: <mailto:libvir-list@redhat.com>
List-Help: <mailto:libvir-list-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/libvir-list>,
	<mailto:libvir-list-request@redhat.com?subject=subscribe>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Sender: libvir-list-bounces@redhat.com
Errors-To: libvir-list-bounces@redhat.com
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14
X-Greylist: Sender IP whitelisted,
 not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]);
 Wed, 26 Jul 2017 17:51:51 +0000 (UTC)
X-ZohoMail: RSF_0  Z_629925259 SPT_0
Content-Type: text/plain; charset="utf-8"

The 'name' attribute on <a...> elements is deprecated in favour
of the 'id' attribute which is allowed on any element. HTML5
drops 'name' support entirely.

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
---
 docs/acl.html.in                     |   6 +-
 docs/aclpolkit.html.in               |  32 +++---
 docs/api.html.in                     |   8 +-
 docs/api_extension.html.in           |  12 +--
 docs/apps.html.in                    |  30 +++---
 docs/architecture.html.in            |   6 +-
 docs/auditlog.html.in                |  38 +++----
 docs/auth.html.in                    |  14 +--
 docs/bugs.html.in                    |  10 +-
 docs/cgroups.html.in                 |  24 ++---
 docs/compiling.html.in               |   6 +-
 docs/contact.html.in                 |   6 +-
 docs/contribute.html.in              |  10 +-
 docs/csharp.html.in                  |  18 ++--
 docs/downloads.html.in               |  12 +--
 docs/drivers.html.in                 |   4 +-
 docs/drvbhyve.html.in                |  20 ++--
 docs/drvesx.html.in                  |  44 ++++----
 docs/drvhyperv.html.in               |  10 +-
 docs/drvlxc.html.in                  |  52 +++++-----
 docs/drvnodedev.html.in              |   8 +-
 docs/drvopenvz.html.in               |  12 +--
 docs/drvphyp.html.in                 |   6 +-
 docs/drvqemu.html.in                 |  32 +++---
 docs/drvuml.html.in                  |   2 +-
 docs/drvvbox.html.in                 |   4 +-
 docs/drvvirtuozzo.html.in            |   6 +-
 docs/drvvmware.html.in               |   4 +-
 docs/drvxen.html.in                  |  14 +--
 docs/firewall.html.in                |   6 +-
 docs/formatcaps.html.in              |   8 +-
 docs/formatdomain.html.in            | 192 +++++++++++++++++--------------=
----
 docs/formatdomaincaps.html.in        |  24 ++---
 docs/formatnetwork.html.in           |  32 +++---
 docs/formatnode.html.in              |   4 +-
 docs/formatnwfilter.html.in          |  68 ++++++-------
 docs/formatsecret.html.in            |  10 +-
 docs/formatsnapshot.html.in          |   4 +-
 docs/formatstorage.html.in           |  28 ++---
 docs/formatstorageencryption.html.in |  10 +-
 docs/governance.html.in              |  12 +--
 docs/hacking.html.in                 |  40 ++++----
 docs/hooks.html.in                   |  30 +++---
 docs/internals/command.html.in       |  32 +++---
 docs/internals/eventloop.html.in     |   6 +-
 docs/internals/locking.html.in       |  16 +--
 docs/internals/oomtesting.html.in    |   8 +-
 docs/internals/rpc.html.in           |  42 ++++----
 docs/locking-lockd.html.in           |   8 +-
 docs/locking-sanlock.html.in         |  10 +-
 docs/locking.html.in                 |   2 +-
 docs/logging.html.in                 |  14 +--
 docs/migration.html.in               |  36 +++----
 docs/nss.html.in                     |  10 +-
 docs/page.xsl                        |  14 +--
 docs/remote.html.in                  |  28 ++---
 docs/secureusage.html.in             |  14 +--
 docs/securityprocess.html.in         |  12 +--
 docs/storage.html.in                 |  26 ++---
 docs/uri.html.in                     |  28 ++---
 docs/virshcmdref.html.in             |   8 +-
 docs/windows.html.in                 |  18 ++--
 62 files changed, 624 insertions(+), 626 deletions(-)

diff --git a/docs/acl.html.in b/docs/acl.html.in
index 6d280c194..5936c6d20 100644
--- a/docs/acl.html.in
+++ b/docs/acl.html.in
@@ -12,7 +12,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"intro">Access control introduction</a></h2>
+    <h2><a id=3D"intro">Access control introduction</a></h2>
=20
     <p>
       In a default configuration, the libvirtd daemon has three levels
@@ -42,7 +42,7 @@
       <code>getattr</code> permission.
     </p>
=20
-    <h2><a name=3D"drivers">Access control drivers</a></h2>
+    <h2><a id=3D"drivers">Access control drivers</a></h2>
=20
     <p>
       The access control framework is designed as a pluggable
@@ -83,7 +83,7 @@
       the libvirtd daemon be restarted.
     </p>
=20
-    <h2><a name=3D"perms">Objects and permissions</a></h2>
+    <h2><a id=3D"perms">Objects and permissions</a></h2>
=20
     <p>
       Libvirt applies access control to all the main object
diff --git a/docs/aclpolkit.html.in b/docs/aclpolkit.html.in
index 7967a0f3d..d1f327c70 100644
--- a/docs/aclpolkit.html.in
+++ b/docs/aclpolkit.html.in
@@ -14,7 +14,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"intro">Introduction</a></h2>
+    <h2><a id=3D"intro">Introduction</a></h2>
=20
     <p>
       A default install of libvirt will typically use
@@ -27,7 +27,7 @@
       object.
     </p>
=20
-    <h2><a name=3D"perms">Permission names</a></h2>
+    <h2><a id=3D"perms">Permission names</a></h2>
=20
     <p>
       The libvirt <a href=3D"acl.html#perms">object names and permission n=
ames</a>
@@ -53,7 +53,7 @@
       permissions default to deny access.
     </p>
=20
-    <h2><a name=3D"attrs">Object identity attributes</a></h2>
+    <h2><a id=3D"attrs">Object identity attributes</a></h2>
=20
     <p>
       To allow polkit authorization rules to be written to match
@@ -63,7 +63,7 @@
       of object being checked
     </p>
=20
-    <h3><a name=3D"object_connect">virConnectPtr</a></h3>
+    <h3><a id=3D"object_connect">virConnectPtr</a></h3>
     <table class=3D"acl">
       <thead>
         <tr>
@@ -79,7 +79,7 @@
       </tbody>
     </table>
=20
-    <h3><a name=3D"object_domain">virDomainPtr</a></h3>
+    <h3><a id=3D"object_domain">virDomainPtr</a></h3>
     <table class=3D"acl">
       <thead>
         <tr>
@@ -103,7 +103,7 @@
       </tbody>
     </table>
=20
-    <h3><a name=3D"object_interface">virInterfacePtr</a></h3>
+    <h3><a id=3D"object_interface">virInterfacePtr</a></h3>
     <table class=3D"acl">
       <thead>
         <tr>
@@ -127,7 +127,7 @@
       </tbody>
     </table>
=20
-    <h3><a name=3D"object_network">virNetworkPtr</a></h3>
+    <h3><a id=3D"object_network">virNetworkPtr</a></h3>
     <table class=3D"acl">
       <thead>
         <tr>
@@ -151,7 +151,7 @@
       </tbody>
     </table>
=20
-    <h3><a name=3D"object_node_device">virNodeDevicePtr</a></h3>
+    <h3><a id=3D"object_node_device">virNodeDevicePtr</a></h3>
     <table class=3D"acl">
       <thead>
         <tr>
@@ -171,7 +171,7 @@
       </tbody>
     </table>
=20
-    <h3><a name=3D"object_nwfilter">virNWFilterPtr</a></h3>
+    <h3><a id=3D"object_nwfilter">virNWFilterPtr</a></h3>
     <table class=3D"acl">
       <thead>
         <tr>
@@ -195,7 +195,7 @@
       </tbody>
     </table>
=20
-    <h3><a name=3D"object_secret">virSecretPtr</a></h3>
+    <h3><a id=3D"object_secret">virSecretPtr</a></h3>
     <table class=3D"acl">
       <thead>
         <tr>
@@ -231,7 +231,7 @@
       </tbody>
     </table>
=20
-    <h3><a name=3D"object_storage_pool">virStoragePoolPtr</a></h3>
+    <h3><a id=3D"object_storage_pool">virStoragePoolPtr</a></h3>
     <table class=3D"acl">
       <thead>
         <tr>
@@ -255,7 +255,7 @@
       </tbody>
     </table>
=20
-    <h3><a name=3D"object_storage_vol">virStorageVolPtr</a></h3>
+    <h3><a id=3D"object_storage_vol">virStorageVolPtr</a></h3>
     <table class=3D"acl">
       <thead>
         <tr>
@@ -288,7 +288,7 @@
     </table>
=20
=20
-    <h2><a name=3D"user">User identity attributes</a></h2>
+    <h2><a id=3D"user">User identity attributes</a></h2>
=20
     <p>
       At this point in time, the only attribute provided by
@@ -307,7 +307,7 @@
     </p>
=20
=20
-    <h2><a name=3D"checks">Writing access control policies</a></h2>
+    <h2><a id=3D"checks">Writing access control policies</a></h2>
=20
     <p>
       If using versions of polkit prior to 0.106 then it is only
@@ -358,7 +358,7 @@ polkit.addRule(function(action, subject) {
     for a more complex example.
     </p>
=20
-    <h3><a name=3D"exconnect">Example: restricting ability to connect to d=
rivers</a></h3>
+    <h3><a id=3D"exconnect">Example: restricting ability to connect to dri=
vers</a></h3>
=20
     <p>
       Consider a local user <code>berrange</code>
@@ -386,7 +386,7 @@ polkit.addRule(function(action, subject) {
 });
     </pre>
=20
-    <h3><a name=3D"exdomain">Example: restricting access to a single domai=
n</a></h3>
+    <h3><a id=3D"exdomain">Example: restricting access to a single domain<=
/a></h3>
=20
     <p>
       Consider a local user <code>berrange</code>
diff --git a/docs/api.html.in b/docs/api.html.in
index c38bed28c..1cd166364 100644
--- a/docs/api.html.in
+++ b/docs/api.html.in
@@ -9,7 +9,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"Objects">Objects Exposed</a></h2>
+    <h2><a id=3D"Objects">Objects Exposed</a></h2>
     <p> As defined in the <a href=3D"goals.html">goals section</a>, the li=
bvirt
     API is designed to expose all the resources needed to manage the
     virtualization support of recent operating systems. The first object
@@ -121,7 +121,7 @@
       set of nodes.</p></li>
     </ul>
=20
-    <h2><a name=3D"Functions">Functions and Naming Conventions</a></h2>
+    <h2><a id=3D"Functions">Functions and Naming Conventions</a></h2>
     <p> The naming of the functions present in the library is usually
       composed by a prefix describing the object associated to the function
       and a verb describing the action on that object.</p>
@@ -297,7 +297,7 @@
     <p> For more in-depth details of the storage related APIs see
       <a href=3D"storage.html">the storage management page</a>.
     </p>
-    <h2><a name=3D"Drivers">The libvirt Drivers</a></h2>
+    <h2><a id=3D"Drivers">The libvirt Drivers</a></h2>
     <p>Drivers are the basic building block for libvirt functionality
     to support the capability to handle specific hypervisor driver calls.
     Drivers are discovered and registered during connection processing as
@@ -325,7 +325,7 @@
     the various functions and support found in each driver by the version
     support was added into libvirt.
     </p>
-    <h2><a name=3D"Remote">Daemon and Remote Access</a></h2>
+    <h2><a id=3D"Remote">Daemon and Remote Access</a></h2>
     <p>Access to libvirt drivers is primarily handled by the libvirtd
     daemon through the <a href=3D"remote.html">remote</a> driver via an
     <a href=3D"internals/rpc.html">RPC</a>. Some hypervisors do support
diff --git a/docs/api_extension.html.in b/docs/api_extension.html.in
index ac7097b91..fdc7eb296 100644
--- a/docs/api_extension.html.in
+++ b/docs/api_extension.html.in
@@ -273,7 +273,7 @@
       <li>unlocks the remote driver.</li>
     </ol>
=20
-    <h3><a name=3D"serverdispatch">Implement the server side dispatcher</a=
></h3>
+    <h3><a id=3D"serverdispatch">Implement the server side dispatcher</a><=
/h3>
=20
     <p>
       Implementing the server side of the remote function call is simply a
@@ -300,7 +300,7 @@
=20
     <p class=3D"example">See <a href=3D"api_extension/0005-implement-the-r=
emote-protocol.patch">0005-implement-the-remote-protocol.patch</a></p>
=20
-    <h2><a name=3D"internaluseapi">Use the new API internally</a></h2>
+    <h2><a id=3D"internaluseapi">Use the new API internally</a></h2>
=20
     <p>
       Sometimes, a new API serves as a superset of existing API, by
@@ -314,7 +314,7 @@
=20
     <p class=3D"example">See <a href=3D"api_extension/0006-make-old-API-tr=
ivially-wrap-to-new-API.patch">0006-make-old-API-trivially-wrap-to-new-API.=
patch</a></p>
=20
-    <h2><a name=3D"virshuseapi">Expose the new API in virsh</a></h2>
+    <h2><a id=3D"virshuseapi">Expose the new API in virsh</a></h2>
=20
     <p>
       All new API should be manageable from the virsh command line
@@ -345,7 +345,7 @@
=20
     <p class=3D"example">See <a href=3D"api_extension/0007-add-virsh-suppo=
rt.patch">0007-add-virsh-support.patch</a></p>
=20
-    <h2><a name=3D"driverimpl">Implement the driver methods</a></h2>
+    <h2><a id=3D"driverimpl">Implement the driver methods</a></h2>
=20
     <p>
       So, after all that, we get to the fun part.  All functionality in
@@ -356,7 +356,7 @@
       adding.
     </p>
=20
-    <h3><a name=3D"commonimpl">Implement common handling</a></h3>
+    <h3><a id=3D"commonimpl">Implement common handling</a></h3>
=20
     <p>
       If the new API is applicable to more than one driver, it may
@@ -373,7 +373,7 @@
=20
     <p class=3D"example">See <a href=3D"api_extension/0008-support-new-xml=
.patch">0008-support-new-xml.patch</a></p>
=20
-    <h3><a name=3D"drivercode">Implement driver handling</a></h3>
+    <h3><a id=3D"drivercode">Implement driver handling</a></h3>
=20
     <p>
       The remaining patches should only touch one driver at a time.
diff --git a/docs/apps.html.in b/docs/apps.html.in
index 44e5b644f..760004715 100644
--- a/docs/apps.html.in
+++ b/docs/apps.html.in
@@ -11,7 +11,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"add">Add an application</a></h2>
+    <h2><a id=3D"add">Add an application</a></h2>
=20
     <p>
       To add an application not listed on this page, send a message
@@ -30,7 +30,7 @@
       <img src=3D"logos/logo-square-powered-256.png" alt=3D"libvirt powere=
d"/>
     </p>
=20
-    <h2><a name=3D"clientserver">Client/Server applications</a></h2>
+    <h2><a id=3D"clientserver">Client/Server applications</a></h2>
=20
     <dl>
       <dt><a href=3D"http://archipelproject.org">Archipel</a></dt>
@@ -50,7 +50,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"command">Command line tools</a></h2>
+    <h2><a id=3D"command">Command line tools</a></h2>
=20
     <dl>
       <dt><a href=3D"http://libguestfs.org">guestfish</a></dt>
@@ -121,7 +121,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"configmgmt">Configuration Management</a></h2>
+    <h2><a id=3D"configmgmt">Configuration Management</a></h2>
=20
     <dl>
       <dt><a href=3D"https://wiki.lcfg.org/bin/view/LCFG/LcfgLibvirt">LCFG=
</a></dt>
@@ -139,7 +139,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"continuousintegration">Continuous Integration</a></h2>
+    <h2><a id=3D"continuousintegration">Continuous Integration</a></h2>
=20
     <dl>
       <dt><a href=3D"http://buildbot.net/buildbot/docs/current/Libvirt.htm=
l">BuildBot</a></dt>
@@ -163,7 +163,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"conversion">Conversion</a></h2>
+    <h2><a id=3D"conversion">Conversion</a></h2>
=20
     <dl>
       <dt><a href=3D"http://libguestfs.org/virt-p2v.1.html">virt-p2v</a></=
dt>
@@ -194,7 +194,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"desktop">Desktop applications</a></h2>
+    <h2><a id=3D"desktop">Desktop applications</a></h2>
=20
     <dl>
       <dt><a href=3D"http://virt-manager.org/">virt-manager</a></dt>
@@ -224,7 +224,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"iaas">Infrastructure as a Service (IaaS)</a></h2>
+    <h2><a id=3D"iaas">Infrastructure as a Service (IaaS)</a></h2>
=20
     <dl>
       <dt><a href=3D"http://cc1.ifj.edu.pl">Cracow Cloud One</a></dt>
@@ -288,7 +288,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"libraries">Libraries</a></h2>
+    <h2><a id=3D"libraries">Libraries</a></h2>
=20
     <dl>
       <dt><a href=3D"http://libguestfs.org">libguestfs</a></dt>
@@ -321,7 +321,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"livecd">LiveCD / Appliances</a></h2>
+    <h2><a id=3D"livecd">LiveCD / Appliances</a></h2>
=20
     <dl>
       <dt><a href=3D"http://et.redhat.com/~rjones/virt-p2v/">virt-p2v</a><=
/dt>
@@ -334,7 +334,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"monitoring">Monitoring</a></h2>
+    <h2><a id=3D"monitoring">Monitoring</a></h2>
     <dl>
       <dt><a href=3D"http://collectd.org/plugins/libvirt.shtml">collectd</=
a></dt>
       <dd>
@@ -381,7 +381,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"provisioning">Provisioning</a></h2>
+    <h2><a id=3D"provisioning">Provisioning</a></h2>
=20
     <dl>
       <dt><a href=3D"http://www.ibm.com/software/tivoli/products/prov-mgr/=
">Tivoli Provisioning Manager</a></dt>
@@ -415,7 +415,7 @@
     </dl>
=20
=20
-    <h2><a name=3D"web">Web applications</a></h2>
+    <h2><a id=3D"web">Web applications</a></h2>
=20
     <dl>
       <dt><a href=3D"http://community.abiquo.com/display/AbiCloud">AbiClou=
d</a></dt>
@@ -468,7 +468,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"mobile">Mobile applications</a></h2>
+    <h2><a id=3D"mobile">Mobile applications</a></h2>
=20
     <dl>
       <dt><a href=3D"https://market.android.com/details?id=3Dvm.manager">V=
M Manager</a></dt>
@@ -479,7 +479,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"other">Other</a></h2>
+    <h2><a id=3D"other">Other</a></h2>
=20
     <dl>
       <dt><a href=3D"http://cuckoosandbox.org/">Cuckoo Sandbox</a></dt>
diff --git a/docs/architecture.html.in b/docs/architecture.html.in
index 5d3d441ba..33a4ccb97 100644
--- a/docs/architecture.html.in
+++ b/docs/architecture.html.in
@@ -13,7 +13,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"Xen">Xen support</a></h2>
+    <h2><a id=3D"Xen">Xen support</a></h2>
=20
     <p>When running in a Xen environment, programs using libvirt have to e=
xecute
 in "Domain 0", which is the primary Linux OS loaded on the machine. That OS
@@ -46,7 +46,7 @@ connect to initialize the library. It will then fork a li=
bvirt_proxy
 program running as root and providing read_only access to the API, this is
 then only useful for reporting and monitoring.</p>
=20
-    <h2><a name=3D"QEmu">QEmu and KVM support</a></h2>
+    <h2><a id=3D"QEmu">QEmu and KVM support</a></h2>
=20
     <p>The model for QEmu and KVM is completely similar, basically KVM is =
based
 on QEmu for the process controlling a new domain, only small details diffe=
rs
@@ -60,7 +60,7 @@ domain, by specifying the architecture and machine type t=
argeted.</p>
     <p>The code controlling the QEmu process is available in the
 <code>qemud/</code> directory.</p>
=20
-    <h2><a name=3D"drivers">Driver based architecture</a></h2>
+    <h2><a id=3D"drivers">Driver based architecture</a></h2>
=20
     <p>As the previous section explains, libvirt can communicate using dif=
ferent
 channels with the current hypervisor, and should also be able to use
diff --git a/docs/auditlog.html.in b/docs/auditlog.html.in
index 0c778aafe..54da12b5c 100644
--- a/docs/auditlog.html.in
+++ b/docs/auditlog.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"intro">Introduction</a></h2>
+    <h2><a id=3D"intro">Introduction</a></h2>
=20
     <p>
       A number of the libvirt virtualization drivers (QEMU/KVM and LXC) in=
clude
@@ -17,7 +17,7 @@
       the logs will usually end up in <code>/var/log/audit/audit.log</code>
     </p>
=20
-    <h2><a name=3D"config">Configuration</a></h2>
+    <h2><a id=3D"config">Configuration</a></h2>
=20
     <p>
       The libvirt audit integration is enabled by default on any host whic=
h has
@@ -48,7 +48,7 @@
       mentioned above.
     </p>
=20
-    <h2><a name=3D"types">Message types</a></h2>
+    <h2><a id=3D"types">Message types</a></h2>
=20
     <p>
       Libvirt defines three core audit message types each of which will
@@ -90,7 +90,7 @@
       <dd>Result of the action, either <code>success</code> or <code>faile=
d</code></dd>
     </dl>
=20
-    <h3><a name=3D"typecontrol">VIRT_CONTROL</a></h3>
+    <h3><a id=3D"typecontrol">VIRT_CONTROL</a></h3>
=20
     <p>
       Reports change in the lifecycle state of a virtual machine. The <cod=
e>msg</code>
@@ -110,7 +110,7 @@
       <dd>Namespace ID of the <code>init</code> process in a container. On=
ly if <code>op=3Dinit</code> and <code>virt=3Dlxc</code></dd>
     </dl>
=20
-    <h3><a name=3D"typemachine">VIRT_MACHINE_ID</a></h3>
+    <h3><a id=3D"typemachine">VIRT_MACHINE_ID</a></h3>
=20
     <p>
       Reports the association of a security context with a guest. The <cod=
e>msg</code>
@@ -126,7 +126,7 @@
       <dd>Security context for the guest disk images and other assigned ho=
st resources</dd>
     </dl>
=20
-    <h3><a name=3D"typeresource">VIRT_RESOURCE</a></h3>
+    <h3><a id=3D"typeresource">VIRT_RESOURCE</a></h3>
=20
     <p>
       Reports the usage of a host resource by a guest. The fields include =
will
@@ -137,7 +137,7 @@
       be generated.
     </p>
=20
-    <h4><a name=3D"typeresourcevcpu">Virtual CPU</a></h4>
+    <h4><a id=3D"typeresourcevcpu">Virtual CPU</a></h4>
=20
     <p>
       The <code>msg</code> field will include the following sub-fields
@@ -155,7 +155,7 @@
     </dl>
=20
=20
-    <h4><a name=3D"typeresourcemem">Memory</a></h4>
+    <h4><a id=3D"typeresourcemem">Memory</a></h4>
=20
     <p>
       The <code>msg</code> field will include the following sub-fields
@@ -172,7 +172,7 @@
       <dd>Updated memory size in bytes</dd>
     </dl>
=20
-    <h4><a name=3D"typeresourcedisk">Disk</a></h4>
+    <h4><a id=3D"typeresourcedisk">Disk</a></h4>
     <p>
       The <code>msg</code> field will include the following sub-fields
     </p>
@@ -188,7 +188,7 @@
       <dd>Updated host file or device path acting as the disk backing file=
</dd>
     </dl>
=20
-    <h4><a name=3D"typeresourcenic">Network interface</a></h4>
+    <h4><a id=3D"typeresourcenic">Network interface</a></h4>
=20
     <p>
       The <code>msg</code> field will include the following sub-fields
@@ -221,7 +221,7 @@
       <dd>Name of the host network interface</dd>
     </dl>
=20
-    <h4><a name=3D"typeresourcefs">Filesystem</a></h4>
+    <h4><a id=3D"typeresourcefs">Filesystem</a></h4>
     <p>
       The <code>msg</code> field will include the following sub-fields
     </p>
@@ -237,7 +237,7 @@
       <dd>Updated host directory, file or device path backing the filesyst=
em</dd>
     </dl>
=20
-    <h4><a name=3D"typeresourcehost">Host device</a></h4>
+    <h4><a id=3D"typeresourcehost">Host device</a></h4>
     <p>
       The <code>msg</code> field will include the following sub-fields
     </p>
@@ -255,7 +255,7 @@
       <dd>The path of the character device assigned to the guest, if <code=
>resrc=3Dhostdev</code></dd>
     </dl>
=20
-    <h4><a name=3D"typeresourcetpm">TPM</a></h4>
+    <h4><a id=3D"typeresourcetpm">TPM</a></h4>
     <p>
       The <code>msg</code> field will include the following sub-fields
     </p>
@@ -269,7 +269,7 @@
       <dd>The path of the host TPM device assigned to the guest</dd>
     </dl>
=20
-    <h4><a name=3D"typeresourcerng">RNG</a></h4>
+    <h4><a id=3D"typeresourcerng">RNG</a></h4>
     <p>
       The <code>msg</code> field will include the following sub-fields
     </p>
@@ -285,7 +285,7 @@
       <dd>Updated path of the host entropy source for the RNG</dd>
     </dl>
=20
-    <h4><a name=3D"typeresourcechardev">console/serial/parallel/channel</a=
></h4>
+    <h4><a id=3D"typeresourcechardev">console/serial/parallel/channel</a><=
/h4>
     <p>
       The <code>msg</code> field will include the following sub-fields
     </p>
@@ -301,7 +301,7 @@
       <dd>Updated path of the backing character device for given emulated =
device</dd>
     </dl>
=20
-    <h4><a name=3D"typeresourcesmartcard">smartcard</a></h4>
+    <h4><a id=3D"typeresourcesmartcard">smartcard</a></h4>
     <p>
       The <code>msg</code> field will include the following sub-fields
     </p>
@@ -321,7 +321,7 @@
       </dd>
     </dl>
=20
-    <h4><a name=3D"typeresourceredir">Redirected device</a></h4>
+    <h4><a id=3D"typeresourceredir">Redirected device</a></h4>
     <p>
       The <code>msg</code> field will include the following sub-fields
     </p>
@@ -337,7 +337,7 @@
       <dd>The device type, only <code>USB redir</code> allowed</dd>
     </dl>
=20
-    <h4><a name=3D"typeresourcecgroup">Control group</a></h4>
+    <h4><a id=3D"typeresourcecgroup">Control group</a></h4>
=20
     <p>
       The <code>msg</code> field will include the following sub-fields
@@ -353,7 +353,7 @@
     </dl>
=20
=20
-    <h4><a name=3D"typeresourceshmem">Shared memory</a></h4>
+    <h4><a id=3D"typeresourceshmem">Shared memory</a></h4>
     <p>
       The <code>msg</code> field will include the following sub-fields
     </p>
diff --git a/docs/auth.html.in b/docs/auth.html.in
index f75454416..9c9afe7b4 100644
--- a/docs/auth.html.in
+++ b/docs/auth.html.in
@@ -14,7 +14,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"Auth_client_config">Client configuration</a></h2>
+    <h2><a id=3D"Auth_client_config">Client configuration</a></h2>
=20
     <p>
       When connecting to a remote hypervisor which requires authentication,
@@ -142,7 +142,7 @@ credentials=3Ddefgrp</pre>
       to storage VNC or SPICE login credentials
     </p>
=20
-    <h2><a name=3D"ACL_server_config">Server configuration</a></h2>
+    <h2><a id=3D"ACL_server_config">Server configuration</a></h2>
     <p>
 The libvirt daemon allows the administrator to choose the authentication
 mechanisms used for client connections on each network socket independentl=
y.
@@ -153,7 +153,7 @@ currently a choice of <code>none</code>, <code>polkit</=
code>, and <code>sasl</co
 The SASL scheme can be further configured to choose between a large
 number of different mechanisms.
 </p>
-    <h2><a name=3D"ACL_server_unix_perms">UNIX socket permissions/group</a=
></h2>
+    <h2><a id=3D"ACL_server_unix_perms">UNIX socket permissions/group</a><=
/h2>
     <p>
 If libvirt does not contain support for PolicyKit, then access control for
 the UNIX domain socket is done using traditional file user/group ownership
@@ -170,7 +170,7 @@ parameter. For example, setting the former to mode <cod=
e>0770</code> and the
 latter <code>wheel</code> would let any user in the wheel group connect to
 the libvirt daemon.
 </p>
-    <h2><a name=3D"ACL_server_polkit">UNIX socket PolicyKit auth</a></h2>
+    <h2><a id=3D"ACL_server_polkit">UNIX socket PolicyKit auth</a></h2>
     <p>
 If libvirt contains support for PolicyKit, then access control options are
 more advanced. The <code>auth_unix_rw</code> parameter will default to
@@ -204,7 +204,7 @@ ResultActive=3Dyes</pre>
 Further examples of PolicyKit setup can be found on the
 <a href=3D"http://wiki.libvirt.org/page/SSHPolicyKitSetup">wiki page</a>.
     </p>
-    <h2><a name=3D"ACL_server_sasl">SASL pluggable authentication</a></h2>
+    <h2><a id=3D"ACL_server_sasl">SASL pluggable authentication</a></h2>
=20
     <p>
 Libvirt integrates with the cyrus-sasl library to provide a pluggable auth=
entication
@@ -255,7 +255,7 @@ GSSAPI plugin is considered acceptably secure by modern=
 standards:
       TLS or UNIX socket listeners.
     </p>
=20
-    <h3><a name=3D"ACL_server_username">Username/password auth</a></h3>
+    <h3><a id=3D"ACL_server_username">Username/password auth</a></h3>
     <p>
 As noted above, the DIGEST-MD5 mechanism is considered obsolete and should
 not be used anymore. To provide a simple username/password auth scheme on
@@ -297,7 +297,7 @@ again:
     <pre>
 # saslpasswd2 -a libvirt -d fred
 </pre>
-    <h3><a name=3D"ACL_server_kerberos">GSSAPI/Kerberos auth</a></h3>
+    <h3><a id=3D"ACL_server_kerberos">GSSAPI/Kerberos auth</a></h3>
     <p>
 The plain TCP listener of the libvirt daemon defaults to using SASL for au=
thentication.
 The libvirt SASL config also defaults to GSSAPI, so there is no need to ed=
it the
diff --git a/docs/bugs.html.in b/docs/bugs.html.in
index 55ceb6007..7ba8dd6a4 100644
--- a/docs/bugs.html.in
+++ b/docs/bugs.html.in
@@ -7,7 +7,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"security">Security Issues</a></h2>
+    <h2><a id=3D"security">Security Issues</a></h2>
=20
     <p>
       If you think that an issue with libvirt may have security
@@ -19,7 +19,7 @@
       <a href=3D"securityprocess.html">security process</a> instead.
     </p>
=20
-    <h2><a name=3D"bugzilla">Bug Tracking</a></h2>
+    <h2><a id=3D"bugzilla">Bug Tracking</a></h2>
=20
     <p>
       If you are using libvirt binaries from a Linux distribution
@@ -27,7 +27,7 @@
       first.
     </p>
=20
-    <h2><a name=3D"general">General libvirt bug reports</a></h2>
+    <h2><a id=3D"general">General libvirt bug reports</a></h2>
=20
     <p>
       The <a href=3D"http://bugzilla.redhat.com">Red Hat Bugzilla Server</=
a>
@@ -69,7 +69,7 @@
       <li><a href=3D"http://bugzilla.redhat.com/bugzilla/enter_bug.cgi?pro=
duct=3DVirtualization%20Tools&amp;component=3Dlibvirt">New libvirt ticket</=
a></li>
     </ul>
=20
-    <h2><a name=3D"distribution">Linux Distribution specific bug reports</=
a></h2>
+    <h2><a id=3D"distribution">Linux Distribution specific bug reports</a>=
</h2>
     <ul>
       <li>
         If you are using binaries from <strong>Fedora</strong>, enter
@@ -107,7 +107,7 @@
     </ul>
=20
=20
-    <h2><a name=3D"quality">How to file high quality bug reports</a></h2>
+    <h2><a id=3D"quality">How to file high quality bug reports</a></h2>
=20
     <p>
       To increase the likelihood of your bug report being addressed it is
diff --git a/docs/cgroups.html.in b/docs/cgroups.html.in
index 60b47da1f..ac6390960 100644
--- a/docs/cgroups.html.in
+++ b/docs/cgroups.html.in
@@ -11,7 +11,7 @@
       for applying resource management to their virtual machines and conta=
iners.
     </p>
=20
-    <h2><a name=3D"requiredControllers">Required controllers</a></h2>
+    <h2><a id=3D"requiredControllers">Required controllers</a></h2>
=20
     <p>
       The control groups filesystem supports multiple "controllers". By de=
fault
@@ -42,7 +42,7 @@
       which use them will cease to operate.
     </p>
=20
-    <h2><a name=3D"currentLayout">Current cgroups layout</a></h2>
+    <h2><a id=3D"currentLayout">Current cgroups layout</a></h2>
=20
     <p>
       As of libvirt 1.0.5 or later, the cgroups layout created by libvirt =
has been
@@ -63,14 +63,14 @@
       in two, one describing systemd hosts and the other non-systemd hosts.
     </p>
=20
-    <h3><a name=3D"currentLayoutSystemd">Systemd cgroups integration</a></=
h3>
+    <h3><a id=3D"currentLayoutSystemd">Systemd cgroups integration</a></h3>
=20
     <p>
       On hosts which use systemd, each consumer maps to a systemd scope un=
it,
       while partitions map to a system slice unit.
     </p>
=20
-    <h4><a name=3D"systemdScope">Systemd scope naming</a></h4>
+    <h4><a id=3D"systemdScope">Systemd scope naming</a></h4>
=20
     <p>
       The systemd convention is for the scope name of virtual machines / c=
ontainers
@@ -83,7 +83,7 @@
       The scope names map directly to the cgroup directory names.
     </p>
=20
-    <h4><a name=3D"systemdSlice">Systemd slice naming</a></h4>
+    <h4><a id=3D"systemdSlice">Systemd slice naming</a></h4>
=20
     <p>
       The systemd convention for slice naming is that a slice should inclu=
de the
@@ -96,7 +96,7 @@
       by libvirt will be associated with <code>machine.slice</code> by def=
ault.
     </p>
=20
-    <h4><a name=3D"systemdLayout">Systemd cgroup layout</a></h4>
+    <h4><a id=3D"systemdLayout">Systemd cgroup layout</a></h4>
=20
     <p>
       Given this, a possible systemd cgroups layout involving 3 qemu guest=
s,
@@ -145,7 +145,7 @@ $ROOT
           +- machine-lxc\x2dcontainer3.scope
     </pre>
=20
-    <h3><a name=3D"currentLayoutGeneric">Non-systemd cgroups layout</a></h=
3>
+    <h3><a id=3D"currentLayoutGeneric">Non-systemd cgroups layout</a></h3>
=20
     <p>
       On hosts which do not use systemd, each consumer has a corresponding=
 cgroup
@@ -206,7 +206,7 @@ $ROOT
           +- container3.libvirt-lxc
     </pre>
=20
-    <h2><a name=3D"customPartiton">Using custom partitions</a></h2>
+    <h2><a id=3D"customPartiton">Using custom partitions</a></h2>
=20
     <p>
       If there is a need to apply resource constraints to groups of
@@ -255,7 +255,7 @@ $ROOT
       later in this document did not support customization per guest.
     </p>
=20
-    <h3><a name=3D"createSystemd">Creating custom partitions (systemd)</a>=
</h3>
+    <h3><a id=3D"createSystemd">Creating custom partitions (systemd)</a></=
h3>
=20
     <p>
       Given the XML config above, the admin on a systemd based host would
@@ -272,7 +272,7 @@ EOF
 # systemctl start machine-testing.slice
     </pre>
=20
-    <h3><a name=3D"createNonSystemd">Creating custom partitions (non-syste=
md)</a></h3>
+    <h3><a id=3D"createNonSystemd">Creating custom partitions (non-systemd=
)</a></h3>
=20
     <p>
       Given the XML config above, the admin on a non-systemd based host
@@ -291,7 +291,7 @@ EOF
   done
 </pre>
=20
-    <h2><a name=3D"resourceAPIs">Resource management APIs/commands</a></h2>
+    <h2><a id=3D"resourceAPIs">Resource management APIs/commands</a></h2>
=20
     <p>
       Since libvirt aims to provide an API which is portable across
@@ -354,7 +354,7 @@ swap_hard_limit: unlimited
       network interfaces.
     </p>
=20
-    <h2><a name=3D"legacyLayout">Legacy cgroups layout</a></h2>
+    <h2><a id=3D"legacyLayout">Legacy cgroups layout</a></h2>
=20
     <p>
       Prior to libvirt 1.0.5, the cgroups layout created by libvirt was di=
fferent
diff --git a/docs/compiling.html.in b/docs/compiling.html.in
index 3a0c7fdd1..af22199ef 100644
--- a/docs/compiling.html.in
+++ b/docs/compiling.html.in
@@ -2,11 +2,11 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.or=
g/TR/xhtml1/DTD/xhtml1-strict.dtd">
 <html xmlns=3D"http://www.w3.org/1999/xhtml">
   <body>
-    <h1><a name=3D"installation">libvirt Installation</a></h1>
+    <h1><a id=3D"installation">libvirt Installation</a></h1>
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"compiling">Compiling a release tarball</a></h2>
+    <h2><a id=3D"compiling">Compiling a release tarball</a></h2>
=20
     <p>
       libvirt uses the standard configure/make/install steps:
@@ -58,7 +58,7 @@ $ <b>sudo</b> <i>make install</i></pre>
       to update your list of installed shared libs.
     </p>
=20
-    <h2><a name=3D"building">Building from a GIT checkout</a></h2>
+    <h2><a id=3D"building">Building from a GIT checkout</a></h2>
=20
     <p>
       The libvirt build process uses GNU autotools, so after obtaining a
diff --git a/docs/contact.html.in b/docs/contact.html.in
index 9ea16748a..1f84527b2 100644
--- a/docs/contact.html.in
+++ b/docs/contact.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"security">Security Issues</a></h2>
+    <h2><a id=3D"security">Security Issues</a></h2>
=20
     <p>
       If you think that an issue with libvirt may have security
@@ -18,7 +18,7 @@
       <a href=3D"securityprocess.html">security process</a> instead.
     </p>
=20
-    <h2><a name=3D"email">Mailing lists</a></h2>
+    <h2><a id=3D"email">Mailing lists</a></h2>
=20
     <p>
       There are three mailing-lists:
@@ -95,7 +95,7 @@
       page.
     </p>
=20
-    <h2><a name=3D"irc">IRC discussion</a></h2>
+    <h2><a id=3D"irc">IRC discussion</a></h2>
=20
     <p>
       Some of the libvirt developers may be found on IRC on the <a href=3D=
"http://oftc.net">OFTC IRC</a>
diff --git a/docs/contribute.html.in b/docs/contribute.html.in
index 32935b1fa..c169b6700 100644
--- a/docs/contribute.html.in
+++ b/docs/contribute.html.in
@@ -11,7 +11,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"skills">Contributions required</a></h2>
+    <h2><a id=3D"skills">Contributions required</a></h2>
=20
     <p>
       The libvirt project is always looking for new contributors to
@@ -97,7 +97,7 @@
         these help forums.</li>
     </ul>
=20
-    <h2><a name=3D"comms">Communication</a></h2>
+    <h2><a id=3D"comms">Communication</a></h2>
=20
     <p>
       For full details on contacting other project contributors
@@ -106,7 +106,7 @@
       between contributors:
     </p>
=20
-    <h3><a name=3D"email">Mailing lists</a></h3>
+    <h3><a id=3D"email">Mailing lists</a></h3>
=20
     <p>
       The project has a number of
@@ -118,7 +118,7 @@
       to follow the traffic.
     </p>
=20
-    <h3><a name=3D"irc">Instant messaging / chat</a></h3>
+    <h3><a id=3D"irc">Instant messaging / chat</a></h3>
=20
     <p>
       Contributors to libvirt are encouraged to join the
@@ -127,7 +127,7 @@
       with others members.
     </p>
=20
-    <h2><a name=3D"outreach">Student / outreach coding programs</a></h2>
+    <h2><a id=3D"outreach">Student / outreach coding programs</a></h2>
=20
     <p>
       Since 2016, the libvirt project directly participates as an
diff --git a/docs/csharp.html.in b/docs/csharp.html.in
index 4c35c871d..e1c0fefba 100644
--- a/docs/csharp.html.in
+++ b/docs/csharp.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"description">Description</a></h2>
+    <h2><a id=3D"description">Description</a></h2>
=20
     <p>
       The C# libvirt bindings are a class library.  They use a Microsoft
@@ -21,7 +21,7 @@
=20
     <p>&nbsp;</p>
=20
-    <h2><a name=3D"requirements">Requirements</a></h2>
+    <h2><a id=3D"requirements">Requirements</a></h2>
=20
     <p>
       These bindings depend upon the libvirt libraries being installed.
@@ -34,7 +34,7 @@
     <p>&nbsp;</p>
=20
 <!-- 2010-10-19 JC: Commented out until we have C# tarballs to download
-    <h2><a name=3D"getting">Getting them</a></h2>
+    <h2><a id=3D"getting">Getting them</a></h2>
=20
     <p>
       The latest versions of the libvirt C# bindings can be downloaded fro=
m:
@@ -46,7 +46,7 @@
     </ul>
 -->
=20
-    <h2><a name=3D"git">GIT source repository</a></h2>
+    <h2><a id=3D"git">GIT source repository</a></h2>
     <p>
       The C# bindings source code is maintained in a <a
       href=3D"http://git-scm.com/">git</a> repository available on
@@ -67,7 +67,7 @@ git clone git://libvirt.org/libvirt-csharp.git
=20
     <p>&nbsp;</p>
=20
-    <h2><a name=3D"usage">Usage</a></h2>
+    <h2><a id=3D"usage">Usage</a></h2>
=20
     <p>
       The libvirt C# bindings class library exposes the <b>Libvirt</b>
@@ -118,7 +118,7 @@ git clone git://libvirt.org/libvirt-csharp.git
=20
     <p>&nbsp;</p>
=20
-    <h2><a name=3D"authors">Authors</a></h2>
+    <h2><a id=3D"authors">Authors</a></h2>
=20
     <p>
       The C# bindings are the work of Arnaud Champion
@@ -128,7 +128,7 @@ git clone git://libvirt.org/libvirt-csharp.git
=20
     <p>&nbsp;</p>
=20
-    <h2><a name=3D"notes">Test Configuration</a></h2>
+    <h2><a id=3D"notes">Test Configuration</a></h2>
=20
     <p>
       Testing is performed using the following configurations:
@@ -141,7 +141,7 @@ git clone git://libvirt.org/libvirt-csharp.git
=20
     <p>&nbsp;</p>
=20
-    <h2><a name=3D"type">Type Coverage</a></h2>
+    <h2><a id=3D"type">Type Coverage</a></h2>
=20
     <p>
       Coverage of the libvirt types is:
@@ -219,7 +219,7 @@ git clone git://libvirt.org/libvirt-csharp.git
=20
     <p>&nbsp;</p>
=20
-    <h2><a name=3D"funccover">Function Coverage</a></h2>
+    <h2><a id=3D"funccover">Function Coverage</a></h2>
=20
     <p>
       Coverage of the libvirt functions is:
diff --git a/docs/downloads.html.in b/docs/downloads.html.in
index 030694549..21d79df4e 100644
--- a/docs/downloads.html.in
+++ b/docs/downloads.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"releases">Project modules</a></h2>
+    <h2><a id=3D"releases">Project modules</a></h2>
=20
     <p>
       The libvirt project maintains a number of inter-related modules beyo=
nd
@@ -435,7 +435,7 @@
       <li><a href=3D"https://libvirt.org/sources/">libvirt.org HTTPS serve=
r</a></li>
     </ul>
=20
-    <h2><a name=3D"hourly">Hourly development snapshots</a></h2>
+    <h2><a id=3D"hourly">Hourly development snapshots</a></h2>
=20
     <p>
       Once an hour, an automated snapshot is made from the git server
@@ -450,7 +450,7 @@
       <li><a href=3D"http://libvirt.org/sources/libvirt-git-snapshot.tar.x=
z">libvirt.org HTTP server</a></li>
     </ul>
=20
-    <h2><a name=3D"schedule">Primary release schedule</a></h2>
+    <h2><a id=3D"schedule">Primary release schedule</a></h2>
=20
     <p>
       The core libvirt module follows a time based plan, with releases made
@@ -462,7 +462,7 @@
       independant ad-hoc releases with no fixed time schedle.
     </p>
=20
-    <h2><a name=3D"numbering">Release numbering</a></h2>
+    <h2><a id=3D"numbering">Release numbering</a></h2>
=20
     <p>
       Since libvirt 2.0.0, a time based version numbering rule
@@ -497,7 +497,7 @@
       digits.
     </p>
=20
-    <h2><a name=3D"maintenance">Maintenance releases</a></h2>
+    <h2><a id=3D"maintenance">Maintenance releases</a></h2>
     <p>
       In the git repository are several stable maintenance branches
       for the core library, matching the
@@ -525,7 +525,7 @@
       wiki page</a>.
     </p>
=20
-    <h2><a name=3D"git">GIT source repository</a></h2>
+    <h2><a id=3D"git">GIT source repository</a></h2>
=20
     <p>
       All modules maintained by the libvirt project have their primary
diff --git a/docs/drivers.html.in b/docs/drivers.html.in
index 61993861e..79b204d1a 100644
--- a/docs/drivers.html.in
+++ b/docs/drivers.html.in
@@ -18,7 +18,7 @@
       network and storage driver active.
     </p>
=20
-    <h2><a name=3D"hypervisor">Hypervisor drivers</a></h2>
+    <h2><a id=3D"hypervisor">Hypervisor drivers</a></h2>
=20
     <p>
       The hypervisor drivers currently supported by libvirt are:
@@ -40,7 +40,7 @@
       <li><strong><a href=3D"drvbhyve.html">Bhyve</a></strong> - The BSD H=
ypervisor</li>
     </ul>
=20
-    <h2><a name=3D"storage">Storage drivers</a></h2>
+    <h2><a id=3D"storage">Storage drivers</a></h2>
=20
     <ul>
       <li><strong><a href=3D"storage.html#StorageBackendDir">Directory bac=
kend</a></strong></li>
diff --git a/docs/drvbhyve.html.in b/docs/drvbhyve.html.in
index f083db91c..7b1829b65 100644
--- a/docs/drvbhyve.html.in
+++ b/docs/drvbhyve.html.in
@@ -31,7 +31,7 @@ $
 Additional information on bhyve could be obtained on <a href=3D"http://bhy=
ve.org/">bhyve.org</a>.
 </p>
=20
-<h2><a name=3D"uri">Connections to the Bhyve driver</a></h2>
+<h2><a id=3D"uri">Connections to the Bhyve driver</a></h2>
 <p>
 The libvirt bhyve driver is a single-instance privileged driver. Some samp=
le
 connection URIs are:
@@ -43,7 +43,7 @@ bhyve+unix:///system                (local access)
 bhyve+ssh://root@example.com/system (remote access, SSH tunnelled)
 </pre>
=20
-<h2><a name=3D"exconfig">Example guest domain XML configurations</a></h2>
+<h2><a id=3D"exconfig">Example guest domain XML configurations</a></h2>
=20
 <h3>Example config</h3>
 <p>
@@ -206,9 +206,9 @@ Note the addition of &lt;bootloader&gt;.
=20
 <p>Please refer to the <a href=3D"#uefi">UEFI</a> section for a more detai=
led explanation.</p>
=20
-<h2><a name=3D"usage">Guest usage / management</a></h2>
+<h2><a id=3D"usage">Guest usage / management</a></h2>
=20
-<h3><a name=3D"console">Connecting to a guest console</a></h3>
+<h3><a id=3D"console">Connecting to a guest console</a></h3>
=20
 <p>
 Guest console connection is supported through the <code>nmdm</code> device=
. It could be enabled by adding
@@ -253,7 +253,7 @@ device) is:</p>
=20
 <pre>cu -l /dev/nmdm0B</pre>
=20
-<h3><a name=3D"xmltonative">Converting from domain XML to Bhyve args</a></=
h3>
+<h3><a id=3D"xmltonative">Converting from domain XML to Bhyve args</a></h3>
=20
 <p>
 The <code>virsh domxml-to-native</code> command can preview the actual
@@ -275,7 +275,7 @@ tweak them.</p>
 /usr/sbin/bhyve -c 2 -m 214 -A -I -H -P -s 0:0,hostbridge -s 3:0,virtio-ne=
t,tap0,mac=3D52:54:00:5d:74:e3 -s 2:0,virtio-blk,/home/user/vm1.img -s 1,lp=
c -l com1,/dev/nmdm0A vm1
 </pre>
=20
-<h3><a name=3D"zfsvolume">Using ZFS volumes</a></h3>
+<h3><a id=3D"zfsvolume">Using ZFS volumes</a></h3>
=20
 <p>It's possible to use ZFS volumes as disk devices <span class=3D"since">=
since 1.2.8</span>.
 An example of domain XML device entry for that will look like:</p>
@@ -291,7 +291,7 @@ An example of domain XML device entry for that will loo=
k like:</p>
 <p>Please refer to the <a href=3D"storage.html">Storage documentation</a> =
for more details on storage
 management.</p>
=20
-<h3><a name=3D"grubbhyve">Using grub2-bhyve or Alternative Bootloaders</a>=
</h3>
+<h3><a id=3D"grubbhyve">Using grub2-bhyve or Alternative Bootloaders</a></=
h3>
=20
 <p>It's possible to boot non-FreeBSD guests by specifying an explicit
 bootloader, e.g. <code>grub-bhyve(1)</code>. Arguments to the bootloader m=
ay be
@@ -312,7 +312,7 @@ attempt to boot from the first partition in the disk im=
age.</p>
 <p>Caveat: <code>bootloader_args</code> does not support any quoting.
 Filenames, etc, must not have spaces or they will be tokenized incorrectly=
.</p>
=20
-<h3><a name=3D"uefi">Using UEFI bootrom, VNC, and USB tablet</a></h3>
+<h3><a id=3D"uefi">Using UEFI bootrom, VNC, and USB tablet</a></h3>
=20
 <p><span class=3D"since">Since 3.2.0</span>, in addition to <a href=3D"#gr=
ubbhyve">grub-bhyve</a>,
 non-FreeBSD guests could be also booted using an UEFI boot ROM, provided b=
oth guest OS and
@@ -381,7 +381,7 @@ will be used. Please refer to the
 manual page and the <a href=3D"https://wiki.freebsd.org/bhyve">bhyve wiki<=
/a> for more details on using
 the <code>vgaconf</code> option.</p>
=20
-<h3><a name=3D"clockconfig">Clock configuration</a></h3>
+<h3><a id=3D"clockconfig">Clock configuration</a></h3>
=20
 <p>Originally bhyve supported only localtime for RTC. Support for UTC time=
 was introduced in
 <a href=3D"http://svnweb.freebsd.org/changeset/base/284894">r284894</a> fo=
r <i>10-STABLE</i> and
@@ -409,7 +409,7 @@ you'll need to explicitly specify 'localtime' in this c=
ase:</p>
 &lt;/domain&gt;
 </pre>
=20
-<h3><a name=3D"e1000">e1000 NIC</a></h3>
+<h3><a id=3D"e1000">e1000 NIC</a></h3>
=20
 <p>As of <a href=3D"https://svnweb.freebsd.org/changeset/base/302504">r302=
504</a> bhyve
 supports Intel e1000 network adapter emulation. It's supported in libvirt
diff --git a/docs/drvesx.html.in b/docs/drvesx.html.in
index 5ba7bc121..d503d65b8 100644
--- a/docs/drvesx.html.in
+++ b/docs/drvesx.html.in
@@ -11,7 +11,7 @@
         connect to a VMware vCenter 2.5/4.x/5.x (VPX).
     </p>
=20
-    <h2><a name=3D"project">Project Links</a></h2>
+    <h2><a id=3D"project">Project Links</a></h2>
=20
     <ul>
       <li>
@@ -20,7 +20,7 @@
       </li>
     </ul>
=20
-    <h2><a name=3D"prereq">Deployment pre-requisites</a></h2>
+    <h2><a id=3D"prereq">Deployment pre-requisites</a></h2>
     <p>
         None. Any out-of-the-box installation of VPX/ESX(i)/GSX should wor=
k. No
         preparations are required on the server side, no libvirtd must be
@@ -34,7 +34,7 @@
         VMware vSphere API</a>.
     </p>
=20
-    <h2><a name=3D"uri">Connections to the VMware ESX driver</a></h2>
+    <h2><a id=3D"uri">Connections to the VMware ESX driver</a></h2>
     <p>
         Some example remote connection URIs for the driver are:
     </p>
@@ -54,7 +54,7 @@ esx://example-esx.com/?no_verify=3D1     (ESX over HTTPS,=
 but doesn't verify the s
     </p>
=20
=20
-    <h3><a name=3D"uriformat">URI Format</a></h3>
+    <h3><a id=3D"uriformat">URI Format</a></h3>
     <p>
         URIs have this general form (<code>[...]</code> marks an optional =
part).
     </p>
@@ -93,7 +93,7 @@ vpx://example-vcenter.com/folder1/dc1/folder2/example-esx=
.com
 </pre>
=20
=20
-    <h4><a name=3D"extraparams">Extra parameters</a></h4>
+    <h4><a id=3D"extraparams">Extra parameters</a></h4>
     <p>
         Extra parameters can be added to a URI as part of the query string
         (the part following <code>?</code>). A single parameter is formed =
by a
@@ -188,7 +188,7 @@ vpx://example-vcenter.com/folder1/dc1/folder2/example-e=
sx.com
     </table>
=20
=20
-    <h3><a name=3D"auth">Authentication</a></h3>
+    <h3><a id=3D"auth">Authentication</a></h3>
     <p>
         In order to perform any useful operation the driver needs to log i=
nto
         the ESX server. Therefore, only <code>virConnectOpenAuth</code> ca=
n be
@@ -208,7 +208,7 @@ vpx://example-vcenter.com/folder1/dc1/folder2/example-e=
sx.com
     </p>
=20
=20
-    <h3><a name=3D"certificates">Certificates for HTTPS</a></h3>
+    <h3><a id=3D"certificates">Certificates for HTTPS</a></h3>
     <p>
         By default the ESX driver uses HTTPS to communicate with an ESX se=
rver.
         Proper HTTPS communication requires correctly configured SSL
@@ -244,7 +244,7 @@ error: internal error curl_easy_perform() returned an e=
rror: Peer certificate ca
     </ul>
=20
=20
-    <h3><a name=3D"connproblems">Connection problems</a></h3>
+    <h3><a id=3D"connproblems">Connection problems</a></h3>
     <p>
         There are also other causes for connection problems than the
         <a href=3D"#certificates">HTTPS certificate</a> related ones.
@@ -303,7 +303,7 @@ error: invalid argument in libvirt was built without th=
e 'esx' driver
     </ul>
=20
=20
-    <h2><a name=3D"questions">Questions blocking tasks</a></h2>
+    <h2><a id=3D"questions">Questions blocking tasks</a></h2>
     <p>
         Some methods of the VI API start tasks, for example
         <code>PowerOnVM_Task()</code>. Such tasks may be blocked by questi=
ons
@@ -322,12 +322,12 @@ error: invalid argument in libvirt was built without =
the 'esx' driver
     </p>
=20
=20
-    <h2><a name=3D"xmlspecial">Specialties in the domain XML config</a></h=
2>
+    <h2><a id=3D"xmlspecial">Specialties in the domain XML config</a></h2>
     <p>
         There are several specialties in the domain XML config for ESX dom=
ains.
     </p>
=20
-    <h3><a name=3D"restrictions">Restrictions</a></h3>
+    <h3><a id=3D"restrictions">Restrictions</a></h3>
     <p>
         There are some restrictions for some values of the domain XML conf=
ig.
         The driver will complain if this restrictions are violated.
@@ -347,7 +347,7 @@ error: invalid argument in libvirt was built without th=
e 'esx' driver
     </ul>
=20
=20
-    <h3><a name=3D"datastore">Datastore references</a></h3>
+    <h3><a id=3D"datastore">Datastore references</a></h3>
     <p>
         Storage is managed in datastores. VMware uses a special path forma=
t to
         reference files in a datastore. Basically, the datastore name is p=
ut
@@ -366,7 +366,7 @@ error: invalid argument in libvirt was built without th=
e 'esx' driver
     </p>
=20
=20
-    <h3><a name=3D"macaddresses">MAC addresses</a></h3>
+    <h3><a id=3D"macaddresses">MAC addresses</a></h3>
     <p>
         VMware has registered two MAC address prefixes for domains:
         <code>00:0c:29</code> and <code>00:50:56</code>. These prefixes are
@@ -427,7 +427,7 @@ ethernet0.checkMACAddress =3D "false"
 </pre>
=20
=20
-    <h3><a name=3D"hardware">Available hardware</a></h3>
+    <h3><a id=3D"hardware">Available hardware</a></h3>
     <p>
         VMware ESX supports different models of SCSI controllers and netwo=
rk
         cards.
@@ -523,14 +523,14 @@ ethernet0.checkMACAddress =3D "false"
 </pre>
=20
=20
-    <h2><a name=3D"importexport">Import and export of domain XML configs</=
a></h2>
+    <h2><a id=3D"importexport">Import and export of domain XML configs</a>=
</h2>
     <p>
         The ESX driver currently supports a native config format known as
         <code>vmware-vmx</code> to handle VMware VMX configs.
     </p>
=20
=20
-    <h3><a name=3D"xmlimport">Converting from VMware VMX config to domain =
XML config</a></h3>
+    <h3><a id=3D"xmlimport">Converting from VMware VMX config to domain XM=
L config</a></h3>
     <p>
         The <code>virsh domxml-from-native</code> provides a way to conver=
t an
         existing VMware VMX config into a domain XML config that can then =
be
@@ -621,7 +621,7 @@ Enter root password for example.com:
 </pre>
=20
=20
-    <h3><a name=3D"xmlexport">Converting from domain XML config to VMware =
VMX config</a></h3>
+    <h3><a id=3D"xmlexport">Converting from domain XML config to VMware VM=
X config</a></h3>
     <p>
       The <code>virsh domxml-to-native</code> provides a way to convert a
       domain XML config into a VMware VMX config.
@@ -675,7 +675,7 @@ ethernet0.address =3D "00:50:56:25:48:C7"
 </pre>
=20
=20
-    <h2><a name=3D"xmlconfig">Example domain XML configs</a></h2>
+    <h2><a id=3D"xmlconfig">Example domain XML configs</a></h2>
=20
     <h3>Fedora11 on x86_64</h3>
 <pre>
@@ -704,7 +704,7 @@ ethernet0.address =3D "00:50:56:25:48:C7"
 </pre>
=20
=20
-    <h2><a name=3D"migration">Migration</a></h2>
+    <h2><a id=3D"migration">Migration</a></h2>
     <p>
         A migration cannot be initiated on an ESX server directly, a VMware
         vCenter is necessary for this. The <code>vcenter</code> query
@@ -749,7 +749,7 @@ Enter administrator password for example-vcenter.com:
 </pre>
=20
=20
-    <h2><a name=3D"scheduler">Scheduler configuration</a></h2>
+    <h2><a id=3D"scheduler">Scheduler configuration</a></h2>
     <p>
         The driver exposes the ESX CPU scheduler. The parameters listed be=
low
         are available to control the scheduler.
@@ -780,7 +780,7 @@ Enter administrator password for example-vcenter.com:
     </dl>
=20
=20
-    <h2><a name=3D"tools">VMware tools</a></h2>
+    <h2><a id=3D"tools">VMware tools</a></h2>
     <p>
         Some actions require installed VMware tools. If the VMware tools a=
re
         not installed in the guest and one of the actions below is to be
@@ -796,7 +796,7 @@ Enter administrator password for example-vcenter.com:
     </ul>
=20
=20
-    <h2><a name=3D"links">Links</a></h2>
+    <h2><a id=3D"links">Links</a></h2>
     <ul>
         <li>
             <a href=3D"http://www.vmware.com/support/developer/vc-sdk/">
diff --git a/docs/drvhyperv.html.in b/docs/drvhyperv.html.in
index e87d8cbc1..ac2fa7017 100644
--- a/docs/drvhyperv.html.in
+++ b/docs/drvhyperv.html.in
@@ -9,7 +9,7 @@
     </p>
=20
=20
-    <h2><a name=3D"project">Project Links</a></h2>
+    <h2><a id=3D"project">Project Links</a></h2>
     <ul>
       <li>
         The <a href=3D"http://www.microsoft.com/hyper-v-server/">Microsoft=
 Hyper-V</a>
@@ -18,7 +18,7 @@
     </ul>
=20
=20
-    <h2><a name=3D"uri">Connections to the Microsoft Hyper-V driver</a></h=
2>
+    <h2><a id=3D"uri">Connections to the Microsoft Hyper-V driver</a></h2>
     <p>
         Some example remote connection URIs for the driver are:
     </p>
@@ -36,7 +36,7 @@ hyperv://example-hyperv.com/?transport=3Dhttp  (over HTTP)
     </p>
=20
=20
-    <h3><a name=3D"uriformat">URI Format</a></h3>
+    <h3><a id=3D"uriformat">URI Format</a></h3>
     <p>
         URIs have this general form (<code>[...]</code> marks an optional =
part).
     </p>
@@ -49,7 +49,7 @@ hyperv://[username@]hostname[:port]/[?extraparameters]
     </p>
=20
=20
-    <h4><a name=3D"extraparams">Extra parameters</a></h4>
+    <h4><a id=3D"extraparams">Extra parameters</a></h4>
     <p>
         Extra parameters can be added to a URI as part of the query string
         (the part following <code>?</code>). A single parameter is formed =
by a
@@ -83,7 +83,7 @@ hyperv://[username@]hostname[:port]/[?extraparameters]
     </table>
=20
=20
-    <h3><a name=3D"auth">Authentication</a></h3>
+    <h3><a id=3D"auth">Authentication</a></h3>
     <p>
         In order to perform any useful operation the driver needs to log i=
nto
         the Hyper-V server. Therefore, only <code>virConnectOpenAuth</code=
> can
diff --git a/docs/drvlxc.html.in b/docs/drvlxc.html.in
index c0c26ca35..180dc6834 100644
--- a/docs/drvlxc.html.in
+++ b/docs/drvlxc.html.in
@@ -18,7 +18,7 @@ particular sVirt for mandatory access control, auditing o=
f operations,
 integration with control groups and many other features.
 </p>
=20
-<h2><a name=3D"cgroups">Control groups Requirements</a></h2>
+<h2><a id=3D"cgroups">Control groups Requirements</a></h2>
=20
 <p>
 In order to control the resource usage of processes inside containers, the
@@ -32,7 +32,7 @@ init service will be required. For further information, c=
onsult the general
 libvirt <a href=3D"cgroups.html">cgroups documentation</a>.
 </p>
=20
-<h2><a name=3D"namespaces">Namespace requirements</a></h2>
+<h2><a id=3D"namespaces">Namespace requirements</a></h2>
=20
 <p>
 In order to separate processes inside a container from those in the
@@ -47,9 +47,9 @@ configured UID/GID mapping is a pre-requisite to making c=
ontainers
 secure, in the absence of sVirt confinement.</strong>
 </p>
=20
-<h2><a name=3D"init">Default container setup</a></h2>
+<h2><a id=3D"init">Default container setup</a></h2>
=20
-<h3><a name=3D"cliargs">Command line arguments</a></h3>
+<h3><a id=3D"cliargs">Command line arguments</a></h3>
=20
 <p>
 When the container "init" process is started, it will typically
@@ -70,7 +70,7 @@ would use the following XML
 &lt;/os&gt;
 </pre>
=20
-<h3><a name=3D"envvars">Environment variables</a></h3>
+<h3><a id=3D"envvars">Environment variables</a></h3>
=20
 <p>
 When the container "init" process is started, it will be given several use=
ful
@@ -108,7 +108,7 @@ Use of this is discouraged, in favour of passing argume=
nts directly to the
 container init process via the <code>initarg</code> config element.</dd>
 </dl>
=20
-<h3><a name=3D"fsmounts">Filesystem mounts</a></h3>
+<h3><a id=3D"fsmounts">Filesystem mounts</a></h3>
=20
 <p>
 In the absence of any explicit configuration, the container will
@@ -131,7 +131,7 @@ only expose the sub-tree associated with the container<=
/li>
 </ul>
=20
=20
-<h3><a name=3D"devnodes">Device nodes</a></h3>
+<h3><a id=3D"devnodes">Device nodes</a></h3>
=20
 <p>
 The container init process will be started with <code>CAP_MKNOD</code>
@@ -178,7 +178,7 @@ Further block or character devices will be made availab=
le to containers
 depending on their configuration.
 </p>
=20
-<h2><a name=3D"security">Security considerations</a></h2>
+<h2><a id=3D"security">Security considerations</a></h2>
=20
 <p>
 The libvirt LXC driver is fairly flexible in how it can be configured,
@@ -190,7 +190,7 @@ isolation between a container and the host must ensure =
that they are
 writing a suitable configuration.
 </p>
=20
-<h3><a name=3D"securenetworking">Network isolation</a></h3>
+<h3><a id=3D"securenetworking">Network isolation</a></h3>
=20
 <p>
 If the guest configuration does not list any network interfaces,
@@ -205,7 +205,7 @@ namespace is not wanted, then applications should set t=
he
 <code>&lt;features&gt;....&lt;/features&gt;</code> element.
 </p>
=20
-<h3><a name=3D"securefs">Filesystem isolation</a></h3>
+<h3><a id=3D"securefs">Filesystem isolation</a></h3>
=20
 <p>
 If the guest configuration does not list any filesystems, then
@@ -250,7 +250,7 @@ a bind mount to hide them. This is particularly importa=
nt for the
 </p>
=20
=20
-<h3><a name=3D"secureusers">User and group isolation</a></h3>
+<h3><a id=3D"secureusers">User and group isolation</a></h3>
=20
 <p>
 If the guest configuration does not list any ID mapping, then the
@@ -281,7 +281,7 @@ causes libvirt to activate the user namespace feature.
 </p>
=20
=20
-<h2><a name=3D"activation">Systemd Socket Activation Integration</a></h2>
+<h2><a id=3D"activation">Systemd Socket Activation Integration</a></h2>
=20
 <p>
 The libvirt LXC driver provides the ability to pass across pre-opened file
@@ -477,7 +477,7 @@ configured to block read/write/mknod from all devices e=
xcept those
 that a container is authorized to use.
 </p>
=20
-<h2><a name=3D"exconfig">Example configurations</a></h2>
+<h2><a id=3D"exconfig">Example configurations</a></h2>
=20
 <h3>Example config version 1</h3>
 <p></p>
@@ -542,7 +542,7 @@ debootstrap, whatever) under /opt/vm-1-root:
 &lt;/domain&gt;
 </pre>
=20
-<h2><a name=3D"capabilities">Altering the available capabilities</a></h2>
+<h2><a id=3D"capabilities">Altering the available capabilities</a></h2>
=20
 <p>
 By default the libvirt LXC driver drops some capabilities among which CAP_=
MKNOD.
@@ -590,7 +590,7 @@ Note that allowing capabilities that are normally dropp=
ed by default can serious
 affect the security of the container and the host.
 </p>
=20
-<h2><a name=3D"share">Inherit namespaces</a></h2>
+<h2><a id=3D"share">Inherit namespaces</a></h2>
=20
 <p>
 Libvirt allows you to inherit the namespace from container/process just li=
ke lxc tools
@@ -615,7 +615,7 @@ ignored.
 The use of namespace passthrough requires libvirt >=3D 1.2.19
 </p>
=20
-<h2><a name=3D"usage">Container usage / management</a></h2>
+<h2><a id=3D"usage">Container usage / management</a></h2>
=20
 <p>
 As with any libvirt virtualization driver, LXC containers can be
@@ -629,7 +629,7 @@ and LXC. For further details about usage of virsh consu=
lt its
 manual page.
 </p>
=20
-<h3><a name=3D"usageSave">Defining (saving) container configuration</a></h=
3>
+<h3><a id=3D"usageSave">Defining (saving) container configuration</a></h3>
=20
 <p>
 The <code>virsh define</code> command takes an XML configuration
@@ -640,7 +640,7 @@ document and loads it into libvirt, saving the configur=
ation on disk
 # virsh -c lxc:/// define myguest.xml
 </pre>
=20
-<h3><a name=3D"usageView">Viewing container configuration</a></h3>
+<h3><a id=3D"usageView">Viewing container configuration</a></h3>
=20
 <p>
 The <code>virsh dumpxml</code> command can be used to view the
@@ -655,7 +655,7 @@ using the <code>--inactive</code> flag
 # virsh -c lxc:/// dumpxml myguest
 </pre>
=20
-<h3><a name=3D"usageStart">Starting containers</a></h3>
+<h3><a id=3D"usageStart">Starting containers</a></h3>
=20
 <p>
 The <code>virsh start</code> command can be used to start a
@@ -677,7 +677,7 @@ by libvirt, using the <code>virsh create</code> command.
 </pre>
=20
=20
-<h3><a name=3D"usageStop">Stopping containers</a></h3>
+<h3><a id=3D"usageStop">Stopping containers</a></h3>
=20
 <p>
 The <code>virsh shutdown</code> command can be used
@@ -702,7 +702,7 @@ request, it can be forcibly stopped using the <code>vir=
sh destroy</code>
 </pre>
=20
=20
-<h3><a name=3D"usageReboot">Rebooting a container</a></h3>
+<h3><a id=3D"usageReboot">Rebooting a container</a></h3>
=20
 <p>
 The <code>virsh reboot</code> command can be used
@@ -717,7 +717,7 @@ to PID 1 inside the container.
 # virsh -c lxc:/// reboot myguest
 </pre>
=20
-<h3><a name=3D"usageDelete">Undefining (deleting) a container configuratio=
n</a></h3>
+<h3><a id=3D"usageDelete">Undefining (deleting) a container configuration<=
/a></h3>
=20
 <p>
 The <code>virsh undefine</code> command can be used to delete the
@@ -729,7 +729,7 @@ running, this will turn it into a "transient" guest.
 # virsh -c lxc:/// undefine myguest
 </pre>
=20
-<h3><a name=3D"usageConnect">Connecting to a container console</a></h3>
+<h3><a id=3D"usageConnect">Connecting to a container console</a></h3>
=20
 <p>
 The <code>virsh console</code> command can be used to connect
@@ -752,7 +752,7 @@ as 'console0', 'console1', 'console2', etc.
 # virsh -c lxc:/// console myguest --devname console1
 </pre>
=20
-<h3><a name=3D"usageEnter">Running commands in a container</a></h3>
+<h3><a id=3D"usageEnter">Running commands in a container</a></h3>
=20
 <p>
 The <code>virsh lxc-enter-namespace</code> command can be used
@@ -764,7 +764,7 @@ and then execute an arbitrary command.
 # virsh -c lxc:/// lxc-enter-namespace myguest -- /bin/ls -al /dev
 </pre>
=20
-<h3><a name=3D"usageTop">Monitoring container utilization</a></h3>
+<h3><a id=3D"usageTop">Monitoring container utilization</a></h3>
=20
 <p>
 The <code>virt-top</code> command can be used to monitor the
@@ -776,7 +776,7 @@ host
 # virt-top -c lxc:///
 </pre>
=20
-<h3><a name=3D"usageConvert">Converting LXC container configuration</a></h=
3>
+<h3><a id=3D"usageConvert">Converting LXC container configuration</a></h3>
=20
 <p>
 The <code>virsh domxml-from-native</code> command can be used to convert
diff --git a/docs/drvnodedev.html.in b/docs/drvnodedev.html.in
index 26c52dd0d..439bbe7d0 100644
--- a/docs/drvnodedev.html.in
+++ b/docs/drvnodedev.html.in
@@ -98,7 +98,7 @@
=20
     <ul id=3D"toc"/>
=20
-    <h2><a name=3D"PCI">PCI host devices</a></h2>
+    <h2><a id=3D"PCI">PCI host devices</a></h2>
     <dl>
       <dt><code>capability</code></dt>
       <dd>
@@ -139,7 +139,7 @@
       element will be included for each capability the device supports.
     </p>
=20
-    <h3><a name=3D"SRIOVCap">SR-IOV capability</a></h3>
+    <h3><a id=3D"SRIOVCap">SR-IOV capability</a></h3>
     <p>
       Single root input/output virtualization (SR-IOV) allows sharing of t=
he
       PCIe resources by multiple virtual environments. That is achieved by
@@ -186,7 +186,7 @@
 ...
 &lt;device&gt;</pre>
=20
-    <h3><a name=3D"MDEVCap">MDEV capability</a></h3>
+    <h3><a id=3D"MDEVCap">MDEV capability</a></h3>
     <p>
       A PCI device capable of creating mediated devices will include a nes=
ted
       capability <code>mdev_types</code> which enumerates all supported md=
ev
@@ -252,7 +252,7 @@
   &lt;/capability&gt;
 &lt;/device&gt;</pre>
=20
-    <h2><a name=3D"MDEV">Mediated devices (MDEVs)</a></h2>
+    <h2><a id=3D"MDEV">Mediated devices (MDEVs)</a></h2>
     <p>
       Mediated devices (<span class=3D"since">Since 3.2.0</span>) are soft=
ware
       devices defining resource allocation on the backing physical device =
which
diff --git a/docs/drvopenvz.html.in b/docs/drvopenvz.html.in
index e2e72e7a3..30e0c6b7e 100644
--- a/docs/drvopenvz.html.in
+++ b/docs/drvopenvz.html.in
@@ -15,7 +15,7 @@
     undue trouble.
     </p>
=20
-    <h2><a name=3D"project">Project Links</a></h2>
+    <h2><a id=3D"project">Project Links</a></h2>
=20
     <ul>
       <li>
@@ -24,7 +24,7 @@
       </li>
     </ul>
=20
-    <h2><a name=3D"connections">Connections to OpenVZ driver</a></h2>
+    <h2><a id=3D"connections">Connections to OpenVZ driver</a></h2>
=20
     <p>
     The libvirt OpenVZ driver is a single-instance privileged driver,
@@ -40,7 +40,7 @@ openvz+tcp://example.com/system      (remote access, SASl=
/Kerberos)
 openvz+ssh://root@example.com/system (remote access, SSH tunnelled)
 </pre>
=20
-    <h2><a name=3D"notes">Notes on bridged networking</a></h2>
+    <h2><a id=3D"notes">Notes on bridged networking</a></h2>
=20
     <p>
     Bridged networking enables a guest domain (ie container) to have its
@@ -49,7 +49,7 @@ openvz+ssh://root@example.com/system (remote access, SSH =
tunnelled)
     the host OS.
     </p>
=20
-    <h3><a name=3D"host">Host network devices</a></h3>
+    <h3><a id=3D"host">Host network devices</a></h3>
=20
     <p>
     One or more of the physical devices must be attached to a bridge. The
@@ -60,7 +60,7 @@ openvz+ssh://root@example.com/system (remote access, SSH =
tunnelled)
     physical device "eth0", or a bonding device "bond0".
     </p>
=20
-    <h3><a name=3D"tools">OpenVZ tools configuration</a></h3>
+    <h3><a id=3D"tools">OpenVZ tools configuration</a></h3>
=20
     <p>
     OpenVZ releases later than 3.0.23 ship with a standard network device
@@ -85,7 +85,7 @@ EXTERNAL_SCRIPT=3D"/usr/sbin/vznetaddbr"
     </p>
=20
=20
-    <h2><a name=3D"example">Example guest domain XML configuration</a></h2>
+    <h2><a id=3D"example">Example guest domain XML configuration</a></h2>
=20
     <p>
     The current libvirt OpenVZ driver has a restriction that the
diff --git a/docs/drvphyp.html.in b/docs/drvphyp.html.in
index bb1f69e51..c75a830c4 100644
--- a/docs/drvphyp.html.in
+++ b/docs/drvphyp.html.in
@@ -10,7 +10,7 @@
     </p>
=20
=20
-    <h2><a name=3D"project">Project Links</a></h2>
+    <h2><a id=3D"project">Project Links</a></h2>
     <ul>
       <li>
         The <a href=3D"http://www-03.ibm.com/systems/power/software/virtua=
lization/index.html">IBM
@@ -19,7 +19,7 @@
     </ul>
=20
=20
-    <h2><a name=3D"uri">Connections to the PowerVM driver</a></h2>
+    <h2><a id=3D"uri">Connections to the PowerVM driver</a></h2>
     <p>
         Some example remote connection URIs for the driver are:
     </p>
@@ -38,7 +38,7 @@ phyp://user@ivm/system (IVM connection)
     </p>
=20
=20
-    <h3><a name=3D"uriformat">URI Format</a></h3>
+    <h3><a id=3D"uriformat">URI Format</a></h3>
     <p>
         URIs have this general form (<code>[...]</code> marks an
         optional part, <code>{...|...}</code> marks a mandatory choice).
diff --git a/docs/drvqemu.html.in b/docs/drvqemu.html.in
index fa1eca78a..a2a830a23 100644
--- a/docs/drvqemu.html.in
+++ b/docs/drvqemu.html.in
@@ -11,7 +11,7 @@
       version 0.12.0 or later.
     </p>
=20
-    <h2><a name=3D"project">Project Links</a></h2>
+    <h2><a id=3D"project">Project Links</a></h2>
=20
     <ul>
       <li>
@@ -23,7 +23,7 @@
       </li>
     </ul>
=20
-    <h2><a name=3D"prereq">Deployment pre-requisites</a></h2>
+    <h2><a id=3D"prereq">Deployment pre-requisites</a></h2>
=20
     <ul>
       <li>
@@ -43,7 +43,7 @@
       </li>
     </ul>
=20
-    <h2><a name=3D"uris">Connections to QEMU driver</a></h2>
+    <h2><a id=3D"uris">Connections to QEMU driver</a></h2>
=20
     <p>
     The libvirt QEMU driver is a multi-instance driver, providing a single
@@ -63,14 +63,14 @@ qemu+tcp://example.com/system        (remote access, SA=
Sl/Kerberos)
 qemu+ssh://root@example.com/system   (remote access, SSH tunnelled)
 </pre>
=20
-    <h2><a name=3D"security">Driver security architecture</a></h2>
+    <h2><a id=3D"security">Driver security architecture</a></h2>
=20
     <p>
       There are multiple layers to security in the QEMU driver, allowing f=
or
       flexibility in the use of QEMU based virtual machines.
     </p>
=20
-    <h3><a name=3D"securitydriver">Driver instances</a></h3>
+    <h3><a id=3D"securitydriver">Driver instances</a></h3>
=20
     <p>
       As explained above there are two ways to access the QEMU driver
@@ -94,7 +94,7 @@ qemu+ssh://root@example.com/system   (remote access, SSH =
tunnelled)
       elevated privileges.
     </p>
=20
-    <h3><a name=3D"securitydac">POSIX users/groups</a></h3>
+    <h3><a id=3D"securitydac">POSIX users/groups</a></h3>
=20
     <p>
       In the "session" instance, the POSIX users/groups model restricts QE=
MU
@@ -187,7 +187,7 @@ chmod o+x /path/to/directory
       </li>
     </ul>
=20
-    <h3><a name=3D"securitycap">Linux process capabilities</a></h3>
+    <h3><a id=3D"securitycap">Linux process capabilities</a></h3>
=20
     <p>
       The libvirt QEMU driver has a build time option allowing it to use
@@ -224,7 +224,7 @@ chmod o+x /path/to/directory
       to changing the <code>/etc/libvirt/qemu.conf</code> settings.
     </p>
=20
-    <h3><a name=3D"securityselinux">SELinux basic confinement</a></h3>
+    <h3><a id=3D"securityselinux">SELinux basic confinement</a></h3>
=20
     <p>
       The basic SELinux protection for QEMU virtual machines is intended to
@@ -255,7 +255,7 @@ chmod o+x /path/to/directory
       SELinux boolean.
     </p>
=20
-    <h3><a name=3D"securitysvirt">SELinux sVirt confinement</a></h3>
+    <h3><a id=3D"securitysvirt">SELinux sVirt confinement</a></h3>
=20
     <p>
       The SELinux sVirt protection for QEMU virtual machines builds to the
@@ -305,7 +305,7 @@ chmod o+x /path/to/directory
       file can be used to change the setting to <code>security_driver=3D"n=
one"</code>
     </p>
=20
-    <h3><a name=3D"securitysvirtaa">AppArmor sVirt confinement</a></h3>
+    <h3><a id=3D"securitysvirtaa">AppArmor sVirt confinement</a></h3>
=20
     <p>
       When using basic AppArmor protection for the libvirtd daemon and
@@ -373,7 +373,7 @@ chmod o+x /path/to/directory
     </p>
=20
=20
-    <h3><a name=3D"securityacl">Cgroups device ACLs</a></h3>
+    <h3><a id=3D"securityacl">Cgroups device ACLs</a></h3>
=20
     <p>
       Recent Linux kernels have a capability known as "cgroups" which is u=
sed
@@ -416,7 +416,7 @@ mount -t cgroup none /dev/cgroup -o devices
       <code>/dev/cgroup/libvirt/qemu/$VMNAME/</code>
     </p>
=20
-    <h2><a name=3D"imex">Import and export of libvirt domain XML configs</=
a></h2>
+    <h2><a id=3D"imex">Import and export of libvirt domain XML configs</a>=
</h2>
=20
     <p>The QEMU driver currently supports a single native
       config format known as <code>qemu-argv</code>. The data for this for=
mat
@@ -424,7 +424,7 @@ mount -t cgroup none /dev/cgroup -o devices
       then the QEMu binary name, finally followed by the QEMU command line
       arguments</p>
=20
-    <h3><a name=3D"xmlimport">Converting from QEMU args to domain XML</a><=
/h3>
+    <h3><a id=3D"xmlimport">Converting from QEMU args to domain XML</a></h=
3>
=20
     <p>
       The <code>virsh domxml-from-native</code> provides a way to
@@ -473,7 +473,7 @@ $ virsh domxml-from-native qemu-argv demo.args
=20
     <p>NB, don't include the literal \ in the args, put everything on one =
line</p>
=20
-    <h3><a name=3D"xmlexport">Converting from domain XML to QEMU args</a><=
/h3>
+    <h3><a id=3D"xmlexport">Converting from domain XML to QEMU args</a></h=
3>
=20
     <p>
       The <code>virsh domxml-to-native</code> provides a way to convert a
@@ -515,7 +515,7 @@ $ virsh domxml-to-native qemu-argv demo.xml
   -serial none -parallel none -usb
 </pre>
=20
-    <h2><a name=3D"qemucommand">Pass-through of arbitrary qemu
+    <h2><a id=3D"qemucommand">Pass-through of arbitrary qemu
     commands</a></h2>
=20
     <p>Libvirt provides an XML namespace and an optional
@@ -582,7 +582,7 @@ $ virsh domxml-to-native qemu-argv demo.xml
 &lt;/domain&gt;
 </pre>
=20
-    <h2><a name=3D"xmlconfig">Example domain XML config</a></h2>
+    <h2><a id=3D"xmlconfig">Example domain XML config</a></h2>
=20
     <h3>QEMU emulated guest on x86_64</h3>
=20
diff --git a/docs/drvuml.html.in b/docs/drvuml.html.in
index 03c04eff4..832592024 100644
--- a/docs/drvuml.html.in
+++ b/docs/drvuml.html.in
@@ -13,7 +13,7 @@
     has pre-created TAP devices.
     </p>
=20
-    <h2><a name=3D"project">Project Links</a></h2>
+    <h2><a id=3D"project">Project Links</a></h2>
=20
     <ul>
       <li>
diff --git a/docs/drvvbox.html.in b/docs/drvvbox.html.in
index 4888dd266..d6ed6aabf 100644
--- a/docs/drvvbox.html.in
+++ b/docs/drvvbox.html.in
@@ -8,7 +8,7 @@
         from version 2.2 onwards.
     </p>
=20
-    <h2><a name=3D"project">Project Links</a></h2>
+    <h2><a id=3D"project">Project Links</a></h2>
=20
     <ul>
       <li>
@@ -43,7 +43,7 @@ vbox+ssh://user@example.com/session  (remote access, SSH =
tunnelled)
         work is completed to get the libvirtd daemon working there.</stron=
g>
     </p>
=20
-    <h2><a name=3D"xmlconfig">Example domain XML config</a></h2>
+    <h2><a id=3D"xmlconfig">Example domain XML config</a></h2>
=20
 <pre>
 &lt;domain type=3D'vbox'&gt;
diff --git a/docs/drvvirtuozzo.html.in b/docs/drvvirtuozzo.html.in
index 28c8242a1..3c4a85fe0 100644
--- a/docs/drvvirtuozzo.html.in
+++ b/docs/drvvirtuozzo.html.in
@@ -9,7 +9,7 @@
     </p>
=20
=20
-    <h2><a name=3D"project">Project Links</a></h2>
+    <h2><a id=3D"project">Project Links</a></h2>
     <ul>
       <li>
         The <a href=3D"http://www.odin.com/products/virtuozzo/">Virtuozzo<=
/a> Solution.
@@ -17,7 +17,7 @@
     </ul>
=20
=20
-    <h2><a name=3D"uri">Connections to the Virtuozzo driver</a></h2>
+    <h2><a id=3D"uri">Connections to the Virtuozzo driver</a></h2>
     <p>
         The libvirt Virtuozzo driver is a single-instance privileged drive=
r, with a driver name of 'virtuozzo'. Some example connection URIs for the =
libvirt driver are:
     </p>
@@ -29,7 +29,7 @@ vz+tcp://example.com/system      (remote access, SASl/Ker=
beros)
 vz+ssh://root@example.com/system (remote access, SSH tunnelled)
 </pre>
=20
-    <h2><a name=3D"example">Example guest domain XML configuration</a></h2>
+    <h2><a id=3D"example">Example guest domain XML configuration</a></h2>
=20
     <p>
     Virtuozzo driver require at least one hard disk for new domains
diff --git a/docs/drvvmware.html.in b/docs/drvvmware.html.in
index 240afd005..45f6fe261 100644
--- a/docs/drvvmware.html.in
+++ b/docs/drvvmware.html.in
@@ -15,7 +15,7 @@
     from <a href=3D"http://www.vmware.com/support/developer/vix-api/">here=
</a>.
     </p>
=20
-    <h2><a name=3D"project">Project Links</a></h2>
+    <h2><a id=3D"project">Project Links</a></h2>
=20
     <ul>
       <li>
@@ -51,7 +51,7 @@ vmwarews+tcp://user@example.com/session  (remote access t=
o VMware Workstation, S
 vmwarews+ssh://user@example.com/session  (remote access to VMware Workstat=
ion, SSH tunnelled)
 </pre>
=20
-    <h2><a name=3D"xmlconfig">Example domain XML config</a></h2>
+    <h2><a id=3D"xmlconfig">Example domain XML config</a></h2>
=20
 <pre>
 &lt;domain type=3D'vmware'&gt;
diff --git a/docs/drvxen.html.in b/docs/drvxen.html.in
index 649ba42bf..6af15f44b 100644
--- a/docs/drvxen.html.in
+++ b/docs/drvxen.html.in
@@ -11,7 +11,7 @@
       on any Xen release from 3.0.1 onwards.
     </p>
=20
-    <h2><a name=3D"project">Project Links</a></h2>
+    <h2><a id=3D"project">Project Links</a></h2>
=20
     <ul>
       <li>
@@ -20,7 +20,7 @@
       </li>
     </ul>
=20
-    <h2><a name=3D"prereq">Deployment pre-requisites</a></h2>
+    <h2><a id=3D"prereq">Deployment pre-requisites</a></h2>
=20
     <p>
       The libvirt Xen driver uses a combination of channels to manage Xen
@@ -65,7 +65,7 @@
       </li>
     </ul>
=20
-    <h2><a name=3D"uri">Connections to Xen driver</a></h2>
+    <h2><a id=3D"uri">Connections to Xen driver</a></h2>
=20
     <p>
     The libvirt Xen driver is a single-instance privileged driver,
@@ -81,7 +81,7 @@ xen+tcp://example.com/         (remote access, SASl/Kerbe=
ros)
 xen+ssh://root@example.com/    (remote access, SSH tunnelled)
 </pre>
=20
-    <h2><a name=3D"imex">Import and export of libvirt domain XML configs</=
a></h2>
+    <h2><a id=3D"imex">Import and export of libvirt domain XML configs</a>=
</h2>
=20
     <p>The Xen driver currently supports two native
       config formats. The first known as <code>xen-xm</code> is the format
@@ -89,7 +89,7 @@ xen+ssh://root@example.com/    (remote access, SSH tunnel=
led)
       known as <code>xen-sxpr</code>, is the format used for interacting
       with the XenD's legacy HTTP RPC service.</p>
=20
-    <h3><a name=3D"xmlimport">Converting from XM config files to domain XM=
L</a></h3>
+    <h3><a id=3D"xmlimport">Converting from XM config files to domain XML<=
/a></h3>
=20
     <p>
       The <code>virsh domxml-from-native</code> provides a way to convert =
an
@@ -135,7 +135,7 @@ xen+ssh://root@example.com/    (remote access, SSH tunn=
elled)
   &lt;/devices&gt;
 &lt;/domain&gt;</pre>
=20
-    <h3><a name=3D"xmlexport">Converting from domain XML to XM config file=
s</a></h3>
+    <h3><a id=3D"xmlexport">Converting from domain XML to XM config files<=
/a></h3>
=20
     <p>
       The <code>virsh domxml-to-native</code> provides a way to convert a
@@ -163,7 +163,7 @@ vnclisten =3D "0.0.0.0"
 disk =3D [ "tap:aio:/var/lib/xen/images/rhel5pv.img,xvda,w", "tap:qcow:/ro=
ot/qcow1-xen.img,xvdd,w" ]
 vif =3D [ "mac=3D00:16:3e:60:36:ba,bridge=3Dvirbr0,script=3Dvif-bridge,vif=
name=3Dvif5.0" ]</pre>
=20
-    <h2><a name=3D"xmlconfig">Example domain XML config</a></h2>
+    <h2><a id=3D"xmlconfig">Example domain XML config</a></h2>
=20
     <p>
       Below are some example XML configurations for Xen guest domains.
diff --git a/docs/firewall.html.in b/docs/firewall.html.in
index 5bb6dc143..b21891ac9 100644
--- a/docs/firewall.html.in
+++ b/docs/firewall.html.in
@@ -35,8 +35,7 @@
       </li>
     </ul>
=20
-    <h3><a name=3D"name-fw-virtual-network-driver"
-           id=3D"id-fw-virtual-network-driver">The virtual network driver<=
/a>
+    <h3><a id=3D"fw-virtual-network-driver">The virtual network driver</a>
     </h3>
     <p>The typical configuration for guests is to use bridging of the
        physical NIC on the host to connect the guest directly to the LAN.
@@ -130,8 +129,7 @@ MASQUERADE all  --  *      *       192.168.122.0/24    =
!192.168.122.0/24</pre>
       </li>
     </ul>
=20
-    <h3><a name=3D"name-fw-network-filter-driver"
-           id=3D"id-fw-network-filter-driver">The network filter driver</a>
+    <h3><a id=3D"fw-network-filter-driver">The network filter driver</a>
     </h3>
     <p>This driver provides a fully configurable network filtering capabil=
ity
        that leverages ebtables, iptables and ip6tables. This was written by
diff --git a/docs/formatcaps.html.in b/docs/formatcaps.html.in
index bc4511c66..d224523ef 100644
--- a/docs/formatcaps.html.in
+++ b/docs/formatcaps.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"elements">Element and attribute overview</a></h2>
+    <h2><a id=3D"elements">Element and attribute overview</a></h2>
=20
     <p>As new virtualization engine support gets added to libvirt, and to
     handle cases like QEMU supporting a variety of emulations, a query
@@ -28,7 +28,7 @@
     the set of architectures the host can run at the moment.</p>
=20
=20
-    <h3><a name=3D"elementHost">Host capabilities</a></h3>
+    <h3><a id=3D"elementHost">Host capabilities</a></h3>
=20
     <p>The <code>&lt;host/&gt;</code> element consists of the following ch=
ild
     elements:</p>
@@ -61,7 +61,7 @@
     </dl>
=20
=20
-    <h3><a name=3D"elementGuest">Guest capabilities</a></h3>
+    <h3><a id=3D"elementGuest">Guest capabilities</a></h3>
=20
     <p>While the <a href=3D"#elementHost">previous section</a> aims at host
     capabilities, this one focuses on capabilities available to a guest
@@ -138,7 +138,7 @@
         </dd>
     </dl>
=20
-    <h3><a name=3D"elementExamples">Examples</a></h3>
+    <h3><a id=3D"elementExamples">Examples</a></h3>
=20
     <p>For example, in the case of a 64-bit machine with hardware
     virtualization capabilities enabled in the chip and
diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
index bceddd2aa..fb22dd1db 100644
--- a/docs/formatdomain.html.in
+++ b/docs/formatdomain.html.in
@@ -14,7 +14,7 @@
     </p>
=20
=20
-    <h2><a name=3D"elements">Element and attribute overview</a></h2>
+    <h2><a id=3D"elements">Element and attribute overview</a></h2>
=20
     <p>
       The root element required for all virtual machines is
@@ -28,7 +28,7 @@
     </p>
=20
=20
-    <h3><a name=3D"elementsMetadata">General metadata</a></h3>
+    <h3><a id=3D"elementsMetadata">General metadata</a></h3>
=20
 <pre>
 &lt;domain type=3D'xen' id=3D'3'&gt;
@@ -82,14 +82,14 @@
         element). <span class=3D"since">Since 0.9.10</span></dd>
    </dl>
=20
-    <h3><a name=3D"elementsOS">Operating system booting</a></h3>
+    <h3><a id=3D"elementsOS">Operating system booting</a></h3>
=20
     <p>
       There are a number of different ways to boot virtual machines
       each with their own pros and cons.
     </p>
=20
-    <h4><a name=3D"elementsOSBIOS">BIOS bootloader</a></h4>
+    <h4><a id=3D"elementsOSBIOS">BIOS bootloader</a></h4>
=20
     <p>
       Booting via the BIOS is available for hypervisors supporting
@@ -229,7 +229,7 @@
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsOSBootloader">Host bootloader</a></h4>
+    <h4><a id=3D"elementsOSBootloader">Host bootloader</a></h4>
=20
     <p>
       Hypervisors employing paravirtualization do not usually emulate
@@ -262,7 +262,7 @@
=20
     </dl>
=20
-    <h4><a name=3D"elementsOSKernel">Direct kernel boot</a></h4>
+    <h4><a id=3D"elementsOSKernel">Direct kernel boot</a></h4>
=20
     <p>
       When installing a new guest OS it is often useful to boot directly
@@ -315,7 +315,7 @@
         <span class=3D"since">Since 1.3.5 (QEMU only)</span></dd>
     </dl>
=20
-    <h4><a name=3D"elementsOSContainer">Container boot</a></h4>
+    <h4><a id=3D"elementsOSContainer">Container boot</a></h4>
=20
     <p>
       When booting a domain using container based virtualization, instead
@@ -379,7 +379,7 @@
     </pre>
=20
=20
-    <h3><a name=3D"elementsSysinfo">SMBIOS System Information</a></h3>
+    <h3><a id=3D"elementsSysinfo">SMBIOS System Information</a></h3>
=20
     <p>
       Some hypervisors allow control over what system information is
@@ -502,7 +502,7 @@
       </dd>
     </dl>
=20
-    <h3><a name=3D"elementsCPUAllocation">CPU Allocation</a></h3>
+    <h3><a id=3D"elementsCPUAllocation">CPU Allocation</a></h3>
=20
 <pre>
 &lt;domain&gt;
@@ -610,7 +610,7 @@
       </dd>
     </dl>
=20
-    <h3><a name=3D"elementsIOThreadsAllocation">IOThreads Allocation</a></=
h3>
+    <h3><a id=3D"elementsIOThreadsAllocation">IOThreads Allocation</a></h3>
       <p>
         IOThreads are dedicated event loop threads for supported disk
         devices to perform block I/O requests in order to improve
@@ -667,7 +667,7 @@
        </dd>
     </dl>
=20
-    <h3><a name=3D"elementsCPUTuning">CPU Tuning</a></h3>
+    <h3><a id=3D"elementsCPUTuning">CPU Tuning</a></h3>
=20
 <pre>
 &lt;domain&gt;
@@ -837,7 +837,7 @@
     </dl>
=20
=20
-    <h3><a name=3D"elementsMemoryAllocation">Memory Allocation</a></h3>
+    <h3><a id=3D"elementsMemoryAllocation">Memory Allocation</a></h3>
=20
 <pre>
 &lt;domain&gt;
@@ -910,7 +910,7 @@
     </dl>
=20
=20
-    <h3><a name=3D"elementsMemoryBacking">Memory Backing</a></h3>
+    <h3><a id=3D"elementsMemoryBacking">Memory Backing</a></h3>
=20
 <pre>
 &lt;domain&gt;
@@ -980,7 +980,7 @@
     </dl>
=20
=20
-    <h3><a name=3D"elementsMemoryTuning">Memory Tuning</a></h3>
+    <h3><a id=3D"elementsMemoryTuning">Memory Tuning</a></h3>
=20
 <pre>
 &lt;domain&gt;
@@ -1044,7 +1044,7 @@
     </dl>
=20
=20
-    <h3><a name=3D"elementsNUMATuning">NUMA Node Tuning</a></h3>
+    <h3><a id=3D"elementsNUMATuning">NUMA Node Tuning</a></h3>
=20
 <pre>
 &lt;domain&gt;
@@ -1105,7 +1105,7 @@
     </dl>
=20
=20
-    <h3><a name=3D"elementsBlockTuning">Block I/O Tuning</a></h3>
+    <h3><a id=3D"elementsBlockTuning">Block I/O Tuning</a></h3>
 <pre>
 &lt;domain&gt;
   ...
@@ -1174,7 +1174,7 @@
       </dl></dd></dl>
=20
=20
-    <h3><a name=3D"resPartition">Resource partitioning</a></h3>
+    <h3><a id=3D"resPartition">Resource partitioning</a></h3>
=20
     <p>
       Hypervisors may allow for virtual machines to be placed into
@@ -1203,7 +1203,7 @@
       in all mounted controllers. <span class=3D"since">Since 1.0.5</span>
     </p>
=20
-    <h3><a name=3D"elementsCPU">CPU model and topology</a></h3>
+    <h3><a id=3D"elementsCPU">CPU model and topology</a></h3>
=20
     <p>
       Requirements for CPU model, its features and topology can be specifi=
ed
@@ -1532,7 +1532,7 @@
       This guest NUMA specification is currently available only for QEMU/K=
VM.
     </p>
=20
-    <h3><a name=3D"elementsEvents">Events configuration</a></h3>
+    <h3><a id=3D"elementsEvents">Events configuration</a></h3>
=20
     <p>
       It is sometimes necessary to override the default actions taken
@@ -1643,7 +1643,7 @@
       <dd>Keep the domain running as if nothing happened.</dd>
     </dl>
=20
-    <h3><a name=3D"elementsPowerManagement">Power Management</a></h3>
+    <h3><a id=3D"elementsPowerManagement">Power Management</a></h3>
=20
     <p>
       <span class=3D"since">Since 0.10.2</span> it is possible to
@@ -1667,7 +1667,7 @@
         left with its default value.</dd>
     </dl>
=20
-    <h3><a name=3D"elementsFeatures">Hypervisor features</a></h3>
+    <h3><a id=3D"elementsFeatures">Hypervisor features</a></h3>
=20
     <p>
       Hypervisors may allow certain CPU / machine features to be
@@ -1869,7 +1869,7 @@
       </dd>
     </dl>
=20
-    <h3><a name=3D"elementsTime">Time keeping</a></h3>
+    <h3><a id=3D"elementsTime">Time keeping</a></h3>
=20
     <p>
       The guest clock is typically initialized from the host clock.
@@ -2037,7 +2037,7 @@
       </dd>
     </dl>
=20
-    <h3><a name=3D"elementsPerf">Performance monitoring events</a></h3>
+    <h3><a id=3D"elementsPerf">Performance monitoring events</a></h3>
=20
     <p>
       Some platforms allow monitoring of performance of the virtual machin=
e and
@@ -2218,7 +2218,7 @@
     </tr>
   </table>
=20
-    <h3><a name=3D"elementsDevices">Devices</a></h3>
+    <h3><a id=3D"elementsDevices">Devices</a></h3>
=20
     <p>
       The final set of XML elements are all used to describe devices
@@ -2245,7 +2245,7 @@
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsDisks">Hard drives, floppy disks, CDROMs</a></h=
4>
+    <h4><a id=3D"elementsDisks">Hard drives, floppy disks, CDROMs</a></h4>
=20
     <p>
       Any device that looks like a disk, be it a floppy, harddisk,
@@ -3185,7 +3185,7 @@
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsFilesystems">Filesystems</a></h4>
+    <h4><a id=3D"elementsFilesystems">Filesystems</a></h4>
=20
     <p>
       A directory on the host that can be accessed directly from the guest.
@@ -3368,7 +3368,7 @@
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsAddress">Device Addresses</a></h4>
+    <h4><a id=3D"elementsAddress">Device Addresses</a></h4>
=20
     <p>
       Many devices have an optional <code>&lt;address&gt;</code>
@@ -3485,7 +3485,7 @@
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsVirtio">Virtio-related options</a></h4>
+    <h4><a id=3D"elementsVirtio">Virtio-related options</a></h4>
=20
     <p>
       QEMU's virtio devices have some attributes related to the virtio tra=
nsport under
@@ -3498,7 +3498,7 @@
       <span class=3D"since">Since 3.5.0</span>
     </p>
=20
-    <h4><a name=3D"elementsControllers">Controllers</a></h4>
+    <h4><a id=3D"elementsControllers">Controllers</a></h4>
=20
     <p>
       Depending on the guest architecture, some device buses can
@@ -3884,7 +3884,7 @@
 &lt;/devices&gt;
 ...</pre>
=20
-    <h4><a name=3D"elementsLease">Device leases</a></h4>
+    <h4><a id=3D"elementsLease">Device leases</a></h4>
=20
     <p>
       When using a lock manager, it may be desirable to record device leas=
es
@@ -3924,9 +3924,9 @@
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsHostDev">Host device assignment</a></h4>
+    <h4><a id=3D"elementsHostDev">Host device assignment</a></h4>
=20
-    <h5><a name=3D"elementsHostDevSubsys">USB / PCI / SCSI devices</a></h5>
+    <h5><a id=3D"elementsHostDevSubsys">USB / PCI / SCSI devices</a></h5>
=20
     <p>
       USB, PCI and SCSI devices attached to the host can be passed through
@@ -4237,7 +4237,7 @@
     </dl>
=20
=20
-    <h5><a name=3D"elementsHostDevCaps">Block / character devices</a></h5>
+    <h5><a id=3D"elementsHostDevCaps">Block / character devices</a></h5>
=20
     <p>
       Block / character devices from the host can be passed through
@@ -4294,7 +4294,7 @@
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsRedir">Redirected devices</a></h4>
+    <h4><a id=3D"elementsRedir">Redirected devices</a></h4>
=20
     <p>
       USB device redirection through a character device is
@@ -4361,7 +4361,7 @@
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsSmartcard">Smartcard devices</a></h4>
+    <h4><a id=3D"elementsSmartcard">Smartcard devices</a></h4>
=20
     <p>
       A virtual smartcard device can be supplied to the guest via the
@@ -4454,7 +4454,7 @@
       smartcard, with an address of bus=3D0 slot=3D0.
     </p>
=20
-    <h4><a name=3D"elementsNICS">Network interfaces</a></h4>
+    <h4><a id=3D"elementsNICS">Network interfaces</a></h4>
=20
 <pre>
 ...
@@ -4494,7 +4494,7 @@
       as <a href=3D"#elementsAddress">documented above</a>.
     </p>
=20
-    <h5><a name=3D"elementsNICSVirtual">Virtual network</a></h5>
+    <h5><a id=3D"elementsNICSVirtual">Virtual network</a></h5>
=20
     <p>
       <strong><em>
@@ -4600,7 +4600,7 @@
 &lt;/devices&gt;
 ...</pre>
=20
-    <h5><a name=3D"elementsNICSBridge">Bridge to LAN</a></h5>
+    <h5><a id=3D"elementsNICSBridge">Bridge to LAN</a></h5>
=20
     <p>
       <strong><em>
@@ -4691,7 +4691,7 @@
 &lt;/devices&gt;
 ...</pre>
=20
-    <h5><a name=3D"elementsNICSSlirp">Userspace SLIRP stack</a></h5>
+    <h5><a id=3D"elementsNICSSlirp">Userspace SLIRP stack</a></h5>
=20
     <p>
       Provides a virtual LAN with NAT to the outside world. The virtual
@@ -4714,7 +4714,7 @@
 ...</pre>
=20
=20
-    <h5><a name=3D"elementsNICSEthernet">Generic ethernet connection</a></=
h5>
+    <h5><a id=3D"elementsNICSEthernet">Generic ethernet connection</a></h5>
=20
     <p>
       Provides a means for the administrator to execute an arbitrary script
@@ -4738,7 +4738,7 @@
 &lt;/devices&gt;
 ...</pre>
=20
-    <h5><a name=3D"elementsNICSDirect">Direct attachment to physical inter=
face</a></h5>
+    <h5><a id=3D"elementsNICSDirect">Direct attachment to physical interfa=
ce</a></h5>
=20
     <p>
       Provides direct attachment of the virtual machine's NIC to the given
@@ -4883,7 +4883,7 @@
 </pre>
=20
=20
-    <h5><a name=3D"elementsNICSHostdev">PCI Passthrough</a></h5>
+    <h5><a id=3D"elementsNICSHostdev">PCI Passthrough</a></h5>
=20
     <p>
       A PCI network device (specified by the &lt;source&gt; element)
@@ -4956,7 +4956,7 @@
 ...</pre>
=20
=20
-    <h5><a name=3D"elementsNICSMulticast">Multicast tunnel</a></h5>
+    <h5><a id=3D"elementsNICSMulticast">Multicast tunnel</a></h5>
=20
     <p>
       A multicast group is setup to represent a virtual network. Any VMs
@@ -4980,7 +4980,7 @@
 &lt;/devices&gt;
 ...</pre>
=20
-    <h5><a name=3D"elementsNICSTCP">TCP tunnel</a></h5>
+    <h5><a id=3D"elementsNICSTCP">TCP tunnel</a></h5>
=20
     <p>
       A TCP client/server architecture provides a virtual network. One VM
@@ -5006,7 +5006,7 @@
 &lt;/devices&gt;
 ...</pre>
=20
-    <h5><a name=3D"elementsNICSUDP">UDP unicast tunnel</a></h5>
+    <h5><a id=3D"elementsNICSUDP">UDP unicast tunnel</a></h5>
=20
     <p>
     A UDP unicast architecture provides a virtual network which enables
@@ -5030,7 +5030,7 @@
 &lt;/devices&gt;
 ...</pre>
=20
-    <h5><a name=3D"elementsNICSModel">Setting the NIC model</a></h5>
+    <h5><a id=3D"elementsNICSModel">Setting the NIC model</a></h5>
=20
 <pre>
 ...
@@ -5065,7 +5065,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       ne2k_isa i82551 i82557b i82559er ne2k_pci pcnet rtl8139 e1000 virtio
     </p>
=20
-    <h5><a name=3D"elementsDriverBackendOptions">Setting NIC driver-specif=
ic options</a></h5>
+    <h5><a id=3D"elementsDriverBackendOptions">Setting NIC driver-specific=
 options</a></h5>
=20
 <pre>
 ...
@@ -5240,7 +5240,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       </dd>
     </dl>
=20
-    <h5><a name=3D"elementsBackendOptions">Setting network backend-specifi=
c options</a></h5>
+    <h5><a id=3D"elementsBackendOptions">Setting network backend-specific =
options</a></h5>
=20
 <pre>
 ...
@@ -5271,7 +5271,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       adjust the size of send buffer in the host. <span class=3D"since">Si=
nce
       0.8.8</span>
     </p>
-    <h5><a name=3D"elementsNICSTargetOverride">Overriding the target eleme=
nt</a></h5>
+    <h5><a id=3D"elementsNICSTargetOverride">Overriding the target element=
</a></h5>
=20
 <pre>
 ...
@@ -5309,7 +5309,7 @@ qemu-kvm -net nic,model=3D? /dev/null
 &lt;/devices&gt;
 ...</pre>
=20
-    <h5><a name=3D"elementsNICSBoot">Specifying boot order</a></h5>
+    <h5><a id=3D"elementsNICSBoot">Specifying boot order</a></h5>
=20
 <pre>
 ...
@@ -5332,7 +5332,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       <span class=3D"since">Since 0.8.8</span>
     </p>
=20
-    <h5><a name=3D"elementsNICSROM">Interface ROM BIOS configuration</a></=
h5>
+    <h5><a id=3D"elementsNICSROM">Interface ROM BIOS configuration</a></h5>
=20
 <pre>
 ...
@@ -5361,7 +5361,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       network device.
       <span class=3D"since">Since 0.9.10 (QEMU and KVM only)</span>.
     </p>
-    <h5><a name=3D"elementDomain">Setting up a network backend in a driver=
 domain</a></h5>
+    <h5><a id=3D"elementDomain">Setting up a network backend in a driver d=
omain</a></h5>
 <pre>
 ...
 &lt;devices&gt;
@@ -5385,7 +5385,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       <span class=3D"since">Since 1.2.13 (Xen only)</span>
     </p>
=20
-    <h5><a name=3D"elementQoS">Quality of service</a></h5>
+    <h5><a id=3D"elementQoS">Quality of service</a></h5>
=20
 <pre>
 ...
@@ -5409,7 +5409,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       the Network XML.
     </p>
=20
-    <h5><a name=3D"elementVlanTag">Setting VLAN tag (on supported network =
types only)</a></h5>
+    <h5><a id=3D"elementVlanTag">Setting VLAN tag (on supported network ty=
pes only)</a></h5>
=20
 <pre>
 ...
@@ -5477,7 +5477,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       traffic for that VLAN will be tagged.
     </p>
=20
-    <h5><a name=3D"elementLink">Modifying virtual link state</a></h5>
+    <h5><a id=3D"elementLink">Modifying virtual link state</a></h5>
 <pre>
 ...
 &lt;devices&gt;
@@ -5498,7 +5498,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       <span class=3D"since">Since 0.9.5</span>
     </p>
=20
-    <h5><a name=3D"mtu">MTU configuration</a></h5>
+    <h5><a id=3D"mtu">MTU configuration</a></h5>
 <pre>
 ...
 &lt;devices&gt;
@@ -5517,7 +5517,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       <span class=3D"since">Since 3.1.0</span>
     </p>
=20
-    <h5><a name=3D"coalesce">Coalesce settings</a></h5>
+    <h5><a id=3D"coalesce">Coalesce settings</a></h5>
 <pre>
 ...
 &lt;devices&gt;
@@ -5544,7 +5544,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       <span class=3D"since">Since 3.3.0</span>
     </p>
=20
-    <h5><a name=3D"ipconfig">IP configuration</a></h5>
+    <h5><a id=3D"ipconfig">IP configuration</a></h5>
 <pre>
 ...
 &lt;devices&gt;
@@ -5623,7 +5623,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       configure the guest side of the interface (described above).
     </p>
=20
-    <h5><a name=3D"elementVhostuser">vhost-user interface</a></h5>
+    <h5><a id=3D"elementVhostuser">vhost-user interface</a></h5>
=20
     <p>
     <span class=3D"since">Since 1.2.7</span> the vhost-user enables the
@@ -5660,7 +5660,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       <code>&lt;model&gt;</code> element is mandatory.
     </p>
=20
-    <h5><a name=3D"elementNwfilter">Traffic filtering with NWFilter</a></h=
5>
+    <h5><a id=3D"elementNwfilter">Traffic filtering with NWFilter</a></h5>
=20
     <p>
     <span class=3D"since">Since 0.8.0</span> an <code>nwfilter</code> prof=
ile
@@ -5700,7 +5700,7 @@ qemu-kvm -net nic,model=3D? /dev/null
     </p>
=20
=20
-    <h4><a name=3D"elementsInput">Input devices</a></h4>
+    <h4><a id=3D"elementsInput">Input devices</a></h4>
=20
     <p>
       Input devices allow interaction with the graphical framebuffer
@@ -5755,7 +5755,7 @@ qemu-kvm -net nic,model=3D? /dev/null
         set. (<span class=3D"since">Since 3.5.0</span>)
     </p>
=20
-    <h4><a name=3D"elementsHub">Hub devices</a></h4>
+    <h4><a id=3D"elementsHub">Hub devices</a></h4>
=20
     <p>
       A hub is a device that expands a single port into several so
@@ -5784,7 +5784,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       above</a>.
     </p>
=20
-    <h4><a name=3D"elementsGraphics">Graphical framebuffers</a></h4>
+    <h4><a id=3D"elementsGraphics">Graphical framebuffers</a></h4>
=20
     <p>
       A graphics device allows for graphical interaction with the
@@ -6082,7 +6082,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsVideo">Video devices</a></h4>
+    <h4><a id=3D"elementsVideo">Video devices</a></h4>
     <p>
       A video device.
     </p>
@@ -6197,7 +6197,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsConsole">Consoles, serial, parallel &amp; chann=
el devices</a></h4>
+    <h4><a id=3D"elementsConsole">Consoles, serial, parallel &amp; channel=
 devices</a></h4>
=20
     <p>
       A character device provides a way to interact with the virtual machi=
ne.
@@ -6283,14 +6283,14 @@ qemu-kvm -net nic,model=3D? /dev/null
       slot.
     </p>
=20
-    <h5><a name=3D"elementsCharGuestInterface">Guest interface</a></h5>
+    <h5><a id=3D"elementsCharGuestInterface">Guest interface</a></h5>
=20
     <p>
       A character device presents itself to the guest as one of the follow=
ing
       types.
     </p>
=20
-    <h6><a name=3D"elementCharParallel">Parallel port</a></h6>
+    <h6><a id=3D"elementCharParallel">Parallel port</a></h6>
=20
 <pre>
 ...
@@ -6308,7 +6308,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       usually 0, 1 or 2 parallel ports.
     </p>
=20
-    <h6><a name=3D"elementCharSerial">Serial port</a></h6>
+    <h6><a id=3D"elementCharSerial">Serial port</a></h6>
=20
 <pre>
 ...
@@ -6337,7 +6337,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       <code>type=3D'pci'</code> to select desired location on the PCI bus.
     </p>
=20
-    <h6><a name=3D"elementCharConsole">Console</a></h6>
+    <h6><a id=3D"elementCharConsole">Console</a></h6>
=20
     <p>
       The console element is used to represent interactive consoles. Depen=
ding
@@ -6409,7 +6409,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       only 1 console.
     </p>
=20
-    <h6><a name=3D"elementCharChannel">Channel</a></h6>
+    <h6><a id=3D"elementCharChannel">Channel</a></h6>
=20
     <p>
       This represents a private communication channel between the host and=
 the
@@ -6501,14 +6501,14 @@ qemu-kvm -net nic,model=3D? /dev/null
         <span class=3D"since">Since 0.8.8</span></dd>
     </dl>
=20
-    <h5><a name=3D"elementsCharHostInterface">Host interface</a></h5>
+    <h5><a id=3D"elementsCharHostInterface">Host interface</a></h5>
=20
     <p>
       A character device presents itself to the host as one of the followi=
ng
       types.
     </p>
=20
-    <h6><a name=3D"elementsCharSTDIO">Domain logfile</a></h6>
+    <h6><a id=3D"elementsCharSTDIO">Domain logfile</a></h6>
=20
     <p>
       This disables all input on the character device, and sends output
@@ -6525,7 +6525,7 @@ qemu-kvm -net nic,model=3D? /dev/null
 ...</pre>
=20
=20
-    <h6><a name=3D"elementsCharFle">Device logfile</a></h6>
+    <h6><a id=3D"elementsCharFle">Device logfile</a></h6>
=20
     <p>
       A file is opened and all data sent to the character
@@ -6542,7 +6542,7 @@ qemu-kvm -net nic,model=3D? /dev/null
 &lt;/devices&gt;
 ...</pre>
=20
-    <h6><a name=3D"elementsCharVC">Virtual console</a></h6>
+    <h6><a id=3D"elementsCharVC">Virtual console</a></h6>
=20
     <p>
       Connects the character device to the graphical framebuffer in
@@ -6559,7 +6559,7 @@ qemu-kvm -net nic,model=3D? /dev/null
 &lt;/devices&gt;
 ...</pre>
=20
-    <h6><a name=3D"elementsCharNull">Null device</a></h6>
+    <h6><a id=3D"elementsCharNull">Null device</a></h6>
=20
     <p>
       Connects the character device to the void. No data is ever
@@ -6575,7 +6575,7 @@ qemu-kvm -net nic,model=3D? /dev/null
 &lt;/devices&gt;
 ...</pre>
=20
-    <h6><a name=3D"elementsCharPTY">Pseudo TTY</a></h6>
+    <h6><a id=3D"elementsCharPTY">Pseudo TTY</a></h6>
=20
     <p>
       A Pseudo TTY is allocated using /dev/ptmx. A suitable client
@@ -6600,7 +6600,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       with existing syntax for &lt;console&gt; tags.
     </p>
=20
-    <h6><a name=3D"elementsCharHost">Host device proxy</a></h6>
+    <h6><a id=3D"elementsCharHost">Host device proxy</a></h6>
=20
     <p>
       The character device is passed through to the underlying
@@ -6620,7 +6620,7 @@ qemu-kvm -net nic,model=3D? /dev/null
 &lt;/devices&gt;
 ...</pre>
=20
-    <h6><a name=3D"elementsCharPipe">Named pipe</a></h6>
+    <h6><a id=3D"elementsCharPipe">Named pipe</a></h6>
=20
     <p>
       The character device writes output to a named pipe. See pipe(7) for
@@ -6637,7 +6637,7 @@ qemu-kvm -net nic,model=3D? /dev/null
 &lt;/devices&gt;
 ...</pre>
=20
-    <h6><a name=3D"elementsCharTCP">TCP client/server</a></h6>
+    <h6><a id=3D"elementsCharTCP">TCP client/server</a></h6>
=20
     <p>
       The character device acts as a TCP client connecting to a
@@ -6726,7 +6726,7 @@ qemu-kvm -net nic,model=3D? /dev/null
 &lt;/devices&gt;
 ...</pre>
=20
-    <h6><a name=3D"elementsCharUDP">UDP network console</a></h6>
+    <h6><a id=3D"elementsCharUDP">UDP network console</a></h6>
=20
     <p>
       The character device acts as a UDP netconsole service,
@@ -6744,7 +6744,7 @@ qemu-kvm -net nic,model=3D? /dev/null
 &lt;/devices&gt;
 ...</pre>
=20
-    <h6><a name=3D"elementsCharUNIX">UNIX domain socket client/server</a><=
/h6>
+    <h6><a id=3D"elementsCharUNIX">UNIX domain socket client/server</a></h=
6>
=20
     <p>
       The character device acts as a UNIX domain socket server,
@@ -6761,7 +6761,7 @@ qemu-kvm -net nic,model=3D? /dev/null
 &lt;/devices&gt;
 ...</pre>
=20
-    <h6><a name=3D"elementsCharSpiceport">Spice channel</a></h6>
+    <h6><a id=3D"elementsCharSpiceport">Spice channel</a></h6>
=20
     <p>
       The character device is accessible through spice connection
@@ -6784,7 +6784,7 @@ qemu-kvm -net nic,model=3D? /dev/null
 &lt;/devices&gt;
 ...</pre>
=20
-    <h6><a name=3D"elementsNmdm">Nmdm device</a></h6>
+    <h6><a id=3D"elementsNmdm">Nmdm device</a></h6>
=20
     <p>
       The nmdm device driver, available on FreeBSD, provides two
@@ -6815,7 +6815,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       to the guest console. Device is specified by a fully qualified path.=
</dd>
     </dl>
=20
-    <h4><a name=3D"elementsSound">Sound devices</a></h4>
+    <h4><a id=3D"elementsSound">Sound devices</a></h4>
=20
     <p>
       A virtual sound card can be attached to the host via the
@@ -6868,7 +6868,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       slot, <a href=3D"#elementsAddress">documented above</a>.
     </p>
=20
-    <h4><a name=3D"elementsWatchdog">Watchdog device</a></h4>
+    <h4><a id=3D"elementsWatchdog">Watchdog device</a></h4>
=20
     <p>
       A virtual hardware watchdog device can be added to the guest via
@@ -6958,7 +6958,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsMemBalloon">Memory balloon device</a></h4>
+    <h4><a id=3D"elementsMemBalloon">Memory balloon device</a></h4>
=20
     <p>
       A virtual memory balloon device is added to all Xen and KVM/QEMU
@@ -7043,7 +7043,7 @@ qemu-kvm -net nic,model=3D? /dev/null
         set. (<span class=3D"since">Since 3.5.0</span>)
       </dd>
     </dl>
-    <h4><a name=3D"elementsRng">Random number generator device</a></h4>
+    <h4><a id=3D"elementsRng">Random number generator device</a></h4>
=20
     <p>
       The virtual random number generator device allows the host to pass
@@ -7137,7 +7137,7 @@ qemu-kvm -net nic,model=3D? /dev/null
=20
     </dl>
=20
-    <h4><a name=3D"elementsTpm">TPM device</a></h4>
+    <h4><a id=3D"elementsTpm">TPM device</a></h4>
=20
     <p>
       The TPM device enables a QEMU guest to have access to TPM
@@ -7197,7 +7197,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsNVRAM">NVRAM device</a></h4>
+    <h4><a id=3D"elementsNVRAM">NVRAM device</a></h4>
     <p>
       nvram device is always added to pSeries guest on PPC64, and its addr=
ess
       is allowed to be changed.  Element <code>nvram</code> (only valid for
@@ -7231,7 +7231,7 @@ qemu-kvm -net nic,model=3D? /dev/null
     </dd>
   </dl>
=20
-    <h4><a name=3D"elementsPanic">panic device</a></h4>
+    <h4><a id=3D"elementsPanic">panic device</a></h4>
     <p>
       panic device enables libvirt to receive panic notification from a QE=
MU
       guest.
@@ -7288,7 +7288,7 @@ qemu-kvm -net nic,model=3D? /dev/null
     </dd>
   </dl>
=20
-  <h4><a name=3D"elementsShmem">Shared memory device</a></h4>
+  <h4><a id=3D"elementsShmem">Shared memory device</a></h4>
=20
     <p>
       A shared memory device allows to share a memory region between
@@ -7352,7 +7352,7 @@ qemu-kvm -net nic,model=3D? /dev/null
     </dd>
   </dl>
=20
-    <h4><a name=3D"elementsMemory">Memory devices</a></h4>
+    <h4><a id=3D"elementsMemory">Memory devices</a></h4>
=20
     <p>
         In addition to the initial memory assigned to the guest, memory de=
vices
@@ -7495,7 +7495,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       </dd>
     </dl>
=20
-    <h4><a name=3D"elementsIommu">IOMMU devices</a></h4>
+    <h4><a id=3D"elementsIommu">IOMMU devices</a></h4>
=20
     <p>
       The <code>iommu</code> element can be used to add an IOMMU device.
@@ -7575,7 +7575,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       </dd>
     </dl>
=20
-    <h3><a name=3D"seclabel">Security label</a></h3>
+    <h3><a id=3D"seclabel">Security label</a></h3>
=20
     <p>
       The <code>seclabel</code> element allows control over the
@@ -7704,7 +7704,7 @@ qemu-kvm -net nic,model=3D? /dev/null
       being on a file system that lacks security labeling.
     </p>
=20
-    <h3><a name=3D"keywrap">Key Wrap</a></h3>
+    <h3><a id=3D"keywrap">Key Wrap</a></h3>
=20
        <p>The content of the optional <code>keywrap</code> element specifi=
es
         whether the guest will be allowed to perform the S390 cryptographi=
c key
@@ -7743,7 +7743,7 @@ qemu-kvm -net nic,model=3D? /dev/null
=20
     <p>Note: DEA/TDEA is synonymous with DES/TDES.</p>
=20
-    <h2><a name=3D"examples">Example configs</a></h2>
+    <h2><a id=3D"examples">Example configs</a></h2>
=20
     <p>
       Example configurations for each driver are provide on the
diff --git a/docs/formatdomaincaps.html.in b/docs/formatdomaincaps.html.in
index 007cab62d..5e63fb7ca 100644
--- a/docs/formatdomaincaps.html.in
+++ b/docs/formatdomaincaps.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"Overview">Overview</a></h2>
+    <h2><a id=3D"Overview">Overview</a></h2>
=20
     <p>Sometimes, when a new domain is to be created it may come handy to =
know
     the capabilities of the hypervisor so the correct combination of devic=
es and
@@ -37,7 +37,7 @@
     management application to choose an appropriate mode for a pass-through
     host device as well as which adapter to utilize.</p>
=20
-    <h2><a name=3D"elements">Element and attribute overview</a></h2>
+    <h2><a id=3D"elements">Element and attribute overview</a></h2>
=20
     <p> A new query interface was added to the virConnect API's to retriev=
e the
     XML listing of the set of domain capabilities (<span class=3D"since">S=
ince
@@ -79,7 +79,7 @@
=20
     </dl>
=20
-    <h3><a name=3D"elementsCPUAllocation">CPU Allocation</a></h3>
+    <h3><a id=3D"elementsCPUAllocation">CPU Allocation</a></h3>
=20
     <p>Before any devices capability occurs, there might be a info on doma=
in
     wide capabilities, e.g. virtual CPUs:</p>
@@ -97,7 +97,7 @@
       <dd>The maximum number of supported virtual CPUs</dd>
     </dl>
=20
-    <h3><a name=3D"elementsOSBIOS">BIOS bootloader</a></h3>
+    <h3><a id=3D"elementsOSBIOS">BIOS bootloader</a></h3>
=20
     <p>Sometimes users might want to tweak some BIOS knobs or use
     UEFI. For cases like that, <a
@@ -143,7 +143,7 @@
       &lt;loader/&gt; element.</dd>
     </dl>
=20
-    <h3><a name=3D"elementsCPU">CPU configuration</a></h3>
+    <h3><a id=3D"elementsCPU">CPU configuration</a></h3>
=20
     <p>
       The <code>cpu</code> element exposes options usable for configuring
@@ -208,7 +208,7 @@
       </dd>
     </dl>
=20
-    <h3><a name=3D"elementsDevices">Devices</a></h3>
+    <h3><a id=3D"elementsDevices">Devices</a></h3>
=20
     <p>
       Another set of XML elements describe the supported devices and their
@@ -240,7 +240,7 @@
     support the values <code>disk</code>, <code>cdrom</code>,
     <code>floppy</code>, or <code>lun</code>.</p>
=20
-    <h4><a name=3D"elementsDisks">Hard drives, floppy disks, CDROMs</a></h=
4>
+    <h4><a id=3D"elementsDisks">Hard drives, floppy disks, CDROMs</a></h4>
     <p>Disk capabilities are exposed under the <code>disk</code> element. =
For
     instance:</p>
=20
@@ -283,7 +283,7 @@
     </dl>
=20
=20
-    <h4><a name=3D"elementsGraphics">Graphical framebuffers</a></h4>
+    <h4><a id=3D"elementsGraphics">Graphical framebuffers</a></h4>
     <p>Graphics device capabilities are exposed under the
     <code>graphics</code> element. For instance:</p>
=20
@@ -310,7 +310,7 @@
     </dl>
=20
=20
-    <h4><a name=3D"elementsVideo">Video device</a></h4>
+    <h4><a id=3D"elementsVideo">Video device</a></h4>
     <p>Video device capabilities are exposed under the
     <code>video</code> element. For instance:</p>
=20
@@ -339,7 +339,7 @@
     </dl>
=20
=20
-    <h4><a name=3D"elementsHostDev">Host device assignment</a></h4>
+    <h4><a id=3D"elementsHostDev">Host device assignment</a></h4>
     <p>Some host devices can be passed through to a guest (e.g. USB, PCI a=
nd
     SCSI). Well, only if the following is enabled:</p>
=20
@@ -401,7 +401,7 @@
       element.</dd>
     </dl>
=20
-    <h3><a name=3D"elementsFeatures">Features</a></h3>
+    <h3><a id=3D"elementsFeatures">Features</a></h3>
=20
     <p>One more set of XML elements describe the supported features and
     their capabilities. All features occur as children of the main
@@ -431,7 +431,7 @@
     the domain XML documentation.
     </p>
=20
-    <h4><a name=3D"elementsGIC">GIC capabilities</a></h4>
+    <h4><a id=3D"elementsGIC">GIC capabilities</a></h4>
=20
     <p>GIC capabilities are exposed under the <code>gic</code> element.</p>
=20
diff --git a/docs/formatnetwork.html.in b/docs/formatnetwork.html.in
index b410dd64e..e8e618e42 100644
--- a/docs/formatnetwork.html.in
+++ b/docs/formatnetwork.html.in
@@ -13,7 +13,7 @@
       <a href=3D"https://wiki.libvirt.org/page/Networking">relevant wiki p=
age</a>.
     </p>
=20
-    <h2><a name=3D"elements">Element and attribute overview</a></h2>
+    <h2><a id=3D"elements">Element and attribute overview</a></h2>
=20
     <p>
       The root element required for all virtual networks is
@@ -27,7 +27,7 @@
       available <span class=3D"since">since 0.3.0</span>
     </p>
=20
-    <h3><a name=3D"elementsMetadata">General metadata</a></h3>
+    <h3><a id=3D"elementsMetadata">General metadata</a></h3>
=20
     <p>
       The first elements provide basic metadata about the virtual
@@ -83,7 +83,7 @@
         override the setting in the network.</dd>
     </dl>
=20
-    <h3><a name=3D"elementsConnect">Connectivity</a></h3>
+    <h3><a id=3D"elementsConnect">Connectivity</a></h3>
=20
     <p>
       The next set of elements control how a virtual network is
@@ -514,7 +514,7 @@
=20
       </dd>
     </dl>
-    <h5><a name=3D"elementQoS">Quality of service</a></h5>
+    <h5><a id=3D"elementQoS">Quality of service</a></h5>
=20
 <pre>
 ...
@@ -634,7 +634,7 @@
         <span class=3D"since">since 1.0.1</span>.
       </p>
=20
-    <h5><a name=3D"elementVlanTag">Setting VLAN tag (on supported network =
types only)</a></h5>
+    <h5><a id=3D"elementVlanTag">Setting VLAN tag (on supported network ty=
pes only)</a></h5>
=20
 <pre>
 &lt;network&gt;
@@ -712,7 +712,7 @@
       or <code>&lt;interface&gt;</code>.
     </p>
=20
-    <h5><a name=3D"elementsPortgroup">Portgroups</a></h5>
+    <h5><a id=3D"elementsPortgroup">Portgroups</a></h5>
=20
 <pre>
 ...
@@ -790,7 +790,7 @@
       setting in the portgroup.
     </p>
=20
-    <h5><a name=3D"elementsStaticroute">Static Routes</a></h5>
+    <h5><a id=3D"elementsStaticroute">Static Routes</a></h5>
     <p>
       Static route definitions are used to provide routing information
       to the virtualization host for networks which are not directly
@@ -845,7 +845,7 @@
 ...
     </pre>
=20
-    <h3><a name=3D"elementsAddress">Addressing</a></h3>
+    <h3><a id=3D"elementsAddress">Addressing</a></h3>
=20
     <p>
       The final set of elements define the addresses (IPv4 and/or
@@ -1079,9 +1079,9 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"examples">Example configuration</a></h2>
+    <h2><a id=3D"examples">Example configuration</a></h2>
=20
-    <h3><a name=3D"examplesNAT">NAT based network</a></h3>
+    <h3><a id=3D"examplesNAT">NAT based network</a></h3>
=20
     <p>
       This example is the so called "default" virtual network. It is
@@ -1129,7 +1129,7 @@
   &lt;/ip&gt;
 &lt;/network&gt;</pre>
=20
-    <h3><a name=3D"examplesRoute">Routed network config</a></h3>
+    <h3><a id=3D"examplesRoute">Routed network config</a></h3>
=20
     <p>
       This is a variant on the default network which routes traffic
@@ -1211,7 +1211,7 @@
   &lt;route family=3D"ipv6" address=3D"2001:db8:ca2:8::" prefix=3D"64" gat=
eway=3D"2001:db8:ca2:7::4"/&gt;
 &lt;/network&gt;</pre>
=20
-    <h3><a name=3D"examplesPrivate">Isolated network config</a></h3>
+    <h3><a id=3D"examplesPrivate">Isolated network config</a></h3>
=20
     <p>
       This variant provides a completely isolated private network
@@ -1233,7 +1233,7 @@
   &lt;ip family=3D"ipv6" address=3D"2001:db8:ca2:3::1" prefix=3D"64"/&gt;
 &lt;/network&gt;</pre>
=20
-    <h3><a name=3D"examplesPrivate6">Isolated IPv6 network config</a></h3>
+    <h3><a id=3D"examplesPrivate6">Isolated IPv6 network config</a></h3>
=20
     <p>
       This variation of an isolated network defines only IPv6.
@@ -1259,7 +1259,7 @@
   &lt;/ip&gt;
 &lt;/network&gt;</pre>
=20
-    <h3><a name=3D"examplesBridge">Using an existing host bridge</a></h3>
+    <h3><a id=3D"examplesBridge">Using an existing host bridge</a></h3>
=20
     <p>
       <span class=3D"since">Since 0.9.4</span>
@@ -1277,7 +1277,7 @@
   &lt;bridge name=3D"br0"/&gt;
 &lt;/network&gt;</pre>
=20
-    <h3><a name=3D"examplesDirect">Using a macvtap "direct" connection</a>=
</h3>
+    <h3><a id=3D"examplesDirect">Using a macvtap "direct" connection</a></=
h3>
=20
     <p>
       <span class=3D"since">Since 0.9.4, QEMU and KVM only, requires
@@ -1312,7 +1312,7 @@
   &lt;/forward&gt;
 &lt;/network&gt;</pre>
=20
-    <h3><a name=3D"examplesNoGateway">Network config with no gateway addre=
sses</a></h3>
+    <h3><a id=3D"examplesNoGateway">Network config with no gateway address=
es</a></h3>
=20
     <p>
     A valid network definition can contain no IPv4 or IPv6 addresses.  Suc=
h a definition
diff --git a/docs/formatnode.html.in b/docs/formatnode.html.in
index 32451d557..f82aecf3a 100644
--- a/docs/formatnode.html.in
+++ b/docs/formatnode.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"NodedevAttributes">Node Device XML</a></h2>
+    <h2><a id=3D"NodedevAttributes">Node Device XML</a></h2>
=20
     <p>
       There are several libvirt functions, all with the
@@ -340,7 +340,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"nodeExample">Examples</a></h2>
+    <h2><a id=3D"nodeExample">Examples</a></h2>
=20
     <p>The following are some example node device XML outputs:</p>
     <pre>
diff --git a/docs/formatnwfilter.html.in b/docs/formatnwfilter.html.in
index 0d32893cb..5eb60e12c 100644
--- a/docs/formatnwfilter.html.in
+++ b/docs/formatnwfilter.html.in
@@ -12,7 +12,7 @@
       their goals, concepts and XML format.
     </p>
=20
-    <h2><a name=3D"goals">Goals and background</a></h2>
+    <h2><a id=3D"goals">Goals and background</a></h2>
=20
     <p>
       The goal of the network filtering XML is to enable administrators
@@ -43,7 +43,7 @@
       (QEMU, KVM)</span>
     </p>
=20
-    <h2><a name=3D"nwfconcepts">Concepts</a></h2>
+    <h2><a id=3D"nwfconcepts">Concepts</a></h2>
     <p>
       The network traffic filtering subsystem enables configuration
       of network traffic filtering rules on individual network
@@ -111,7 +111,7 @@
       <br/><br/>
     </p>
=20
-    <h3><a name=3D"nwfconceptschains">Filtering chains</a></h3>
+    <h3><a id=3D"nwfconceptschains">Filtering chains</a></h3>
     <p>
       Filtering rules are organized in filter chains. These chains can be
       thought of as having a tree structure with packet
@@ -192,7 +192,7 @@
       traverse the ARP chain.
       <br/><br/>
     </p>
-    <h3><a name=3D"nwfconceptschainpriorities">Filtering chain priorities<=
/a></h3>
+    <h3><a id=3D"nwfconceptschainpriorities">Filtering chain priorities</a=
></h3>
     <p>
       All chains are connected to the <code>root</code> chain. The order in
       which those chains are accessed is influenced by the priority of the
@@ -236,7 +236,7 @@
       node. The above example filter shows the default priority of -500
       for <code>arp</code> chains.
     </p>
-    <h3><a name=3D"nwfconceptsvars">Usage of variables in filters</a></h3>
+    <h3><a id=3D"nwfconceptsvars">Usage of variables in filters</a></h3>
     <p>
=20
       Two variables names have so far been reserved for usage by the
@@ -374,7 +374,7 @@ DSTPORTS =3D [ 80, 8080 ]
       former notation always assumes the iterator with Id '0'.
     </p>
=20
-    <h3><a name=3D"nwfelemsRulesAdvIPAddrDetection">Automatic IP address d=
etection</a></h3>
+    <h3><a id=3D"nwfelemsRulesAdvIPAddrDetection">Automatic IP address det=
ection</a></h3>
     <p>
        The detection of IP addresses used on a virtual machine's interface
        is automatically activated if the variable <code>IP</code> is refer=
enced
@@ -448,7 +448,7 @@ DSTPORTS =3D [ 80, 8080 ]
 &lt;/interface&gt;
 </pre>
=20
-    <h3><a name=3D"nwfelemsReservedVars">Reserved Variables</a></h3>
+    <h3><a id=3D"nwfelemsReservedVars">Reserved Variables</a></h3>
     <p>
       The following table lists reserved variables in use by libvirt.
     </p>
@@ -485,7 +485,7 @@ DSTPORTS =3D [ 80, 8080 ]
        </tr>
       </table>
=20
-    <h2><a name=3D"nwfelems">Element and attribute overview</a></h2>
+    <h2><a id=3D"nwfelems">Element and attribute overview</a></h2>
=20
     <p>
       The root element required for all network filters is
@@ -498,7 +498,7 @@ DSTPORTS =3D [ 80, 8080 ]
       ipv4, ipv6, arp and rarp</code>.
     </p>
=20
-    <h3><a name=3D"nwfelemsRefs">References to other filters</a></h3>
+    <h3><a id=3D"nwfelemsRefs">References to other filters</a></h3>
     <p>
      Any filter may hold references to other filters. Individual
      filters may be referenced multiple times in a filter tree but
@@ -536,7 +536,7 @@ DSTPORTS =3D [ 80, 8080 ]
     attached.
     </p>
=20
-    <h3><a name=3D"nwfelemsRules">Filter rules</a></h3>
+    <h3><a id=3D"nwfelemsRules">Filter rules</a></h3>
     <p>
     The following XML shows a simple example of a network
     traffic filter implementing a rule to drop traffic if
@@ -618,7 +618,7 @@ DSTPORTS =3D [ 80, 8080 ]
      filtered.
     </p>
=20
-    <h4><a name=3D"nwfelemsRulesProto">Supported protocols</a></h4>
+    <h4><a id=3D"nwfelemsRulesProto">Supported protocols</a></h4>
     <p>
      The following sections enumerate the list of protocols that
      are supported by the network filtering subsystem. The
@@ -677,7 +677,7 @@ DSTPORTS =3D [ 80, 8080 ]
     </p>
=20
=20
-    <h5><a name=3D"nwfelemsRulesProtoMAC">MAC (Ethernet)</a></h5>
+    <h5><a id=3D"nwfelemsRulesProtoMAC">MAC (Ethernet)</a></h5>
     <p>
       Protocol ID: <code>mac</code>
       <br/>
@@ -729,7 +729,7 @@ DSTPORTS =3D [ 80, 8080 ]
 [...]
 </pre>
=20
-    <h5><a name=3D"nwfelemsRulesProtoVLAN">VLAN (802.1Q)</a>
+    <h5><a id=3D"nwfelemsRulesProtoVLAN">VLAN (802.1Q)</a>
       <span class=3D"since">(Since 0.9.8)</span>
     </h5>
     <p>
@@ -784,7 +784,7 @@ DSTPORTS =3D [ 80, 8080 ]
       Valid Strings for <code>encap-protocol</code> are: arp, ipv4, ipv6
     </p>
=20
-    <h5><a name=3D"nwfelemsRulesProtoSTP">STP (Spanning Tree Protocol)</a>
+    <h5><a id=3D"nwfelemsRulesProtoSTP">STP (Spanning Tree Protocol)</a>
       <span class=3D"since">(Since 0.9.8)</span>
     </h5>
     <p>
@@ -926,7 +926,7 @@ DSTPORTS =3D [ 80, 8080 ]
        </tr>
       </table>
=20
-    <h5><a name=3D"nwfelemsRulesProtoARP">ARP/RARP</a></h5>
+    <h5><a id=3D"nwfelemsRulesProtoARP">ARP/RARP</a></h5>
     <p>
       Protocol ID: <code>arp</code> or <code>rarp</code>
       <br/>
@@ -1022,7 +1022,7 @@ DSTPORTS =3D [ 80, 8080 ]
       <br/><br/>
     </p>
=20
-    <h5><a name=3D"nwfelemsRulesProtoIP">IPv4</a></h5>
+    <h5><a id=3D"nwfelemsRulesProtoIP">IPv4</a></h5>
     <p>
       Protocol ID: <code>ip</code>
       <br/>
@@ -1118,7 +1118,7 @@ DSTPORTS =3D [ 80, 8080 ]
     </p>
=20
=20
-    <h5><a name=3D"nwfelemsRulesProtoIPv6">IPv6</a></h5>
+    <h5><a id=3D"nwfelemsRulesProtoIPv6">IPv6</a></h5>
     <p>
       Protocol ID: <code>ipv6</code>
       <br/>
@@ -1228,7 +1228,7 @@ DSTPORTS =3D [ 80, 8080 ]
       <br/><br/>
     </p>
=20
-    <h5><a name=3D"nwfelemsRulesProtoTCP-ipv4">TCP/UDP/SCTP</a></h5>
+    <h5><a id=3D"nwfelemsRulesProtoTCP-ipv4">TCP/UDP/SCTP</a></h5>
     <p>
       Protocol ID: <code>tcp</code>, <code>udp</code>, <code>sctp</code>
       <br/>
@@ -1344,7 +1344,7 @@ DSTPORTS =3D [ 80, 8080 ]
     </p>
=20
=20
-    <h5><a name=3D"nwfelemsRulesProtoICMP">ICMP</a></h5>
+    <h5><a id=3D"nwfelemsRulesProtoICMP">ICMP</a></h5>
     <p>
       Protocol ID: <code>icmp</code>
       <br/>
@@ -1458,7 +1458,7 @@ DSTPORTS =3D [ 80, 8080 ]
       <br/><br/>
     </p>
=20
-    <h5><a name=3D"nwfelemsRulesProtoMisc">IGMP, ESP, AH, UDPLITE, 'ALL'</=
a></h5>
+    <h5><a id=3D"nwfelemsRulesProtoMisc">IGMP, ESP, AH, UDPLITE, 'ALL'</a>=
</h5>
     <p>
       Protocol ID: <code>igmp</code>, <code>esp</code>, <code>ah</code>, <=
code>udplite</code>, <code>all</code>
       <br/>
@@ -1563,7 +1563,7 @@ DSTPORTS =3D [ 80, 8080 ]
     </p>
=20
=20
-    <h5><a name=3D"nwfelemsRulesProtoTCP-ipv6">TCP/UDP/SCTP over IPV6</a><=
/h5>
+    <h5><a id=3D"nwfelemsRulesProtoTCP-ipv6">TCP/UDP/SCTP over IPV6</a></h=
5>
     <p>
       Protocol ID: <code>tcp-ipv6</code>, <code>udp-ipv6</code>, <code>sct=
p-ipv6</code>
       <br/>
@@ -1679,7 +1679,7 @@ DSTPORTS =3D [ 80, 8080 ]
     </p>
=20
=20
-    <h5><a name=3D"nwfelemsRulesProtoICMPv6">ICMPv6</a></h5>
+    <h5><a id=3D"nwfelemsRulesProtoICMPv6">ICMPv6</a></h5>
     <p>
       Protocol ID: <code>icmpv6</code>
       <br/>
@@ -1779,7 +1779,7 @@ DSTPORTS =3D [ 80, 8080 ]
       <br/><br/>
     </p>
=20
-    <h5><a name=3D"nwfelemsRulesProtoMiscv6">ESP, AH, UDPLITE, 'ALL' over =
IPv6</a></h5>
+    <h5><a id=3D"nwfelemsRulesProtoMiscv6">ESP, AH, UDPLITE, 'ALL' over IP=
v6</a></h5>
     <p>
       Protocol ID: <code>esp-ipv6</code>, <code>ah-ipv6</code>, <code>udpl=
ite-ipv6</code>, <code>all-ipv6</code>
       <br/>
@@ -1868,13 +1868,13 @@ DSTPORTS =3D [ 80, 8080 ]
       <br/><br/>
     </p>
=20
-    <h3><a name=3D"nwfelemsRulesAdv">Advanced Filter Configuration Topics<=
/a></h3>
+    <h3><a id=3D"nwfelemsRulesAdv">Advanced Filter Configuration Topics</a=
></h3>
     <p>
      The following sections discuss advanced filter configuration
      topics.
     </p>
=20
-    <h4><a name=3D"nwfelemsRulesAdvTracking">Connection tracking</a></h4>
+    <h4><a id=3D"nwfelemsRulesAdvTracking">Connection tracking</a></h4>
     <p>
      The network filtering subsystem (on Linux) makes use of the connection
      tracking support of iptables. This helps in enforcing the
@@ -1908,7 +1908,7 @@ DSTPORTS =3D [ 80, 8080 ]
      which may or may not be desirable.
     </p>
=20
-    <h4><a name=3D"nwfelemsRulesAdvLimiting">Limiting Number of Connection=
s</a></h4>
+    <h4><a id=3D"nwfelemsRulesAdvLimiting">Limiting Number of Connections<=
/a></h4>
     <p>
      To limit the number of connections a VM may establish, a rule must
      be provided that sets a limit of connections for a given
@@ -1981,7 +1981,7 @@ echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_ti=
meout
       traffic behavior in relation to idle connections.
     </p>
=20
-    <h2><a name=3D"nwfcli">Command line tools</a></h2>
+    <h2><a id=3D"nwfcli">Command line tools</a></h2>
     <p>
       The libvirt command line tool <code>virsh</code> has been extended
       with life-cycle support for network filters. All commands related
@@ -1996,7 +1996,7 @@ echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_ti=
meout
      <li>nwfilter-edit : edit a network filter given its name</li>
     </ul>
=20
-    <h2><a name=3D"nwfexamples">Pre-existing network filters</a></h2>
+    <h2><a id=3D"nwfexamples">Pre-existing network filters</a></h2>
     <p>
      The following is a list of example network filters that are
      automatically installed with libvirt.</p>
@@ -2051,7 +2051,7 @@ echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_ti=
meout
      on top of the prevention of packet spoofing.
     </p>
=20
-    <h2><a name=3D"nwfwrite">Writing your own filters</a></h2>
+    <h2><a id=3D"nwfwrite">Writing your own filters</a></h2>
=20
     <p>
      Since libvirt only provides a couple of example networking filters, y=
ou
@@ -2124,7 +2124,7 @@ echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_ti=
meout
     <code>udp-ipv6</code> traffic filtering node.
     </p>
=20
-    <h3><a name=3D"nwfwriteexample">Example custom filter</a></h3>
+    <h3><a id=3D"nwfwriteexample">Example custom filter</a></h3>
     <p>
      As an example we want to now build a filter that fulfills the followi=
ng
      list of requirements:
@@ -2227,7 +2227,7 @@ echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_ti=
meout
 &lt;/rule&gt;
 </pre>
=20
-    <h3><a name=3D"nwfwriteexample2nd">Second example custom filter</a></h=
3>
+    <h3><a id=3D"nwfwriteexample2nd">Second example custom filter</a></h3>
     <p>
      In this example we now want to build a similar filter as in the
      example above, but extend the list of requirements with an
@@ -2400,13 +2400,13 @@ modprobe ip_conntrack_ftp   # if above is not avail=
able
=20
 </pre>
=20
-    <h2><a name=3D"nwflimits">Limitations</a></h2>
+    <h2><a id=3D"nwflimits">Limitations</a></h2>
     <p>
      The following sections list (current) limitations of the network
      filtering subsystem.
     </p>
=20
-    <h3><a name=3D"nwflimitsmigr">VM Migration</a></h3>
+    <h3><a id=3D"nwflimitsmigr">VM Migration</a></h3>
      <p>
       VM migration is only supported if the whole filter tree
       that is referenced by a virtual machine's top level filter
@@ -2424,7 +2424,7 @@ modprobe ip_conntrack_ftp   # if above is not availab=
le
       0.8.1 or later in order not to lose the network traffic filters
       associated with an interface.
      </p>
-    <h3><a name=3D"nwflimitsvlan">VLAN filtering on Linux</a></h3>
+    <h3><a id=3D"nwflimitsvlan">VLAN filtering on Linux</a></h3>
      <p>
       VLAN (802.1Q) packets, if sent by a virtual machine, cannot be filte=
red
       with rules for protocol IDs <code>arp</code>, <code>rarp</code>,
diff --git a/docs/formatsecret.html.in b/docs/formatsecret.html.in
index 21b93397c..86b8de5b9 100644
--- a/docs/formatsecret.html.in
+++ b/docs/formatsecret.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"SecretAttributes">Secret XML</a></h2>
+    <h2><a id=3D"SecretAttributes">Secret XML</a></h2>
=20
     <p>
       Secrets stored by libvirt may have attributes associated with them, =
using
@@ -47,7 +47,7 @@
       </dd>
     </dl>
=20
-    <h3><a name=3D"VolumeUsageType">Usage type "volume"</a></h3>
+    <h3><a id=3D"VolumeUsageType">Usage type "volume"</a></h3>
=20
     <p>
       This secret is associated with a volume, whether the format is either
@@ -120,7 +120,7 @@ Secret value set
 #
     </pre>
=20
-    <h3><a name=3D"CephUsageType">Usage type "ceph"</a></h3>
+    <h3><a id=3D"CephUsageType">Usage type "ceph"</a></h3>
     <p>
       This secret is associated with a Ceph RBD (rados block device).
       The <code>&lt;usage type=3D'ceph'&gt;</code> element must contain
@@ -187,7 +187,7 @@ Secret value set
 &lt;/auth&gt;
     </pre>
=20
-    <h3><a name=3D"iSCSIUsageType">Usage type "iscsi"</a></h3>
+    <h3><a id=3D"iSCSIUsageType">Usage type "iscsi"</a></h3>
=20
     <p>
       This secret is associated with an iSCSI target for CHAP authenticati=
on.
@@ -272,7 +272,7 @@ Secret value set
 &lt;/auth&gt;
     </pre>
=20
-    <h3><a name=3D"tlsUsageType">Usage type "tls"</a></h3>
+    <h3><a id=3D"tlsUsageType">Usage type "tls"</a></h3>
=20
     <p>
       This secret may be used in order to provide the passphrase for the
diff --git a/docs/formatsnapshot.html.in b/docs/formatsnapshot.html.in
index 5e8e21c8a..52682646b 100644
--- a/docs/formatsnapshot.html.in
+++ b/docs/formatsnapshot.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"SnapshotAttributes">Snapshot XML</a></h2>
+    <h2><a id=3D"SnapshotAttributes">Snapshot XML</a></h2>
=20
     <p>
       There are several types of snapshots:
@@ -243,7 +243,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"example">Examples</a></h2>
+    <h2><a id=3D"example">Examples</a></h2>
=20
     <p>Using this XML to create a disk snapshot of just vda on a qemu
       domain with two disks:</p>
diff --git a/docs/formatstorage.html.in b/docs/formatstorage.html.in
index 4946ddf70..c6eab0278 100644
--- a/docs/formatstorage.html.in
+++ b/docs/formatstorage.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"StoragePool">Storage pool XML</a></h2>
+    <h2><a id=3D"StoragePool">Storage pool XML</a></h2>
=20
     <p>
       Although all storage pool backends share the same public APIs and
@@ -29,7 +29,7 @@
       3.1.0</span>). This corresponds to the
       storage backend drivers listed further along in this document.
     </p>
-    <h3><a name=3D"StoragePoolFirst">General metadata</a></h3>
+    <h3><a id=3D"StoragePoolFirst">General metadata</a></h3>
=20
     <pre>
 &lt;pool type=3D"iscsi"&gt;
@@ -66,7 +66,7 @@
         pool. <span class=3D"since">Since 0.4.1</span></dd>
     </dl>
=20
-    <h3><a name=3D"StoragePoolSource">Source elements</a></h3>
+    <h3><a id=3D"StoragePoolSource">Source elements</a></h3>
=20
     <p>
       A single <code>source</code> element is contained within the top lev=
el
@@ -394,7 +394,7 @@
         is backend specific.  <span class=3D"since">Since 0.8.4</span></dd>
     </dl>
=20
-    <h3><a name=3D"StoragePoolTarget">Target elements</a></h3>
+    <h3><a id=3D"StoragePoolTarget">Target elements</a></h3>
=20
     <p>
       A single <code>target</code> element is contained within the top lev=
el
@@ -458,7 +458,7 @@
       </dd>
     </dl>
=20
-    <h3><a name=3D"StoragePoolExtents">Device extents</a></h3>
+    <h3><a id=3D"StoragePoolExtents">Device extents</a></h3>
=20
     <p>
       If a storage pool exposes information about its underlying
@@ -478,7 +478,7 @@
       device, measured in bytes.  <span class=3D"since">Since 0.4.1</span>
     </p>
=20
-    <h2><a name=3D"StorageVol">Storage volume XML</a></h2>
+    <h2><a id=3D"StorageVol">Storage volume XML</a></h2>
     <p>
       A storage volume will generally be either a file or a device
       node; <span class=3D"since">since 1.2.0</span>, an optional
@@ -488,7 +488,7 @@
       XML format is available <span class=3D"since">since 0.4.1</span>
     </p>
=20
-    <h3><a name=3D"StorageVolFirst">General metadata</a></h3>
+    <h3><a id=3D"StorageVolFirst">General metadata</a></h3>
=20
     <pre>
 &lt;volume type=3D'file'&gt;
@@ -567,7 +567,7 @@
         on the local host. <span class=3D"since">Since 0.4.1</span></dd>
     </dl>
=20
-    <h3><a name=3D"StorageVolTarget">Target elements</a></h3>
+    <h3><a id=3D"StorageVolTarget">Target elements</a></h3>
=20
     <p>
       A single <code>target</code> element is contained within the top lev=
el
@@ -683,7 +683,7 @@
       </dd>
     </dl>
=20
-    <h3><a name=3D"StorageVolBacking">Backing store elements</a></h3>
+    <h3><a id=3D"StorageVolBacking">Backing store elements</a></h3>
=20
     <p>
       A single <code>backingStore</code> element is contained within the t=
op level
@@ -729,14 +729,14 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"examples">Example configuration</a></h2>
+    <h2><a id=3D"examples">Example configuration</a></h2>
=20
     <p>
       Here are a couple of examples, for a more complete set demonstrating
       every type of storage pool, consult the <a href=3D"storage.html">sto=
rage driver page</a>
     </p>
=20
-    <h3><a name=3D"exampleFile">File based storage pool</a></h3>
+    <h3><a id=3D"exampleFile">File based storage pool</a></h3>
=20
     <pre>
 &lt;pool type=3D"dir"&gt;
@@ -746,7 +746,7 @@
   &lt;/target&gt;
 &lt;/pool&gt;</pre>
=20
-    <h3><a name=3D"exampleISCSI">iSCSI based storage pool</a></h3>
+    <h3><a id=3D"exampleISCSI">iSCSI based storage pool</a></h3>
=20
     <pre>
 &lt;pool type=3D"iscsi"&gt;
@@ -763,7 +763,7 @@
   &lt;/target&gt;
 &lt;/pool&gt;</pre>
=20
-    <h3><a name=3D"exampleVol">Storage volume</a></h3>
+    <h3><a id=3D"exampleVol">Storage volume</a></h3>
=20
     <pre>
 &lt;volume&gt;
@@ -781,7 +781,7 @@
   &lt;/target&gt;
 &lt;/volume&gt;</pre>
=20
-    <h3><a name=3D"exampleLuks">Storage volume using LUKS</a></h3>
+    <h3><a id=3D"exampleLuks">Storage volume using LUKS</a></h3>
=20
     <pre>
 &lt;volume&gt;
diff --git a/docs/formatstorageencryption.html.in b/docs/formatstorageencry=
ption.html.in
index ec09bc661..ba19e268a 100644
--- a/docs/formatstorageencryption.html.in
+++ b/docs/formatstorageencryption.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"StorageEncryption">Storage volume encryption XML</a></h=
2>
+    <h2><a id=3D"StorageEncryption">Storage volume encryption XML</a></h2>
=20
     <p>
       Storage volumes may be encrypted, the XML snippet described below is=
 used
@@ -37,7 +37,7 @@
       secret value at the time of volume creation, and store it using the
       specified <code>uuid</code>.
     </p>
-    <h3><a name=3D"StorageEncryptionDefault">"default" format</a></h3>
+    <h3><a id=3D"StorageEncryptionDefault">"default" format</a></h3>
     <p>
       <code>&lt;encryption format=3D"default"/&gt;</code> can be specified=
 only
       when creating a qcow volume.  If the volume is successfully created,=
 the
@@ -47,7 +47,7 @@
       in later operations with the volume, or when setting up a domain that
       uses the volume.
     </p>
-    <h3><a name=3D"StorageEncryptionQcow">"qcow" format</a></h3>
+    <h3><a id=3D"StorageEncryptionQcow">"qcow" format</a></h3>
     <p>
       The <code>qcow</code> format specifies that the built-in encryption
       support in <code>qcow</code>- or <code>qcow2</code>-formatted volume
@@ -56,7 +56,7 @@
       the <code>secret</code> element is not present during volume creatio=
n,
       a secret is automatically generated and attached to the volume.
     </p>
-    <h3><a name=3D"StorageEncryptionLuks">"luks" format</a></h3>
+    <h3><a id=3D"StorageEncryptionLuks">"luks" format</a></h3>
     <p>
       The <code>luks</code> format is specific to a luks encrypted volume
       and the secret is used in order to either encrypt during volume crea=
tion
@@ -119,7 +119,7 @@
     </dl>
=20
=20
-    <h2><a name=3D"example">Examples</a></h2>
+    <h2><a id=3D"example">Examples</a></h2>
=20
     <p>
       Here is a simple example, specifying use of the <code>qcow</code> fo=
rmat:
diff --git a/docs/governance.html.in b/docs/governance.html.in
index 2f0428130..81c093bbd 100644
--- a/docs/governance.html.in
+++ b/docs/governance.html.in
@@ -14,7 +14,7 @@
       influence, within the community.
     </p>
=20
-    <h2><a name=3D"codeofconduct">Code of conduct</a></h2>
+    <h2><a id=3D"codeofconduct">Code of conduct</a></h2>
=20
     <p>
       The libvirt project community covers people from a wide variety of
@@ -49,7 +49,7 @@
         from them. Playing a blame game doesn't help anyone.</li>
     </ul>
=20
-    <h2><a name=3D"roles">Roles and responsibilities</a></h2>
+    <h2><a id=3D"roles">Roles and responsibilities</a></h2>
=20
     <h3><a href=3D"users">Users</a></h3>
=20
@@ -91,7 +91,7 @@
       ways listed in the next section.
     </p>
=20
-    <h3><a name=3D"contributors">Contributors</a></h3>
+    <h3><a id=3D"contributors">Contributors</a></h3>
=20
     <p>
       The contributors are community members who have some concrete impact
@@ -156,7 +156,7 @@
       covered are found in the source repositories, or website in question.
     </p>
=20
-    <h3><a name=3D"committers">Committers</a></h3>
+    <h3><a id=3D"committers">Committers</a></h3>
=20
     <p>
       The committers are the subset of contributors who have direct access
@@ -227,7 +227,7 @@
       to retain their role as a committer.
     </p>
=20
-    <h3><a name=3D"secteam">Security team</a></h3>
+    <h3><a id=3D"secteam">Security team</a></h3>
=20
     <p>
       The security team consists of a subset of the project committers
@@ -252,7 +252,7 @@
       before disclosing a private issue.
     </p>
=20
-    <h2><a name=3D"roughconsensus">Rough consensus</a></h2>
+    <h2><a id=3D"roughconsensus">Rough consensus</a></h2>
=20
     <p>
       A core concept for governance of the project described above is
diff --git a/docs/hacking.html.in b/docs/hacking.html.in
index 975ee6935..efd053d16 100644
--- a/docs/hacking.html.in
+++ b/docs/hacking.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"patches">General tips for contributing patches</a></h2>
+    <h2><a id=3D"patches">General tips for contributing patches</a></h2>
     <ol>
       <li>
         <p>Discuss any large changes on the mailing list first.  Post patc=
hes
@@ -336,7 +336,7 @@
         Richard Jones' guide to working with open source projects</a>.
     </p>
=20
-    <h2><a name=3D"tooling">Tooling</a></h2>
+    <h2><a id=3D"tooling">Tooling</a></h2>
=20
     <p>
       libvirt includes support for some useful development tools right in =
its
@@ -356,7 +356,7 @@
       </li>
     </ul>
=20
-    <h2><a name=3D"naming">Naming conventions</a></h2>
+    <h2><a id=3D"naming">Naming conventions</a></h2>
=20
     <p>
       When reading libvirt code, a number of different naming conventions =
will
@@ -450,7 +450,7 @@
       </dd>
     </dl>
=20
-    <h2><a name=3D"indent">Code indentation</a></h2>
+    <h2><a id=3D"indent">Code indentation</a></h2>
     <p>
       Libvirt's C source code generally adheres to some basic code-formatt=
ing
       conventions.  The existing code base is not totally consistent on th=
is
@@ -487,7 +487,7 @@
       which will load the .lvimrc only when you edit libvirt code.
     </p>
=20
-    <h2><a name=3D"formatting">Code formatting (especially for new code)</=
a></h2>
+    <h2><a id=3D"formatting">Code formatting (especially for new code)</a>=
</h2>
=20
     <p>
       With new code, we can be even more strict.
@@ -523,7 +523,7 @@
     </p>
=20
=20
-    <h2><a name=3D"bracket_spacing">Bracket spacing</a></h2>
+    <h2><a id=3D"bracket_spacing">Bracket spacing</a></h2>
=20
     <p>
       The keywords <code>if</code>, <code>for</code>, <code>while</code>,
@@ -572,7 +572,7 @@
       int foo(int wizz);    // Good
 </pre>
=20
-    <h2><a name=3D"comma">Commas</a></h2>
+    <h2><a id=3D"comma">Commas</a></h2>
=20
     <p>
       Commas should always be followed by a space or end of line, and
@@ -609,7 +609,7 @@
       };
 </pre>
=20
-    <h2><a name=3D"semicolon">Semicolons</a></h2>
+    <h2><a id=3D"semicolon">Semicolons</a></h2>
=20
     <p>
       Semicolons should never have a space beforehand.  Inside the
@@ -638,7 +638,7 @@
       }
 </pre>
=20
-    <h2><a name=3D"curly_braces">Curly braces</a></h2>
+    <h2><a id=3D"curly_braces">Curly braces</a></h2>
=20
     <p>
       Omit the curly braces around an <code>if</code>, <code>while</code>,
@@ -819,7 +819,7 @@
   }
 </pre>
=20
-    <h2><a name=3D"preprocessor">Preprocessor</a></h2>
+    <h2><a id=3D"preprocessor">Preprocessor</a></h2>
=20
     <p>Macros defined with an ALL_CAPS name should generally be
       assumed to be unsafe with regards to arguments with side-effects
@@ -844,7 +844,7 @@
   #endif
 </pre>
=20
-    <h2><a name=3D"types">C types</a></h2>
+    <h2><a id=3D"types">C types</a></h2>
=20
     <p>
       Use the right type.
@@ -919,7 +919,7 @@
       it points to, or it is aliased to another pointer that is.
     </p>
=20
-    <h2><a name=3D"memalloc">Low level memory management</a></h2>
+    <h2><a id=3D"memalloc">Low level memory management</a></h2>
=20
     <p>
       Use of the malloc/free/realloc/calloc APIs is deprecated in the libv=
irt
@@ -1013,7 +1013,7 @@
       </li>
     </ul>
=20
-    <h2><a name=3D"file_handling">File handling</a></h2>
+    <h2><a id=3D"file_handling">File handling</a></h2>
=20
     <p>
       Usage of the <code>fdopen()</code>, <code>close()</code>, <code>fclo=
se()</code>
@@ -1059,7 +1059,7 @@
       </li>
     </ul>
=20
-    <h2><a name=3D"string_comparision">String comparisons</a></h2>
+    <h2><a id=3D"string_comparision">String comparisons</a></h2>
=20
     <p>
       Do not use the strcmp, strncmp, etc functions directly. Instead use
@@ -1109,7 +1109,7 @@
     </ul>
=20
=20
-    <h2><a name=3D"string_copying">String copying</a></h2>
+    <h2><a id=3D"string_copying">String copying</a></h2>
=20
     <p>
       Do not use the strncpy function.  According to the man page, it
@@ -1169,7 +1169,7 @@
       and usually considered a flaw.
     </p>
=20
-    <h2><a name=3D"strbuf">Variable length string buffer</a></h2>
+    <h2><a id=3D"strbuf">Variable length string buffer</a></h2>
=20
     <p>
       If there is a need for complex string concatenations, avoid using
@@ -1202,7 +1202,7 @@
 </pre>
=20
=20
-    <h2><a name=3D"includes">Include files</a></h2>
+    <h2><a id=3D"includes">Include files</a></h2>
=20
     <p>
       There are now quite a large number of include files, both libvirt
@@ -1251,7 +1251,7 @@
     </p>
=20
=20
-    <h2><a name=3D"printf">Printf-style functions</a></h2>
+    <h2><a id=3D"printf">Printf-style functions</a></h2>
=20
     <p>
       Whenever you add a new printf-style function, i.e., one with a format
@@ -1280,7 +1280,7 @@
       does for snprintf.
     </p>
=20
-    <h2><a name=3D"goto">Use of goto</a></h2>
+    <h2><a id=3D"goto">Use of goto</a></h2>
=20
     <p>
       The use of goto is not forbidden, and goto is widely used
@@ -1363,7 +1363,7 @@ int foo()
=20
=20
=20
-    <h2><a name=3D"committers">Libvirt committer guidelines</a></h2>
+    <h2><a id=3D"committers">Libvirt committer guidelines</a></h2>
=20
     <p>
       The AUTHORS files indicates the list of people with commit access ri=
ght
diff --git a/docs/hooks.html.in b/docs/hooks.html.in
index 11073cb78..7a04ac198 100644
--- a/docs/hooks.html.in
+++ b/docs/hooks.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"intro">Custom event scripts</a></h2>
+    <h2><a id=3D"intro">Custom event scripts</a></h2>
     <p>Beginning with libvirt 0.8.0, specific events on a host system will
        trigger custom scripts.</p>
     <p>These custom <b>hook</b> scripts are executed when any of the follo=
wing
@@ -26,7 +26,7 @@
           (<span class=3D"since">since 1.2.2</span>)<br/><br/></li>
     </ul>
=20
-    <h2><a name=3D"location">Script location</a></h2>
+    <h2><a id=3D"location">Script location</a></h2>
     <p>The libvirt hook scripts are located in the directory
        <code>$SYSCONFDIR/libvirt/hooks/</code>.</p>
     <ul>
@@ -42,7 +42,7 @@
        them executable.</p>
     <br/>
=20
-    <h2><a name=3D"names">Script names</a></h2>
+    <h2><a id=3D"names">Script names</a></h2>
     <p>At present, there are five hook scripts that can be called:</p>
     <ul>
       <li><code>/etc/libvirt/hooks/daemon</code><br/><br/>
@@ -61,7 +61,7 @@
     </ul>
     <br/>
=20
-    <h2><a name=3D"structure">Script structure</a></h2>
+    <h2><a id=3D"structure">Script structure</a></h2>
     <p>The hook scripts are executed using standard Linux process creation
        functions.  Therefore, they must begin with the declaration of the
        command interpreter to use.</p>
@@ -73,7 +73,7 @@
        binary, so you are welcome to use your favourite languages.</p>
     <br/>
=20
-    <h2><a name=3D"arguments">Script arguments</a></h2>
+    <h2><a id=3D"arguments">Script arguments</a></h2>
     <p>The hook scripts are called with specific command line arguments,
        depending upon the script, and the operation being performed.</p>
     <p>The guest hook scripts, qemu and lxc, are also given the <b>full</b>
@@ -128,10 +128,10 @@
           none.</li>
     </ol>
=20
-    <h4><a name=3D"arguments_specifics">Specifics</a></h4>
+    <h4><a id=3D"arguments_specifics">Specifics</a></h4>
     <p>This translates to the following specifics for each hook script:</p>
=20
-    <h5><a name=3D"daemon">/etc/libvirt/hooks/daemon</a></h5>
+    <h5><a id=3D"daemon">/etc/libvirt/hooks/daemon</a></h5>
     <ul>
       <li>When the libvirt daemon is started, this script is called as:<br=
/>
           <pre>/etc/libvirt/hooks/daemon - start - start</pre></li>
@@ -146,7 +146,7 @@
        with the "start" operation.  There is no specific operation to indi=
cate
        a "restart" is occurring.</p>
=20
-    <h5><a name=3D"qemu">/etc/libvirt/hooks/qemu</a></h5>
+    <h5><a id=3D"qemu">/etc/libvirt/hooks/qemu</a></h5>
     <ul>
       <li>Before a QEMU guest is started, the qemu hook script is
         called in three locations; if any location fails, the guest
@@ -206,7 +206,7 @@
       </li>
     </ul>
=20
-    <h5><a name=3D"lxc">/etc/libvirt/hooks/lxc</a></h5>
+    <h5><a id=3D"lxc">/etc/libvirt/hooks/lxc</a></h5>
     <ul>
       <li>Before a LXC guest is started, the lxc hook script is
         called in three locations; if any location fails, the guest
@@ -240,7 +240,7 @@
       </li>
     </ul>
=20
-    <h5><a name=3D"libxl">/etc/libvirt/hooks/libxl</a></h5>
+    <h5><a id=3D"libxl">/etc/libvirt/hooks/libxl</a></h5>
     <ul>
       <li>Before a Xen guest is started using libxl driver, the libxl hook
         script is called in three locations; if any location fails, the gu=
est
@@ -284,7 +284,7 @@
       </li>
     </ul>
=20
-    <h5><a name=3D"network">/etc/libvirt/hooks/network</a></h5>
+    <h5><a id=3D"network">/etc/libvirt/hooks/network</a></h5>
     <ul>
       <li><span class=3D"since">Since 1.2.2</span>, before a network is st=
arted,
         this script is called as:<br/>
@@ -310,7 +310,7 @@
=20
     <br/>
=20
-    <h2><a name=3D"execution">Script execution</a></h2>
+    <h2><a id=3D"execution">Script execution</a></h2>
     <ul>
       <li>The "start" operation for the guest and network hook scripts,
           executes <b>prior</b> to the object (guest or network) being cre=
ated.
@@ -335,7 +335,7 @@
     </ul>
     <br/>
=20
-    <h2><a name=3D"qemu_migration">QEMU guest migration</a></h2>
+    <h2><a id=3D"qemu_migration">QEMU guest migration</a></h2>
     <p>Migration of a QEMU guest involves running hook scripts on both the
        source and destination hosts:</p>
     <ol>
@@ -357,14 +357,14 @@
     </ol>
     <br/>
=20
-    <h2><a name=3D"recursive">Calling libvirt functions from within a hook=
 script</a></h2>
+    <h2><a id=3D"recursive">Calling libvirt functions from within a hook s=
cript</a></h2>
     <p><b>DO NOT DO THIS!</b></p>
     <p>A hook script must not call back into libvirt, as the libvirt daemon
        is already waiting for the script to exit.</p>
     <p>A deadlock is likely to occur.</p>
     <br/>
=20
-    <h2><a name=3D"return_codes">Return codes and logging</a></h2>
+    <h2><a id=3D"return_codes">Return codes and logging</a></h2>
     <p>If a hook script returns with an exit code of 0, the libvirt daemon
        regards this as successful and performs no logging of it.</p>
     <p>However, if a hook script returns with a non zero exit code, the li=
bvirt
diff --git a/docs/internals/command.html.in b/docs/internals/command.html.in
index 2d8b09308..e21b12e53 100644
--- a/docs/internals/command.html.in
+++ b/docs/internals/command.html.in
@@ -12,7 +12,7 @@
       All code is required to use these APIs
     </p>
=20
-    <h2><a name=3D"posix">Problems with standard POSIX APIs</a></h2>
+    <h2><a id=3D"posix">Problems with standard POSIX APIs</a></h2>
=20
     <p>
       The POSIX specification includes a number of APIs for
@@ -62,7 +62,7 @@
       error prone, particularly wrt memory leak / OOM handling.
     </p>
=20
-    <h2><a name=3D"api">The libvirt command execution API</a></h2>
+    <h2><a id=3D"api">The libvirt command execution API</a></h2>
=20
     <p>
       There is now a high level API that provides a safe and
@@ -72,7 +72,7 @@
       header which can be imported using <code>#include "vircommand.h"</co=
de>
     </p>
=20
-    <h3><a name=3D"initial">Defining commands in libvirt</a></h3>
+    <h3><a id=3D"initial">Defining commands in libvirt</a></h3>
=20
     <p>
       The first step is to declare what command is to be
@@ -92,7 +92,7 @@ virCommandPtr cmd =3D virCommandNew("/usr/bin/dnsmasq");
       reported at a later time.
     </p>
=20
-    <h3><a name=3D"args">Adding arguments to the command</a></h3>
+    <h3><a id=3D"args">Adding arguments to the command</a></h3>
=20
     <p>
       There are a number of APIs for adding arguments to a
@@ -150,7 +150,7 @@ virCommandPtr cmd2 =3D virCommandNewArgList("/usr/bin/d=
nsmasq",
                                           "--domain", "localdomain", NULL);
 </pre>
=20
-    <h3><a name=3D"env">Setting up the environment</a></h3>
+    <h3><a id=3D"env">Setting up the environment</a></h3>
=20
     <p>
       By default a command will inherit all environment variables
@@ -199,7 +199,7 @@ virCommandAddEnvPair(cmd, "TERM", "xterm");
 virCommandAddEnvString(cmd, "TERM=3Dxterm");
 </pre>
=20
-    <h3><a name=3D"misc">Miscellaneous other options</a></h3>
+    <h3><a id=3D"misc">Miscellaneous other options</a></h3>
=20
     <p>
       Normally the spawned command will retain the current
@@ -229,7 +229,7 @@ virCommandSetPidFile(cmd, "/var/run/dnsmasq.pid");
       the intermediate process exits.
     </p>
=20
-    <h3><a name=3D"privs">Reducing command privileges</a></h3>
+    <h3><a id=3D"privs">Reducing command privileges</a></h3>
=20
     <p>
       Normally a command will inherit all privileges of
@@ -243,7 +243,7 @@ virCommandSetPidFile(cmd, "/var/run/dnsmasq.pid");
 virCommandClearCaps(cmd);
 </pre>
=20
-    <h3><a name=3D"fds">Managing file handles</a></h3>
+    <h3><a id=3D"fds">Managing file handles</a></h3>
=20
     <p>
       To prevent unintended resource leaks to child processes, the
@@ -329,7 +329,7 @@ virCommandSetErrorFD(cmd, &amp;errfd);
 virCommandNonblockingFDs(cmd);
 </pre>
=20
-    <h3><a name=3D"buffers">Feeding &amp; capturing strings to/from the ch=
ild</a></h3>
+    <h3><a id=3D"buffers">Feeding &amp; capturing strings to/from the chil=
d</a></h3>
=20
     <p>
       Often dealing with file handles for stdin/out/err is
@@ -382,7 +382,7 @@ virCommandSetErrorBuffer(cmd, &amp;errors);
       case the child process interleaves output into a single string.
     </p>
=20
-    <h3><a name=3D"directory">Setting working directory</a></h3>
+    <h3><a id=3D"directory">Setting working directory</a></h3>
=20
     <p>
       Daemonized commands are always run with "/" as the current
@@ -395,7 +395,7 @@ virCommandSetErrorBuffer(cmd, &amp;errors);
 virCommandSetWorkingDirectory(cmd, LOCALSTATEDIR);
 </pre>
=20
-    <h3><a name=3D"hooks">Any additional hooks</a></h3>
+    <h3><a id=3D"hooks">Any additional hooks</a></h3>
=20
     <p>
       If anything else is needed, it is possible to request a hook
@@ -409,7 +409,7 @@ virCommandSetWorkingDirectory(cmd, LOCALSTATEDIR);
 virCommandSetPreExecHook(cmd, hook, opaque);
 </pre>
=20
-    <h3><a name=3D"logging">Logging commands</a></h3>
+    <h3><a id=3D"logging">Logging commands</a></h3>
=20
     <p>
       Sometimes, it is desirable to log what command will be run, or
@@ -434,7 +434,7 @@ if (virCommandRun(cmd, NULL) &lt; 0)
     return -1;
 </pre>
=20
-    <h3><a name=3D"sync">Running commands synchronously</a></h3>
+    <h3><a id=3D"sync">Running commands synchronously</a></h3>
=20
     <p>
       For most commands, the desired behaviour is to spawn
@@ -480,7 +480,7 @@ if (WIFEXITED(status) &amp;&amp; WEXITSTATUS(status) =
=3D=3D 1) {
 }
 </pre>
=20
-    <h3><a name=3D"async">Running commands asynchronously</a></h3>
+    <h3><a id=3D"async">Running commands asynchronously</a></h3>
=20
     <p>
       In certain complex scenarios, particularly special
@@ -530,7 +530,7 @@ if (WEXITSTATUS(status)...) {
       virCommandAbort to reap the process.
     </p>
=20
-    <h3><a name=3D"release">Releasing resources</a></h3>
+    <h3><a id=3D"release">Releasing resources</a></h3>
=20
     <p>
       Once the command has been executed, or if execution
@@ -550,7 +550,7 @@ virCommandFree(cmd);
       it will be forcibly killed and cleaned up (via waitpid).
     </p>
=20
-    <h2><a name=3D"example">Complete examples</a></h2>
+    <h2><a id=3D"example">Complete examples</a></h2>
=20
     <p>
       This shows a complete example usage of the APIs roughly
diff --git a/docs/internals/eventloop.html.in b/docs/internals/eventloop.ht=
ml.in
index a01e104e8..fe7bf3aaf 100644
--- a/docs/internals/eventloop.html.in
+++ b/docs/internals/eventloop.html.in
@@ -11,7 +11,7 @@
       libvirt. Both server and client.
     </p>
=20
-    <h2><a name=3D"event_loop">Event driven programming</a></h2>
+    <h2><a id=3D"event_loop">Event driven programming</a></h2>
=20
     <p>Traditionally, a program simply ran once, then terminated.
     This type of program was very common in the early days of
@@ -38,7 +38,7 @@
     file descriptor which is then watched for incoming events,
     e.g. messages. </p>
=20
-    <h2><a name=3D"api">The event loop API</a></h2>
+    <h2><a id=3D"api">The event loop API</a></h2>
=20
     <p>To work with event loop from our code we have plenty of
     APIs.</p>
@@ -62,7 +62,7 @@
     <p>For more information on these APIs continue reading <a
     href=3D"../html/libvirt-libvirt-event.html">here</a>.</p>
=20
-    <h2><a name=3D"worker_pool">Worker pool</a></h2>
+    <h2><a id=3D"worker_pool">Worker pool</a></h2>
=20
     <p>Looking back at the image above we can see one big
     limitation. While processing a message event loop is blocked
diff --git a/docs/internals/locking.html.in b/docs/internals/locking.html.in
index 09cc2ba4a..4222c44d3 100644
--- a/docs/internals/locking.html.in
+++ b/docs/internals/locking.html.in
@@ -12,7 +12,7 @@
       access to content.
     </p>
=20
-    <h2><a name=3D"goals">Goals</a></h2>
+    <h2><a id=3D"goals">Goals</a></h2>
=20
     <p>
       The high level goal is to prevent the same disk image being
@@ -36,7 +36,7 @@
       </li>
     </ol>
=20
-    <h2><a name=3D"requirement">Requirements</a></h2>
+    <h2><a id=3D"requirement">Requirements</a></h2>
=20
     <p>
       The high level goal leads to a set of requirements
@@ -67,7 +67,7 @@
       </li>
     </ol>
=20
-    <h2><a name=3D"design">Design</a></h2>
+    <h2><a id=3D"design">Design</a></h2>
=20
     <p>
       Within a lock manager the following series of operations
@@ -102,7 +102,7 @@
       </li>
     </ul>
=20
-    <h2><a name=3D"impl">Plugin Implementations</a></h2>
+    <h2><a id=3D"impl">Plugin Implementations</a></h2>
=20
     <p>
       Lock manager implementations are provided as LGPLv2+
@@ -132,7 +132,7 @@
       in the previously mentioned header file
     </p>
=20
-    <h2><a name=3D"qemuIntegrate">QEMU Driver integration</a></h2>
+    <h2><a id=3D"qemuIntegrate">QEMU Driver integration</a></h2>
=20
     <p>
       With the QEMU driver, the lock plugin will be set
@@ -149,7 +149,7 @@ lockManager=3D"sanlock"
       for backwards compatibility
     </p>
=20
-    <h2><a name=3D"usagePatterns">Lock usage patterns</a></h2>
+    <h2><a id=3D"usagePatterns">Lock usage patterns</a></h2>
=20
     <p>
       The following pseudo code illustrates the common
@@ -157,7 +157,7 @@ lockManager=3D"sanlock"
       manager plugin callbacks.
     </p>
=20
-    <h3><a name=3D"usageLockAcquire">Lock acquisition</a></h3>
+    <h3><a id=3D"usageLockAcquire">Lock acquisition</a></h3>
=20
     <p>
       Initial lock acquisition will be performed from the
@@ -205,7 +205,7 @@ if (virLockManagerAcquire(lock, NULL, 0) &lt; 0);
   ...abort...
     </pre>
=20
-    <h3><a name=3D"usageLockAttach">Lock release</a></h3>
+    <h3><a id=3D"usageLockAttach">Lock release</a></h3>
=20
     <p>
       The locks are all implicitly released when the process
diff --git a/docs/internals/oomtesting.html.in b/docs/internals/oomtesting.=
html.in
index c5edacff6..aca8fde13 100644
--- a/docs/internals/oomtesting.html.in
+++ b/docs/internals/oomtesting.html.in
@@ -26,7 +26,7 @@ $ ./configure --enable-test-oom
 </pre>
=20
=20
-    <h2><a name=3D"basicoom">Basic OOM testing support</a></h2>
+    <h2><a id=3D"basicoom">Basic OOM testing support</a></h2>
=20
     <p>
       The first step in validating OOM usage is to run a test suite
@@ -64,7 +64,7 @@ $ VIR_TEST_OOM=3D1 ./qemuxml2argvtest
       of memory allocations from that test case.
     </p>
=20
-    <h3><a name=3D"valgrind">Tracking failures with valgrind</a></h3>
+    <h3><a id=3D"valgrind">Tracking failures with valgrind</a></h3>
=20
     <p>
       The test suite should obviously *not* crash during OOM testing.
@@ -88,7 +88,7 @@ $ VIR_TEST_OOM=3D1 VIR_TEST_RANGE=3D5 ../run valgrind ./q=
emuxml2argvtest
       access.
     </p>
=20
-    <h3><a name=3D"stacktraces">Tracking failures with stack traces</a></h=
3>
+    <h3><a id=3D"stacktraces">Tracking failures with stack traces</a></h3>
=20
     <p>
       With some really difficult bugs valgrind is not sufficient to
@@ -191,7 +191,7 @@ _start
 ??:?
     </pre>
=20
-    <h3><a name=3D"noncrash">Non-crash related problems</a></h3>
+    <h3><a id=3D"noncrash">Non-crash related problems</a></h3>
=20
     <p>
       Not all memory allocation bugs result in code crashing. Sometimes
diff --git a/docs/internals/rpc.html.in b/docs/internals/rpc.html.in
index 9107b97a2..98f8be07b 100644
--- a/docs/internals/rpc.html.in
+++ b/docs/internals/rpc.html.in
@@ -17,7 +17,7 @@
     </p>
=20
=20
-    <h2><a name=3D"protocol">RPC protocol</a></h2>
+    <h2><a id=3D"protocol">RPC protocol</a></h2>
=20
     <p>
       libvirt uses a simple, variable length, packet based RPC protocol.
@@ -193,14 +193,14 @@
       definition for the program+version in question
     </p>
=20
-    <h3><a name=3D"wireexamples">Wire examples</a></h3>
+    <h3><a id=3D"wireexamples">Wire examples</a></h3>
=20
     <p>
       The following diagrams illustrate some example packet exchanges
       between a client and server
     </p>
=20
-    <h4><a name=3D"wireexamplescall">Method call</a></h4>
+    <h4><a id=3D"wireexamplescall">Method call</a></h4>
=20
     <p>
       A single method call and successful
@@ -219,7 +219,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;--=
 S  (reply)
        +--+-----------------------+--------+
     </pre>
=20
-    <h4><a name=3D"wireexamplescallerr">Method call with error</a></h4>
+    <h4><a id=3D"wireexamplescallerr">Method call with error</a></h4>
=20
     <p>
       An unsuccessful method call will instead return an error object
@@ -235,7 +235,7 @@ C &lt;--  |48| 8 | 1 | 3 | 2 | 1 | 0 | .o.oOo.o.oOo.o.o=
Oo.o.oOo |  &lt;-- S  (er
        +--+-----------------------+--------------------------+
     </pre>
=20
-    <h4><a name=3D"wireexamplescallup">Method call with upload stream</a><=
/h4>
+    <h4><a id=3D"wireexamplescallup">Method call with upload stream</a></h=
4>
=20
     <p>
       A method call which also involves uploading some data over
@@ -272,7 +272,7 @@ C &lt;--  |24| 8 | 1 | 3 | 3 | 1 | 0 | &lt;-- S  (strea=
m finish)
        +--+-----------------------+
     </pre>
=20
-    <h4><a name=3D"wireexamplescallbi">Method call bidirectional stream</a=
></h4>
+    <h4><a id=3D"wireexamplescallbi">Method call bidirectional stream</a><=
/h4>
=20
     <p>
       A method call which also involves a bi-directional stream will
@@ -328,7 +328,7 @@ C &lt;--  |24| 8 | 1 | 3 | 3 | 1 | 0 | &lt;-- S  (strea=
m finish)
     </pre>
=20
=20
-    <h4><a name=3D"wireexamplescallmany">Method calls overlapping</a></h4>
+    <h4><a id=3D"wireexamplescallmany">Method calls overlapping</a></h4>
     <pre>
        +--+-----------------------+-----------+
 C --&gt;  |38| 8 | 1 | 3 | 0 | 1 | 0 | .o.oOo.o. |  --&gt; S  (call 1)
@@ -356,7 +356,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 4 | 0 | .o.oOo |  &lt;--=
 S  (reply 4)
        +--+-----------------------+--------+
     </pre>
=20
-    <h4><a name=3D"wireexamplescallfd">Method call with passed FD</a></h4>
+    <h4><a id=3D"wireexamplescallfd">Method call with passed FD</a></h4>
=20
     <p>
       A single method call with 2 passed file descriptors and successful
@@ -378,14 +378,14 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;=
-- S  (reply)
     </pre>
=20
=20
-    <h2><a name=3D"security">RPC security</a></h2>
+    <h2><a id=3D"security">RPC security</a></h2>
=20
     <p>
       There are various things to consider to ensure an implementation
       of the RPC protocol can be satisfactorily secured
     </p>
=20
-    <h3><a name=3D"securitytls">Authentication/encryption</a></h3>
+    <h3><a id=3D"securitytls">Authentication/encryption</a></h3>
=20
     <p>
       The basic RPC protocol does not define or require any specific
@@ -399,7 +399,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;--=
 S  (reply)
       stream can of course be tunnelled over transports such as SSH.
     </p>
=20
-    <h3><a name=3D"securitylimits">Data limits</a></h3>
+    <h3><a id=3D"securitylimits">Data limits</a></h3>
=20
     <p>
       Although the protocol itself defines many arbitrary sized data value=
s in the
@@ -411,7 +411,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;--=
 S  (reply)
       breaking compatibility of the RPC data on the wire.
     </p>
=20
-    <h3><a name=3D"securityvalidate">Data validation</a></h3>
+    <h3><a id=3D"securityvalidate">Data validation</a></h3>
=20
     <p>
       It is important that all data be fully validated before performing
@@ -427,7 +427,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;--=
 S  (reply)
       execution API (e.g. corresponding libvirt public API).
     </p>
=20
-    <h2><a name=3D"internals">RPC internal APIs</a></h2>
+    <h2><a id=3D"internals">RPC internal APIs</a></h2>
=20
     <p>
       The generic internal RPC library code lives in the <code>src/rpc/</c=
ode>
@@ -436,7 +436,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;--=
 S  (reply)
       purposes are:
     </p>
=20
-    <h3><a name=3D"apioverview">Overview of RPC objects</a></h3>
+    <h3><a id=3D"apioverview">Overview of RPC objects</a></h3>
=20
     <p>
       The following is a high level overview of the role of each
@@ -568,7 +568,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;--=
 S  (reply)
       </dd>
     </dl>
=20
-    <h3><a name=3D"apiclientdispatch">Client RPC dispatch</a></h3>
+    <h3><a id=3D"apiclientdispatch">Client RPC dispatch</a></h3>
=20
     <p>
       The client RPC code must allow for multiple overlapping RPC method
@@ -601,7 +601,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;--=
 S  (reply)
       grabs the buck, and re-enabled when the buck is released.
     </p>
=20
-    <h4><a name=3D"apiclientdispatchex1">Example with buck passing</a></h4>
+    <h4><a id=3D"apiclientdispatchex1">Example with buck passing</a></h4>
=20
     <p>
       In the first example, a second thread issues an API call
@@ -649,7 +649,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;--=
 S  (reply)
                       Return API2()
     </pre>
=20
-    <h4><a name=3D"apiclientdispatchex2">Example without buck passing</a><=
/h4>
+    <h4><a id=3D"apiclientdispatchex2">Example without buck passing</a></h=
4>
=20
     <p>
       In this second example, a second thread issues an API call
@@ -699,7 +699,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;--=
 S  (reply)
        Return API1()
     </pre>
=20
-    <h4><a name=3D"apiclientdispatchex3">Example with async events</a></h4>
+    <h4><a id=3D"apiclientdispatchex3">Example with async events</a></h4>
=20
     <p>
       In this example, only one thread is present and it has to
@@ -739,7 +739,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;--=
 S  (reply)
                           ...
     </pre>
=20
-    <h3><a name=3D"apiserverdispatch">Server RPC dispatch</a></h3>
+    <h3><a id=3D"apiserverdispatch">Server RPC dispatch</a></h3>
=20
     <p>
       The RPC server code must support receipt of incoming RPC requests fr=
om
@@ -827,7 +827,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;--=
 S  (reply)
       queue.
     </p>
=20
-    <h4><a name=3D"apiserverdispatchex1">Example with overlapping methods<=
/a></h4>
+    <h4><a id=3D"apiserverdispatchex1">Example with overlapping methods</a=
></h4>
=20
     <p>
       This example illustrates processing of two incoming methods with
@@ -874,7 +874,7 @@ C &lt;--  |32| 8 | 1 | 3 | 1 | 1 | 0 | .o.oOo |  &lt;--=
 S  (reply)
       ...
     </pre>
=20
-    <h4><a name=3D"apiserverdispatchex2">Example with stream data</a></h4>
+    <h4><a id=3D"apiserverdispatchex2">Example with stream data</a></h4>
=20
     <p>
       This example illustrates processing of stream data
diff --git a/docs/locking-lockd.html.in b/docs/locking-lockd.html.in
index fe007b107..42fcf0e68 100644
--- a/docs/locking-lockd.html.in
+++ b/docs/locking-lockd.html.in
@@ -12,7 +12,7 @@
       plugin for virtual machine disk mutual exclusion.
     </p>
=20
-    <h2><a name=3D"background">virtlockd background</a></h2>
+    <h2><a id=3D"background">virtlockd background</a></h2>
=20
     <p>
       The virtlockd daemon is a single purpose binary which
@@ -26,7 +26,7 @@
       commonly used filesystems.
     </p>
=20
-    <h2><a name=3D"sanlock">virtlockd daemon setup</a></h2>
+    <h2><a id=3D"sanlock">virtlockd daemon setup</a></h2>
=20
     <p>
       In most OS, the virtlockd daemon itself will not require
@@ -53,7 +53,7 @@
       setup at all.
     </p>
=20
-    <h2><a name=3D"lockdplugin">libvirt lockd plugin configuration</a></h2>
+    <h2><a id=3D"lockdplugin">libvirt lockd plugin configuration</a></h2>
=20
     <p>
       Once the virtlockd daemon is running, or setup to autostart,
@@ -127,7 +127,7 @@ $ su - root
       the same locking mechanism
     </p>
=20
-    <h2><a name=3D"qemuconfig">QEMU/KVM driver configuration</a></h2>
+    <h2><a id=3D"qemuconfig">QEMU/KVM driver configuration</a></h2>
=20
     <p>
       The QEMU driver is capable of using the virtlockd plugin
diff --git a/docs/locking-sanlock.html.in b/docs/locking-sanlock.html.in
index 12fc3d724..08182065d 100644
--- a/docs/locking-sanlock.html.in
+++ b/docs/locking-sanlock.html.in
@@ -13,7 +13,7 @@
       plugin for virtual machine disk mutual exclusion.
     </p>
=20
-    <h2><a name=3D"sanlock">Sanlock daemon setup</a></h2>
+    <h2><a id=3D"sanlock">Sanlock daemon setup</a></h2>
=20
     <p>
       On many operating systems, the <strong>sanlock</strong> plugin
@@ -68,7 +68,7 @@ SANLOCKOPTS=3D"-w 0"
       steps as necessary.
     </p>
=20
-    <h2><a name=3D"sanlockplugin">libvirt sanlock plugin configuration</a>=
</h2>
+    <h2><a id=3D"sanlockplugin">libvirt sanlock plugin configuration</a></=
h2>
=20
     <p>
       Once the sanlock daemon is running, the next step is to
@@ -91,7 +91,7 @@ $ su - root
       unique value for the host.
     </p>
=20
-    <h2><a name=3D"sanlockstorage">libvirt sanlock storage configuration</=
a></h2>
+    <h2><a id=3D"sanlockstorage">libvirt sanlock storage configuration</a>=
</h2>
=20
     <p>
       The sanlock plugin needs to create leases in a directory
@@ -152,7 +152,7 @@ augtool -s set /files/etc/libvirt/qemu-sanlock.conf/gro=
up sanlock
       it should be sufficient to run the cleanup once a week.
     </p>
=20
-    <h2><a name=3D"qemuconfig">QEMU/KVM driver configuration</a></h2>
+    <h2><a id=3D"qemuconfig">QEMU/KVM driver configuration</a></h2>
=20
     <p>
       The QEMU/KVM driver is fully integrated with the lock
@@ -219,7 +219,7 @@ __LIBVIRT__DISKS__
 &lt;/pool&gt;
     </pre>
=20
-    <h2><a name=3D"domainconfig">Domain configuration</a></h2>
+    <h2><a id=3D"domainconfig">Domain configuration</a></h2>
=20
     <p>
       In case sanlock loses access to disk locks for some reason, it will
diff --git a/docs/locking.html.in b/docs/locking.html.in
index aca18113d..f0e0a3868 100644
--- a/docs/locking.html.in
+++ b/docs/locking.html.in
@@ -15,7 +15,7 @@
       aware filesystem.
     </p>
=20
-    <h2><a name=3D"plugins">Lock manager plugins</a></h2>
+    <h2><a id=3D"plugins">Lock manager plugins</a></h2>
=20
     <p>
       The lock manager framework has a pluggable architecture,
diff --git a/docs/logging.html.in b/docs/logging.html.in
index bcec17940..534afa1cd 100644
--- a/docs/logging.html.in
+++ b/docs/logging.html.in
@@ -12,7 +12,7 @@
     <ul id=3D"toc"/>
=20
     <h2>
-      <a name=3D"log_library">Logging in the library</a>
+      <a id=3D"log_library">Logging in the library</a>
     </h2>
     <p>The logging functionalities in libvirt are based on 3 key concepts,
        similar to the one present in other generic logging facilities like
@@ -40,7 +40,7 @@
     </ul>
=20
     <h2>
-      <a name=3D"log_config">Configuring logging in the library</a>
+      <a id=3D"log_config">Configuring logging in the library</a>
     </h2>
     <p>The library configuration of logging is through 3 environment varia=
bles
     allowing to control the logging behaviour:</p>
@@ -61,7 +61,7 @@
        have an error in a filter or output string, some of the settings ma=
y be
        applied up to the point at which libvirt encountered the error.</p>
     <h2>
-      <a name=3D"log_daemon">Logging in the daemon</a>
+      <a id=3D"log_daemon">Logging in the daemon</a>
     </h2>
     <p>Similarly the daemon logging behaviour can be tuned using 3 config
     variables, stored in the configuration file:</p>
@@ -96,7 +96,7 @@
        for debugging purposes by sending the daemon a USR2 signal:</p>
        <pre>killall -USR2 libvirtd</pre>
     <h2>
-      <a name=3D"log_syntax">Syntax for filters and output values</a>
+      <a id=3D"log_syntax">Syntax for filters and output values</a>
     </h2>
     <p>The syntax for filters and outputs is the same for both types of
        variables.</p>
@@ -149,7 +149,7 @@ x:+name (log message + stack trace)</pre>
        but also log all debug and information included in the
        file <code>/tmp/libvirt.log</code></p>
=20
-    <h2><a name=3D"journald">Systemd journal fields</a></h2>
+    <h2><a id=3D"journald">Systemd journal fields</a></h2>
=20
     <p>
       When logging to the systemd journal, the following fields
@@ -176,7 +176,7 @@ x:+name (log message + stack trace)</pre>
       <dd>The libvirt error code (values from virErrorCode enum), if LIBVI=
RT_SOURCE=3D"error"</dd>
     </dl>
=20
-    <h3><a name=3D"journaldids">Well known message ID values</a></h3>
+    <h3><a id=3D"journaldids">Well known message ID values</a></h3>
=20
     <p>
       Certain areas of the code will emit log records tagged with well kno=
wn
@@ -221,7 +221,7 @@ $ journalctl MESSAGE_ID=3D8ae2f3fb-2dbe-498e-8fbd-012d4=
0afa361 --output=3Djson
     </pre>
=20
     <h2>
-      <a name=3D"log_examples">Examples</a>
+      <a id=3D"log_examples">Examples</a>
     </h2>
     <p>For example setting up the following:</p>
     <pre>export LIBVIRT_DEBUG=3D1
diff --git a/docs/migration.html.in b/docs/migration.html.in
index a57f27918..d82fb54b4 100644
--- a/docs/migration.html.in
+++ b/docs/migration.html.in
@@ -13,7 +13,7 @@
       libvirt implements several options for migration.
     </p>
=20
-    <h2><a name=3D"transport">Network data transports</a></h2>
+    <h2><a id=3D"transport">Network data transports</a></h2>
=20
     <p>
       There are two options for the data transport used during migration, =
either
@@ -21,7 +21,7 @@
       over a libvirtd connection.
     </p>
=20
-    <h3><a name=3D"transportnative">Hypervisor native transport</a></h3>
+    <h3><a id=3D"transportnative">Hypervisor native transport</a></h3>
     <p>
       <em>Native</em> data transports may or may not support encryption, d=
epending
       on the hypervisor in question, but will typically have the lowest co=
mputational costs
@@ -35,7 +35,7 @@
       <img class=3D"diagram" src=3D"migration-native.png" alt=3D"Migration=
 native path"/>
     </p>
=20
-    <h3><a name=3D"transporttunnel">libvirt tunnelled transport</a></h3>
+    <h3><a id=3D"transporttunnel">libvirt tunnelled transport</a></h3>
     <p>
       <em>Tunnelled</em> data transports will always be capable of strong =
encryption
       since they are able to leverage the capabilities built in to the lib=
virt RPC protocol.
@@ -53,7 +53,7 @@
       <img class=3D"diagram" src=3D"migration-tunnel.png" alt=3D"Migration=
 tunnel path"/>
     </p>
=20
-    <h2><a name=3D"flow">Communication control paths/flows</a></h2>
+    <h2><a id=3D"flow">Communication control paths/flows</a></h2>
=20
     <p>
       Migration of virtual machines requires close co-ordination of the two
@@ -61,7 +61,7 @@
       which may be on the source, the destination, or a third host.
     </p>
=20
-    <h3><a name=3D"flowmanageddirect">Managed direct migration</a></h3>
+    <h3><a id=3D"flowmanageddirect">Managed direct migration</a></h3>
=20
     <p>
       With <em>managed direct</em> migration, the libvirt client process
@@ -81,7 +81,7 @@
     </p>
=20
=20
-    <h3><a name=3D"flowpeer2peer">Managed peer to peer migration</a></h3>
+    <h3><a id=3D"flowpeer2peer">Managed peer to peer migration</a></h3>
=20
     <p>
       With <em>peer to peer</em> migration, the libvirt client process only
@@ -103,7 +103,7 @@
     </p>
=20
=20
-    <h3><a name=3D"flowunmanageddirect">Unmanaged direct migration</a></h3>
+    <h3><a id=3D"flowunmanageddirect">Unmanaged direct migration</a></h3>
=20
     <p>
       With <em>unmanaged direct</em> migration, neither the libvirt client
@@ -119,7 +119,7 @@
     </p>
=20
=20
-    <h2><a name=3D"security">Data security</a></h2>
+    <h2><a id=3D"security">Data security</a></h2>
=20
     <p>
       Since the migration data stream includes a complete copy of the guest
@@ -138,7 +138,7 @@
       facility should be used.
     </p>
=20
-    <h2><a name=3D"offline">Offline migration</a></h2>
+    <h2><a id=3D"offline">Offline migration</a></h2>
=20
     <p>
       Offline migration transfers inactive the definition of a domain
@@ -153,7 +153,7 @@
       offline migration.
     </p>
=20
-    <h2><a name=3D"uris">Migration URIs</a></h2>
+    <h2><a id=3D"uris">Migration URIs</a></h2>
=20
     <p>
       Initiating a guest migration requires the client application to
@@ -203,7 +203,7 @@
         to comply with local firewall policies.</li>
     </ol>
=20
-    <h2><a name=3D"config">Configuration file handling</a></h2>
+    <h2><a id=3D"config">Configuration file handling</a></h2>
=20
     <p>
       There are two types of virtual machine known to libvirt. A <em>trans=
ient</em>
@@ -446,10 +446,10 @@
       </tbody>
     </table>
=20
-    <h2><a name=3D"scenarios">Migration scenarios</a></h2>
+    <h2><a id=3D"scenarios">Migration scenarios</a></h2>
=20
=20
-    <h3><a name=3D"scenarionativedirect">Native migration, client to two l=
ibvirtd servers</a></h3>
+    <h3><a id=3D"scenarionativedirect">Native migration, client to two lib=
virtd servers</a></h3>
=20
     <p>
       At an API level this requires use of virDomainMigrate, without the
@@ -479,7 +479,7 @@ virsh migrate web1 xen+tcp://desthost/system  xenmigr:1=
0.0.0.1/
       Supported by Xen, QEMU, VMware and VirtualBox drivers
     </p>
=20
-    <h3><a name=3D"scenarionativepeer2peer">Native migration, client to an=
d peer2peer between, two libvirtd servers</a></h3>
+    <h3><a id=3D"scenarionativepeer2peer">Native migration, client to and =
peer2peer between, two libvirtd servers</a></h3>
=20
     <p>
       virDomainMigrate, with the VIR_MIGRATE_PEER2PEER flag set,
@@ -503,7 +503,7 @@ virsh migrate web1 xen+tcp://desthost/system  xenmigr:1=
0.0.0.1/
       Supported by QEMU driver
     </p>
=20
-    <h3><a name=3D"scenariotunnelpeer2peer1">Tunnelled migration, client a=
nd peer2peer between two libvirtd servers</a></h3>
+    <h3><a id=3D"scenariotunnelpeer2peer1">Tunnelled migration, client and=
 peer2peer between two libvirtd servers</a></h3>
=20
     <p>
       virDomainMigrate, with the VIR_MIGRATE_PEER2PEER &amp; VIR_MIGRATE_T=
UNNELLED
@@ -526,7 +526,7 @@ virsh migrate web1 xen+tcp://desthost/system  xenmigr:1=
0.0.0.1/
       Supported by QEMU driver
     </p>
=20
-    <h3><a name=3D"nativedirectunmanaged">Native migration, client to one =
libvirtd server</a></h3>
+    <h3><a id=3D"nativedirectunmanaged">Native migration, client to one li=
bvirtd server</a></h3>
=20
     <p>
       virDomainMigrateToURI, without the VIR_MIGRATE_PEER2PEER flag set,
@@ -550,7 +550,7 @@ virsh migrate --direct web1 xenmigr://desthost/
       Supported by Xen driver
     </p>
=20
-    <h3><a name=3D"nativepeer2peer">Native migration, peer2peer between tw=
o libvirtd servers</a></h3>
+    <h3><a id=3D"nativepeer2peer">Native migration, peer2peer between two =
libvirtd servers</a></h3>
=20
     <p>
       virDomainMigrateToURI, with the VIR_MIGRATE_PEER2PEER flag set,
@@ -587,7 +587,7 @@ virsh migrate --p2p web1 qemu+ssh://desthost/system qem=
u+ssh://10.0.0.1/system
       Supported by the QEMU driver
     </p>
=20
-    <h3><a name=3D"scenariotunnelpeer2peer2">Tunnelled migration, peer2pee=
r between two libvirtd servers</a></h3>
+    <h3><a id=3D"scenariotunnelpeer2peer2">Tunnelled migration, peer2peer =
between two libvirtd servers</a></h3>
=20
     <p>
       virDomainMigrateToURI, with the VIR_MIGRATE_PEER2PEER &amp; VIR_MIGR=
ATE_TUNNELLED
diff --git a/docs/nss.html.in b/docs/nss.html.in
index 2a5a46cd1..369c9ff61 100644
--- a/docs/nss.html.in
+++ b/docs/nss.html.in
@@ -25,7 +25,7 @@
     users. This is where NSS module comes handy.
     </p>
=20
-    <h2><a name=3D"Installation">Installation</a></h2>
+    <h2><a id=3D"Installation">Installation</a></h2>
=20
     <p>
     Installing the module is really easy:
@@ -35,7 +35,7 @@
 # yum install libvirt-nss
 </pre>
=20
-    <h2><a name=3D"Configuration">Configuration</a></h2>
+    <h2><a id=3D"Configuration">Configuration</a></h2>
=20
     <p>
     Enabling the module is really easy. Just add <b>libvirt</b> into
@@ -62,7 +62,7 @@ hosts:       files libvirt dns
     lookup given host name.
     </p>
=20
-    <h2><a name=3D"Sources">Sources of information</a></h2>
+    <h2><a id=3D"Sources">Sources of information</a></h2>
=20
     <p>
     As of <code>v3.0.0</code> release, libvirt offers two NSS modules
@@ -104,7 +104,7 @@ hosts:       files libvirt libvirt_guest dns
     resolved).
     </p>
=20
-    <h2><a name=3D"Internals">How does it work?</a></h2>
+    <h2><a id=3D"Internals">How does it work?</a></h2>
=20
     <p>
     Whenever an Unix process wants to do a host name translation
@@ -139,7 +139,7 @@ hosts:       files libvirt libvirt_guest dns
     should carefully chose the lookup order.
     </p>
=20
-    <h2><a name=3D"Limitations">Limitations</a></h2>
+    <h2><a id=3D"Limitations">Limitations</a></h2>
=20
     <ol>
       <li>The <code>libvirt</code> NSS module matches only hostnames provi=
ded by guest.
diff --git a/docs/page.xsl b/docs/page.xsl
index 1d662c670..57f85e618 100644
--- a/docs/page.xsl
+++ b/docs/page.xsl
@@ -27,30 +27,30 @@
       <xsl:for-each select=3D"/html:html/html:body/html:h2[count(html:a) =
=3D 1]">
         <xsl:variable name=3D"thish2" select=3D"."/>
         <li>
-          <a href=3D"#{html:a/@name}"><xsl:value-of select=3D"html:a/text(=
)"/></a>
+          <a href=3D"#{html:a/@id}"><xsl:value-of select=3D"html:a/text()"=
/></a>
           <xsl:if test=3D"count(./following-sibling::html:h3[preceding-sib=
ling::html:h2[1] =3D $thish2 and count(html:a) =3D 1]) > 0">
             <ul>
               <xsl:for-each select=3D"./following-sibling::html:h3[precedi=
ng-sibling::html:h2[1] =3D $thish2 and count(html:a) =3D 1]">
                 <xsl:variable name=3D"thish3" select=3D"."/>
                 <li>
-                  <a href=3D"#{html:a/@name}"><xsl:value-of select=3D"html=
:a/text()"/></a>
+                  <a href=3D"#{html:a/@id}"><xsl:value-of select=3D"html:a=
/text()"/></a>
                   <xsl:if test=3D"count(./following-sibling::html:h4[prece=
ding-sibling::html:h3[1] =3D $thish3 and count(html:a) =3D 1]) > 0">
                     <ul>
                       <xsl:for-each select=3D"./following-sibling::html:h4=
[preceding-sibling::html:h3[1] =3D $thish3 and count(html:a) =3D 1]">
                         <xsl:variable name=3D"thish4" select=3D"."/>
                         <li>
-                          <a href=3D"#{html:a/@name}"><xsl:value-of select=
=3D"html:a/text()"/></a>
+                          <a href=3D"#{html:a/@id}"><xsl:value-of select=
=3D"html:a/text()"/></a>
                           <xsl:if test=3D"count(./following-sibling::html:=
h5[preceding-sibling::html:h4[1] =3D $thish4 and count(html:a) =3D 1]) > 0">
                             <ul>
                               <xsl:for-each select=3D"./following-sibling:=
:html:h5[preceding-sibling::html:h4[1] =3D $thish4 and count(html:a) =3D 1]=
">
                                 <xsl:variable name=3D"thish5" select=3D"."=
/>
                                 <li>
-                                  <a href=3D"#{html:a/@name}"><xsl:value-o=
f select=3D"html:a/text()"/></a>
+                                  <a href=3D"#{html:a/@id}"><xsl:value-of =
select=3D"html:a/text()"/></a>
                                   <xsl:if test=3D"count(./following-siblin=
g::html:h6[preceding-sibling::html:h5[1] =3D $thish5 and count(html:a) =3D =
1]) > 0">
                                     <ul>
                                       <xsl:for-each select=3D"./following-=
sibling::html:h6[preceding-sibling::html:h5[1] =3D $thish5 and count(html:a=
) =3D 1]">
                                         <li>
-                                          <a href=3D"#{html:a/@name}"><xsl=
:value-of select=3D"html:a/text()"/></a>
+                                          <a href=3D"#{html:a/@id}"><xsl:v=
alue-of select=3D"html:a/text()"/></a>
                                         </li>
                                       </xsl:for-each>
                                     </ul>
@@ -155,8 +155,8 @@
   <xsl:template match=3D"html:h2 | html:h3 | html:h4 | html:h5 | html:h6" =
mode=3D"content">
     <xsl:element name=3D"{name()}">
       <xsl:apply-templates mode=3D"copy" />
-      <xsl:if test=3D"./html:a/@name">
-        <a class=3D"headerlink" href=3D"#{html:a/@name}" title=3D"Permalin=
k to this headline">&#xb6;</a>
+      <xsl:if test=3D"./html:a/@id">
+        <a class=3D"headerlink" href=3D"#{html:a/@id}" title=3D"Permalink =
to this headline">&#xb6;</a>
       </xsl:if>
     </xsl:element>
   </xsl:template>
diff --git a/docs/remote.html.in b/docs/remote.html.in
index 117ee3477..47e95400b 100644
--- a/docs/remote.html.in
+++ b/docs/remote.html.in
@@ -10,7 +10,7 @@ machines through authenticated and encrypted connections.
     <ul id=3D"toc"></ul>
=20
     <h2>
-      <a name=3D"Remote_basic_usage">Basic usage</a>
+      <a id=3D"Remote_basic_usage">Basic usage</a>
     </h2>
     <p>
 On the remote machine, <code>libvirtd</code> should be running in general.
@@ -50,7 +50,7 @@ relating to failures in the remote transport itself. </li>
 much slower than, say, direct hypervisor calls. </li>
     </ul>
     <h2>
-      <a name=3D"Remote_transports">Transports</a>
+      <a id=3D"Remote_transports">Transports</a>
     </h2>
     <p>
 Remote libvirt supports a range of transports:
@@ -111,7 +111,7 @@ netcat is required on the remote side.</dd>
 The default transport, if no other is specified, is <code>tls</code>.
 </p>
     <h2>
-      <a name=3D"Remote_URI_reference">Remote URIs</a>
+      <a id=3D"Remote_URI_reference">Remote URIs</a>
     </h2>
     <p>
 See also: <a href=3D"uri.html">documentation on ordinary ("local") URIs</a=
>.
@@ -158,7 +158,7 @@ Connect to a remote host using a ssh connection with th=
e libssh driver
 and use a different known_hosts file.</li>
     </ul>
     <h3>
-      <a name=3D"Remote_URI_parameters">Extra parameters</a>
+      <a id=3D"Remote_URI_parameters">Extra parameters</a>
     </h3>
     <p>
 Extra parameters can be added to remote URIs as part
@@ -364,10 +364,10 @@ Note that parameter values must be
       </tr>
     </table>
     <h2>
-      <a name=3D"Remote_certificates">Generating TLS certificates</a>
+      <a id=3D"Remote_certificates">Generating TLS certificates</a>
     </h2>
     <h3>
-      <a name=3D"Remote_PKI">Public Key Infrastructure set up</a>
+      <a id=3D"Remote_PKI">Public Key Infrastructure set up</a>
     </h3>
     <p>
 If you are unsure how to create TLS certificates, skip to the
@@ -472,7 +472,7 @@ next section.
       <li> For the root user, the global default locations will always be =
used.</li>
     </ul>
     <h3>
-      <a name=3D"Remote_TLS_background">Background to TLS certificates</a>
+      <a id=3D"Remote_TLS_background">Background to TLS certificates</a>
     </h3>
     <p>
 Libvirt supports TLS certificates for verifying the identity
@@ -507,7 +507,7 @@ address.  You may want to change this to make it less (=
or more)
 permissive, depending on your needs.
 </p>
     <h3>
-      <a name=3D"Remote_TLS_CA">Setting up a Certificate Authority (CA)</a>
+      <a id=3D"Remote_TLS_CA">Setting up a Certificate Authority (CA)</a>
     </h3>
     <p>
 You will need the <a href=3D"http://www.gnu.org/software/gnutls/manual/htm=
l_node/Invoking-certtool.html">GnuTLS
@@ -578,7 +578,7 @@ key carefully as you will need it when you come to issu=
e certificates
 for your clients and servers.
 </p>
     <h3>
-      <a name=3D"Remote_TLS_server_certificates">Issuing server certificat=
es</a>
+      <a id=3D"Remote_TLS_server_certificates">Issuing server certificates=
</a>
     </h3>
     <p>
 For each server (libvirtd) you need to issue a certificate
@@ -661,7 +661,7 @@ which can be installed on the server as
 </li>
     </ul>
     <h3>
-      <a name=3D"Remote_TLS_client_certificates">Issuing client certificat=
es</a>
+      <a id=3D"Remote_TLS_client_certificates">Issuing client certificates=
</a>
     </h3>
     <p>
 For each client (ie. any program linked with libvirt, such as
@@ -714,7 +714,7 @@ cp clientcert.pem /etc/pki/libvirt/clientcert.pem
 </li>
     </ol>
     <h3>
-      <a name=3D"Remote_TLS_troubleshooting">Troubleshooting TLS certifica=
te problems</a>
+      <a id=3D"Remote_TLS_troubleshooting">Troubleshooting TLS certificate=
 problems</a>
     </h3>
     <dl>
       <dt> failed to verify client's certificate </dt>
@@ -732,7 +732,7 @@ to analyze the setup on the client or server machines, =
preferably as root.
 It will try to point out the possible problems and provide solutions to
 fix the set up up to a point where you have secure remote access.</p>
     <h2>
-      <a name=3D"Remote_libvirtd_configuration">libvirtd configuration fil=
e</a>
+      <a id=3D"Remote_libvirtd_configuration">libvirtd configuration file<=
/a>
     </h2>
     <p>
 Libvirtd (the remote daemon) is configured from a file called
@@ -900,7 +900,7 @@ Blank lines and comments beginning with <code>#</code> =
are ignored.
       </tr>
     </table>
     <h2>
-      <a name=3D"Remote_IPv6">IPv6 support</a>
+      <a id=3D"Remote_IPv6">IPv6 support</a>
     </h2>
     <p>
 The libvirtd service and libvirt remote client driver both use the
@@ -913,7 +913,7 @@ connection will be made, otherwise IPv4 will be used. I=
n summary it
 should just 'do the right thing(tm)'.
 </p>
     <h2>
-      <a name=3D"Remote_limitations">Limitations</a>
+      <a id=3D"Remote_limitations">Limitations</a>
     </h2>
     <ul>
       <li> Fine-grained authentication: libvirt in general,
diff --git a/docs/secureusage.html.in b/docs/secureusage.html.in
index af47a0f53..6a9490bac 100644
--- a/docs/secureusage.html.in
+++ b/docs/secureusage.html.in
@@ -14,9 +14,9 @@
     </p>
=20
=20
-    <h2><a name=3D"diskimage">Disk image handling</a></h2>
+    <h2><a id=3D"diskimage">Disk image handling</a></h2>
=20
-    <h3><a name=3D"diskimageformat">Disk image format probing</a></h3>
+    <h3><a id=3D"diskimageformat">Disk image format probing</a></h3>
=20
     <p>
       Historically there have been multiple flaws in QEMU and most
@@ -40,7 +40,7 @@
       are accessible to / originate from an untrusted source.
     </p>
=20
-    <h3><a name=3D"diskimagebacking">Disk image backing files</a></h3>
+    <h3><a id=3D"diskimagebacking">Disk image backing files</a></h3>
=20
     <p>
       If a management application allows users to upload pre-created
@@ -59,7 +59,7 @@
       file set. If a backing file is seen, reject the image.
     </p>
=20
-    <h3><a name=3D"diskimagesize">Disk image size validation</a></h3>
+    <h3><a id=3D"diskimagesize">Disk image size validation</a></h3>
=20
     <p>
       If an application allows users to upload pre-created disk
@@ -78,7 +78,7 @@
       limit.
     </p>
=20
-    <h3><a name=3D"diskimageaccess">Disk image data access</a></h3>
+    <h3><a id=3D"diskimageaccess">Disk image data access</a></h3>
=20
     <p>
       If an untrusted disk image is ever mounted on the host OS by
@@ -104,7 +104,7 @@
       tools and APIs for accessing disks
     </p>
=20
-    <h2><a name=3D"migration">Guest migration network</a></h2>
+    <h2><a id=3D"migration">Guest migration network</a></h2>
=20
     <p>
       Most hypervisors with support for guest migration between hosts
@@ -145,7 +145,7 @@
         RPC protocol connections.</li>
     </ul>
=20
-    <h2><a name=3D"storage">Storage encryption</a></h2>
+    <h2><a id=3D"storage">Storage encryption</a></h2>
=20
     <p>
       Virtual disk images will typically contain confidential data
diff --git a/docs/securityprocess.html.in b/docs/securityprocess.html.in
index bdef1e9d8..d37276d15 100644
--- a/docs/securityprocess.html.in
+++ b/docs/securityprocess.html.in
@@ -15,7 +15,7 @@
       potential security issues.
     </p>
=20
-    <h2><a name=3D"reporting">Reporting security issues</a></h2>
+    <h2><a id=3D"reporting">Reporting security issues</a></h2>
=20
     <p>
       In the event that a bug in libvirt is found which is
@@ -37,7 +37,7 @@
       moderator and the reporter copied on any replies.
     </p>
=20
-    <h2><a name=3D"seclist">Security team</a></h2>
+    <h2><a id=3D"seclist">Security team</a></h2>
=20
     <p>
       The libvirt security team is made up of a subset of the libvirt
@@ -61,7 +61,7 @@
       described below.
     </p>
=20
-    <h2><a name=3D"embargo">Publication embargo policy</a></h2>
+    <h2><a id=3D"embargo">Publication embargo policy</a></h2>
=20
     <p>
       The libvirt security team operates a policy of
@@ -84,7 +84,7 @@
     </p>
=20
=20
-    <h2><a name=3D"cve">CVE allocation</a></h2>
+    <h2><a id=3D"cve">CVE allocation</a></h2>
=20
     <p>
       The libvirt security team will associate each security issue with
@@ -92,7 +92,7 @@
       the vendor security engineers on the security team.
     </p>
=20
-    <h2><a name=3D"branches">Branch fixing policy</a></h2>
+    <h2><a id=3D"branches">Branch fixing policy</a></h2>
=20
     <p>
       The libvirt community maintains one or more stable release branches
@@ -103,7 +103,7 @@
       other release branches where applicable.
     </p>
=20
-    <h2><a name=3D"notification">Notification of issues</a></h2>
+    <h2><a id=3D"notification">Notification of issues</a></h2>
=20
     <p>
       When an embargo expires, security issues will be announced on both
diff --git a/docs/storage.html.in b/docs/storage.html.in
index 89ebb7097..aad5751ef 100644
--- a/docs/storage.html.in
+++ b/docs/storage.html.in
@@ -85,7 +85,7 @@
     </p>
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"StorageBackendDir">Directory pool</a></h2>
+    <h2><a id=3D"StorageBackendDir">Directory pool</a></h2>
     <p>
       A pool with a type of <code>dir</code> provides the means to manage
       files within a directory. The files can be fully allocated raw files,
@@ -138,7 +138,7 @@
=20
     </p>
=20
-    <h2><a name=3D"StorageBackendFS">Filesystem pool</a></h2>
+    <h2><a id=3D"StorageBackendFS">Filesystem pool</a></h2>
     <p>
       This is a variant of the directory pool. Instead of creating a
       directory on an existing mounted filesystem though, it expects
@@ -212,7 +212,7 @@
     </p>
=20
=20
-    <h2><a name=3D"StorageBackendNetFS">Network filesystem pool</a></h2>
+    <h2><a id=3D"StorageBackendNetFS">Network filesystem pool</a></h2>
     <p>
       This is a variant of the filesystem pool. Instead of requiring
       a local block device as the source, it requires the name of a
@@ -266,7 +266,7 @@
     </p>
=20
=20
-    <h2><a name=3D"StorageBackendLogical">Logical volume pool</a></h2>
+    <h2><a id=3D"StorageBackendLogical">Logical volume pool</a></h2>
     <p>
       This provides a pool based on an LVM volume group. For a
       pre-defined LVM volume group, simply providing the group
@@ -303,7 +303,7 @@
     </p>
=20
=20
-    <h2><a name=3D"StorageBackendDisk">Disk pool</a></h2>
+    <h2><a id=3D"StorageBackendDisk">Disk pool</a></h2>
     <p>
       This provides a pool based on a physical disk. Volumes are created
       by adding partitions to the disk. Disk pools have constraints
@@ -394,7 +394,7 @@
     </ul>
=20
=20
-    <h2><a name=3D"StorageBackendISCSI">iSCSI pool</a></h2>
+    <h2><a id=3D"StorageBackendISCSI">iSCSI pool</a></h2>
     <p>
       This provides a pool based on an iSCSI target. Volumes must be
       pre-allocated on the iSCSI server, and cannot be created via
@@ -433,7 +433,7 @@
       The iSCSI volume pool does not use the volume format type element.
     </p>
=20
-    <h2><a name=3D"StorageBackendSCSI">SCSI pool</a></h2>
+    <h2><a id=3D"StorageBackendSCSI">SCSI pool</a></h2>
     <p>
       This provides a pool based on a SCSI HBA. Volumes are preexisting SC=
SI
       LUNs, and cannot be created via the libvirt APIs. Since /dev/XXX nam=
es
@@ -465,7 +465,7 @@
       The SCSI volume pool does not use the volume format type element.
     </p>
=20
-    <h2><a name=3D"StorageBackendMultipath">Multipath pool</a></h2>
+    <h2><a id=3D"StorageBackendMultipath">Multipath pool</a></h2>
     <p>
       This provides a pool that contains all the multipath devices on the
       host. Therefore, only one Multipath pool may be configured per host.
@@ -498,7 +498,7 @@
       The Multipath volume pool does not use the volume format type elemen=
t.
     </p>
=20
-    <h2><a name=3D"StorageBackendRBD">RBD pool</a></h2>
+    <h2><a id=3D"StorageBackendRBD">RBD pool</a></h2>
     <p>
       This storage driver provides a pool which contains all RBD
       images in a RADOS pool.  RBD (RADOS Block Device) is part
@@ -571,7 +571,7 @@
       The RBD pool does not use the volume format type element.
     </p>
=20
-    <h2><a name=3D"StorageBackendSheepdog">Sheepdog pool</a></h2>
+    <h2><a id=3D"StorageBackendSheepdog">Sheepdog pool</a></h2>
     <p>
       This provides a pool based on a Sheepdog Cluster.
       Sheepdog is a distributed storage system for QEMU/KVM.
@@ -630,7 +630,7 @@
       The Sheepdog pool does not use the volume format type element.
     </p>
=20
-    <h2><a name=3D"StorageBackendGluster">Gluster pool</a></h2>
+    <h2><a id=3D"StorageBackendGluster">Gluster pool</a></h2>
     <p>
       This provides a pool based on native Gluster access.  Gluster is
       a distributed file system that can be exposed to the user via
@@ -716,7 +716,7 @@
       pool type.
     </p>
=20
-    <h2><a name=3D"StorageBackendZFS">ZFS pool</a></h2>
+    <h2><a id=3D"StorageBackendZFS">ZFS pool</a></h2>
     <p>
       This provides a pool based on the ZFS filesystem. Initially it was d=
eveloped
       for FreeBSD, and <span class=3D"since">since 1.3.2</span> experiment=
al support
@@ -754,7 +754,7 @@
     <p>
       The ZFS volume pool does not use the volume format type element.
     </p>
-    <h2><a name=3D"StorageBackendVstorage">Vstorage pool</a></h2>
+    <h2><a id=3D"StorageBackendVstorage">Vstorage pool</a></h2>
     <p>
       This provides a pool based on Virtuozzo storage. Virtuozzo Storage is
       a highly available distributed software-defined storage with built-in
diff --git a/docs/uri.html.in b/docs/uri.html.in
index 7702ccc6e..defb9eec2 100644
--- a/docs/uri.html.in
+++ b/docs/uri.html.in
@@ -16,7 +16,7 @@ machine over the network.
 To this end, libvirt uses URIs as used on the Web and as defined in <a hre=
f=3D"http://www.ietf.org/rfc/rfc2396.txt">RFC 2396</a>. This page
 documents libvirt URIs.
 </p>
-    <h2><a name=3D"URI_libvirt">Specifying URIs to libvirt</a></h2>
+    <h2><a id=3D"URI_libvirt">Specifying URIs to libvirt</a></h2>
=20
     <p>
       The URI is passed as the <code>name</code> parameter to
@@ -33,7 +33,7 @@ documents libvirt URIs.
 virConnectPtr conn =3D virConnectOpenReadOnly (<b>"test:///default"</b>);
 </pre>
     <h2>
-      <a name=3D"URI_config">Configuring URI aliases</a>
+      <a id=3D"URI_config">Configuring URI aliases</a>
     </h2>
=20
     <p>
@@ -61,7 +61,7 @@ uri_aliases =3D [
   set, no alias lookup will be attempted.
 </p>
=20
-    <h2><a name=3D"URI_default">Default URI choice</a></h2>
+    <h2><a id=3D"URI_default">Default URI choice</a></h2>
=20
     <p>
 If the URI passed to <code>virConnectOpen*</code> is NULL, then libvirt wi=
ll use the following
@@ -75,7 +75,7 @@ logic to determine what URI to use.
     </ol>
=20
     <h2>
-      <a name=3D"URI_virsh">Specifying URIs to virsh, virt-manager and vir=
t-install</a>
+      <a id=3D"URI_virsh">Specifying URIs to virsh, virt-manager and virt-=
install</a>
     </h2>
     <p>
 In virsh use the <code>-c</code> or <code>--connect</code> option:
@@ -107,7 +107,7 @@ In virt-install use the <code>--connect=3D</code><i>URI=
</i> option:
 virt-install <b>--connect=3Dtest:///default</b> <i>[other options]</i>
 </pre>
     <h2>
-      <a name=3D"URI_xen">xen:/// URI</a>
+      <a id=3D"URI_xen">xen:/// URI</a>
     </h2>
     <p>
       <i>This section describes a feature which is new in libvirt &gt;
@@ -118,7 +118,7 @@ To access a Xen hypervisor running on the local machine
 use the URI <code>xen:///</code>.
 </p>
     <h2>
-      <a name=3D"URI_qemu">qemu:///... QEMU and KVM URIs</a>
+      <a id=3D"URI_qemu">qemu:///... QEMU and KVM URIs</a>
     </h2>
     <p>
 To use QEMU support in libvirt you must be running the
@@ -150,7 +150,7 @@ KVM guests in the <a href=3D"format.html#KVM1">guest XM=
L as described
 here</a>.
 </p>
     <h2>
-      <a name=3D"URI_remote">Remote URIs</a>
+      <a id=3D"URI_remote">Remote URIs</a>
     </h2>
     <p>
 Remote URIs are formed by taking ordinary local URIs and adding a
@@ -213,7 +213,7 @@ remote URI reference</a> and <a href=3D"remote.html">fu=
ll documentation
 for libvirt remote support</a>.
 </p>
     <h2>
-      <a name=3D"URI_test">test:///... Test URIs</a>
+      <a id=3D"URI_test">test:///... Test URIs</a>
     </h2>
     <p>
 The test driver is a dummy hypervisor for test purposes.
@@ -227,10 +227,10 @@ a set of host definitions held in the named file.
 </li>
     </ul>
     <h2>
-      <a name=3D"URI_legacy">Other &amp; legacy URI formats</a>
+      <a id=3D"URI_legacy">Other &amp; legacy URI formats</a>
     </h2>
     <h3>
-      <a name=3D"URI_NULL">NULL and empty string URIs</a>
+      <a id=3D"URI_NULL">NULL and empty string URIs</a>
     </h3>
     <p>
 Libvirt allows you to pass a <code>NULL</code> pointer to
@@ -254,7 +254,7 @@ application wishes to connect specifically to a Xen hyp=
ervisor, then
 for future proofing it should choose a full <a href=3D"#URI_xen"><code>xen=
:///</code> URI</a>.
 </p>
     <h3>
-      <a name=3D"URI_file">File paths (xend-unix-server)</a>
+      <a id=3D"URI_file">File paths (xend-unix-server)</a>
     </h3>
     <p>
 If XenD is running and configured in <code>/etc/xen/xend-config.sxp</code>:
@@ -271,7 +271,7 @@ using a file URI such as:
 virsh -c ///var/run/xend/xend-socket
 </pre>
     <h3>
-      <a name=3D"URI_http">Legacy: <code>http://...</code> (xend-http-serv=
er)</a>
+      <a id=3D"URI_http">Legacy: <code>http://...</code> (xend-http-server=
)</a>
     </h3>
     <p>
 If XenD is running and configured in <code>/etc/xen/xend-config.sxp</code>:
@@ -307,7 +307,7 @@ Notes:
  documentation as "unix server" or "http server".</li>
     </ol>
     <h3>
-      <a name=3D"URI_legacy_xen">Legacy: <code>"xen"</code></a>
+      <a id=3D"URI_legacy_xen">Legacy: <code>"xen"</code></a>
     </h3>
     <p>
 Another legacy URI is to specify name as the string
@@ -315,7 +315,7 @@ Another legacy URI is to specify name as the string
 hypervisor.  However you should prefer a full <a href=3D"#URI_xen"><code>x=
en:///</code> URI</a> in all future code.
 </p>
     <h3>
-      <a name=3D"URI_legacy_proxy">Legacy: Xen proxy</a>
+      <a id=3D"URI_legacy_proxy">Legacy: Xen proxy</a>
     </h3>
     <p>
 Libvirt continues to support connections to a separately running Xen
diff --git a/docs/virshcmdref.html.in b/docs/virshcmdref.html.in
index 5503ca0da..f7cc5ddae 100644
--- a/docs/virshcmdref.html.in
+++ b/docs/virshcmdref.html.in
@@ -6,7 +6,7 @@
=20
     <ul id=3D"toc"></ul>
=20
-    <h2><a name=3D"description">Description</a></h2>
+    <h2><a id=3D"description">Description</a></h2>
=20
     <p>
       The new <b>Virsh Command Reference</b>, for documenting the commands
@@ -24,7 +24,7 @@
=20
     <p>&nbsp;</p>
=20
-   <h2><a name=3D"viewing">Viewing Online</a></h2>
+   <h2><a id=3D"viewing">Viewing Online</a></h2>
=20
     <p>
       The latest version can be viewed directly online:
@@ -41,7 +41,7 @@
=20
     <p>&nbsp;</p>
=20
-    <h2><a name=3D"downloading">Downloading</a></h2>
+    <h2><a id=3D"downloading">Downloading</a></h2>
=20
     <p>
       The latest version of the Virsh Command Reference can be downloaded:
@@ -68,7 +68,7 @@
       </li>
     </ul>
=20
-    <h2><a name=3D"git">DocBook source GIT repository</a></h2>
+    <h2><a id=3D"git">DocBook source GIT repository</a></h2>
     <p>
       The DocBook source is maintained in a <a
       href=3D"http://git-scm.com/">git</a> repository available on
diff --git a/docs/windows.html.in b/docs/windows.html.in
index a0fe533a3..708bb1b18 100644
--- a/docs/windows.html.in
+++ b/docs/windows.html.in
@@ -12,7 +12,7 @@
       as well but we either haven't tested or received reports for them.
     </p>
=20
-    <h2><a name=3D"installer">Installation packages</a></h2>
+    <h2><a id=3D"installer">Installation packages</a></h2>
=20
     <p>
       Users who need pre-built Windows DLLs of libvirt are advised
@@ -29,7 +29,7 @@
       against libvirt.
     </p>
=20
-    <h2><a name=3D"conntypes">Connection types</a></h2>
+    <h2><a id=3D"conntypes">Connection types</a></h2>
=20
     <p>
       These connection types are known to work:
@@ -71,7 +71,7 @@
       be used in security sensitive environments.</b>
     </p>
=20
-    <h2><a name=3D"esx">Connecting to VMware ESX/vSphere</a></h2>
+    <h2><a id=3D"esx">Connecting to VMware ESX/vSphere</a></h2>
=20
     <p>
       Details on the capabilities, certificates, and connection string
@@ -81,7 +81,7 @@
=20
     <a href=3D"http://libvirt.org/drvesx.html">http://libvirt.org/drvesx.h=
tml</a>
=20
-    <h2><a name=3D"tlscerts">TLS Certificates</a></h2>
+    <h2><a id=3D"tlscerts">TLS Certificates</a></h2>
=20
     <p>
       TLS certificates need to have been created and placed in the correct
@@ -141,21 +141,21 @@
       <li>C:\Users\someuser\AppData\Roaming\libvirt\pki\libvirt\private\cl=
ientkey.pem</li>
     </ul>
=20
-    <h2><a name=3D"feedback">Feedback</a></h2>
+    <h2><a id=3D"feedback">Feedback</a></h2>
=20
     <p>
       Feedback and suggestions on changes to make and what else to include
       <a href=3D"contact.html">are desired</a>.
     </p>
=20
-    <h2><a name=3D"compiling">Compiling yourself</a></h2>
+    <h2><a id=3D"compiling">Compiling yourself</a></h2>
=20
     <p>
       Libvirt can be compiled on Windows using the free
       <a href=3D"http://www.mingw.org/">MinGW compiler</a>.
     </p>
=20
-    <h3><a name=3D"msys_setup">MSYS Build script</a></h3>
+    <h3><a id=3D"msys_setup">MSYS Build script</a></h3>
=20
     <p>
       The easiest way is to use the <b>msys_setup</b> script, developed by
@@ -165,7 +165,7 @@
=20
     <a href=3D"https://github.com/photron/msys_setup">https://github.com/p=
hotron/msys_setup</a>
=20
-    <h3><a name=3D"cross-compile">Cross compiling</a></h3>
+    <h3><a id=3D"cross-compile">Cross compiling</a></h3>
=20
     <p>
       You can also cross-compile to a Windows target from a Fedora machine
@@ -174,7 +174,7 @@
       (which includes a working libvirt specfile).
     </p>
=20
-    <h3><a name=3D"configure">By hand</a></h3>
+    <h3><a id=3D"configure">By hand</a></h3>
=20
     <p>
       Use these options when following the instructions on the
--=20
2.13.3

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list