[PATCH 26/67] docs: formatdomain: Remove 'elementsNICS' anchor

The one local link addition prompted rewrapping of the whole paragraph. Signed-off-by: Peter Krempa <pkrempa(a)redhat.com&gt; --- docs/formatdomain.rst | 11 +++++------ docs/formatnetwork.rst | 4 ++-- docs/formatnetworkport.rst | 2 +- 3 files changed, 8 insertions(+), 9 deletions(-) diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst index 65197d6e3d..3618b1212a 100644 --- a/docs/formatdomain.rst +++ b/docs/formatdomain.rst @@ -239,11 +239,11 @@ harddisk, cdrom, network) determining where to obtain/find the boot image. (the sorted list is vda, vdb, hda, hdc). Similar domain with hdc, vda, vdb, and hda disks will boot from hda (sorted disks are: hda, hdc, vda, vdb). It can be tricky to configure in the desired way, which is why per-device boot - elements (see `Hard drives, floppy disks, CDROMs`_, `network - interfaces <#elementsNICS>`__, and `Host device assignment`_ - sections below) were introduced and they are the preferred way providing full - control over booting order. The ``boot`` element and per-device boot elements - are mutually exclusive. :since:`Since 0.1.3, per-device boot since 0.8.8` + elements (see `Hard drives, floppy disks, CDROMs`_, `Network interfaces`_, + and `Host device assignment`_ sections below) were introduced and they are + the preferred way providing full control over booting order. + The ``boot`` element and per-device boot elements are mutually exclusive. + :since:`Since 0.1.3, per-device boot since 0.8.8` ``smbios`` How to populate SMBIOS information visible in the guest. The ``mode`` attribute must be specified, and is either "emulate" (let the hypervisor @@ -4441,7 +4441,6 @@ Each mode supports an optional sub-element ``<address>`` (See `Device Addresses` which fine-tunes the correlation between the smartcard and a ccid bus controller. For now, qemu only supports at most one smartcard, with an address of bus=0 slot=0. -:anchor:`<a id="elementsNICS"/>` Network interfaces ~~~~~~~~~~~~~~~~~~ diff --git a/docs/formatnetwork.rst b/docs/formatnetwork.rst index d6550f6df9..d956178e56 100644 --- a/docs/formatnetwork.rst +++ b/docs/formatnetwork.rst @@ -61,7 +61,7 @@ The first elements provide basic metadata about the virtual network. The optional parameter ``trustGuestRxFilters`` can be used to set that attribute of the same name for each domain interface connected to this network ( :since:`since 1.2.10` ). See the `Network - interfaces <formatdomain.html#elementsNICS>`__ section of the domain XML + interfaces <formatdomain.html#network-interfaces>`__ section of the domain XML documentation for more details. Note that an explicit setting of this attribute in a portgroup or the individual domain interface will override the setting in the network. @@ -616,7 +616,7 @@ starting. portgroups also support the optional parameter ``trustGuestRxFilters`` which can be used to set that attribute of the same name for each domain interface using this portgroup ( :since:`since 1.2.10` ). See the `Network -interfaces <formatdomain.html#elementsNICS>`__ section of the domain XML +interfaces <formatdomain.html#network-interfaces>`__ section of the domain XML documentation for more details. Note that an explicit setting of this attribute in the portgroup overrides the network-wide setting, and an explicit setting in the individual domain interface will override the setting in the portgroup. diff --git a/docs/formatnetworkport.rst b/docs/formatnetworkport.rst index 6f1a24a52c..394c65c2b7 100644 --- a/docs/formatnetworkport.rst +++ b/docs/formatnetworkport.rst @@ -98,7 +98,7 @@ The following elements are common to one or more of the plug types listed later ``virtualport`` The ``virtualport`` element describes metadata that needs to be provided to the underlying network subsystem. It is described in the domain XML - `interface documentation <formatdomain.html#elementsNICS>`__. + `interface documentation <formatdomain.html#network-interfaces>`__. Plugs ~~~~~ -- 2.35.3