Fix links

user/advanced-topics/disposablevm-customization.md

@@ -102,8 +102,8 @@ For example, with `qvm-prefs work netvm sys-firewall2`.
 
 To create one with a PCI device attached such as for `sys-net` or `sys-usb`, use the additional commands as follows.
 
-**Note** You can use `qvm-pci` to [determine](/doc/pci-devices/#qvm-pci-usage) the `<BDF>`.
-Also, you will often need to include the `-o no-strict-reset=True` [option](/doc/pci-devices/#no-strict-reset) with USB controllers.
+**Note** You can use `qvm-pci` to [determine](/doc/how-to-use-pci-devices/#qvm-pci-usage) the `<BDF>`.
+Also, you will often need to include the `-o no-strict-reset=True` [option](/doc/how-to-use-pci-devices/#no-strict-reset) with USB controllers.
 
 ~~~
 qvm-create -C DispVM -l red <sys-VMName>
@@ -209,7 +209,7 @@ Using DisposableVMs in this manner is ideal for untrusted qubes which require pe
     [user@dom0 ~]$ qvm-pci
     ```
 
-6. Attach the network PCI device(s) to `disp-sys-net` (finding and assigning PCI devices can be found [here](/doc/pci-devices/):
+6. Attach the network PCI device(s) to `disp-sys-net` (finding and assigning PCI devices can be found [here](/doc/how-to-use-pci-devices/):
 
     ```shell_session
     [user@dom0 ~]$ qvm-pci attach --persistent disp-sys-net <backend>:<bdf>
@@ -306,7 +306,7 @@ Using DisposableVMs in this manner is ideal for untrusted qubes which require pe
     ```
 
 5. Attach the USB controller to the `disp-sys-usb`:
-   >_**Note:**_ Most of the commonly used USB controllers (all Intel integrated controllers) require the `-o no-strict-reset=True` option to be set. Instructions detailing how this option is set can be found [here](/doc/pci-devices/#no-strict-reset).
+   >_**Note:**_ Most of the commonly used USB controllers (all Intel integrated controllers) require the `-o no-strict-reset=True` option to be set. Instructions detailing how this option is set can be found [here](/doc/how-to-use-pci-devices/#no-strict-reset).
 
     ```shell_session
     [user@dom0 ~]$ qvm-pci attach --persistent disp-sys-usb <backined>:<bdf>

user/advanced-topics/usb-qubes.md

@@ -25,7 +25,7 @@ If you find yourself in this situation, see this [issue](https://github.com/Qube
 
 A USB qube acts as a secure handler for potentially malicious USB devices, preventing them from coming into contact with dom0 (which could otherwise be fatal to the security of the whole system). It thereby mitigates some of the [security implications](/doc/device-handling-security/#usb-security) of using USB devices.
 With a USB qube, every time you connect an untrusted USB drive to a USB port managed by that USB controller, you will have to attach it to the qube in which you wish to use it (if different from the USB qube itself), either by using Qubes VM Manager or the command line (see instructions above).
-The USB controller may be assigned on the **Devices** tab of a qube's settings page in Qubes VM Manager or by using the [qvm-pci](/doc/pci-devices/) command.
+The USB controller may be assigned on the **Devices** tab of a qube's settings page in Qubes VM Manager or by using the [qvm-pci](/doc/how-to-use-pci-devices/) command.
 For guidance on finding the correct USB controller, see the [according passage on PCI-devices](/doc/usb-devices/#finding-the-right-usb-controller).
 You can create a USB qube using the management stack by performing the following steps as root in dom0:
 
@@ -35,7 +35,7 @@ sudo qubesctl state.sls qvm.sys-usb
 
 Alternatively, you can create a USB qube manually as follows:
 
-1. Read the [PCI Devices](/doc/pci-devices/) page to learn how to list and identify your USB controllers.
+1. Read the [PCI Devices](/doc/how-to-use-pci-devices/) page to learn how to list and identify your USB controllers.
    Carefully check whether you have a USB controller that would be appropriate to assign to a USB qube.
    Note that it should be free of input devices, programmable devices, and any other devices that must be directly available to dom0.
    If you find a free controller, note its name and proceed to step 2.

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

@@ -26,7 +26,7 @@ To permanently install new software in a TemplateVM:
 5. Restart all [TemplateBasedVMs](/doc/glossary/#templatebasedvm) based on the TemplateVM so the changes can take effect.
 6. (Optional) In the relevant [TemplateBasedVMs](/doc/glossary/#templatebasedvm)' **Qube Settings**, go to the **Applications** tab, select the new application(s) from the list, and press OK.
     These new shortcuts will appear in the Applications Menu.
-    (If you encounter problems, see [here](/doc/managing-appvm-shortcuts/) for troubleshooting.)
+    (If you encounter problems, see [here](/doc/app-menu-shortcut-troubleshooting/) for troubleshooting.)
 
 ![[The Applications tab in Qube Settings](/attachment/wiki/ManagingAppVmShortcuts/r4.1-dom0-appmenu-select.png)](/attachment/wiki/ManagingAppVmShortcuts/r4.1-dom0-appmenu-select.png)
 

user/how-to-guides/how-to-use-devices.md

@@ -14,7 +14,7 @@ title: How to Use Devices
 
 
 This is an overview of device handling in Qubes OS.
-For specific devices ([block](/doc/block-devices/), [USB](/doc/usb-devices/) and [PCI](/doc/pci-devices/) devices), please visit their respective pages.
+For specific devices ([block](/doc/block-devices/), [USB](/doc/usb-devices/) and [PCI](/doc/how-to-use-pci-devices/) devices), please visit their respective pages.
 
 **Important security warning:** Device handling comes with many security implications.
 Please make sure you carefully read and understand the **[security considerations](/doc/device-handling-security/)**.

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

@@ -150,7 +150,7 @@ This should output something like:
 ../../../devices/pci-0/pci0000:00/0000:00:1a.0/usb3
 ```
 
-Now you see the path and the text between `/pci0000:00/0000:` and `/usb3` i.e. `00:1a.0` is the BDF address. Strip the address and pass it to the [`qvm-pci` tool](/doc/pci-devices/) to attach the controller to the targetVM.
+Now you see the path and the text between `/pci0000:00/0000:` and `/usb3` i.e. `00:1a.0` is the BDF address. Strip the address and pass it to the [`qvm-pci` tool](/doc/how-to-use-pci-devices/) to attach the controller to the targetVM.
 
 For example, On R 4.0 the command would look something like
 

user/troubleshooting/app-menu-shortcut-troubleshooting.md

@@ -62,7 +62,7 @@ If you only want to create a shortcut for a single AppVM, you can create a custo
 1. Open a terminal window to Dom0.
 2. Create a custom `.desktop` file in `~/.local/share/applications`.
    Look in the same directory for existing examples, or see the full [file specification](https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html).
-   You may use `qvm-run` inside the `.desktop` file; see [Behind the scenes](/doc/managing-appvm-shortcuts/#behind-the-scenes) for more details.
+   You may use `qvm-run` inside the `.desktop` file; see [Behind the scenes](/doc/app-menu-shortcut-troubleshooting/#behind-the-scenes) for more details.
 3. Edit the `~/.config/menus/applications-merged/<vmname>-vm.menu` file for the AppVM.
 4. Add a custom menu entry referring to your newly created `.desktop` file.
 

user/troubleshooting/pci-troubleshooting.md

@@ -30,7 +30,7 @@ There is a way to enable permissive mode for it.
 See also: [this thread](https://groups.google.com/forum/#!topic/qubes-users/Fs94QAc3vQI) and the Xen wiki's [PCI passthrough](https://wiki.xen.org/wiki/Xen_PCI_Passthrough) page.
 Other times, you may instead need to disable the FLR requirement on a device.
 
-Both can be achieved during attachment with `qvm-pci` as described [PCI Devices documentation](/doc/pci-devices/#additional-attach-options).
+Both can be achieved during attachment with `qvm-pci` as described [PCI Devices documentation](/doc/how-to-use-pci-devices/#additional-attach-options).
 
 ## "Unable to reset PCI device" errors