Refactor links in order to obey the new convention rule

CONTRIBUTING.md

@@ -3,8 +3,7 @@ Contributing to `qubes-doc`
 
 Thank you for your interest in contributing to `qubes-doc`, the Qubes OS
 Project's dedicated documentation repository! Please take a moment to read our
-[Documentation Guidelines] before you begin writing. These guidelines are
+[Documentation Guidelines](https://www.qubes-os.org/doc/doc-guidelines/) before you begin writing. These guidelines are
 important to maintaining high quality documentation, and following them will
 increase the likelihood that your contribution will be accepted.
 
-[Documentation Guidelines]: https://www.qubes-os.org/doc/doc-guidelines/

README.md

@@ -3,15 +3,11 @@ Qubes OS Documentation
 
 Canonical URL: https://www.qubes-os.org/doc/
 
-All [Qubes OS Project] documentation pages are stored as plain text
+All [Qubes OS Project](https://github.com/QubesOS) documentation pages are stored as plain text
 files in this dedicated repository. By cloning and regularly pulling from
 this repo, users can maintain their own up-to-date offline copy of all
 Qubes documentation rather than relying solely on the Web.
 
 For more information about the documentation, including how to contribute,
-please see the [Documentation Guidelines].
+please see the [Documentation Guidelines](https://www.qubes-os.org/doc/doc-guidelines/).
-
-
-[Qubes OS Project]: https://github.com/QubesOS
-[documentation guidelines]: https://www.qubes-os.org/doc/doc-guidelines/
 

user/hardware/certified-hardware.md

@@ -63,7 +63,7 @@ Another important requirement is that Qubes-certified hardware should run only *
 The only exception is the use of (properly authenticated) CPU-vendor-provided blobs for silicon and memory initialization (see [Intel FSP](https://firmware.intel.com/learn/fsp/about-intel-fsp)) as well as other internal operations (see [Intel ME](https://www.apress.com/9781430265719)).
 However, we specifically require all code used for and dealing with the System Management Mode (SMM) to be open-source.
 
-While we [recognize](https://blog.invisiblethings.org/papers/2015/x86_harmful.pdf) the potential problems that proprietary CPU-vendor code can cause, we are also pragmatic enough to realize that we need to take smaller steps first, before we can implement even stronger countermeasures such as a [stateless laptop].
+While we [recognize](https://blog.invisiblethings.org/papers/2015/x86_harmful.pdf) the potential problems that proprietary CPU-vendor code can cause, we are also pragmatic enough to realize that we need to take smaller steps first, before we can implement even stronger countermeasures such as a [stateless laptop](https://blog.invisiblethings.org/papers/2015/state_harmful.pdf).
 A switch to open source boot firmware is one such important step.
 To be compatible with Qubes OS, the BIOS must properly expose all the VT-x, VT-d, and SLAT functionality that the underlying hardware offers (and which we require).
 Among other things, this implies **proper DMAR ACPI table** construction.
@@ -94,5 +94,3 @@ While we are willing to troubleshoot simple issues, we will need to charge a con
 
 If you are interested in having your hardware certified, please [contact us](mailto:business@qubes-os.org).
 
-[stateless laptop]: https://blog.invisiblethings.org/2015/12/23/state_harmful.html
-[stateless laptop]: https://blog.invisiblethings.org/papers/2015/state_harmful.pdf