Merge pull request #324 from 3mdeb/seo_fixes

Add SEO fixes

Author: artur-rs

docs/debug/iommu.md

@@ -10,7 +10,7 @@ This document is related to changes submitted to [mainline coreboot](https://rev
 * patches under redesign in upstream
 * planned firmware release to include patches v4.8.0.3
 * tested on Xen 4.8.3 and Debian stretch with Linux 4.14.50
-* `xl dmesg` dump with apic and iommu verbose [here](logs/iommu_enabled_xl_dmesg.log)
+* `xl dmesg` dump with apic and iommu verbose [here](https://github.com/pcengines/apu2-documentation/blob/master/docs/logs/iommu_enabled_xl_dmesg.log)
 * `CPUX: No irq handler for vector e7` log is still visible, but doesn't affect
 boot process. We look for solution for that log [here](https://github.com/pcengines/coreboot/pull/186)
 * platform survived 100x reboots to Xen without issue
@@ -70,7 +70,7 @@ information about groups in AMD IOMMU spec.
 ```
 
 # How to check features with Xen
-Please [read this blog post](TBD)
+Please [read this blog post](https://www.brendangregg.com/blog/2014-05-09/xen-feature-detection.html)
 
 # How to test IOMMU features
 

docs/debug/usb-debugging.md

@@ -472,8 +472,10 @@ reboot test immediately after failed cold boot (only one stick was detected).
 
 Full boot logs:
 
-* [tiano.log](../log/tiano.log) - both sticks detected
-* [tiano2.log](../log/tiano2.log) - one stick detected
+* [tiano.log](https://github.com/pcengines/apu2-documentation/blob/master/docs/logs/tiano.log) -
+both sticks detected
+* [tiano2.log](https://github.com/pcengines/apu2-documentation/blob/master/docs/logs/tiano2.log) -
+one stick detected
 
 The stick that was not detected for some reason is still visible as a boot
 option in the second log, but boot order was changed. Note that there are more

docs/ipxe_compile.md

@@ -5,8 +5,10 @@ iPXE - compilation, configuration and including in firmware
 
 ## Compilation
 
-1. Prepare [build environment](building_env.md), if you haven't done so yet
-2. [Build firmware](building_firmware.md),  if you haven't done so yet
+1. Prepare [build environment](https://github.com/pcengines/apu2-documentation/blob/864294e6c2219d70f174272f2e1b5f99b8b7b1db/docs/building_env.md),
+if you haven't done so yet
+2. [Build firmware](https://github.com/pcengines/apu2-documentation/blob/864294e6c2219d70f174272f2e1b5f99b8b7b1db/docs/building_firmware.md),
+if you haven't done so yet
 3. Clone iPXE repository:
 
     ```
@@ -29,7 +31,7 @@ iPXE - compilation, configuration and including in firmware
     * download proto: TFTP, HTTP, HTTPS, FTP, SLAM, NFS
     * image: NBI, ELF, MULTIBOOT, PXE, SCRIPT, BZIMAGE, COMBOOT, SDI, PNM, PNG
 
-    For more details please check [general.h](../ipxe/general.h).
+    For more details please check [general.h](https://github.com/pcengines/apu2-documentation/blob/master/ipxe/general.h).
 
     ```
     make bin/8086157b.rom EMBED=./shell.ipxe

docs/mpcie_modules.md

@@ -117,7 +117,7 @@ with interrupts. Related issues:
 
 - [coreboot #206](https://github.com/pcengines/coreboot/issues/206)
 - [coreboot #285](https://github.com/pcengines/coreboot/issues/285)
-- [coreboot #323](https://github.com/pcengines/coreboot/issues/323) 
+- [coreboot #323](https://github.com/pcengines/coreboot/issues/323)
 
 **Compatible slots:**
 
@@ -222,7 +222,7 @@ operating system.
 
 ### AW7915-NP1
 
-![AW7915-NP1](../images/mt7915e.jpg)
+![AW7915-NP1](images/mt7915e.jpg)
 
 The AW7915-NP1 is a MediaTek MT7915E based Wi-Fi 6 (802.11ax) card from AsiaRF.
 It features 4x4 MIMO and support for 160MHz channels, and a maximum theoretical
@@ -276,7 +276,7 @@ can be done, for example in Debian OS, by performing those steps:
     lines:
     ```
     deb http://ftp.pl.debian.org/debian stretch main non-free
-    deb-src  http://ftp.pl.debian.org/debian stretch main non-free   
+    deb-src  http://ftp.pl.debian.org/debian stretch main non-free
     ```
     - Update apt-get:
     ```
@@ -302,11 +302,11 @@ Due to apu boards construction, it is possible to test that module only under
 apu2 mPCIe2 slot. Capacitors placed near the mPCIe1 slot prevent connecting the
 SATA cables to the module. Therefore, module was tested only in mPCIe2 slot.
 After multiple tests performed, it turned out that ASM1061 module is not
-supported by PC Engines apu2 platform.  
+supported by PC Engines apu2 platform.
 
 **Tests results**
 
-Carried out tests and their results are presented in [debug documentation](/debug/mpcie2.md).
+Carried out tests and their results are presented in [debug documentation](debug/mpcie2.md).
 Detection problem is described more precisely there. Also, possible reasons
 of ASM1061 behavior are presented. Anyway, in every case and configuration
 that module doesn't work properly.

docs/research/tpm2-triage.md

@@ -10,7 +10,7 @@ Linux 0.10.0 and Debian jessie.
 
 HW used: APU2 with TPM LPC addon
 
-1. Install 4.13.0-rc6 kernel - [config](4_13_rc6_tpm_config)
+1. Install 4.13.0-rc6 kernel - [config](https://github.com/pcengines/apu2-documentation/blob/master/docs/research/4_13_rc6_tpm_config)
 2. Enable tpm2 module:
 
     ```

docs/rs-232.jpg

@@ -11,7 +11,7 @@ Intro
 Coreboot ROM building process
 -----------------------------
 
-1. [Build environment container](https://github.com/pcengines/apu2-documentation/blob/master/docs/building_env.md).
+1. [Build environment container](https://github.com/pcengines/apu2-documentation/blob/864294e6c2219d70f174272f2e1b5f99b8b7b1db/docs/building_env.md).
 
 2. Clone coreboot repository:
     ```

docs/supported_coreboot_build.md

@@ -119,7 +119,7 @@ extracted kernel files are placed.
 docker run --rm -v ${PWD}:/workdir -t -i pc-engines/apu2 bash
 ```
 
-If you don't have `pc-engines/apu2` environment built follow [this instruction](./building_env.md).
+If you don't have `pc-engines/apu2` environment built follow [this instruction](https://github.com/pcengines/apu2-documentation/blob/864294e6c2219d70f174272f2e1b5f99b8b7b1db/docs/building_env.md).
 
 6. Read old config file: