Replace all anchors links by ref roles

* duplicate titles were removed
* minor fixes for links like "below", etc.
This commit is contained in:
parulin 2025-09-16 07:57:56 -04:00
parent 12f2c7a9bd
commit 98d89c5b13
No known key found for this signature in database
GPG key ID: 65099A5B0E31336C
38 changed files with 139 additions and 133 deletions

View file

@ -41,7 +41,7 @@ Beware that when you attach a whole block device, partitions can be identified b
If several different block-devices are attached to a single VM, the last letter of the device node name is advanced through the alphabet, so after ``xvdi`` the next device will be named ``xvdj``, the next ``xvdk``, and so on.
To specify this device node name, you need to use the command line tool and its `frontend-dev-option <#frontend-dev>`__.
To specify this device node name, you need to use the command line tool and its :ref:`frontend-dev-option <user/how-to-guides/how-to-use-block-storage-devices:frontend-dev>`.
Command Line Tool Guide
-----------------------
@ -131,7 +131,7 @@ To recover from this error state, in dom0 run
(where ``targetVM`` is to be replaced with the VM name you attached the device to and ``xvdi`` is to be replaced with the used `frontend device node <#frontend-dev>`__.)
(where ``targetVM`` is to be replaced with the VM name you attached the device to and ``xvdi`` is to be replaced with the used :ref:`frontend device node <user/how-to-guides/how-to-use-block-storage-devices:frontend-dev>`.)
However, if the block device originated in dom0, you will have to refer to the next section.