Merge branch 'md-refactoring-links' of https://github.com/tokideveloper/qubes-doc into tokideveloper-md-refactoring-links

user/troubleshooting/hardware-troubleshooting.md

@@ -16,7 +16,7 @@ By default, the kernel that is installed in dom0 comes from the `kernel` package
 For most cases this works fine since the Linux kernel developers backport fixes to this kernel, but for some newer hardware, you may run into issues.
 For example, the audio might not work if the sound card is too new for the LTS kernel.
 To fix this, you can try the `kernel-latest` package -- though be aware that it's less tested!
-(See [here][dom0-kernel-upgrade] for more information about upgrading kernels in dom0).
+(See [here](/doc/software-update-dom0/#kernel-upgrade) for more information about upgrading kernels in dom0).
 In dom0:
 
 ~~~
@@ -51,10 +51,5 @@ Do not edit it by hand, unless you know what you are doing.
 Restarting `xorg` is required.
 The most straightforward way is to reboot the system.
 
-More information in [this discussion][layout_discussion] and [this GitHub issue][layout_issue].
+More information in [this discussion](https://groups.google.com/d/topic/qubes-devel/d8ZQ_62asKI/discussion) and [this GitHub issue](https://github.com/QubesOS/qubes-issues/issues/1396).
 
-
-[dom0-kernel-upgrade]: /doc/software-update-dom0/#kernel-upgrade
-[hardware-reqs]: /doc/installation-guide/#hardware-requirements
-[layout_discussion]: https://groups.google.com/d/topic/qubes-devel/d8ZQ_62asKI/discussion
-[layout_issue]: https://github.com/QubesOS/qubes-issues/issues/1396

user/troubleshooting/installation-troubleshooting.md

@@ -91,11 +91,10 @@ During Qubes installation, you may come across the error message which reads "Un
 Missing features: IOMMU/VT-d/AMD-Vi, Interrupt Remapping. Without these features, Qubes OS will not function normally". 
 
 This error message indicates that IOMMU-virtualization hasn’t been activated in the BIOS. 
-Return to the [hardware requirements][hardware-reqs] section to learn how to activate it. 
+Return to the [hardware requirements](/doc/installation-guide/#hardware-requirements) section to learn how to activate it. 
 If the setting is not configured correctly, it means that your hardware won’t be able to leverage some Qubes security features, such as a strict isolation of the networking and USB hardware.
 
 In Qubes 4.0, the default installation won't function properly without IOMMU, as default sys-net and sys-usb qubes require IOMMU. It is possible to configure them to reduce isolation and not use IOMMU by changing virtualization mode of these two VMs to "PV".
 
 In Qubes 4.1, IOMMU is strictly required, even when the virtualization mode of a VM is changed to "PV"; it is not possible to use Qubes on a system without IOMMU.
 
-[hardware-reqs]: /doc/installation-guide/#hardware-requirements

user/troubleshooting/update-troubleshooting.md

@@ -15,11 +15,11 @@ Usually, this is due to network problems (especially if downloading updates over
 Often, the problem can be resolved by trying again on a different connection (a different Tor circuit, if using Tor) or waiting and trying again later.
 Here are some examples of non-Qubes reports about this problem:
 
-- <https://ask.fedoraproject.org/en/question/88086/error-failed-to-synchronize-cache-for-repo-fedora/>
-- <https://unix.stackexchange.com/questions/390805/repos-not-working-on-fedora-error-failed-to-synchronize-cache-for-repo-update>
-- <https://www.reddit.com/r/Fedora/comments/74nldq/fedora_26_dnf_error_failed_to_synchronize_cache/>
-- <https://bugzilla.redhat.com/show_bug.cgi?id=1494178>
-- <https://stackoverflow.com/questions/45318256/error-failed-to-synchronize-cache-for-repo-updates>
+- [https://ask.fedoraproject.org/en/question/88086/error-failed-to-synchronize-cache-for-repo-fedora/](https://ask.fedoraproject.org/en/question/88086/error-failed-to-synchronize-cache-for-repo-fedora/)
+- [https://unix.stackexchange.com/questions/390805/repos-not-working-on-fedora-error-failed-to-synchronize-cache-for-repo-update](https://unix.stackexchange.com/questions/390805/repos-not-working-on-fedora-error-failed-to-synchronize-cache-for-repo-update)
+- [https://www.reddit.com/r/Fedora/comments/74nldq/fedora\_26\_dnf\_error\_failed\_to\_synchronize\_cache/](https://www.reddit.com/r/Fedora/comments/74nldq/fedora_26_dnf_error_failed_to_synchronize_cache/)
+- [https://bugzilla.redhat.com/show\_bug.cgi?id=1494178](https://bugzilla.redhat.com/show_bug.cgi?id=1494178)
+- [https://stackoverflow.com/questions/45318256/error-failed-to-synchronize-cache-for-repo-updates](https://stackoverflow.com/questions/45318256/error-failed-to-synchronize-cache-for-repo-updates)
 
 More examples can be found by searching for "Failed to synchronize cache for repo" (with quotation marks) on your preferred search engine.
 

user/troubleshooting/usb-troubleshooting.md

@@ -62,9 +62,9 @@ Errors suggesting this issue:
 
 - during `qvm-start sys-usb`:
 
-    `
+    ```
     internal error: Unable to reset PCI device [...]  no FLR, PM reset or bus reset available.
-    `
+    ```
 
 Another solution would be to set the pci_strictreset option in dom0: