Replace all anchors links by ref roles

* duplicate titles were removed
* minor fixes for links like "below", etc.

user/how-to-guides/how-to-back-up-restore-and-migrate.rst

@@ -60,7 +60,7 @@ Creating a backup
 
 5. When you are ready, click **Next**. Qubes will proceed to create your backup. Once the progress bar has completed, you may click **Finish**.
 
-6. Test restore your backup. Follow the `restore procedure <#restoring-from-a-backup>`__, selecting **Verify backup integrity, do not restore the data**. This step is optional but strongly recommended. A backup is useless if you can’t restore your data from it, and you can’t be sure that your backup is good until you try to restore.
+6. Test restore your backup. Follow the :ref:`restore procedure <user/how-to-guides/how-to-back-up-restore-and-migrate:restoring from a backup>`, selecting **Verify backup integrity, do not restore the data**. This step is optional but strongly recommended. A backup is useless if you can’t restore your data from it, and you can’t be sure that your backup is good until you try to restore.
 
 
 

user/how-to-guides/how-to-copy-from-dom0.rst

@@ -41,7 +41,7 @@ Use the **Qubes Clipboard** widget:
 
 
 
-Alternatively, you can put your text in a file, then `copy it as a file <#copying-files-from-dom0>`__. Or, you can write the data you wish to copy into ``/var/run/qubes/qubes-clipboard.bin``, then ``echo -n dom0 > /var/run/qubes/qubes-clipboard.bin.source``. Then use Ctrl+Shift+V to paste the data to the target qube.
+Alternatively, you can put your text in a file, then :ref:`copy it as a file <user/how-to-guides/how-to-copy-from-dom0:copying files from dom0>`. Or, you can write the data you wish to copy into ``/var/run/qubes/qubes-clipboard.bin``, then ``echo -n dom0 > /var/run/qubes/qubes-clipboard.bin.source``. Then use Ctrl+Shift+V to paste the data to the target qube.
 
 Copying logs from dom0
 ^^^^^^^^^^^^^^^^^^^^^^
@@ -65,7 +65,7 @@ Copying *to* dom0
 -----------------
 
 
-Copying anything into dom0 is not advised, since doing so can compromise the security of your Qubes system. For this reason, there is no simple means of copying anything into dom0, unlike `copying from dom0 <#copying-from-dom0>`__.
+Copying anything into dom0 is not advised, since doing so can compromise the security of your Qubes system. For this reason, there is no simple means of copying anything into dom0, unlike :ref:`user/how-to-guides/how-to-copy-from-dom0:copying *from* dom0`.
 
 There should normally be few reasons for the user to want to copy anything from domUs to dom0, as dom0 only acts as a “thin trusted terminal”, and no user applications run there. Sometimes, new users feel the urge to copy a desktop wallpaper image into dom0, but that is not necessary. A safer approach is simply to display the image in :doc:`full-screen mode </user/how-to-guides/how-to-enter-fullscreen-mode>` in an app qube, then take a screenshot from dom0, which results in exactly the image needed for a wallpaper, created securely and natively in dom0.
 

user/how-to-guides/how-to-install-software.rst

@@ -56,7 +56,7 @@ If you are using another installation method fetching remote resources, you migh
 Using direct networking
 ^^^^^^^^^^^^^^^^^^^^^^^
 
-.. Warning:: This method gives your template direct network access, which is `risky <#why-dont-templates-have-normal-network-access>`__. This method is **not** recommended for trusted templates. Moreover, depending on how you install this software, it may not get updated automatically when you :doc:`update Qubes normally </user/how-to-guides/how-to-update>`, which means you may have to update it manually yourself.
+.. Warning:: This method gives your template direct network access, which is :ref:`risky <user/how-to-guides/how-to-install-software:why don't templates have normal network access?>`. This method is **not** recommended for trusted templates. Moreover, depending on how you install this software, it may not get updated automatically when you :doc:`update Qubes normally </user/how-to-guides/how-to-update>`, which means you may have to update it manually yourself.
 
 This method assumes that you are trying to follow instructions to install some piece of software in a normal operating system, except *that* operating system is running as a template in Qubes OS.
 
@@ -112,7 +112,7 @@ Please see :doc:`/user/how-to-guides/how-to-update`.
 Why don't templates have normal network access?
 -----------------------------------------------
 
-In order to protect you from performing risky activities in templates, they do not have normal network access by default. Instead, templates use an :ref:`updates-proxy` which allows you to install and update software using the distribution’s package manager over the proxy connection. **The updates proxy is already set up to work automatically out-of-the-box and requires no special action from you.** Most users should simply follow the normal instructions for :ref:`installing-software-from-default-repositories` and :doc:`updating </user/how-to-guides/how-to-update>` software. If your software is not available in the default repositories, see `installing software from other sources <#installing-software-from-other-sources>`__.
+In order to protect you from performing risky activities in templates, they do not have normal network access by default. Instead, templates use an :ref:`updates-proxy` which allows you to install and update software using the distribution’s package manager over the proxy connection. **The updates proxy is already set up to work automatically out-of-the-box and requires no special action from you.** Most users should simply follow the normal instructions for :ref:`installing-software-from-default-repositories` and :doc:`updating </user/how-to-guides/how-to-update>` software. If your software is not available in the default repositories, see :ref:`user/how-to-guides/how-to-install-software:installing software from other sources`.
 
 Advanced
 --------

user/how-to-guides/how-to-update.rst

@@ -45,7 +45,7 @@ Installing updates
 ------------------
 
 
-The standard way to install updates is with the **Qubes Update** tool. (However, you can also perform the same action via the `command-line interface <#command-line-interface>`__.)
+The standard way to install updates is with the **Qubes Update** tool. (However, you can also perform the same action via the :ref:`user/how-to-guides/how-to-update:command-line interface`.)
 
 |Qubes Update|
 

user/how-to-guides/how-to-use-block-storage-devices.rst

@@ -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.
 

user/how-to-guides/how-to-use-usb-devices.rst

@@ -68,7 +68,7 @@ Attaching selected USB device:
       sys-usb:2-1     03f0:0641 PixArt_Optical_Mouse
 
 
-Now, you can use your USB device (camera in this case) in the ``work`` qube. If you see the error ``ERROR: qubes-usb-proxy not installed in the qube`` instead, please refer to the `Installation Section <#installation-of-qubes-usb-proxy>`__.
+Now, you can use your USB device (camera in this case) in the ``work`` qube. If you see the error ``ERROR: qubes-usb-proxy not installed in the qube`` instead, please refer to the :ref:`Installation Section <installation-of-qubes-usb-proxy>`.
 
 When you finish, detach the device.
 
@@ -92,6 +92,8 @@ Creating and using a USB qube
 
 If you’ve selected to install a usb-qube during system installation, everything is already set up for you in ``sys-usb``. If you’ve later decided to create a usb-qube, please follow :doc:`this guide </user/advanced-topics/usb-qubes>`.
 
+.. _installation-of-qubes-usb-proxy:
+
 Installation of ``qubes-usb-proxy``
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^