diff --git a/user/advanced-topics/disposable-customization.md b/user/advanced-topics/disposable-customization.md
index 16515a21..bb34cd98 100644
--- a/user/advanced-topics/disposable-customization.md
+++ b/user/advanced-topics/disposable-customization.md
@@ -324,7 +324,7 @@ Using disposables in this manner is ideal for untrusted qubes which require pers
     [user@dom0 ~]$ qvm-features disp-sys-usb appmenus-dispvm ''
     ```
 
-8. Users should now follow instructions on [How to hide USB controllers from dom0](/doc/usb-qubes/#how-to-hide-all-usb-controllers-from-dom0).
+8. Users should now follow instructions on [How to hide USB controllers from dom0](/doc/usb-qubes/#how-to-hide-usb-controllers-from-dom0).
 
 9. At this point, your mouse may not work.
    Edit the `qubes.InputMouse` policy file in dom0, which is located here:
diff --git a/user/advanced-topics/usb-qubes.md b/user/advanced-topics/usb-qubes.md
index 532a6256..0539f349 100644
--- a/user/advanced-topics/usb-qubes.md
+++ b/user/advanced-topics/usb-qubes.md
@@ -236,7 +236,7 @@ entry](/faq/#i-created-a-usb-vm-and-assigned-usb-controllers-to-it-now-the-usb-v
 
 USB controllers are automatically hidden from dom0 if you opt to create a USB
 qube during installation. This also occurs automatically if you choose to
-[create a USB qube](#creating-and-using-a-usb-qube) using the `qubesctl`
+[create a USB qube](#how-to-create-a-usb-qube) using the `qubesctl`
 method. However, if you create a USB qube manually and do not hide USB
 controllers from dom0, there will be a brief period of time during the boot
 process when dom0 will be exposed to your USB controllers (and any attached
diff --git a/user/downloading-installing-upgrading/install-security.md b/user/downloading-installing-upgrading/install-security.md
index 4ee21ff4..b8c58f78 100644
--- a/user/downloading-installing-upgrading/install-security.md
+++ b/user/downloading-installing-upgrading/install-security.md
@@ -41,7 +41,7 @@ From a Qubes-specific security perspective, each has certain pros and cons.
 
 Pros:
 
-* Works via USB, including with a [USB qube](/doc/usb-qubes/#creating-and-using-a-usb-qube).
+* Works via USB, including with a [USB qube](/doc/usb-qubes/).
 * Non-fixed capacity.
   (Easy to find one on which the ISO can fit.)
 
diff --git a/user/how-to-guides/how-to-use-usb-devices.md b/user/how-to-guides/how-to-use-usb-devices.md
index 50a08cbd..e515231f 100644
--- a/user/how-to-guides/how-to-use-usb-devices.md
+++ b/user/how-to-guides/how-to-use-usb-devices.md
@@ -115,7 +115,7 @@ If you receive this error: `ERROR: qubes-usb-proxy not installed in the VM`, you
 
 **Warning:** especially keyboards need to be accepted by default when using them to login! Please make sure you carefully read and understood the **[security considerations](/doc/device-handling-security/#usb-security)** before continuing!
 
-Mouse and keyboard setup are part of [setting up a USB-qube](/doc/usb-qubes/#enable-a-usb-keyboard-for-login).
+Mouse and keyboard setup are part of [setting up a USB qube](/doc/usb-qubes/).
 
 ### Finding The Right USB Controller
 
diff --git a/user/troubleshooting/usb-troubleshooting.md b/user/troubleshooting/usb-troubleshooting.md
index ca08295b..0a573127 100644
--- a/user/troubleshooting/usb-troubleshooting.md
+++ b/user/troubleshooting/usb-troubleshooting.md
@@ -89,7 +89,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](/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 [how to hide USB controllers from dom0](/doc/usb-qubes/#how-to-hide-usb-controllers-from-dom0) (i.e., 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.