Convert absolute to relative links

Absolute links break automatic onion redirection:
https://groups.google.com/g/qubes-users/c/NJdzP27wvmM/

user/common-tasks/backup-emergency-restore-v4.md

@@ -181,8 +181,8 @@ Emergency Recovery Instructions
         https://github.com/QubesOS/qubes-doc.git
 
 [scrypt]: https://www.tarsnap.com/scrypt.html
-[verify signatures]: https://www.qubes-os.org/security/verifying-signatures
-[get and verify the Release 4 Signing Key]: https://www.qubes-os.org/security/verifying-signatures/#2-get-the-release-signing-key
-[Emergency Backup Recovery without Qubes (v2)]: https://www.qubes-os.org/doc/backup-emergency-restore-v2/
-[Emergency Backup Recovery without Qubes (v3)]: https://www.qubes-os.org/doc/backup-emergency-restore-v3/
+[verify signatures]: /security/verifying-signatures
+[get and verify the Release 4 Signing Key]: /security/verifying-signatures/#2-get-the-release-signing-key
+[Emergency Backup Recovery without Qubes (v2)]: /doc/backup-emergency-restore-v2/
+[Emergency Backup Recovery without Qubes (v3)]: /doc/backup-emergency-restore-v3/
 

user/common-tasks/disposablevm.md

@@ -42,7 +42,7 @@ When it is essential to avoid leaving any trace, consider using [Tails](https://
 
 ## DisposableVMs and Networking ##
 
-Similarly to how AppVMs are based on their underlying [TemplateVM](https://www.qubes-os.org/doc/glossary/#templatevm), DisposableVMs are based on their underlying [DisposableVM Template](https://www.qubes-os.org/doc/glossary/#disposablevm-template).
+Similarly to how AppVMs are based on their underlying [TemplateVM](/doc/glossary/#templatevm), DisposableVMs are based on their underlying [DisposableVM Template](/doc/glossary/#disposablevm-template).
 R4.0 introduces the concept of multiple DisposableVM Templates, whereas R3.2 was limited to only one.
 
 On a fresh installation of Qubes, the default DisposableVM Template is called `fedora-XX-dvm` (where `XX` is the Fedora version of the default TemplateVM).

user/security-in-qubes/device-handling-security.md

@@ -81,7 +81,7 @@ Support for [two factor authentication][qubes u2f proxy] was recently added, tho
 [rubber duck]: https://shop.hak5.org/products/usb-rubber-ducky-deluxe
 [USB qube]: /doc/usb-qubes/
 [YubiKey]: /doc/YubiKey/
-[qubes u2f proxy]: https://www.qubes-os.org/news/2018/09/11/qubes-u2f-proxy/
+[qubes u2f proxy]: /news/2018/09/11/qubes-u2f-proxy/
 [4661]: https://github.com/QubesOS/qubes-issues/issues/4661
 [side channel attack]: https://en.wikipedia.org/wiki/Side-channel_attack
 [Xen PCI Passthrough: PV guests and PCI quirks]: https://wiki.xenproject.org/wiki/Xen_PCI_Passthrough#PV_guests_and_PCI_quirks

user/security-in-qubes/firewall.md

@@ -33,7 +33,7 @@ In order to edit rules for a given qube, select it in the Qubes Manager and pres
 ![r4.1-manager-firewall.png](/attachment/wiki/QubesFirewall/r4.1-manager-firewall.png)
 
 *R4.0 note:* ICMP and DNS are no longer accessible in the GUI, but can be changed via `qvm-firewall` described below.
-Connections to Updates Proxy are no longer made over network so can not be allowed or blocked with firewall rules (see [R4.0 Updates proxy](https://www.qubes-os.org/doc/software-update-vm/) for more detail.
+Connections to Updates Proxy are no longer made over network so can not be allowed or blocked with firewall rules (see [R4.0 Updates proxy](/doc/software-update-vm/) for more detail.
 
 Note that if you specify a rule by DNS name it will be resolved to IP(s) *at the moment of applying the rules*, and not on the fly for each new connection.
 This means it will not work for servers using load balancing.

user/troubleshooting/usb-troubleshooting.md

@@ -75,7 +75,7 @@ On boot, the keyboard may be inactive, preventing you from entering your LUKS de
 When you enable a USB qube, it hides all the USB controllers from dom0, even before it gets started. 
 So, if your only keyboard is on USB, you should undo this hiding. 
 
-To solve the problem, disable the USB qube by not having it autostart, or unassigning your USB controller(s) from it. If you had created the USB qube by checking the box in the installer, then your USB controller(s) are probably hidden from dom0. To unhide them, reverse the procedure described in the [USB Qubes documentation](https://www.qubes-os.org/doc/usb-qubes/#how-to-hide-all-usb-controllers-from-dom0) (under "How to hide all USB controllers from dom0"). That is, remove `rd.qubes.hide_all_usb`, instead of adding it. 
+To solve the problem, disable the USB qube by not having it autostart, or unassigning your USB controller(s) from it. If you had created the USB qube by checking the box in the installer, then your USB controller(s) are probably hidden from dom0. To unhide them, reverse the procedure described in the [USB Qubes documentation](/doc/usb-qubes/#how-to-hide-all-usb-controllers-from-dom0) (under "How to hide all USB controllers from dom0"). That is, remove `rd.qubes.hide_all_usb`, instead of adding it. 
 
 Note that this procedure will attach your USB controllers to dom0, so do this only with USB devices you trust.
 

user/troubleshooting/vm-troubleshooting.md

@@ -10,7 +10,7 @@ redirect_from:
 
 ## VM Kernel troubleshooting ##
 
-This troubleshoot applies to the non-default kernel choice described in the [Managing VM docs](https://www.qubes-os.org/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm). 
+This troubleshoot applies to the non-default kernel choice described in the [Managing VM docs](/doc/managing-vm-kernel/#using-kernel-installed-in-the-vm). 
 
 In case of problems, you can access the VM console using `qvm-console-dispvm VMNAME` in dom0, then access the GRUB menu.
 You need to call it just after starting the VM (until `GRUB_TIMEOUT` expires); for example, in a separate dom0 terminal window.