diff --git a/.github/workflows/seo.yml b/.github/workflows/seo.yml
new file mode 100644
index 0000000000..9e9ea65cf7
--- /dev/null
+++ b/.github/workflows/seo.yml
@@ -0,0 +1,79 @@
+---
+name: SEO CI
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+    branches:
+      - master
+
+jobs:
+  linkChecker:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+
+      - name: Link Checker
+        id: lychee
+        uses: lycheeverse/lychee-action@v1.8.0
+        with:
+          fail: true
+          args: --max-redirects 10 -a 403,500,503,504 .
+  seo_spy_orphan_pages:
+    runs-on: ubuntu-latest
+    name: Check orphan pages
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@v3
+      - name: Checkout SEO Spy
+        uses: actions/checkout@v3
+        with:
+          repository: 3mdeb/seo-spy
+          path: seo-spy
+      - uses: actions/setup-python@v3
+        with:
+          python-version: '3.9'
+      - name: Install Dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -r seo-spy/requirements.txt
+          pip install -r requirements.txt
+      - name: Serve site
+        run: |
+          mkdocs build
+          python3 -m http.server --directory site &
+          sed -i 's/https:\/\/docs.dasharo.com/http:\/\/0.0.0.0:8000/g' site/sitemap.xml
+      - name: Check orphan pages
+        uses: 3mdeb/seo-spy-action@main
+        with:
+          domain: 'http://0.0.0.0:8000'
+  seo_spy_canonical_links:
+    runs-on: ubuntu-latest
+    name: Check canonical links
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@v3
+      - name: Checkout SEO Spy
+        uses: actions/checkout@v3
+        with:
+          repository: 3mdeb/seo-spy
+          path: seo-spy
+      - uses: actions/setup-python@v3
+        with:
+          python-version: '3.9'
+      - name: Install Dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -r seo-spy/requirements.txt
+          pip install -r requirements.txt
+      - name: Serve site
+        run: |
+          mkdocs build
+          python3 -m http.server --directory site &
+          sed -i 's/https:\/\/docs.dasharo.com/http:\/\/0.0.0.0:8000/g' site/sitemap.xml
+      - name: Check canonical links
+        uses: 3mdeb/seo-spy-action@main
+        with:
+          domain: 'http://0.0.0.0:8000'
+          args: '-c'
diff --git a/.lycheeignore b/.lycheeignore
new file mode 100644
index 0000000000..dfa85959ad
--- /dev/null
+++ b/.lycheeignore
@@ -0,0 +1,7 @@
+https://www.paypal.com/cgi-bin/webscr
+https://twitter.com/*
+89eBqUwoCpnPoUKD367kJm3Gsw639EUSdG3xwUyQmDroKHWHPyhYmJ63uP41ArHfPsBihNFTYjASpRUGaeSyp3JS9BmtjpQ
+pkt1qyv4gmnvvg2vfyj89e63thzj68jf2y9k7ssee7
+1GUm6FF7Fon6Umrt5CSi3AxxYg8dM2NKvV
+https://reproducible-builds.org/
+https://www.linkedin.com/company/*
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index 7f8e06ad57..134edf3317 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -36,6 +36,19 @@ repos:
     hooks:
       - id: codespell
 
+  - repo: local
+    hooks:
+      - id: double_slashes_url_external
+        name: Check double slashes in external URLs
+        entry: https?:\/\/[^\s]*(?<!http:)((?<!https:)\/\/).*
+        language: pygrep
+        exclude: '^.*.(jpeg|jpg|png|pdf)$'
+      - id: double_slashes_url_markdown
+        name: Check double slashes in markdown URLs
+        entry: (\:\s|\()[^\s]*(?<!http:)((?<!https:)\/\/)
+        language: pygrep
+        exclude: '^.*.(jpeg|jpg|png|pdf)$'
+
 ci:
   autoupdate_commit_msg: 'pre-commit: autoupdate hooks'
   autofix_prs: false
diff --git a/README.md b/README.md
index 769f6a6f30..2534a7576a 100644
--- a/README.md
+++ b/README.md
@@ -28,14 +28,29 @@ render correctly as HTML in local preview.
 
 ### Broken links checker
 
-To check for broken links we use `linkchecker`.  It should be installed through
-[requirements.txt](#local-build). Following command produces
-`linkchecker-out.txt` file, which contains list of broken links, please make
-sure your proposed changes have no broken links reported. Feel free to adjust
-other parameters according to your needs.
+Currently we are using [lychee](https://github.com/lycheeverse/lychee) a fast,
+async, stream-based link checker written in Rust. The automatic check is
+triggered on each push to master PR.
 
-```shell
-linkchecker -f linkcheckerrc http://0.0.0.0:8000
+You can also run it locally using a docker image:
+
+```bash
+$ docker run --init -it --rm -w $(pwd) -v $(pwd):$(pwd) lycheeverse/lychee
+    --max-redirects 10 -a 403,429,500,502,503,999 .
+```
+
+### Relative links
+
+Please avoid using URL-related links like:
+
+```md
+[MSI PRO Z790-P](../../unified/msi/overview)
+```
+
+Instead, use relative links within the repository:
+
+```md
+[MSI PRO Z790-P](../unified/msi/overview.md)
 ```
 
 ### Make sure no TBD or TODO content is displayed
diff --git a/docs/common-coreboot-docs/checkbox.md b/docs/common-coreboot-docs/checkbox.md
index 30a83c5ffc..330c76f98b 100644
--- a/docs/common-coreboot-docs/checkbox.md
+++ b/docs/common-coreboot-docs/checkbox.md
@@ -64,7 +64,7 @@ perform the following steps:
         it.
     - Restart your system for changes to take effect.
 
-![](../images/checkbox_aut_login.jpg)
+![](../images/checkbox_aut_login.png)
 
 ## Download and install Checkbox
 
diff --git a/docs/common-coreboot-docs/dumping_logs.md b/docs/common-coreboot-docs/dumping_logs.md
index f987c1591f..1598652af9 100644
--- a/docs/common-coreboot-docs/dumping_logs.md
+++ b/docs/common-coreboot-docs/dumping_logs.md
@@ -7,7 +7,7 @@ a running system.
 
 ## System information
 
-One may use [Dasharo Tools Suite HCL report](../../dasharo-tools-suite/documentation#hcl-report)
+One may use [Dasharo Tools Suite HCL report](https://docs.dasharo.com/dasharo-tools-suite/documentation#hcl-report)
 or [fwdump-docker image](https://github.com/3mdeb/fwdump-docker) to
 gather all the hardware configuration information from a running system. The
 usage of the tools should result in an archive containing various logs from the
@@ -24,8 +24,8 @@ with the firmware. This method requires Secure Boot to be disabled.
 Options to get `cbmem` utility:
 
 1. Download precompiled utility from [3mdeb cloud](https://cloud.3mdeb.com/index.php/s/zTqkJQdNtJDo5Nd/download)
-2. Use [Dasharo Tools Suite](../../dasharo-tools-suite/releases#v110) v1.1.0 or
-   newer which has `cbmem` utility built in.
+2. Use [Dasharo Tools Suite](https://docs.dasharo.com/dasharo-tools-suite/releases#v110)
+   v1.1.0 or newer which has `cbmem` utility built in.
 3. Compile `cbmem utility`. See procedure below.
 
 Short instruction how to compile and use `cbmem` on Ubuntu 22.04 live CD:
diff --git a/docs/dasharo-tools-suite/overview.md b/docs/dasharo-tools-suite/overview.md
index e7c2bc0b4b..9ad6623323 100644
--- a/docs/dasharo-tools-suite/overview.md
+++ b/docs/dasharo-tools-suite/overview.md
@@ -22,5 +22,5 @@ issues](https://github.com/Dasharo/dasharo-issues/issues?q=is%3Aopen+is%3Aissue+
 
 And if you have already used this system and would be interested in supporting
 the project, please check how to get [Supporters
-Entrance](../../osf-trivia-list/dts/#what-is-dasharo-tools-suite-supporters-entrance),
+Entrance](https://docs.dasharo.com/osf-trivia-list/dts/#what-is-dasharo-tools-suite-supporters-entrance),
 which ensures delivery of Dasharo firmware updates.
diff --git a/docs/dev-proc/smbios-rules.md b/docs/dev-proc/smbios-rules.md
index 6d27b6f736..34d6132515 100644
--- a/docs/dev-proc/smbios-rules.md
+++ b/docs/dev-proc/smbios-rules.md
@@ -37,7 +37,7 @@ Dasharo ([major_framework]+[minor_framework]) v[version]
   primary framework, e.g. a coreboot payload. May not always be used, e.g. if
   `edk2` is used as the primary framework.
 - `version` means version according to official
-  [Dasharo Versioning](../versioning) documentation.
+  [Dasharo Versioning](versioning.md) documentation.
 
 _For [TianoCore UEFIPayloadPkg](https://github.com/Dasharo/edk2/tree/dasharo/UefiPayloadPkg),
 we use the simpler and more recognizable UEFI name._
diff --git a/docs/ecosystem/overview.md b/docs/ecosystem/overview.md
index 068badddd8..a3a22ca833 100644
--- a/docs/ecosystem/overview.md
+++ b/docs/ecosystem/overview.md
@@ -5,7 +5,7 @@
 Dasharo ecosystem contain multiple components on various levels of
 organization. This section overview role of every component.
 
-![](../images/ecosystem_overview.jpg)
+![](../images/ecosystem_overview.png)
 
 * Open Source Firmware Community - semi-organised collections of contributors
   to projects related to embedded firmware. Dasharo project contributors are
diff --git a/docs/glossary.md b/docs/glossary.md
index 59b876aa84..705e1cb824 100644
--- a/docs/glossary.md
+++ b/docs/glossary.md
@@ -10,8 +10,8 @@ keep content added by us minimalistic.
 ## Embedded Firmware
 
 We use definition explained in first chapter of
-["Embedded Firmware Solutions"](https://www.apress.com/gp/book/9781484200711) book
-by Jiming Sun, Marc Jones, Stefan Reinauer and Vincent Zimmer.
+["Embedded Firmware Solutions"](https://link.springer.com/book/10.1007/978-1-4842-0070-4)
+book by Jiming Sun, Marc Jones, Stefan Reinauer and Vincent Zimmer.
 
 Firmware is "layer of software between the hardware and the
 operating system (OS), with the main purpose to initialize and
diff --git a/docs/images/NS51-front-1.jpg b/docs/images/NS51-front-1.jpg
deleted file mode 100644
index 506b60ec59..0000000000
Binary files a/docs/images/NS51-front-1.jpg and /dev/null differ
diff --git a/docs/images/NS51-front-1.png b/docs/images/NS51-front-1.png
new file mode 100644
index 0000000000..828b58a977
Binary files /dev/null and b/docs/images/NS51-front-1.png differ
diff --git a/docs/images/NV4x-front-1.jpg b/docs/images/NV4x-front-1.jpg
deleted file mode 100644
index 33427c4980..0000000000
Binary files a/docs/images/NV4x-front-1.jpg and /dev/null differ
diff --git a/docs/images/NV4x-front-1.png b/docs/images/NV4x-front-1.png
new file mode 100644
index 0000000000..5806a83a5c
Binary files /dev/null and b/docs/images/NV4x-front-1.png differ
diff --git a/docs/images/SD-wire_PCB_elements_1.jpg b/docs/images/SD-wire_PCB_elements_1.jpg
deleted file mode 100644
index b79baf2ef0..0000000000
Binary files a/docs/images/SD-wire_PCB_elements_1.jpg and /dev/null differ
diff --git a/docs/images/SD-wire_PCB_elements_1.png b/docs/images/SD-wire_PCB_elements_1.png
new file mode 100644
index 0000000000..39893a94c3
Binary files /dev/null and b/docs/images/SD-wire_PCB_elements_1.png differ
diff --git a/docs/images/SD-wire_PCB_elements_2.jpg b/docs/images/SD-wire_PCB_elements_2.jpg
deleted file mode 100644
index 92d28c5cac..0000000000
Binary files a/docs/images/SD-wire_PCB_elements_2.jpg and /dev/null differ
diff --git a/docs/images/SD-wire_PCB_elements_2.png b/docs/images/SD-wire_PCB_elements_2.png
new file mode 100644
index 0000000000..d9c1ef59e1
Binary files /dev/null and b/docs/images/SD-wire_PCB_elements_2.png differ
diff --git a/docs/images/SD-wire_scheme-1.jpg b/docs/images/SD-wire_scheme-1.jpg
deleted file mode 100644
index 7f9629e4ab..0000000000
Binary files a/docs/images/SD-wire_scheme-1.jpg and /dev/null differ
diff --git a/docs/images/SD-wire_scheme-1.png b/docs/images/SD-wire_scheme-1.png
new file mode 100644
index 0000000000..f8ad59e365
Binary files /dev/null and b/docs/images/SD-wire_scheme-1.png differ
diff --git a/docs/images/checkbox_aut_login.jpg b/docs/images/checkbox_aut_login.jpg
deleted file mode 100644
index 729fbcbe86..0000000000
Binary files a/docs/images/checkbox_aut_login.jpg and /dev/null differ
diff --git a/docs/images/checkbox_aut_login.png b/docs/images/checkbox_aut_login.png
new file mode 100644
index 0000000000..4e286a22dd
Binary files /dev/null and b/docs/images/checkbox_aut_login.png differ
diff --git a/docs/images/ecosystem_overview.jpg b/docs/images/ecosystem_overview.jpg
deleted file mode 100644
index fb2fd8ee68..0000000000
Binary files a/docs/images/ecosystem_overview.jpg and /dev/null differ
diff --git a/docs/images/ecosystem_overview.png b/docs/images/ecosystem_overview.png
new file mode 100644
index 0000000000..26b508b35a
Binary files /dev/null and b/docs/images/ecosystem_overview.png differ
diff --git a/docs/images/jsm_add_request.jpg b/docs/images/jsm_add_request.jpg
deleted file mode 100644
index 021756c319..0000000000
Binary files a/docs/images/jsm_add_request.jpg and /dev/null differ
diff --git a/docs/images/jsm_add_request.png b/docs/images/jsm_add_request.png
new file mode 100644
index 0000000000..409ce89415
Binary files /dev/null and b/docs/images/jsm_add_request.png differ
diff --git a/docs/images/jsm_view_requests.jpg b/docs/images/jsm_view_requests.jpg
deleted file mode 100644
index 191d64a20e..0000000000
Binary files a/docs/images/jsm_view_requests.jpg and /dev/null differ
diff --git a/docs/images/jsm_view_requests.png b/docs/images/jsm_view_requests.png
new file mode 100644
index 0000000000..22b8051222
Binary files /dev/null and b/docs/images/jsm_view_requests.png differ
diff --git a/docs/images/jsm_workflow.jpg b/docs/images/jsm_workflow.jpg
deleted file mode 100644
index ad1355dcb0..0000000000
Binary files a/docs/images/jsm_workflow.jpg and /dev/null differ
diff --git a/docs/images/jsm_workflow.png b/docs/images/jsm_workflow.png
new file mode 100644
index 0000000000..5f77d8bd1f
Binary files /dev/null and b/docs/images/jsm_workflow.png differ
diff --git a/docs/images/rte-rest-api-interface.jpg b/docs/images/rte-rest-api-interface.jpg
deleted file mode 100644
index 9955fc366d..0000000000
Binary files a/docs/images/rte-rest-api-interface.jpg and /dev/null differ
diff --git a/docs/images/rte-rest-api-interface.png b/docs/images/rte-rest-api-interface.png
new file mode 100644
index 0000000000..3198f53bb7
Binary files /dev/null and b/docs/images/rte-rest-api-interface.png differ
diff --git a/docs/images/rte-v1.1.0-interface-desc.jpg b/docs/images/rte-v1.1.0-interface-desc.jpg
deleted file mode 100644
index 3c4eaf0822..0000000000
Binary files a/docs/images/rte-v1.1.0-interface-desc.jpg and /dev/null differ
diff --git a/docs/images/rte-v1.1.0-interface-desc.png b/docs/images/rte-v1.1.0-interface-desc.png
new file mode 100644
index 0000000000..02ca467c0b
Binary files /dev/null and b/docs/images/rte-v1.1.0-interface-desc.png differ
diff --git a/docs/inquiries/commercial-inquiries.md b/docs/inquiries/commercial-inquiries.md
index d076092803..80206a3180 100644
--- a/docs/inquiries/commercial-inquiries.md
+++ b/docs/inquiries/commercial-inquiries.md
@@ -1,5 +1,5 @@
 # Commercial inquiries
 
 If you have any questions about our services, feel free to contact us using
-[Dasharo contact form](https://dasharo.com/pages/contact.html) or
+[Dasharo contact form](https://www.dasharo.com/pages/contact/) or
 [3mdeb contact form](https://3mdeb.com/contact/), or [book a call with us](https://calendly.com/3mdeb/consulting-remote-meeting).
diff --git a/docs/osf-trivia-list/dasharo.md b/docs/osf-trivia-list/dasharo.md
index 09835457c0..6b432fe18f 100644
--- a/docs/osf-trivia-list/dasharo.md
+++ b/docs/osf-trivia-list/dasharo.md
@@ -19,14 +19,14 @@ Dasharo is an open-source firmware distribution focusing on:
 
 Dasharo consists of [productized services](#dasharo-professional-support), set
 of [open-source repositories](https://github.com/orgs/Dasharo/repositories),
-and [quality control](../../unified-test-documentation/overview/) which help to
-provide scalable, modular, easy to combine open-source BIOS, UEFI, and firmware
-solutions. It offers the components that are needed to develop and maintain a
-high quality, and modular firmware, for the stability and security of your
-platform.
+and [quality control](https://docs.dasharo.com/unified-test-documentation/overview/)
+which help to provide scalable, modular, easy to combine open-source BIOS, UEFI,
+and firmware solutions. It offers the components that are needed to develop
+and maintain a high quality, and modular firmware, for the stability and
+security of your platform.
 
 For individuals Dasharo provides optional features in subscription model called
-[Supporters Entrance](../dts/#how-to-get-dasharo-tools-suite-supporters-entrance).
+[Supporters Entrance](dts.md#how-to-get-dasharo-tools-suite-supporters-entrance).
 
 ## Why 3mdeb created Dasharo?
 
@@ -101,7 +101,7 @@ release notes directly to the customer and does not have to be publicly
 available.
 1. Every firmware produced by Dasharo Ecosystem use [Semantic Versioning
 2.0.0](https://semver.org/) compatible versioning scheme. For details please
-check [description](../../dev-proc/versioning).
+check [description](https://docs.dasharo.com/dev-proc/versioning).
 1. Every firmware produced by Dasharo Ecosystem should use [Keep A Changelog
 1.0.0](https://keepachangelog.com/en/1.0.0/) compatible scheme as changelog
 format.
@@ -129,7 +129,7 @@ Those microcontrollers and IP blocks typically require firmware blobs as well.
 Some of the blobs are clearly visible, some may be obfuscated and hidden inside
 the silicon or other firmware blobs (e.g. Intel Management Engine region
 contains multiple other blobs besides the ME firmware -
-[more about Intel ME blob](../me)).
+[more about Intel ME blob](me.md)).
 
 So Dasharo's binary blob policy is as follows:
 
@@ -270,12 +270,13 @@ and binary blobs transmission, as well as recovery.
 
 For more details about zero-touch initial deployment please read relevant
 DTS
-[documentation](../../dasharo-tools-suite/documentation/#dasharo-zero-touch-initial-deployment).
+[documentation](https://docs.dasharo.com/dasharo-tools-suite/documentation/#dasharo-zero-touch-initial-deployment).
 
 ### Dasharo Clean and Simple Code
 
 Dasharo is an open-source distribution project with a simple code structure
-described in detail [here](../../../dev-proc/source-code-structure). While the
+described in detail
+[here](https://docs.dasharo.com/dev-proc/source-code-structure). While the
 project benefits from the simplicity of the coreboot source code, it is
 continuously researching and improving its development process and tools to
 provide a superior experience for developers.  One example of this ongoing work
@@ -283,7 +284,8 @@ is the improvements made to fork maintenance, currently being tracked in [this
 issue](https://github.com/Dasharo/dasharo-issues/issues/310) on the Dasharo
 GitHub repository. The project also explores the concept of a bootstrapable
 toolchain, discussed in the [build process
-section](../../osf-trolling-list/build_process) of the project documentation.
+section](https://docs.dasharo.com/osf-trolling-list/build_process)
+of the project documentation.
 
 ### Dasharo Long Term Maintenance
 
@@ -479,11 +481,12 @@ such a case, don't hesitate to contact us; we will see what we can do. However,
 the community member who requested support for the platform should also offer
 their help in validating the firmware and maintenance. That kind of request
 will be more than welcome from active community members. New members should
-consider [ways to help us](../../ways-you-can-help-us/) to gain a reputation
-that can lead to influencing Dasharo Community Supported roadmap.
+consider [ways to help us](https://docs.dasharo.com/ways-you-can-help-us/)
+to gain a reputation that can lead to influencing Dasharo Community Supported
+roadmap.
 
 [coreboot-scope]: https://doc.coreboot.org/#scope-of-the-coreboot-project
-[dtsos]: ../../dasharo-tools-suite/overview/
+[dtsos]: ../dasharo-tools-suite/overview.md
 [lvfs]: https://fwupd.org/lvfs/docs/consulting
 [gerrit-review]: https://review.coreboot.org/c/homepage/+/63402
 [cb-distro]: https://doc.coreboot.org/distributions.html
diff --git a/docs/osf-trivia-list/deployment.md b/docs/osf-trivia-list/deployment.md
index 128b5d855c..4d59ecb338 100644
--- a/docs/osf-trivia-list/deployment.md
+++ b/docs/osf-trivia-list/deployment.md
@@ -14,21 +14,19 @@ Following sections explain how to deal with most common `flashrom` problem.
 
 ### How to install Dasharo flashrom fork ?
 
-The following procedure is for advanced users familiar with source compilation
-and can resolve potential missing dependencies or other typical compilation
-problems. If you are unfamiliar with compilation from source, we recommend
-using Dasharo Tools Suite, a minimal Linux environment to deploy, update, and
-maintain firmware on Dasharo-supported devices. Please follow [DTS
-documentation](../../dasharo-tools-suite/overview). Otherwise, please follow
-the compilation procedure.
+* Install flashrom v1.1 or newer with your distribution's package manager if
+  you don't have it installed yet. If your distro doesn't provide flashrom or
+  provides an outdated one, you can build it yourself using
+  [this instruction](https://www.flashrom.org/dev_guide/building_from_source.html).
+* Or compile recent version of flashrom:
 
 If you need flashrom for Dasharo-supported hardware and for some reason you
 cannot use DTS, please consider the compilation of Dasharo [flashrom
 fork](https://github.com/Dasharo/flashrom/tree/dasharo-release).
 
 For compilation details and related issues, please check flashrom
-[documentation](https://review.coreboot.org/plugins/gitiles/flashrom/+/refs/heads/master/README)
-and [community](https://www.flashrom.org/Contact).
+[documentation](https://review.coreboot.org/plugins/gitiles/flashrom/+/refs/heads/master/README.rst)
+and [community](https://www.flashrom.org/contact.html).
 
 ### Perform dry run to detect the problems early
 
@@ -157,7 +155,7 @@ Note: flashrom can never write if the flash chip isn't found automatically.
 
 that means your flashrom version is incorrect. Follow the procedure of
 [building flashrom](#how-to-install-dasharo-flashrom-fork) or use
-[DTS](../../dasharo-tools-suite/overview).
+[DTS](../dasharo-tools-suite/overview.md).
 
 ### Chip write protection enabled
 
@@ -199,7 +197,7 @@ tools that can simplify the operation for the user -->
 It is always a good idea to backup the original BIOS of your hardware, before
 switching to open-source firmware.
 
-* Boot [Dasharo Tools Suite](../../../dasharo-tools-suite/documentation#bootable-usb-stick)
+* Boot [Dasharo Tools Suite](https://docs.dasharo.com/dasharo-tools-suite/documentation#bootable-usb-stick)
 * Choose option 9) Shell.
 * Read content of SPI NOR flash:
 
diff --git a/docs/osf-trivia-list/dts.md b/docs/osf-trivia-list/dts.md
index f1c0ef86c8..74fd70741c 100644
--- a/docs/osf-trivia-list/dts.md
+++ b/docs/osf-trivia-list/dts.md
@@ -24,18 +24,18 @@ Please help us develop Dasharo influence on open-source firmware market and
 spread the word about it. There are multiple ways to do that:
 
 * [Join Dasharo Matrix
-  Community](../../ways-you-can-help-us/#join-dasharo-matrix-community) and
+  Community](../ways-you-can-help-us.md#join-dasharo-matrix-community) and
   support other members of community
 * [Join Dasharo open-source firmware
-  vPub](../../ways-you-can-help-us/#join-dasharo-open-source-firmware-vpub) or
+  vPub](../ways-you-can-help-us.md#join-dasharo-open-source-firmware-vpub) or
   other related event organized by 3mdeb or Dasharo Team.
-* [Write a Google review](../../ways-you-can-help-us/#write-a-google-review)
+* [Write a Google review](../ways-you-can-help-us.md#write-a-google-review)
 * [Follow us on social
-  media](../../ways-you-can-help-us/#follow-us-on-social-media) and help
+  media](../ways-you-can-help-us.md#follow-us-on-social-media) and help
   spreading the word about Dasharo.
-* [Contribute](../../ways-you-can-help-us/#contribute-through-github)
+* [Contribute](../ways-you-can-help-us.md#contribute-through-github)
   documentation, test results, [Dasharo Hardware Compatibility List
-  Reports](../../../dasharo-tools-suite/documentation/#hcl-report)
+  Reports](https://docs.dasharo.com/dasharo-tools-suite/documentation/#hcl-report)
 
 To get access to DTS SE you should [contact 3mdeb](mailto:leads@3mdeb.com) or
 [Dasharo Team](mailto:contact@dasharo.com) and prove your contribution
@@ -44,7 +44,7 @@ would be glad to give you access to DTS SE for a year.
 
 ### I have more time than money and I can't code
 
-Please [contribute](../../ways-you-can-help-us/#contribute-through-github)
+Please [contribute](../ways-you-can-help-us.md#contribute-through-github)
 ideas for new features, review documentation and help testing bug fixes.
 
 If you would like to pursue that path please contact us on [Dasharo -
@@ -57,7 +57,7 @@ SE updates.
 
 ### I have more money than time
 
-Please [donate](../../ways-you-can-help-us/#donate-money) using one of
+Please [donate](../ways-you-can-help-us.md#donate-money) using one of
 available methods and contact [3mdeb](mailto:leads@3mdeb.com) or [Dasharo
 Team](mailto:contact@dasharo.com) to let us know about your donation. Minimal
 donating to access DTS SE with one year update support is 60EUR.
diff --git a/docs/osf-trolling-list/jsm_documentation.md b/docs/osf-trolling-list/jsm_documentation.md
index d001fd6470..0318478753 100644
--- a/docs/osf-trolling-list/jsm_documentation.md
+++ b/docs/osf-trolling-list/jsm_documentation.md
@@ -36,9 +36,9 @@ To add a new request using the web service:
 3. When you are ready to send the request, click Send. Your request is created
    and awaits our response.
 
-![](../images/jsm_add_request.jpg)
+![](../images/jsm_add_request.png)
 
-![](../images/jsm_view_requests.jpg)
+![](../images/jsm_view_requests.png)
 
 ### Raising requests using email
 
@@ -64,7 +64,7 @@ also receive information on which requests will be resolved in the next release.
 
 The diagram below presents what the workflow of JSM requests looks like.
 
-![](../images/jsm_workflow.jpg)
+![](../images/jsm_workflow.png)
 
 * `Open` - your request is created and visible for us, but we didn't start
 working on it yet.
diff --git a/docs/projects/capsule-updates.md b/docs/projects/capsule-updates.md
index 9a5c07e012..f1f9b3e585 100644
--- a/docs/projects/capsule-updates.md
+++ b/docs/projects/capsule-updates.md
@@ -52,7 +52,7 @@ transparent validation, privacy-respecting implementation, liberty for the
 owners, and trustworthiness for all. More details can be found here [\[7\]][7].
 
 [1]: https://github.com/coreboot/coreboot
-[2]: https://docs.dasharo.com/variants/msi_z690/overview/
+[2]: https://docs.dasharo.com/unified/msi/overview/
 [3]: https://docs.dasharo.com/variants/dell_optiplex/overview/
 [4]: https://github.com/tianocore/edk2
 [5]: https://github.com/fwupd/fwupd
diff --git a/docs/transparent-validation/msi-z690/images/reading_power_status.jpg b/docs/transparent-validation/msi-z690/images/reading_power_status.jpg
deleted file mode 100644
index 7fccb64315..0000000000
Binary files a/docs/transparent-validation/msi-z690/images/reading_power_status.jpg and /dev/null differ
diff --git a/docs/transparent-validation/msi-z690/images/reading_power_status.png b/docs/transparent-validation/msi-z690/images/reading_power_status.png
new file mode 100644
index 0000000000..9360af77ab
Binary files /dev/null and b/docs/transparent-validation/msi-z690/images/reading_power_status.png differ
diff --git a/docs/transparent-validation/msi-z690/laboratory-assembly-guide.md b/docs/transparent-validation/msi-z690/laboratory-assembly-guide.md
index 8f3e88681f..9457701967 100644
--- a/docs/transparent-validation/msi-z690/laboratory-assembly-guide.md
+++ b/docs/transparent-validation/msi-z690/laboratory-assembly-guide.md
@@ -11,7 +11,7 @@ The below table contains information about all elements which are needed to
 create the testing stand.
 
 * MSI PRO Z690-A platform
-* [RTE v1.1.0](https://3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/rte/)
+* [RTE v1.1.0](https://shop.3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/rte/)
 * Sonoff S20 type E
 * 4x standard female-female connection wire 2.54 mm raster
 * 7x standard female-female connection wire 2.54/2.00 mm raster
@@ -32,7 +32,7 @@ documentation.
 ### RTE
 
 RTE (acronym: Remote Testing Environment) should be prepared in accordance with
-[Quick start guide](../../rte/v1.1.0/quick-start-guide) documentation dedicated
+[Quick start guide](../rte/v1.1.0/quick-start-guide.md) documentation dedicated
 to the device.
 
 ### Sonoff
@@ -248,7 +248,7 @@ Connect the RTE SPI header to the platform as described in the table:
 Connect the RTE J1 header to the platform JFP1 header as shown in the picture
 below:
 
-![IMG](images/reading_power_status.jpg)
+![IMG](images/reading_power_status.png)
 
 The values ​​of `R1`, `R2`, `V1` and `V2` should meet the relationship according
 to the formula `R1/R2 = V2/V1`. `V1` cannot be greater than 3.3V (RTE property).
@@ -282,7 +282,7 @@ The following sections describe how to use all of the enabled features:
 ### Serial connection
 
 The method of setting and using serial connection is described in the
-[Serial connection guide](../../rte/v1.1.0/serial-port-connection-guide).
+[Serial connection guide](../rte/v1.1.0/serial-port-connection-guide.md).
 
 ### Power supply controlling
 
diff --git a/docs/transparent-validation/msi-z790/laboratory-assembly-guide.md b/docs/transparent-validation/msi-z790/laboratory-assembly-guide.md
index 60129829ad..45c8078e0d 100644
--- a/docs/transparent-validation/msi-z790/laboratory-assembly-guide.md
+++ b/docs/transparent-validation/msi-z790/laboratory-assembly-guide.md
@@ -11,7 +11,7 @@ The below table contains information about all elements which are needed to
 create the testing stand.
 
 * MSI PRO Z790-P platform
-* [RTE v1.1.0](https://3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/rte/)
+* [RTE v1.1.0](https://shop.3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/rte/)
 * Sonoff S20 type E
 * 4x standard female-female connection wire 2.54 mm raster
 * 7x standard female-female connection wire 2.54/2.00 mm raster
@@ -26,13 +26,13 @@ components of the laboratory stand.
 ### MSI PRO Z790-P
 
 MSI PRO Z790-P platform should be prepared in accordance with the
-[Motherboard assembly](presale-assembly-and-validation.md#motherboard-assembly-only)
+[Motherboard assembly](../msi-z690/presale-assembly-and-validation.md#motherboard-assembly-only)
 documentation.
 
 ### RTE
 
 RTE (acronym: Remote Testing Environment) should be prepared in accordance with
-[Quick start guide](../../rte/v1.1.0/quick-start-guide) documentation dedicated
+[Quick start guide](../rte/v1.1.0/quick-start-guide.md) documentation dedicated
 to the device.
 
 ### Sonoff
@@ -248,7 +248,7 @@ Connect the RTE SPI header to the platform as described in the table:
 Connect the RTE J1 header to the platform JFP1 header as shown in the picture
 below:
 
-![IMG](../msi-z690/images/reading_power_status.jpg)
+![IMG](../msi-z690/images/reading_power_status.png)
 
 The values ​​of `R1`, `R2`, `V1` and `V2` should meet the relationship according
 to the formula `R1/R2 = V2/V1`. `V1` cannot be greater than 3.3V (RTE property).
@@ -282,7 +282,7 @@ The following sections describe how to use all of the enabled features:
 ### Serial connection
 
 The method of setting and using serial connection is described in the
-[Serial connection guide](../../rte/v1.1.0/serial-port-connection-guide).
+[Serial connection guide](../rte/v1.1.0/serial-port-connection-guide.md).
 
 ### Power supply controlling
 
diff --git a/docs/transparent-validation/pikvm/assembly-and-validation.md b/docs/transparent-validation/pikvm/assembly-and-validation.md
index 80e4fccb02..20b3f7d807 100644
--- a/docs/transparent-validation/pikvm/assembly-and-validation.md
+++ b/docs/transparent-validation/pikvm/assembly-and-validation.md
@@ -203,4 +203,4 @@ display with 1920x1080 resolution.
 
 ## Where to buy?
 
-The PiKVM is available in our [online shop](https://3mdeb.com/shop/open-source-hardware/pikvm/).
+The PiKVM is available in our [online shop](https://shop.3mdeb.com/shop/open-source-hardware/pikvm/).
diff --git a/docs/transparent-validation/rte/introduction.md b/docs/transparent-validation/rte/introduction.md
index ed913fe32e..bb769f93f2 100644
--- a/docs/transparent-validation/rte/introduction.md
+++ b/docs/transparent-validation/rte/introduction.md
@@ -20,7 +20,7 @@ applications are:
 
 ## Where to buy?
 
-**RTE** can be also bought in our [3mdeb shop](https://3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/rte/).
+**RTE** can be also bought in our [3mdeb shop](https://shop.3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/rte/).
 
 Full Remote Testing Environment set includes:
 
diff --git a/docs/transparent-validation/rte/v1.1.0/flashing-guide.md b/docs/transparent-validation/rte/v1.1.0/flashing-guide.md
index aa24eb5b63..5a3d686a83 100644
--- a/docs/transparent-validation/rte/v1.1.0/flashing-guide.md
+++ b/docs/transparent-validation/rte/v1.1.0/flashing-guide.md
@@ -32,7 +32,7 @@ RTE.
     ![](../../../images/ch341a_rec/wson8_probe2.jpg)
 
 1. Connect the cables coming out from the WSON8 probe to the
-    [SPI header](../specification/) according to the pictures and table
+    [SPI header](specification.md) according to the pictures and table
     below.
 
     - Top view of flash chip:
diff --git a/docs/transparent-validation/rte/v1.1.0/quick-start-guide.md b/docs/transparent-validation/rte/v1.1.0/quick-start-guide.md
index 99781b477a..7a473d5cea 100644
--- a/docs/transparent-validation/rte/v1.1.0/quick-start-guide.md
+++ b/docs/transparent-validation/rte/v1.1.0/quick-start-guide.md
@@ -8,7 +8,7 @@ common preparation of RTE without listed functions.
 
 ## Prerequisites
 
-* [RTE board](https://3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/rte/)
+* [RTE board](https://shop.3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/rte/)
     (this document is based on v1.1.0)
 * Micro-USB 5V 2.5A power supply
 * Orange Pi
@@ -48,8 +48,8 @@ common preparation of RTE without listed functions.
 1. Insert SD card into Orange Pi.
 1. Connect the ethernet cable to Orange Pi.
 1. Plug the USB-UART converter into your computer and connect its pins with
-    [RTE J2 Header](../specification/#uart0-header). (you may need a
-    USB extension cable)
+    [RTE J2 Header](specification.md#uart0-header).
+    (you may need a USB extension cable)
 
     |UART Converter | RTE J2 Header|
     |:-------------:|:------------:|
diff --git a/docs/transparent-validation/rte/v1.1.0/serial-port-connection-guide.md b/docs/transparent-validation/rte/v1.1.0/serial-port-connection-guide.md
index c649227348..aef601f611 100644
--- a/docs/transparent-validation/rte/v1.1.0/serial-port-connection-guide.md
+++ b/docs/transparent-validation/rte/v1.1.0/serial-port-connection-guide.md
@@ -18,7 +18,7 @@ another device.
 ## Setting serial connection
 
 1. Put the two jumpers on
-    [RTE J16 Header](../specification/#uart-output-select-header):
+    [RTE J16 Header](./specification.md#uart-output-select-header):
 
     1. For the RS232 port, they join COM and RS232 rows both on RX and TX
         columns.
diff --git a/docs/transparent-validation/rte/v1.1.0/specification.md b/docs/transparent-validation/rte/v1.1.0/specification.md
index 4b091f31bb..c0310956d0 100644
--- a/docs/transparent-validation/rte/v1.1.0/specification.md
+++ b/docs/transparent-validation/rte/v1.1.0/specification.md
@@ -1,6 +1,6 @@
 # RTE elements
 
-![](../../../images/rte-v1.1.0-interface-desc.jpg)
+![img](../../../images/rte-v1.1.0-interface-desc.png)
 
 * **UART0 header** - 1x3 Orange Pi Zero system debug output and console
   (pins: `RX`, `TX`, `GND`).
@@ -44,7 +44,7 @@
 
 ### RteCtrl: Web interface
 
-![](../../../images/rte-rest-api-interface.jpg)
+![](../../../images/rte-rest-api-interface.png)
 
 **RteCtrl** is a REST API controller used for RTE board. It comes with meta-rte
 operating system and starts automatically on port `8000` without the necessity
diff --git a/docs/transparent-validation/sd-wire/getting-started.md b/docs/transparent-validation/sd-wire/getting-started.md
index 39a1fa59a7..f7b9cb16cc 100644
--- a/docs/transparent-validation/sd-wire/getting-started.md
+++ b/docs/transparent-validation/sd-wire/getting-started.md
@@ -14,5 +14,5 @@ adapter][shop1], like in the [muxPi product][shop2].
 
 ![](./../../images/SD-Wire.jpg)
 
-[shop1]: https://3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/muxsd-adapter/
-[shop2]: https://3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/muxpi/
+[shop1]: https://shop.3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/muxsd-adapter/
+[shop2]: https://shop.3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/muxpi/
diff --git a/docs/transparent-validation/sd-wire/specification.md b/docs/transparent-validation/sd-wire/specification.md
index c5a3c22783..40d44460a8 100644
--- a/docs/transparent-validation/sd-wire/specification.md
+++ b/docs/transparent-validation/sd-wire/specification.md
@@ -20,14 +20,14 @@ LED positions are showed in the image below.
 
 ![](./../../images/SD-wire_leds.jpg)
 
-<center>Source: [wiki.tizen.org](https://wiki.tizen.org/images/thumb/3/3f/SDWire-leds.jpg/300px-SDWire-leds.jpg)</center>
+<center>Source: [wiki.tizen.org](https://wiki.tizen.org/File:SDWire-leds.png)</center>
 
 ## PCB elements and scheme
 
-![](./../../images/SD-wire_PCB_elements_1.jpg)
+![](./../../images/SD-wire_PCB_elements_1.png)
 
-![](./../../images/SD-wire_PCB_elements_2.jpg)
+![](./../../images/SD-wire_PCB_elements_2.png)
 
-![](./../../images/SD-wire_scheme-1.jpg)
+![](./../../images/SD-wire_scheme-1.png)
 
 <center>Source: [wiki.tizen.org](https://wiki.tizen.org/images/c/cb/SDWire-v1.4-sch.pdf)</center>
diff --git a/docs/transparent-validation/sd-wire/usage-validation.md b/docs/transparent-validation/sd-wire/usage-validation.md
index 3e60fb6acb..27802d255e 100644
--- a/docs/transparent-validation/sd-wire/usage-validation.md
+++ b/docs/transparent-validation/sd-wire/usage-validation.md
@@ -281,6 +281,6 @@ References & Projects:
 * [SD Wire & 3d Printer Usage](https://github.com/arekm/OctoPrint-Sdwire)
 
 [tizen]: https://git.tizen.org/cgit/tools/testlab/sd-mux/
-[shop1]: https://3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/rte/
+[shop1]: https://shop.3mdeb.com/shop/open-source-hardware/open-source-hardware-3mdeb/rte/
 [balena]: https://www.balena.io/etcher/
 [rpios]: https://downloads.raspberrypi.org/raspios_armhf/images/raspios_armhf-2021-05-28/2021-05-07-raspios-buster-armhf.zip
diff --git a/docs/unified-test-documentation/dasharo-compatibility/100-coreboot-base-port.md b/docs/unified-test-documentation/dasharo-compatibility/100-coreboot-base-port.md
index df2674f05f..8ac6f65945 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/100-coreboot-base-port.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/100-coreboot-base-port.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Connect to the UART debug interface and open a serial console.
 
 ## CBP001.001 Boot into coreboot stage bootblock
diff --git a/docs/unified-test-documentation/dasharo-compatibility/301-memory-hcl.md b/docs/unified-test-documentation/dasharo-compatibility/301-memory-hcl.md
index cd0543e351..a655e36e61 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/301-memory-hcl.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/301-memory-hcl.md
@@ -16,11 +16,11 @@ module combinations specified in the HCL.
 
 1. Prepare the memory modules specified in the HCL.
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/303-custom-boot-menu-key.md b/docs/unified-test-documentation/dasharo-compatibility/303-custom-boot-menu-key.md
index a7df2c16af..f648610446 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/303-custom-boot-menu-key.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/303-custom-boot-menu-key.md
@@ -14,7 +14,7 @@ hotkey (if it exists).
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -39,7 +39,7 @@ hotkey.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/304-custom-logo.md b/docs/unified-test-documentation/dasharo-compatibility/304-custom-logo.md
index 49fcd0e7db..9878ab35f3 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/304-custom-logo.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/304-custom-logo.md
@@ -14,7 +14,7 @@ This test aims to verify that the DUT is configured to display the specified
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/306-usb-hid-and-msc-support.md b/docs/unified-test-documentation/dasharo-compatibility/306-usb-hid-and-msc-support.md
index fa75490dc0..dac8ba04b9 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/306-usb-hid-and-msc-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/306-usb-hid-and-msc-support.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## USB001.001 USB devices detection (firmware)
 
@@ -27,9 +27,9 @@ correctly by the firmware and all basic keys work according to their labels.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Connect the flash drive using the USB port.
 
 **Test steps**
@@ -142,7 +142,7 @@ by the firmware and all basic keys work according to their labels.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Connect the external USB keyboard using the USB port.
 
 **Test steps**
diff --git a/docs/unified-test-documentation/dasharo-compatibility/307-freebsd-support.md b/docs/unified-test-documentation/dasharo-compatibility/307-freebsd-support.md
index ef73d9e37e..8d4a3096dd 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/307-freebsd-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/307-freebsd-support.md
@@ -5,9 +5,9 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 
 ## BSD001.001 FreeBSD installation and boot
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/308-debian-stable-and-ubuntu-lts-support.md b/docs/unified-test-documentation/dasharo-compatibility/308-debian-stable-and-ubuntu-lts-support.md
index 2dc588a625..4057b3b133 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/308-debian-stable-and-ubuntu-lts-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/308-debian-stable-and-ubuntu-lts-support.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## LBT001.001 Debian Stable installation on USB storage
 
@@ -26,7 +26,7 @@ on USB storage attached to the DUT.
 
 **Test steps**
 
-1. According to the [Documentation](../../generic-test-setup#os-installer)
+1. According to the [Documentation](../generic-test-setup.md#os-installer)
     perform the OS installation process. As disk choose the USB stick.
 
 **Expected result**
@@ -81,7 +81,7 @@ installed on USB storage attached to the DUT.
 
 **Test steps**
 
-1. According to the [Documentation](../../generic-test-setup#os-installer)
+1. According to the [Documentation](../generic-test-setup.md#os-installer)
     perform the OS installation process. As disk choose the USB stick.
 
 **Expected result**
@@ -136,7 +136,7 @@ on the hard disk on the DUT.
 
 **Test steps**
 
-1. According to the [Documentation](../../generic-test-setup#os-installer)
+1. According to the [Documentation](../generic-test-setup.md#os-installer)
     perform the OS installation process. As disk choose the mounted in the
     DUT Hard Disk.
 
@@ -192,7 +192,7 @@ installed on the hard disk on the DUT.
 
 **Test steps**
 
-1. According to the [Documentation](../../generic-test-setup#os-installer)
+1. According to the [Documentation](../generic-test-setup.md#os-installer)
     perform the OS installation process. As disk choose the mounted in the
     DUT Hard Disk.
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/309-qubesos-support.md b/docs/unified-test-documentation/dasharo-compatibility/309-qubesos-support.md
index 5a46d4b7be..a22c6eca11 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/309-qubesos-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/309-qubesos-support.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## QBS001.001 QubesOS installation
 
@@ -25,7 +25,7 @@ This test aims to verify that QubesOS Stable distribution could be installed.
 
 **Test steps**
 
-1. According to the [Documentation](../../generic-test-setup#os-installer)
+1. According to the [Documentation](../generic-test-setup.md#os-installer)
     perform the OS installation process.
 
 **Expected result**
diff --git a/docs/unified-test-documentation/dasharo-compatibility/30A-custom-network-boot-entries.md b/docs/unified-test-documentation/dasharo-compatibility/30A-custom-network-boot-entries.md
index cbf383d90a..958a13d7b4 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/30A-custom-network-boot-entries.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/30A-custom-network-boot-entries.md
@@ -14,7 +14,7 @@ once in the boot option list.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/30L-memtest-payload-support.md b/docs/unified-test-documentation/dasharo-compatibility/30L-memtest-payload-support.md
index 2614f30344..62e193cef2 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/30L-memtest-payload-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/30L-memtest-payload-support.md
@@ -14,7 +14,7 @@ This test aims to verify that the Memtest entry is available in DUT boot
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -40,7 +40,7 @@ This test aims to verify that the DUT enters the Memtestboot option.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -67,7 +67,7 @@ This test aims to verify that the Memtest starts does not hang under DUT.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -95,7 +95,7 @@ This test aims to verify that DUT refreshes Memtest properly.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -123,7 +123,7 @@ This test aims to verify that DUT refreshes Memtest properly.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -149,7 +149,7 @@ This test aims to verify that DUT completes Memtest.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/30M-uefi-compatible-interface.md b/docs/unified-test-documentation/dasharo-compatibility/30M-uefi-compatible-interface.md
index de148f8ea7..140974f2b4 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/30M-uefi-compatible-interface.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/30M-uefi-compatible-interface.md
@@ -15,9 +15,9 @@ UEFI-aware Operating System.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 
 **Test steps**
 
@@ -51,9 +51,9 @@ UEFI-aware Operating System.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/30P-uefi-shell.md b/docs/unified-test-documentation/dasharo-compatibility/30P-uefi-shell.md
index 40c19afd0c..3db1a4ba66 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/30P-uefi-shell.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/30P-uefi-shell.md
@@ -14,7 +14,7 @@ UEFI Shell application.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: Firmware](../../generic-test-setup#firmware).
+   [Generic test setup: Firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/310-fedora-support.md b/docs/unified-test-documentation/dasharo-compatibility/310-fedora-support.md
index 90ef3f62fb..a102a444f9 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/310-fedora-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/310-fedora-support.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## FED001.001 Fedora installation
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/312-nvme-support.md b/docs/unified-test-documentation/dasharo-compatibility/312-nvme-support.md
index 0f7c64ca77..be393e2f6d 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/312-nvme-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/312-nvme-support.md
@@ -14,7 +14,7 @@ detect NVMe disk in the M.2 slot.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -42,10 +42,10 @@ the M.2 slot.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Insert a NVMe disk into the M.2 slot on the DUT.
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 
 **Test steps**
 
@@ -83,10 +83,10 @@ M.2 slot.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Insert a NVMe disk into the M.2 slot on the DUT.
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/315-network-boot.md b/docs/unified-test-documentation/dasharo-compatibility/315-network-boot.md
index e01b2a462d..84a1808f6b 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/315-network-boot.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/315-network-boot.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. The DUT should be connected to the Internet by using an Ethernet cable.
 
 ## PXE001.001 Dasharo Network Boot is bootable
@@ -118,7 +118,7 @@ This test aims to verify that the `Dasharo Tools Suite` option in
 1. Proceed with the
     [Test cases common documentation](#test-cases-common-documentation) section.
 1. Proceed with the
-    [Requirements for DTS](../../../dasharo-tools-suite/documentation#running).
+    [Requirements for DTS](https://docs.dasharo.com/dasharo-tools-suite/documentation#running).
 
 **Test steps**
 
@@ -214,7 +214,7 @@ server.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/315b-netboot-utilities.md b/docs/unified-test-documentation/dasharo-compatibility/315b-netboot-utilities.md
index 3c417ceba8..8fb97266ea 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/315b-netboot-utilities.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/315b-netboot-utilities.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## NBT001.001 Netboot is available
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/316-sdcard-reader.md b/docs/unified-test-documentation/dasharo-compatibility/316-sdcard-reader.md
index 4376dba8c0..9a63f712af 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/316-sdcard-reader.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/316-sdcard-reader.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. Insert an SD card into the SD Card reader.
 
 ## SDC001.001 SD Card reader detection (Ubuntu 22.04)
diff --git a/docs/unified-test-documentation/dasharo-compatibility/317-usb-camera.md b/docs/unified-test-documentation/dasharo-compatibility/317-usb-camera.md
index 0d0723eea3..443fe61e69 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/317-usb-camera.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/317-usb-camera.md
@@ -15,13 +15,13 @@ correctly and can be accessed from the operating system
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. Install ffprobe: `sudo apt install ffmpeg`.
 
 **Test steps**
@@ -67,13 +67,13 @@ correctly and can be accessed from the operating system
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/318-m2-wifi-bluetooth.md b/docs/unified-test-documentation/dasharo-compatibility/318-m2-wifi-bluetooth.md
index 3fb0efab44..ba4dcabda1 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/318-m2-wifi-bluetooth.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/318-m2-wifi-bluetooth.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## WLE001.001 Wireless card detection (Ubuntu 22.04)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/319-nvidia-graphics.md b/docs/unified-test-documentation/dasharo-compatibility/319-nvidia-graphics.md
index f477068098..4f8698daf2 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/319-nvidia-graphics.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/319-nvidia-graphics.md
@@ -6,13 +6,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## NVI001.001 NVIDIA Graphics detect (Ubuntu 22.04)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31A-windows-booting.md b/docs/unified-test-documentation/dasharo-compatibility/31A-windows-booting.md
index 8ef3377675..b06d456ad4 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31A-windows-booting.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31A-windows-booting.md
@@ -5,9 +5,9 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: Firmware](../../generic-test-setup#firmware).
+   [Generic test setup: Firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 
 ## WBT001.001 Windows 11 installation and boot
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31E-display-ports-and-lcd.md b/docs/unified-test-documentation/dasharo-compatibility/31E-display-ports-and-lcd.md
index bc939e412f..9add7e96f0 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31E-display-ports-and-lcd.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31E-display-ports-and-lcd.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## DSP001.001 Internal LCD in firmware
 
@@ -27,7 +27,7 @@ during firmware execution phase.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -167,7 +167,7 @@ during firmware execution phase.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 2. Connect an HDMI cable to the DUT and a display.
 
 **Test steps**
@@ -254,7 +254,7 @@ display during firmware execution phase.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 2. Connect a Display Port cable to the DUT and a display.
 
 **Test steps**
@@ -340,7 +340,7 @@ execution phase.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 2. Connect a video input connector to the VGA and a display.
 
 **Test steps**
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31F-audio-subsystem.md b/docs/unified-test-documentation/dasharo-compatibility/31F-audio-subsystem.md
index e2ff54831d..665579c6a6 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31F-audio-subsystem.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31F-audio-subsystem.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## AUD001.001 Audio subsystem detection (Ubuntu 22.04)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31G-ec-and-superio.md b/docs/unified-test-documentation/dasharo-compatibility/31G-ec-and-superio.md
index 7e7324e76c..c2841960e9 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31G-ec-and-superio.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31G-ec-and-superio.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## ECR001.001 Battery monitoring - charge level in OS (Ubuntu 22.04)
 
@@ -224,7 +224,7 @@ and all basic keys work according to their labels.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware)
+   [Generic test setup: firmware](../generic-test-setup.md#firmware)
 
 **Test steps**
 
@@ -1574,7 +1574,7 @@ illuminates in firmware.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware)
+   [Generic test setup: firmware](../generic-test-setup.md#firmware)
 
 **Test steps**
 
@@ -1669,7 +1669,7 @@ illuminates in firmware.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware)
+   [Generic test setup: firmware](../generic-test-setup.md#firmware)
 
 **Test steps**
 
@@ -1761,7 +1761,7 @@ illuminates in firmware.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware)
+   [Generic test setup: firmware](../generic-test-setup.md#firmware)
 
 **Test steps**
 
@@ -1855,7 +1855,7 @@ illuminates in firmware.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware)
+   [Generic test setup: firmware](../generic-test-setup.md#firmware)
 
 **Test steps**
 
@@ -2067,7 +2067,7 @@ and all basic keys work according to their labels.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware)
+   [Generic test setup: firmware](../generic-test-setup.md#firmware)
 2. Connect PS/2 keyboard to the violet PS/2 port on the board or the PS/2
    splitter (if the board has a unified, black PS/2 connector)
 
@@ -2230,7 +2230,7 @@ and the menu can be traversed with serial console.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware)
+   [Generic test setup: firmware](../generic-test-setup.md#firmware)
 2. Connect DB9 null modem cable to RS232/USB adapter and the onboard serial
    port connector.
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31H-usb-type-c.md b/docs/unified-test-documentation/dasharo-compatibility/31H-usb-type-c.md
index 4ffa5d3645..21927b87a9 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31H-usb-type-c.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31H-usb-type-c.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## UTC001.001 USB Type-A charging capability
 
@@ -544,7 +544,7 @@ re-done several times to specify the platform and connection stability.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. The `USB-C docking station` connected to the USB-C port.
 
 **Test steps**
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31I-nvme-switching.md b/docs/unified-test-documentation/dasharo-compatibility/31I-nvme-switching.md
index 3983f4b9d8..3acba275be 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31I-nvme-switching.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31I-nvme-switching.md
@@ -15,10 +15,10 @@ via the Operating System slot.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Insert an NVMe disk into the M.2 slot on the DUT.
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31J-sleep-mode.md b/docs/unified-test-documentation/dasharo-compatibility/31J-sleep-mode.md
index aba28c9880..2bf4f39d21 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31J-sleep-mode.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31J-sleep-mode.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## SLM001.001 Sleep mode - battery monitoring (Ubuntu 22.04)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31K-minipcie-verification.md b/docs/unified-test-documentation/dasharo-compatibility/31K-minipcie-verification.md
index 157dede333..54e1d4c767 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31K-minipcie-verification.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31K-minipcie-verification.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## MWL001.001 Wireless card detection (Ubuntu 22.04)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31L-smbios.md b/docs/unified-test-documentation/dasharo-compatibility/31L-smbios.md
index c13e33c138..a49fc56613 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31L-smbios.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31L-smbios.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. Install the `dmidecode` package: `sudo apt-get install dmidecode`.
 
 ## DMI001.001 Verify the serial number
@@ -20,7 +20,7 @@
 
 This test aims to verify that the serial number field is filled in correctly
 according to the
-[Dasharo SMBIOS guidelines](../../../dev-proc/smbios-rules/).
+[Dasharo SMBIOS guidelines](https://docs.dasharo.com/dev-proc/smbios-rules/).
 
 **Test configuration data**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31M-emmc-support.md b/docs/unified-test-documentation/dasharo-compatibility/31M-emmc-support.md
index aedfb9d57f..04c88f4fe6 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31M-emmc-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31M-emmc-support.md
@@ -14,9 +14,9 @@ This test aims to verify detection of the eMMC driver via the Operating System.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 2. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31M-platform-suspend-and-resume.md b/docs/unified-test-documentation/dasharo-compatibility/31M-platform-suspend-and-resume.md
index 5b52bde4a8..8b5f9ad415 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31M-platform-suspend-and-resume.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31M-platform-suspend-and-resume.md
@@ -5,11 +5,11 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 
 ## SUSP001.001 Platform suspend and resume (Ubuntu 22.04, wakeup flag)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31N-usb-boot.md b/docs/unified-test-documentation/dasharo-compatibility/31N-usb-boot.md
index 4d52d8d422..d33c0e8ba8 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31N-usb-boot.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31N-usb-boot.md
@@ -17,7 +17,7 @@ to specify the platform and connection stability.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -51,7 +51,7 @@ the platform and connection stability.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -84,7 +84,7 @@ platform and connection stability.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31O-usb-detect.md b/docs/unified-test-documentation/dasharo-compatibility/31O-usb-detect.md
index 4ae29305db..1583f76a1e 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31O-usb-detect.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31O-usb-detect.md
@@ -17,7 +17,7 @@ connection stability.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -48,7 +48,7 @@ may be re-done several times to specify the platform and connection stability.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -78,7 +78,7 @@ several times to specify the platform and connection stability.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31P-flash-write-protection.md b/docs/unified-test-documentation/dasharo-compatibility/31P-flash-write-protection.md
index c367f06cfb..562d44aabb 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31P-flash-write-protection.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31P-flash-write-protection.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Make yourself familiar with
-    [SPI hardware write protection](../../../variants/asus_kgpe_d16/spi-wp/).
+    [SPI hardware write protection](https://docs.dasharo.com/variants/asus_kgpe_d16/spi-wp/).
 
 ## HWP001.001 Hardware flash write protection support
 
@@ -106,9 +106,9 @@ hardware write protection on the DUT.
 
 **Test steps**
 
-1. Based on [the documentation](../../../variants/asus_kgpe_d16/spi-wp/)
+1. Based on [the documentation](https://docs.dasharo.com/variants/asus_kgpe_d16/spi-wp/)
     erase current write protection.
-1. Based on [the documentation](../../../variants/asus_kgpe_d16/spi-wp/)
+1. Based on [the documentation](https://docs.dasharo.com/variants/asus_kgpe_d16/spi-wp/)
     set write protection for a specific range.
 1. Execute the following command in the terminal to check the status and the
     range of write protection:
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31R-pcie-ports.md b/docs/unified-test-documentation/dasharo-compatibility/31R-pcie-ports.md
index 90603e97b7..01d25788d1 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31R-pcie-ports.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31R-pcie-ports.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 2. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 3. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 4. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## PEX001.001 PCI Express card detection (Ubuntu 22.04)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31S-sata-led-and-pc-speaker-error-indication.md b/docs/unified-test-documentation/dasharo-compatibility/31S-sata-led-and-pc-speaker-error-indication.md
index 61415df838..a41db50611 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31S-sata-led-and-pc-speaker-error-indication.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31S-sata-led-and-pc-speaker-error-indication.md
@@ -17,7 +17,7 @@ firmware errors.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31T-cpu-status.md b/docs/unified-test-documentation/dasharo-compatibility/31T-cpu-status.md
index 1a0a7d9855..86d6c52f2a 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31T-cpu-status.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31T-cpu-status.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## CPU001.001 CPU works (Ubuntu 22.04)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31U-heads-bootloader-support.md b/docs/unified-test-documentation/dasharo-compatibility/31U-heads-bootloader-support.md
index 9c1aa877aa..c29a091014 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31U-heads-bootloader-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31U-heads-bootloader-support.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## HDS001.001 Heads installation
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31V-petitboot-payload-support.md b/docs/unified-test-documentation/dasharo-compatibility/31V-petitboot-payload-support.md
index 3bf09cdc2c..ee77b3f4c6 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31V-petitboot-payload-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31V-petitboot-payload-support.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## PBT001.001 Boot into Petitboot
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/31W-device-tree.md b/docs/unified-test-documentation/dasharo-compatibility/31W-device-tree.md
index 949a75d160..eae734ae86 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/31W-device-tree.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/31W-device-tree.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## DVT001.001 Node with coreboot exists
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/320-fwupd-firmware-update.md b/docs/unified-test-documentation/dasharo-compatibility/320-fwupd-firmware-update.md
index 974515ef0b..222c7135ea 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/320-fwupd-firmware-update.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/320-fwupd-firmware-update.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. Install the `dmidecode` package: `sudo apt install dmidecode`.
 1. Make yourself familiar with
     [Updating firmware using fwupd](/unified/novacustom/fwupd-usage)
diff --git a/docs/unified-test-documentation/dasharo-compatibility/325-custom-boot-order.md b/docs/unified-test-documentation/dasharo-compatibility/325-custom-boot-order.md
index 11949a18fc..fbbb6ef505 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/325-custom-boot-order.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/325-custom-boot-order.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## CBO001.001 Custom boot order (SeaBIOS)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/326-dasharo-tools-suite.md b/docs/unified-test-documentation/dasharo-compatibility/326-dasharo-tools-suite.md
index 0680e6c9d1..104a1b82cf 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/326-dasharo-tools-suite.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/326-dasharo-tools-suite.md
@@ -5,12 +5,12 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Wired network connection.
 1. Disable Secure Boot.
-1. Prepare the [bootable USB stick](../../../dasharo-tools-suite/documentation#bootable-usb-stick)
+1. Prepare the [bootable USB stick](https://docs.dasharo.com/dasharo-tools-suite/documentation#bootable-usb-stick)
 1. Make yourself familiar with
-    [Dasharo Tools Suite](../../../dasharo-tools-suite/overview).
+    [Dasharo Tools Suite](https://docs.dasharo.com/dasharo-tools-suite/overview).
 
 ## DTS001.001 Booting DTS from USB works correctly
 
@@ -79,7 +79,7 @@ Example summary output:
 
 ```bash
 SUMMARY
-=======
+========
 
  > All Curl calls exited without errors
  > Attempt to send completed > <report_name>.tar.gz
@@ -325,13 +325,13 @@ firmware by using the built-in script in DTS.
 1. Select the USB stick with DTS using the arrow keys and press `Enter`.
 1. Wait for `Enter an option:`.
 1. Proceed with
-    [Dasharo EC Transition](../../../dasharo-tools-suite/documentation#ec-transition).
+    [Dasharo EC Transition](https://docs.dasharo.com/dasharo-tools-suite/documentation#ec-transition).
 
 **Expected result**
 
 1. After the flashing procedure itself, the DUT should be able to boot.
 1. The EC firmware version, after checking the method described in the
-    above-mentioned [documentation](../../../dasharo-tools-suite/documentation#ec-transition),
+    above-mentioned [documentation](https://docs.dasharo.com/dasharo-tools-suite/documentation#ec-transition),
     should correspond to the latest version.
 
 ## DTS009.001 Update device EC firmware by using DTS works correctly
@@ -359,11 +359,11 @@ firmware by using system76_ectool in DTS.
 1. Wait for `Enter an option:`.
 1. Type in `9` and press `Enter`.
 1. Proceed with
-    [Dasharo EC Update](../../../dasharo-tools-suite/documentation#ec-update).
+    [Dasharo EC Update](https://docs.dasharo.com/dasharo-tools-suite/documentation#ec-update).
 
 **Expected result**
 
 1. After the updating firmware procedure itself, the DUT should be able to boot.
 1. The EC firmware version, after checking the method described in the
-    above-mentioned [documentation](../../../dasharo-tools-suite/documentation#ec-update),
+    above-mentioned [documentation](https://docs.dasharo.com/dasharo-tools-suite/documentation#ec-update),
     should correspond to the binary version used.
diff --git a/docs/unified-test-documentation/dasharo-compatibility/326b-firmware-building-locally.md b/docs/unified-test-documentation/dasharo-compatibility/326b-firmware-building-locally.md
index 3368b9e832..d053f5afa8 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/326b-firmware-building-locally.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/326b-firmware-building-locally.md
@@ -5,11 +5,11 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Make yourself familiar with Building manual procedure dedicated for
     the relevant platform:
     * [NovaCustom laptops](/unified/novacustom/building-manual)
diff --git a/docs/unified-test-documentation/dasharo-compatibility/327-embedded_controller_flashing.md b/docs/unified-test-documentation/dasharo-compatibility/327-embedded_controller_flashing.md
index b977b9474d..0fb7ae150e 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/327-embedded_controller_flashing.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/327-embedded_controller_flashing.md
@@ -14,7 +14,7 @@ EC firmware externally using Arduino.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Make yourself familiar with
     [EC recovery documentation](/unified/novacustom/recovery/#ec-firmware-recovery).
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/328-logo-customization-functionality.md b/docs/unified-test-documentation/dasharo-compatibility/328-logo-customization-functionality.md
index d76435901e..492382bfef 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/328-logo-customization-functionality.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/328-logo-customization-functionality.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Get familiar with
    [Logo customization procedure](/guides/logo-customization)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/341-pfSense-support.md b/docs/unified-test-documentation/dasharo-compatibility/341-pfSense-support.md
index d58f77a7e7..b047997238 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/341-pfSense-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/341-pfSense-support.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## PFS001.001 pfSense stable (serial output) installation on Hard Disk
 
@@ -26,7 +26,7 @@ on the hard disk on the DUT.
 
 **Test steps**
 
-1. According to the [Documentation](../../generic-test-setup#os-installer)
+1. According to the [Documentation](../generic-test-setup.md#os-installer)
    perform the OS installation process.
 
 **Expected result**
@@ -81,7 +81,7 @@ the hard disk on the DUT.
 
 **Test steps**
 
-1. According to the [Documentation](../../generic-test-setup#os-installer)
+1. According to the [Documentation](../generic-test-setup.md#os-installer)
     perform the OS installation process.
 
 **Expected result**
diff --git a/docs/unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md b/docs/unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md
index 53b200120b..e0dd69d51e 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/342-OPNsense-support.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## OPN001.001 OPNsense stable (serial output) installation on Hard Disk
 
@@ -26,7 +26,7 @@ on the hard disk on the DUT.
 
 **Test steps**
 
-1. According to the [Documentation](../../generic-test-setup#os-installer)
+1. According to the [Documentation](../generic-test-setup.md#os-installer)
    perform the OS installation process.
 
 **Expected result**
@@ -81,7 +81,7 @@ the hard disk on the DUT.
 
 **Test steps**
 
-1. According to the [Documentation](../../generic-test-setup#os-installer)
+1. According to the [Documentation](../generic-test-setup.md#os-installer)
    perform the OS installation process.
 
 **Expected result**
diff --git a/docs/unified-test-documentation/dasharo-compatibility/343-super-I-O-initialization-on-QubesOS.md b/docs/unified-test-documentation/dasharo-compatibility/343-super-I-O-initialization-on-QubesOS.md
index 6b52e649a6..f1f7dd8266 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/343-super-I-O-initialization-on-QubesOS.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/343-super-I-O-initialization-on-QubesOS.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## PPS001.001 PS/2 keyboard detection
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/344-power-operations.md b/docs/unified-test-documentation/dasharo-compatibility/344-power-operations.md
index 7c08758f10..737bca337a 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/344-power-operations.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/344-power-operations.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## DPC001.001 Reset button (QubesOS)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/345-display-resolution.md b/docs/unified-test-documentation/dasharo-compatibility/345-display-resolution.md
index 00066e95ab..237bd100cf 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/345-display-resolution.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/345-display-resolution.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## DSR001.001 Changing the display resolution
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/346-SATA-hotplug-detection.md b/docs/unified-test-documentation/dasharo-compatibility/346-SATA-hotplug-detection.md
index 1dcd5a1845..61caf68d9e 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/346-SATA-hotplug-detection.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/346-SATA-hotplug-detection.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## SHT001.001 SATA hot plug (firmware)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/347-sign-of-life.md b/docs/unified-test-documentation/dasharo-compatibility/347-sign-of-life.md
index d610cd390c..dc56a8639f 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/347-sign-of-life.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/347-sign-of-life.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## SOL001.001 SOL string shows Dasharo firmware and EC version
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/348-proxmox-support.md b/docs/unified-test-documentation/dasharo-compatibility/348-proxmox-support.md
index 0be1772b95..a7d07d7c6a 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/348-proxmox-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/348-proxmox-support.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## PVE001.001 Proxmox Virtual Environment stable installation on Hard Disk
 
@@ -26,7 +26,7 @@ disk on the DUT.
 
 **Test steps**
 
-1. According to the [Documentation](../../generic-test-setup#os-installer)
+1. According to the [Documentation](../generic-test-setup.md#os-installer)
    perform the OS installation process.
 
 **Expected result**
diff --git a/docs/unified-test-documentation/dasharo-compatibility/349-ubuntu-server-support.md b/docs/unified-test-documentation/dasharo-compatibility/349-ubuntu-server-support.md
index a15ba1203e..d58c072be8 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/349-ubuntu-server-support.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/349-ubuntu-server-support.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## USS001.001 Ubuntu Server stable installation on Hard Disk
 
@@ -26,7 +26,7 @@ hard disk on the DUT.
 
 **Test steps**
 
-1. According to the [Documentation](../../generic-test-setup#os-installer)
+1. According to the [Documentation](../generic-test-setup.md#os-installer)
    perform the OS installation process.
 
 **Expected result**
diff --git a/docs/unified-test-documentation/dasharo-compatibility/357-bios-menu-function-keys.md b/docs/unified-test-documentation/dasharo-compatibility/357-bios-menu-function-keys.md
index 551df2d9e5..273dea4b1d 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/357-bios-menu-function-keys.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/357-bios-menu-function-keys.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## BMF001.001 Reset to Defaults option
 
@@ -47,4 +47,4 @@ all Dasharo System Features settings.
    System Features.
 1. After using the `F9` key, all `Dasharo System Features` options should be set
    to default. All options covered by this functionality can be found
-   [here](../../../../dasharo-menu-docs/dasharo-system-features/).
+   [here](https://docs.dasharo.com/dasharo-menu-docs/dasharo-system-features/).
diff --git a/docs/unified-test-documentation/dasharo-compatibility/358-suspend-mechanism-switching-S0ix-S3.md b/docs/unified-test-documentation/dasharo-compatibility/358-suspend-mechanism-switching-S0ix-S3.md
index 671801caba..4442dc7e02 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/358-suspend-mechanism-switching-S0ix-S3.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/358-suspend-mechanism-switching-S0ix-S3.md
@@ -5,11 +5,11 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 
 ## SMS001.001 Suspend to Idle (S0ix) check (Ubuntu 22.04)
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/S30-fan-speed.md b/docs/unified-test-documentation/dasharo-compatibility/S30-fan-speed.md
index 6fcd525c94..b4d3fd10b6 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/S30-fan-speed.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/S30-fan-speed.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## FAN001.001 CPU fan speed measure
 
diff --git a/docs/unified-test-documentation/dasharo-compatibility/S31-coreboot-fan-control.md b/docs/unified-test-documentation/dasharo-compatibility/S31-coreboot-fan-control.md
index 4895db357f..2a603b4996 100644
--- a/docs/unified-test-documentation/dasharo-compatibility/S31-coreboot-fan-control.md
+++ b/docs/unified-test-documentation/dasharo-compatibility/S31-coreboot-fan-control.md
@@ -14,13 +14,13 @@ available.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 **Test steps**
 
@@ -54,13 +54,13 @@ temperature.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-performance/400-coreboot-boot-measure.md b/docs/unified-test-documentation/dasharo-performance/400-coreboot-boot-measure.md
index c0d1a2aaca..6aa4062962 100644
--- a/docs/unified-test-documentation/dasharo-performance/400-coreboot-boot-measure.md
+++ b/docs/unified-test-documentation/dasharo-performance/400-coreboot-boot-measure.md
@@ -5,11 +5,11 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Download `cbmem` from <https://cloud.3mdeb.com/index.php/s/zTqkJQdNtJDo5Nd>
     to the DUT.
 
diff --git a/docs/unified-test-documentation/dasharo-performance/401-cpu-temperature.md b/docs/unified-test-documentation/dasharo-performance/401-cpu-temperature.md
index 986092021f..f53c2693fc 100644
--- a/docs/unified-test-documentation/dasharo-performance/401-cpu-temperature.md
+++ b/docs/unified-test-documentation/dasharo-performance/401-cpu-temperature.md
@@ -5,11 +5,11 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Install `lm-sensors` package: `sudo apt install lm-sensors`.
 
 ## CPT001.001 CPU temperature without load (Ubuntu 22.04)
diff --git a/docs/unified-test-documentation/dasharo-performance/402-cpu-frequency.md b/docs/unified-test-documentation/dasharo-performance/402-cpu-frequency.md
index 73a03477d1..87f93f0ccf 100644
--- a/docs/unified-test-documentation/dasharo-performance/402-cpu-frequency.md
+++ b/docs/unified-test-documentation/dasharo-performance/402-cpu-frequency.md
@@ -5,11 +5,11 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 
 ## CPF001.001 CPU not stuck on initial frequency (Ubuntu 22.04)
 
diff --git a/docs/unified-test-documentation/dasharo-performance/403-device-boot-measure.md b/docs/unified-test-documentation/dasharo-performance/403-device-boot-measure.md
index 73873d5c2f..2984ba6f8e 100644
--- a/docs/unified-test-documentation/dasharo-performance/403-device-boot-measure.md
+++ b/docs/unified-test-documentation/dasharo-performance/403-device-boot-measure.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## DBM001.001 Device boot measure after coldboot (Ubuntu 22.04)
 
diff --git a/docs/unified-test-documentation/dasharo-performance/404-platform-stability.md b/docs/unified-test-documentation/dasharo-performance/404-platform-stability.md
index f66d70586f..b2ca32c259 100644
--- a/docs/unified-test-documentation/dasharo-performance/404-platform-stability.md
+++ b/docs/unified-test-documentation/dasharo-performance/404-platform-stability.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## STB001.001 Verify if no reboot occurs in the firmware
 
diff --git a/docs/unified-test-documentation/dasharo-performance/405-fan-control-measure.md b/docs/unified-test-documentation/dasharo-performance/405-fan-control-measure.md
index 113f1ecc13..1a464d3f77 100644
--- a/docs/unified-test-documentation/dasharo-performance/405-fan-control-measure.md
+++ b/docs/unified-test-documentation/dasharo-performance/405-fan-control-measure.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. Check if package `lm-sensors` is installed and if not, use below command in
     the terminal to install:
 
diff --git a/docs/unified-test-documentation/dasharo-performance/406-custom-fan-curve.md b/docs/unified-test-documentation/dasharo-performance/406-custom-fan-curve.md
index 54d57e5be8..b7c5c4d9f1 100644
--- a/docs/unified-test-documentation/dasharo-performance/406-custom-fan-curve.md
+++ b/docs/unified-test-documentation/dasharo-performance/406-custom-fan-curve.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## CFC001.001 Custom fan curve silent profile measure (Ubuntu 22.04)
 
diff --git a/docs/unified-test-documentation/dasharo-performance/407-ubuntu-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/407-ubuntu-booting-performance-test.md
index 4ec66fea25..50f9ed6633 100644
--- a/docs/unified-test-documentation/dasharo-performance/407-ubuntu-booting-performance-test.md
+++ b/docs/unified-test-documentation/dasharo-performance/407-ubuntu-booting-performance-test.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## BUB001.001 Boot Ubuntu LTS from disk after cold-boot
 
diff --git a/docs/unified-test-documentation/dasharo-performance/408-debian-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/408-debian-booting-performance-test.md
index 238a2c3907..a0e55363cb 100644
--- a/docs/unified-test-documentation/dasharo-performance/408-debian-booting-performance-test.md
+++ b/docs/unified-test-documentation/dasharo-performance/408-debian-booting-performance-test.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## BDE001.001 Boot Debian LTS from disk after cold-boot
 
diff --git a/docs/unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md
index 0beb7aa2f3..507e61fe44 100644
--- a/docs/unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md
+++ b/docs/unified-test-documentation/dasharo-performance/409-freebsd-booting-performance-test.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## BFB001.001 Boot FreeBSD-RELEASE from disk after cold-boot
 
diff --git a/docs/unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md
index 007939e629..5c889f5713 100644
--- a/docs/unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md
+++ b/docs/unified-test-documentation/dasharo-performance/410-proxmox-booting-performance-test.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## BPM001.001 Boot Proxmox Virtual Environment from disk after cold-boot
 
diff --git a/docs/unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md
index 7c382005c6..3888796dc1 100644
--- a/docs/unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md
+++ b/docs/unified-test-documentation/dasharo-performance/411-ubuntu-server-booting-performance-test.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## BUS001.001 Boot Ubuntu Server LTS from disk after cold-boot
 
diff --git a/docs/unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md
index 2bbd0ed611..7c842e2d9c 100644
--- a/docs/unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md
+++ b/docs/unified-test-documentation/dasharo-performance/412-opnsense-serial-booting-performance-test.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## BOS001.001 Boot OPNsense (serial output) from disk after cold-boot
 
diff --git a/docs/unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md
index b49ab2d369..15659d4d7d 100644
--- a/docs/unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md
+++ b/docs/unified-test-documentation/dasharo-performance/413-opnsense-vga-booting-performance-test.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## BOV001.001 Boot OPNsense (VGA output) from disk after cold-boot
 
diff --git a/docs/unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md
index 5eaef5a419..15c5d193d2 100644
--- a/docs/unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md
+++ b/docs/unified-test-documentation/dasharo-performance/414-pfsense-serial-booting-performance-test.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## BPS001.001 Boot pfSense LTS CE (serial output) from disk after cold-boot
 
diff --git a/docs/unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md
index a1e37f7aa9..667f09c2ad 100644
--- a/docs/unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md
+++ b/docs/unified-test-documentation/dasharo-performance/415-pfsense-vga-booting-performance-test.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## BPV001.001 Boot pfSense LTS CE (VGA output) from disk after cold-boot
 
diff --git a/docs/unified-test-documentation/dasharo-performance/416-windows-booting-performance-test.md b/docs/unified-test-documentation/dasharo-performance/416-windows-booting-performance-test.md
index 489fe0d277..8549dde0f5 100644
--- a/docs/unified-test-documentation/dasharo-performance/416-windows-booting-performance-test.md
+++ b/docs/unified-test-documentation/dasharo-performance/416-windows-booting-performance-test.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## BWI001.001 Boot Windows 11 from disk after cold-boot
 
diff --git a/docs/unified-test-documentation/dasharo-security/200-tpm-support.md b/docs/unified-test-documentation/dasharo-security/200-tpm-support.md
index 6742362e4e..9e04718a49 100644
--- a/docs/unified-test-documentation/dasharo-security/200-tpm-support.md
+++ b/docs/unified-test-documentation/dasharo-security/200-tpm-support.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## TPM001.001 TPM Support (firmware)
 
diff --git a/docs/unified-test-documentation/dasharo-security/201-verified-boot.md b/docs/unified-test-documentation/dasharo-security/201-verified-boot.md
index 9ea324dfb6..4cacb0cbe9 100644
--- a/docs/unified-test-documentation/dasharo-security/201-verified-boot.md
+++ b/docs/unified-test-documentation/dasharo-security/201-verified-boot.md
@@ -5,11 +5,11 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 
 ## VBO001.001 Generating keys for Verified Boot
 
@@ -222,7 +222,7 @@ functional.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Disable Secure Boot.
 
 **Test steps**
@@ -294,7 +294,7 @@ proceed to boot from Slot A.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Disable Secure Boot.
 
 **Test steps**
diff --git a/docs/unified-test-documentation/dasharo-security/203-measured-boot.md b/docs/unified-test-documentation/dasharo-security/203-measured-boot.md
index c18d5b1f65..c61a9a252f 100644
--- a/docs/unified-test-documentation/dasharo-security/203-measured-boot.md
+++ b/docs/unified-test-documentation/dasharo-security/203-measured-boot.md
@@ -18,13 +18,13 @@ TPM.a.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. Download `cbmem` from the
     [cloud](https://cloud.3mdeb.com/index.php/s/zTqkJQdNtJDo5Nd) to the DUT.
 1. Disable Secure Boot.
diff --git a/docs/unified-test-documentation/dasharo-security/206-secure-boot.md b/docs/unified-test-documentation/dasharo-security/206-secure-boot.md
index 618667b3d7..697043f17c 100644
--- a/docs/unified-test-documentation/dasharo-security/206-secure-boot.md
+++ b/docs/unified-test-documentation/dasharo-security/206-secure-boot.md
@@ -15,7 +15,7 @@ flashing the platform with the Dasharo firmware is correct.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -46,13 +46,13 @@ the DUT reset, it is seen from the OS.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Secure Boot Configuration](../../../dasharo-menu-docs/device-manager/#secure-boot-configuration)
+   [Secure Boot Configuration](https://docs.dasharo.com/dasharo-menu-docs/device-manager/#secure-boot-configuration)
    to enable the `Attempt Secure Boot` option in the
    `Secure Boot Configuration` menu.
 
@@ -100,13 +100,13 @@ the DUT reset, it is seen from the OS.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Secure Boot Configuration](../../../dasharo-menu-docs/device-manager/#secure-boot-configuration)
+   [Secure Boot Configuration](https://docs.dasharo.com/dasharo-menu-docs/device-manager/#secure-boot-configuration)
    to enable the `Attempt Secure Boot` option in the
    `Secure Boot Configuration` menu.
 
@@ -155,7 +155,7 @@ key.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -220,7 +220,7 @@ This test verifies that Secure Boot blocks booting a file without a key.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -272,7 +272,7 @@ key.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -323,7 +323,7 @@ after flashing the platform with the Dasharo firmware.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -353,7 +353,7 @@ This test verifies that the `Reset Secure Boot Keys` option works correctly.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 **Test steps**
 
@@ -468,7 +468,7 @@ incorrect format.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Additional `USB storage` - at least 1GB - for keeping files for booting
 
 **Test steps**
diff --git a/docs/unified-test-documentation/dasharo-security/207-boot-guard-support.md b/docs/unified-test-documentation/dasharo-security/207-boot-guard-support.md
index cb43b4c6cc..fd3753741d 100644
--- a/docs/unified-test-documentation/dasharo-security/207-boot-guard-support.md
+++ b/docs/unified-test-documentation/dasharo-security/207-boot-guard-support.md
@@ -17,13 +17,13 @@ to verify that the implemented Boot Guard mechanism works correctly.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. Download `cbmem` from the
     [cloud](https://cloud.3mdeb.com/index.php/s/zTqkJQdNtJDo5Nd) to the DUT.
 
diff --git a/docs/unified-test-documentation/dasharo-security/20F-me-neuter.md b/docs/unified-test-documentation/dasharo-security/20F-me-neuter.md
index 0d89b782af..4d54db95b3 100644
--- a/docs/unified-test-documentation/dasharo-security/20F-me-neuter.md
+++ b/docs/unified-test-documentation/dasharo-security/20F-me-neuter.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## MNE001.001 Check Intel ME version (Ubuntu 22.04)
 
diff --git a/docs/unified-test-documentation/dasharo-security/20J-bios-lock-support.md b/docs/unified-test-documentation/dasharo-security/20J-bios-lock-support.md
index 68db659c4d..56228732f0 100644
--- a/docs/unified-test-documentation/dasharo-security/20J-bios-lock-support.md
+++ b/docs/unified-test-documentation/dasharo-security/20J-bios-lock-support.md
@@ -17,13 +17,13 @@ by using flashrom tool.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. Disable Secure Boot.
 
 **Test steps**
@@ -80,13 +80,13 @@ the BIOS region overwriting operation is available again.
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. Disable Secure Boot.
 1. Obtain any other binary (e.g. vendor firmware or older Dasharo firmware).
 
diff --git a/docs/unified-test-documentation/dasharo-security/20L-early-boot-dma-protection.md b/docs/unified-test-documentation/dasharo-security/20L-early-boot-dma-protection.md
index fb93815cc5..82a1a3c508 100644
--- a/docs/unified-test-documentation/dasharo-security/20L-early-boot-dma-protection.md
+++ b/docs/unified-test-documentation/dasharo-security/20L-early-boot-dma-protection.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. Disable Secure Boot.
 1. Download `cbmem` from <https://cloud.3mdeb.com/index.php/s/zTqkJQdNtJDo5Nd>
    to the DUT.
diff --git a/docs/unified-test-documentation/dasharo-security/20O-SMM-bios-write-protection.md b/docs/unified-test-documentation/dasharo-security/20O-SMM-bios-write-protection.md
index 5e74c7152d..f22abb21b0 100644
--- a/docs/unified-test-documentation/dasharo-security/20O-SMM-bios-write-protection.md
+++ b/docs/unified-test-documentation/dasharo-security/20O-SMM-bios-write-protection.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. Disable Secure Boot.
 
 ## SMM001.001 SMM BIOS write protection enabling (Ubuntu 22.04)
diff --git a/docs/unified-test-documentation/dasharo-security/20P-boot-menu.md b/docs/unified-test-documentation/dasharo-security/20P-boot-menu.md
index 9e53dce27c..3da76f47b7 100644
--- a/docs/unified-test-documentation/dasharo-security/20P-boot-menu.md
+++ b/docs/unified-test-documentation/dasharo-security/20P-boot-menu.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## BMA001.001 Boot menu enabling
 
diff --git a/docs/unified-test-documentation/dasharo-security/20R-uefi-setup-password.md b/docs/unified-test-documentation/dasharo-security/20R-uefi-setup-password.md
index b55a34c3d5..61d6750bd6 100644
--- a/docs/unified-test-documentation/dasharo-security/20R-uefi-setup-password.md
+++ b/docs/unified-test-documentation/dasharo-security/20R-uefi-setup-password.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## PSW001.001 Check Password Setup option availability and default state
 
diff --git a/docs/unified-test-documentation/dasharo-security/20S-usb-stack.md b/docs/unified-test-documentation/dasharo-security/20S-usb-stack.md
index 47f5fcb8fe..22b44ee94f 100644
--- a/docs/unified-test-documentation/dasharo-security/20S-usb-stack.md
+++ b/docs/unified-test-documentation/dasharo-security/20S-usb-stack.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup/#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 
 ## USS001.001 Enable USB stack (firmware)
 
diff --git a/docs/unified-test-documentation/dasharo-security/20T-network-boot.md b/docs/unified-test-documentation/dasharo-security/20T-network-boot.md
index 1d1261faa5..fcd3356979 100644
--- a/docs/unified-test-documentation/dasharo-security/20T-network-boot.md
+++ b/docs/unified-test-documentation/dasharo-security/20T-network-boot.md
@@ -5,7 +5,7 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. The DUT should be connected to the Internet by using an Ethernet cable.
 
 ## NBA001.001 Enable Network Boot (firmware)
diff --git a/docs/unified-test-documentation/dasharo-stability/01-net-controller-after-coldboot-warmboot-reboot-suspend.md b/docs/unified-test-documentation/dasharo-stability/01-net-controller-after-coldboot-warmboot-reboot-suspend.md
index b0fec1c6e8..d4358edf10 100644
--- a/docs/unified-test-documentation/dasharo-stability/01-net-controller-after-coldboot-warmboot-reboot-suspend.md
+++ b/docs/unified-test-documentation/dasharo-stability/01-net-controller-after-coldboot-warmboot-reboot-suspend.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-    [Generic test setup: firmware](../../generic-test-setup#firmware).
+    [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-    [Generic test setup: OS installer](../../generic-test-setup#os-installer).
+    [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-    [Generic test setup: OS installation](../../generic-test-setup#os-installation).
+    [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-    [Generic test setup: OS boot from disk](../../generic-test-setup#os-boot-from-disk).
+    [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. The `Thunderbolt docking station` connected to the Thunderbolt port.
 
 ## NET001.001 NET controller after coldboot (Ubuntu 22.04)
diff --git a/docs/unified-test-documentation/dasharo-stability/C01-usb-type-a-devices-detection.md b/docs/unified-test-documentation/dasharo-stability/C01-usb-type-a-devices-detection.md
index 28f6de2ba3..9f906e2264 100644
--- a/docs/unified-test-documentation/dasharo-stability/C01-usb-type-a-devices-detection.md
+++ b/docs/unified-test-documentation/dasharo-stability/C01-usb-type-a-devices-detection.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 1. Connect the `USB device` to the USB Type-A port.
 
 ## SUD0001.001 USB devices detection after cold boot (Ubuntu 22.04)
@@ -124,7 +124,7 @@ after performing a reboot. The test should be performed in multiple iterations.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware)
+   [Generic test setup: firmware](../generic-test-setup.md#firmware)
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-stability/C02-m2-wi-fi.md b/docs/unified-test-documentation/dasharo-stability/C02-m2-wi-fi.md
index e98141998e..2934e60411 100644
--- a/docs/unified-test-documentation/dasharo-stability/C02-m2-wi-fi.md
+++ b/docs/unified-test-documentation/dasharo-stability/C02-m2-wi-fi.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## SMW0001.001 Wi-fi connection after cold boot (Ubuntu 22.04)
 
@@ -195,7 +195,7 @@ after performing a reboot. The test should be performed in multiple iterations.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware)
+   [Generic test setup: firmware](../generic-test-setup.md#firmware)
 
 **Test steps**
 
diff --git a/docs/unified-test-documentation/dasharo-stability/C03-nvme-detection.md b/docs/unified-test-documentation/dasharo-stability/C03-nvme-detection.md
index 2e56a91df0..21b4516ba4 100644
--- a/docs/unified-test-documentation/dasharo-stability/C03-nvme-detection.md
+++ b/docs/unified-test-documentation/dasharo-stability/C03-nvme-detection.md
@@ -5,13 +5,13 @@
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup/#firmware).
+   [Generic test setup: firmware](../generic-test-setup.md#firmware).
 1. Proceed with the
-   [Generic test setup: OS installer](../../generic-test-setup/#os-installer).
+   [Generic test setup: OS installer](../generic-test-setup.md#os-installer).
 1. Proceed with the
-   [Generic test setup: OS installation](../../generic-test-setup/#os-installation).
+   [Generic test setup: OS installation](../generic-test-setup.md#os-installation).
 1. Proceed with the
-   [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
+   [Generic test setup: OS boot from disk](../generic-test-setup.md#os-boot-from-disk).
 
 ## SNV0001.001 NVMe detection after cold boot (Ubuntu 22.04)
 
@@ -123,7 +123,7 @@ performing a reboot. The test should be performed in multiple iterations.
 **Test setup**
 
 1. Proceed with the
-   [Generic test setup: firmware](../../generic-test-setup#firmware)
+   [Generic test setup: firmware](../generic-test-setup.md#firmware)
 
 **Test steps**
 
diff --git a/docs/unified/msi/faq.md b/docs/unified/msi/faq.md
index aa41134632..c5992ca2c2 100644
--- a/docs/unified/msi/faq.md
+++ b/docs/unified/msi/faq.md
@@ -32,7 +32,7 @@ the DDR4 WIFI platform. In turn, Dasharo working correctness on
 ## Can I safely try this on my board?
 
 If you are afraid of bricking the board and have no means of [recovering from
-failed installation](../recovery), we **do not recommend** trying it out until
+failed installation](recovery.md), we **do not recommend** trying it out until
 at least the v1.0.0 is released. Recovery process is not suitable for
 inexperienced users right now. We will be trying to make it easier, and if that
 happens, we may change our recommendation here.
@@ -41,9 +41,9 @@ happens, we may change our recommendation here.
 
 We give no warranty, although it is highly unlikely, provided that you use the
 supported board model and follow the [Initial
-Deployment](../initial-deployment). In the worst scenario, you might "brick" the
+Deployment](initial-deployment.md). In the worst scenario, you might "brick" the
 board, rendering it unbootable. It can be fixed by following the [recovery
-procedure](../recovery). In case of concerns, we invite you to buy the equipment
+procedure](recovery.md). In case of concerns, we invite you to buy the equipment
 directly in our [online
 store](https://3mdeb.com/?s=msi&post_type=product&dgwt_wcas=1) with a
 subscription service, under which we perform the Dasharo installation with the
@@ -54,7 +54,7 @@ latest release, and offer full support through invite-only Matrix channel.
 In such a case, you would get stuck with black screen on the display. There will
 be no beeping sounds from the buzzer as well. The only way to get some
 information on what's going on in that state is to use the [Serial
-header](../development/#hardware-connection) to read out error information.
+header](development.md#hardware-connection) to read out error information.
 
 ## What can be the reason of board "bricking"?
 
@@ -62,18 +62,18 @@ The most common reason would be the fact that you DDR memory modules are not
 initialized properly.
 
 The other reason might be improper or interrupted installation. Please make sure
-to follow the [Initial Deployment Manual](../initial-deployment) correctly.
+to follow the [Initial Deployment Manual](initial-deployment.md) correctly.
 
 ## How can I "unbrick" my board?
 
-Please follow the [recovery procedure](../recovery).
+Please follow the [recovery procedure](recovery.md).
 
 ## Which CPUs are supported?
 
 We can say the "supported" one is the one that have been tested during
 Validation Procedure or have been tested by the community.
 
-The list of all supported CPUs is available in the [CPU HCL](../cpu-hcl)
+The list of all supported CPUs is available in the [CPU HCL](hcl.md)
 documentation.
 
 In practice, any Alder Lake-S Processor should work.
@@ -87,7 +87,7 @@ We can say the "supported" one is the one that have been tested during
 Validation Procedure or have been tested by the community.
 
 The list of all supported memory modules is available in the
-[Memory HCL](../memory-hcl) documentation.
+[Memory HCL](hcl.md) documentation.
 
 ## What is the memory profile?
 
@@ -127,7 +127,7 @@ We can say the "supported" one is the one that have been tested during
 Validation Procedure or have been tested by the community.
 
 The list of all supported memory modules is available in the
-[GPU HCL](../gpu-hcl) documentation.
+[GPU HCL](hcl.md) documentation.
 
 ## What does the obligatory Dasharo Subscripion includes?
 
diff --git a/docs/unified/msi/hcl.md b/docs/unified/msi/hcl.md
index a0f49020d6..4556056cd3 100644
--- a/docs/unified/msi/hcl.md
+++ b/docs/unified/msi/hcl.md
@@ -29,7 +29,7 @@ hardware.
     * Source:
         - Link to report if it is public.
         - `Dasharo HCL report` if it was [reported using
-        DTS](../../../dasharo-tools-suite/documentation/#hcl-report).
+        DTS](../../dasharo-tools-suite/documentation.md#hcl-report).
 
     <center>
 
@@ -208,7 +208,7 @@ hardware.
     | MSI GeForce RTX 3060 GAMING Z TRIO LHR | 12 GB     | GDDR6  | 358GB/s   | Gen4      | 1                         | |
 
 For details how to maintain this documentation please consult [Dasharo HCL
-Maintainer documentation](../../../dev-proc/hcl-maintainer).
+Maintainer documentation](../../dev-proc/hcl-maintainer.md).
 
 [1]: https://forum.qubes-os.org/t/msi-pro-z690-a-wifi-ddr4-with-alder-lake-12900k/11490/6
 [2]: https://groups.google.com/g/qubes-users/c/lGOjuApLD_o/m/TBZN0PsXEgAJ
@@ -217,7 +217,7 @@ Maintainer documentation](../../../dev-proc/hcl-maintainer).
 ## Contributing
 
 === "PRO Z690-A (WIFI) DDR4"
-    - Use [Dasharo Tools Suite HCL report](../../../dasharo-tools-suite/documentation/#hcl-report)
+    - Use [Dasharo Tools Suite HCL report](../../dasharo-tools-suite/documentation.md#hcl-report)
       to upload report automatically.
     - Create new issue in [Dasharo issues repository](https://github.com/Dasharo/dasharo-issues/issues/new?assignees=&labels=P%3A+default%2C+T%3A+hcl&template=hcl-report.md&title=CPU+HCL+report+for+msi_z690).
     - Create PR directly to [Dasharo documentation repository](https://github.com/Dasharo/docs).
@@ -244,7 +244,7 @@ Maintainer documentation](../../../dev-proc/hcl-maintainer).
       ```
 
 === "PRO Z690-A (WIFI)"
-    - Use [Dasharo Tools Suite HCL report](../../../dasharo-tools-suite/documentation/#hcl-report)
+    - Use [Dasharo Tools Suite HCL report](../../dasharo-tools-suite/documentation.md#hcl-report)
       to upload report automatically.
     - Create new issue in [Dasharo issues repository](https://github.com/Dasharo/dasharo-issues/issues/new?assignees=&labels=P%3A+default%2C+T%3A+hcl&template=hcl-report.md&title=CPU+HCL+report+for+msi_z690).
     - Create PR directly to [Dasharo documentation repository](https://github.com/Dasharo/docs).
@@ -271,7 +271,7 @@ Maintainer documentation](../../../dev-proc/hcl-maintainer).
       ```
 
 === "PRO Z790-P (WIFI) DDR4"
-    - Use [Dasharo Tools Suite HCL report](../../../dasharo-tools-suite/documentation/#hcl-report)
+    - Use [Dasharo Tools Suite HCL report](../../dasharo-tools-suite/documentation.md#hcl-report)
       to upload report automatically.
     - Create new issue in [Dasharo issues repository](https://github.com/Dasharo/dasharo-issues/issues/new?assignees=&labels=P%3A+default%2C+T%3A+hcl&template=hcl-report.md&title=CPU+HCL+report+for+msi_z790).
     - Create PR directly to [Dasharo documentation repository](https://github.com/Dasharo/docs).
@@ -298,7 +298,7 @@ Maintainer documentation](../../../dev-proc/hcl-maintainer).
       ```
 
 === "PRO Z790-P (WIFI)"
-    - Use [Dasharo Tools Suite HCL report](../../../dasharo-tools-suite/documentation/#hcl-report)
+    - Use [Dasharo Tools Suite HCL report](../../dasharo-tools-suite/documentation.md#hcl-report)
       to upload report automatically.
     - Create new issue in [Dasharo issues repository](https://github.com/Dasharo/dasharo-issues/issues/new?assignees=&labels=P%3A+default%2C+T%3A+hcl&template=hcl-report.md&title=CPU+HCL+report+for+msi_z790).
     - Create PR directly to [Dasharo documentation repository](https://github.com/Dasharo/docs).
diff --git a/docs/unified/msi/initial-deployment.md b/docs/unified/msi/initial-deployment.md
index 8c33d78e86..097806f13d 100644
--- a/docs/unified/msi/initial-deployment.md
+++ b/docs/unified/msi/initial-deployment.md
@@ -24,7 +24,7 @@ running flashrom on Ubuntu 22.04.
 
 ### Build flashrom
 
-Please follow generic guide for [Dasharo flashrom fork](../../../osf-trivia-list/deployment/#how-to-install-dasharo-flashrom-fork).
+Please follow generic guide for [Dasharo flashrom fork](../../osf-trivia-list/deployment.md#how-to-install-dasharo-flashrom-fork).
 
 ### Flashing
 
@@ -198,7 +198,7 @@ echo -n `sudo dmidecode -s baseboard-serial-number` > serial_number.txt
     ```
 
 Note you will need to resign the binary after adding the SMBIOS data. Please
-check [Vboot documentation](../../../guides/vboot-signing) how to
+check [Vboot documentation](../../guides/vboot-signing.md) how to
 resign the data. It is the machine owner's responsibility to generate and use
 own keys during updates.
 
diff --git a/docs/unified/msi/recovery.md b/docs/unified/msi/recovery.md
index c93e270c92..358ae4eed6 100644
--- a/docs/unified/msi/recovery.md
+++ b/docs/unified/msi/recovery.md
@@ -7,8 +7,8 @@ hardware configurations, the Dasharo firmware may not boot correctly (i.e.
 we will have "bricked" the platform). In such a case, the recovery procedure can
 reinstall the original firmware from the board manufacturer.
 
-There are two documented recovery methods: using a [CH341A programming kit](https://3mdeb.com/shop/modules/ch341a-flash-bios-usb-programmer-kit-soic8-sop8/)
-or an [RTE](https://3mdeb.com/shop/open-source-hardware/rte/).
+There are two documented recovery methods: using a [CH341A programming kit](https://shop.3mdeb.com/shop/modules/ch341a-flash-bios-usb-programmer-kit-soic8-sop8/)
+or an [RTE](https://shop.3mdeb.com/shop/open-source-hardware/rte/).
 
 Since Dasharo v1.1.2 (PRO Z690-A) / v0.9.0 (PRO Z790-P) release it is also
 possible to use MSI FlashBIOS button feature to recover using an image placed
@@ -39,7 +39,7 @@ In this case, using external programmer is necessary. We are using
 here.
 
 * Connect programmer to the flash chip as shown in the
-  [Hardware connection / SPI](../development/#hardware-connection) section of
+  [Hardware connection / SPI](development.md#hardware-connection) section of
   the `Development` documentation.
 
 * Download official BIOS from vendor's website (this is the newest version, you
@@ -64,7 +64,7 @@ flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=16000 -w 7D25v13/E7D25IMS.130
 
 #### Prerequisites
 
-The full set is now available at our [online shop](https://3mdeb.com/shop/modules/ch341a-flash-bios-usb-programmer-kit-soic8-sop8/).
+The full set is now available at our [online shop](https://shop.3mdeb.com/shop/modules/ch341a-flash-bios-usb-programmer-kit-soic8-sop8/).
 
 1. CH341A kit with 1.8V level-shifter. Can be bought on e.g. [Amazon](https://www.amazon.com/programmer-ch341a-Programmer-Adapter-Converter/dp/B07WP9FKZ2)
 
@@ -223,7 +223,7 @@ provides the system UUID in the SMBIOS system information structure.
 
 The problem with UUID is that it cannot be recovered if the backup binary or
 SMBIOS logs are lost. You can backup the SMBIOS information with our
-[Dasharo Tools Suite bootable stick](../../../dasharo-tools-suite/documentation#bootable-usb-stick).
+[Dasharo Tools Suite bootablestick](https://docs.dasharo.com/dasharo-tools-suite/documentation#bootable-usb-stick).
 The `dmidecode.log` will have all the necessary information. Things we know
 about MSI system UUID:
 
diff --git a/docs/unified/novacustom/battery-management.md b/docs/unified/novacustom/battery-management.md
index 1a04175f3a..27705475eb 100644
--- a/docs/unified/novacustom/battery-management.md
+++ b/docs/unified/novacustom/battery-management.md
@@ -4,14 +4,14 @@ NovaCustom laptops equipped with Dasharo firmware provide several battery
 management mechanisms to optimize user experience and further prolong the
 battery's lifespan.
 
-## Boot  blocking when the battery is low
+## Boot blocking when the battery is low
 
 To prevent corruption of the bootloader, which may occur due to sudden power cut
 off during the OS boot process, booting the OS is blocked when the battery level
 sits below 5%. When trying to boot the OS with the battery level below the
 defined threshold, following message will be displayed on screen:
 
-![](images/boot_block_popup.jpg)
+![boot_block_popup](../../images/battery_block_popup.jpg)
 
 ## Disconnected battery warning
 
@@ -19,14 +19,14 @@ When the firmware encounters problems with detecting the battery, following
 message will appear suggesting checking the physical connection between the
 battery and mainboard:
 
-![](images/battery_connection.jpg)
+![battery_connection](../../images/battery_connection.jpg)
 
 ## Power information error
 
 When the firmware encounters problems with retrieving information about AC and
 battery state, following error message will be displayed:
 
-![](images/power_error.jpg)
+![power_error](../../images/power_error.jpg)
 
 ## Charge thresholds
 
diff --git a/docs/unified/novacustom/overview.md b/docs/unified/novacustom/overview.md
index 6b0f7df0f9..a5939119a6 100644
--- a/docs/unified/novacustom/overview.md
+++ b/docs/unified/novacustom/overview.md
@@ -9,7 +9,7 @@
     - [NS51 series](https://configurelaptop.eu/ns51-series/)
     - [NS70 series](https://configurelaptop.eu/ns70-series/)
 
-    ![](/images/NS51-front-1.jpg)
+    ![](/images/NS51-front-1.png)
 
 === "NV4x ADL"
     The `NovaCustom NV4x 12th Gen` section is related to the one physical
@@ -17,7 +17,7 @@
 
     - [NV41 series](https://configurelaptop.eu/nv41-series/)
 
-    ![](/images/NV4x-front-1.jpg)
+    ![](/images/NV4x-front-1.png)
 
 === "NS5x TGL"
     The `NovaCustom NS5x/7x 11th Gen` section is related to the two physical
@@ -26,7 +26,7 @@
     - [NS51 series](https://configurelaptop.eu/ns51-series/)
     - [NS70 series](https://configurelaptop.eu/ns70-series/)
 
-    ![](/images/NS51-front-1.jpg)
+    ![](/images/NS51-front-1.png)
 
 === "NV4x TGL"
     The `NovaCustom NV4x 11th Gen` section is related to the one physical
@@ -34,7 +34,7 @@
 
     - [NV41 series](https://configurelaptop.eu/nv41-series/)
 
-    ![](/images/NV4x-front-1.jpg)
+    ![](/images/NV4x-front-1.png)
 
 For more information on the hardware, please refer to the references in above
 links.
diff --git a/docs/unified/novacustom/recovery.md b/docs/unified/novacustom/recovery.md
index a8c0ebfe13..19c80ac2b7 100644
--- a/docs/unified/novacustom/recovery.md
+++ b/docs/unified/novacustom/recovery.md
@@ -48,7 +48,8 @@ The procedure will be slightly different depending on the model of your laptop.
     - USB-A to USB-B cable to connect the Arduino to the host
     - USB-C cable for grounding
 
-The full set for EC firmware recovery is available at our [online shop](https://3mdeb.com/shop/open-source-hardware/ec-flashing-kit/).
+The full set for EC firmware recovery is available at our
+[online shop](https://shop.3mdeb.com/shop/open-source-hardware/ec-flashing-kit/).
 
 #### Preparation
 
diff --git a/docs/variants/asus_kgpe_d16/initial-deployment.md b/docs/variants/asus_kgpe_d16/initial-deployment.md
index 7dcfe9334a..fdb1046bc6 100644
--- a/docs/variants/asus_kgpe_d16/initial-deployment.md
+++ b/docs/variants/asus_kgpe_d16/initial-deployment.md
@@ -23,7 +23,7 @@ installing and running flashrom on Ubuntu 20.04.
 
 ### Build flashrom
 
-Please follow generic guide for [Dasharo flashrom fork](../../../osf-trivia-list/deployment/#how-to-install-dasharo-flashrom-fork).
+Please follow generic guide for [Dasharo flashrom fork](../../osf-trivia-list/deployment.md#how-to-install-dasharo-flashrom-fork).
 
 ### Reading flash contents
 
diff --git a/docs/variants/asus_kgpe_d16/setup.md b/docs/variants/asus_kgpe_d16/setup.md
index 7c30e01c2b..6254edb918 100644
--- a/docs/variants/asus_kgpe_d16/setup.md
+++ b/docs/variants/asus_kgpe_d16/setup.md
@@ -98,8 +98,8 @@ option to connect a TPM, we use the header for that purpose.
 IMPORTANT: Use only TPM modules which match their pinout with the board's
 header! Using a spider web connection degrades the signal quality to the point
 where CPU cannot properly talk to TPM via LPC bus. Tested with
-[PC Engines TPM module](https://3mdeb.com/shop/modules/tpm-2-0/) and failed to
-succeed this way. Designing and producing proper TPM header and/or reliable
+[PC Engines TPM module](https://shop.3mdeb.com/shop/modules/tpm-2-0/) and failed
+to succeed this way. Designing and producing proper TPM header and/or reliable
 adapter, could solve this problem. The [TwPM
 project](https://twpm.dasharo.com/) could help here in the future.
 
@@ -162,7 +162,7 @@ jumper to protect the flash. In order to assembly the adapter you will need
 (16MB)),
 * male pin headers 2.54 mm pitch (6 pins)
 * male long pin headers 2.54 mm pitch (2 pins) for the WP jumper
-* [SOIC-8 to DIP-8 adapter](https://pl.farnell.com/en-PL/aries/lcqt-soic8-8/ic-adaptor-8-soic-to-dip-2-54mm/dp/2476033?ost=lcqt-soic8-8)
+* [SOIC-8 to DIP-8 adapter](https://www.digikey.com/en/products/detail/aries-electronics/LCQT-SOIC8-8/4754588)
 * soldering station and the solder
 
 The build shall look like this:
@@ -262,4 +262,4 @@ to the [Dasharo Newsletter](https://newsletter.3mdeb.com/subscription/wwL90UkXP)
 ![](/images/kgpe_2.jpg)
 ![](/images/kgpe_3.jpg)
 
-[flashchip-adapter]: https://3mdeb.com/shop/adapters/flash-chip-adapters/asus-kgpe-d16-flash-chip-adapter/
+[flashchip-adapter]: https://shop.3mdeb.com/shop/adapters/flash-chip-adapters/asus-kgpe-d16-flash-chip-adapter/
diff --git a/docs/variants/asus_kgpe_d16/spi-wp.md b/docs/variants/asus_kgpe_d16/spi-wp.md
index 8afaead2c3..d8e511bdfb 100644
--- a/docs/variants/asus_kgpe_d16/spi-wp.md
+++ b/docs/variants/asus_kgpe_d16/spi-wp.md
@@ -367,7 +367,8 @@ So our WP range would be 2MB at 6MB offset
 setting the WP range, one may want to sign the firmware with own vboot keys.
 The Dasharo build come by default with Google vboot developer keys, so to take
 advantage of vboot, one should sign the binary before flashing and setting the
-WP range. Refer to [vboot signing](../../../guides/vboot-signing/).
+WP range. Refer to
+[vboot signing](https://docs.dasharo.com/guides/vboot-signing/).
 Unfortunately the utilities support only 2 RW partitions for resiging.
 Otherwise a whole image must be rebuilt. After custo mkeys have been used to
 sign the ifmrware image and the image has been flashed proceed with enalbing
diff --git a/docs/variants/dell_optiplex/faq.md b/docs/variants/dell_optiplex/faq.md
index 003a4bc8cd..11fc56e1e7 100644
--- a/docs/variants/dell_optiplex/faq.md
+++ b/docs/variants/dell_optiplex/faq.md
@@ -3,8 +3,7 @@
 ## I see orange LED blinking, but no output, is my board broken?
 
 It means ME is broken and backup firmware would be required to recover it.
-Please follow
-[additional recovery step](../recovery/#optional-step-7-flash-8mb-me-part)
+Please follow [additional recovery step](./recovery.md#optional-step-7-flash-8mb-me-part)
 to fix that problem.
 
 ## I see white LED, but no output, is my board broken?
@@ -16,7 +15,8 @@ stuck at some point or maybe platform booting normally but all output is
 disabled.
 
 Debugging that requires rebuilding with `CONFIG_DEFAULT_CONSOLE_LOGLEVEL_8=y`.
-Instruction for that can be found [here](../building-manual/#debug-build).
+Instruction for that can be found
+[here](./building-manual.md#debug-build).
 
 ## Is it safe to work without heatsink?
 
@@ -50,8 +50,8 @@ If serial console logs contain:
 ```
 
 It means ME is broken and backup firmware would be required to recover it.
-Please follow
-[additional recovery step](../recovery/#optional-step-7-flash-8mb-me-part)
+Please follow [additional recovery
+step](recovery.md#optional-step-7-flash-8mb-me-part)
 to fix that problem.
 
 This may happen accidentally when you flash whole 12MB BIOS binary without
diff --git a/docs/variants/dell_optiplex/firmware-update.md b/docs/variants/dell_optiplex/firmware-update.md
index 7b895dba07..028ad19182 100644
--- a/docs/variants/dell_optiplex/firmware-update.md
+++ b/docs/variants/dell_optiplex/firmware-update.md
@@ -8,7 +8,7 @@ distribution update.
 ## OS booting
 
 For simplicity we recommend using network booted
-[Dasharo Tools Suite](../../../dasharo-tools-suite/overview).
+[Dasharo Tools Suite](https://docs.dasharo.com/dasharo-tools-suite/overview).
 
 ### Dasharo (coreboot+SeaBIOS) and Dasharo (coreboot+UEFI) update
 
diff --git a/docs/variants/dell_optiplex/initial-deployment.md b/docs/variants/dell_optiplex/initial-deployment.md
index 50bca20ee7..4746fb228c 100644
--- a/docs/variants/dell_optiplex/initial-deployment.md
+++ b/docs/variants/dell_optiplex/initial-deployment.md
@@ -89,7 +89,7 @@ intervention.
 
    ![](../../images/dasharo-black.jpg)
 
-From that point you can use [firmware update](../firmware-update) methods to
+From that point you can use [firmware update](firmware-update.md) methods to
 update your firmware.
 
 ## Troubleshooting
diff --git a/docs/variants/dell_optiplex/recovery.md b/docs/variants/dell_optiplex/recovery.md
index 8767a8b262..877644ebc5 100644
--- a/docs/variants/dell_optiplex/recovery.md
+++ b/docs/variants/dell_optiplex/recovery.md
@@ -5,7 +5,7 @@
 ---
 
 Following documentation describes the process of recovering hardware from brick
-state with [RTE](../../../transparent-validation/rte/introduction/) and Dasharo
+state with [RTE](../../transparent-validation/rte/introduction.md) and Dasharo
 open-source firmware. Following procedure is supported for following models
 
 <center>
@@ -20,7 +20,8 @@ open-source firmware. Following procedure is supported for following models
 
 ## Step 1: Prepare hardware
 
-1. To prepare hardware please follow [hardware preparation](../initial-deployment/#hardware-preparation)
+1. To prepare hardware please follow
+   [hardware preparation](initial-deployment.md#hardware-preparation)
    procedure.
 2. Follow instruction in the video to remove heatsink:
 
@@ -110,7 +111,7 @@ pin of `SPI_1` chip, marked with a small dot engraved on the chip.
 ## Step 5: Prepare recovery binary
 
 Following procedure assume that you use recovery binary created during [backup
-process](../../../osf-trivia-list/deployment/#how-to-use-flashrom-to-backup-vendor-bios).
+process](../../osf-trivia-list/deployment.md#how-to-use-flashrom-to-backup-vendor-bios).
 Backup has 12MB, so it have to be split
 
 ```bash
@@ -142,9 +143,9 @@ flashrom -w xac -p linux_spi:dev=/dev/spidev1.0,spispeed=16000 -c "MX25L3205D/MX
 ## (Optional) Step 7: Flash 8MB (ME) part
 
 If a more serious problem occurs, like
-[broken ME](../faq/#cpu-was-replace-warm-reset-required-loop),
+[broken ME](faq.md#cpu-was-replace-warm-reset-required-loop),
 it may be necessary to use your
-[firmware backup](../initial-deployment/#bios-backup)
+[firmware backup](initial-deployment.md#bios-backup)
 and restore content of 8MB chip.
 
 ### Step 7a: Connect SOIC-16 Pomona clip between RTE and target
diff --git a/docs/variants/msi_z690/releases.md b/docs/variants/msi_z690/releases.md
index 78de56312a..ca82c227d6 100644
--- a/docs/variants/msi_z690/releases.md
+++ b/docs/variants/msi_z690/releases.md
@@ -281,7 +281,7 @@ gpg --verify msi_ms7d25_v0.4.0.rom.sha256.sig msi_ms7d25_v0.4.0.rom.sha256
 - Mainboard-specific SMBIOS data for slots and ports
 - PCI Subsystem ID configuration
 - CPU VR and PCH FIVR configuration
-- [Memory HCL](https://docs.dasharo.com/variants/msi_z690/memory-hcl/)
+- [Memory HCL](https://docs.dasharo.com/unified/msi/hcl/)
 - [UEFI Secure Boot](https://docs.dasharo.com/unified-test-documentation/dasharo-security/206-secure-boot/)
 - [TPM Support](https://docs.dasharo.com/unified-test-documentation/dasharo-security/200-tpm-support/)
 - [Measured Boot](https://docs.dasharo.com/unified-test-documentation/dasharo-security/203-measured-boot/)
diff --git a/docs/variants/novacustom_ns5x_adl/releases.md b/docs/variants/novacustom_ns5x_adl/releases.md
index d0442c9e31..b5557ca116 100644
--- a/docs/variants/novacustom_ns5x_adl/releases.md
+++ b/docs/variants/novacustom_ns5x_adl/releases.md
@@ -101,8 +101,8 @@ Test results for this release can be found
 - [Vboot Verified Boot](https://docs.dasharo.com/unified-test-documentation/dasharo-security/201-verified-boot/)
 - [Vboot recovery mode information popup](https://docs.dasharo.com/unified-test-documentation/dasharo-security/201-verified-boot/#vbo009001-recovery-boot-popup-firmware)
 - [Dasharo setup menu full screen mode support](https://github.com/Dasharo/dasharo-issues/issues/118)
-- [Support for RGB backlit keyboard](../../../unified/novacustom/rgb-keyboard/)
-- [Support for open-source EC firmware](../../../dasharo-tools-suite/documentation#ec-transition)
+- [Support for RGB backlit keyboard](https://docs.dasharo.com/unified/novacustom/rgb-keyboard/)
+- [Support for open-source EC firmware](https://docs.dasharo.com/dasharo-tools-suite/documentation#ec-transition)
 
 ### Known issues
 
diff --git a/docs/variants/novacustom_ns5x_tgl/releases.md b/docs/variants/novacustom_ns5x_tgl/releases.md
index d95069dbc4..1c6ad64ffe 100644
--- a/docs/variants/novacustom_ns5x_tgl/releases.md
+++ b/docs/variants/novacustom_ns5x_tgl/releases.md
@@ -90,7 +90,7 @@ section for more details on upgrading your firmware.
 
 - Rebased on upstream coreboot revision 1a8eb6c0
 
-- [Support for Open EC Firmware](../../../dasharo-tools-suite/documentation#ec-transition)
+- [Support for Open EC Firmware](https://docs.dasharo.com/dasharo-tools-suite/documentation#ec-transition)
 
 - [Disabled UEFI Secure Boot by default](https://docs.dasharo.com/unified-test-documentation/dasharo-security/206-secure-boot/)
 
@@ -167,7 +167,7 @@ using [this key](https://raw.githubusercontent.com/3mdeb/3mdeb-secpack/master/cu
 
 - Support for NovaCustom NS7x
 - [Support for RGB Keyboard](https://docs.dasharo.com/unified/novacustom/rgb-keyboard/)
-- [Persistent boot logo implementation](../../../guides/logo-customization)
+- [Persistent boot logo implementation](https://docs.dasharo.com/guides/logo-customization)
 
 ### Changed
 
diff --git a/docs/variants/novacustom_nv4x_adl/releases.md b/docs/variants/novacustom_nv4x_adl/releases.md
index 9ca3f8c96a..776e373cb3 100644
--- a/docs/variants/novacustom_nv4x_adl/releases.md
+++ b/docs/variants/novacustom_nv4x_adl/releases.md
@@ -101,7 +101,7 @@ using [this key](https://raw.githubusercontent.com/3mdeb/3mdeb-secpack/master/cu
 - [Vboot Verified Boot](https://docs.dasharo.com/unified-test-documentation/dasharo-security/201-verified-boot/)
 - [Vboot Recovery Popup](https://docs.dasharo.com/unified-test-documentation/dasharo-security/201-verified-boot/#vbo009001-recovery-boot-popup-firmware)
 - Fullscreen setup menu
-- [Open-source Embedded Controller Firmware](../../../unified/novacustom/recovery/#ec-firmware-recovery)
+- [Open-source Embedded Controller Firmware](https://docs.dasharo.com/unified/novacustom/recovery/#ec-firmware-recovery)
 
 ### Fixed
 
diff --git a/docs/variants/novacustom_nv4x_tgl/compatibility-check-results-ubuntu.md b/docs/variants/novacustom_nv4x_tgl/compatibility-check-results-ubuntu.md
index d8bbb8f6c8..02772f550c 100644
--- a/docs/variants/novacustom_nv4x_tgl/compatibility-check-results-ubuntu.md
+++ b/docs/variants/novacustom_nv4x_tgl/compatibility-check-results-ubuntu.md
@@ -125,7 +125,7 @@ vendor/Dasharo firmware is shown.
 ### Logs from tests
 
 Logs are available under this
-[link](https://cloud.3mdeb.com/index.php/apps/files/?dir=/projects/novacustom/tat/logs-checkbox&fileid=480327).
+[link](https://cloud.3mdeb.com/index.php/s/rrERogJkmGe9N8a).
 
 ## Summary
 
diff --git a/docs/variants/novacustom_nv4x_tgl/releases.md b/docs/variants/novacustom_nv4x_tgl/releases.md
index 1639321cd9..e2f7c084c0 100644
--- a/docs/variants/novacustom_nv4x_tgl/releases.md
+++ b/docs/variants/novacustom_nv4x_tgl/releases.md
@@ -96,7 +96,7 @@ section for more details on upgrading your firmware.
 ### Changed
 
 - [Rebased on upstream coreboot revision from 18 Aug 2022](https://github.com/Dasharo/coreboot/commits/1a8eb6c0)
-- [Support for open-source EC firmware (transition procedure is required)](../../../dasharo-tools-suite/documentation#ec-transition)
+- [Support for open-source EC firmware (transition procedure is required)](https://docs.dasharo.com/dasharo-tools-suite/documentation#ec-transition)
 - [Disabled UEFI Secure Boot by default](https://docs.dasharo.com/unified-test-documentation/dasharo-security/206-secure-boot/)
 
 ### Fixed
diff --git a/docs/variants/overview.md b/docs/variants/overview.md
index 3ef12fe70a..a72c3ef21d 100644
--- a/docs/variants/overview.md
+++ b/docs/variants/overview.md
@@ -7,46 +7,46 @@ open-source firmware distribution.
 
 * Following network appliances are supported under Dasharo Support Package:
 
-    - [Protectli FW6](../protectli_fw6/overview)
-    - [Protectli VP2410](../protectli_vp2410/overview)
-    - [Protectli VP2420](../protectli_vp2420/overview)
-    - [Protectli VP46xx](../protectli_vp46xx/overview)
+    - [Protectli FW6](protectli_fw6/overview.md)
+    - [Protectli VP2410](protectli_vp2410/overview.md)
+    - [Protectli VP2420](protectli_vp2420/overview.md)
+    - [Protectli VP46xx](protectli_vp46xx/overview.md)
 
 * Following network appliances are planned to be supported under Dasharo
   Community Support:
 
-    - [PC Engines](../pc_engines/post-eol-fw-announcement)
+    - [PC Engines](pc_engines/post-eol-fw-announcement.md)
 
 ## Laptops
 
 * Following laptops are supported under Dasharo Support Package
 
-    - [NovaCustom NV4x 12th Gen](../../unified/novacustom/overview)
-    - [NovaCustom NS5x/7x 12th Gen](../../unified/novacustom/overview)
-    - [NovaCustom NV4x 11th Gen](../../unified/novacustom/overview)
-    - [NovaCustom NS5x/7x 11th Gen](../../unified/novacustom/overview)
+    - [NovaCustom NV4x 12th Gen](../unified/novacustom/overview.md)
+    - [NovaCustom NS5x/7x 12th Gen](../unified/novacustom/overview.md)
+    - [NovaCustom NV4x 11th Gen](../unified/novacustom/overview.md)
+    - [NovaCustom NS5x/7x 11th Gen](../unified/novacustom/overview.md)
 
 * Following laptops are supported under Dasharo Community Support
 
-    - [Tuxedo IBS15](../tuxedo_ibs15/releases)
+    - [Tuxedo IBS15](tuxedo_ibs15/releases.md)
 
 ## Desktop
 
 * Following desktops are supported under Dasharo Community Support
 
-    - [Dell OptiPlex](../dell_optiplex/overview)
-    - [MSI PRO Z690-A](../../unified/msi/overview)
-    - [MSI PRO Z790-P](../../unified/msi/overview)
+    - [Dell OptiPlex](dell_optiplex/overview.md)
+    - [MSI PRO Z790-P](../unified/msi/overview.md)
+    - [MSI PRO Z790-P](../unified/msi/overview.md)
 
 ## Workstation
 
 * Following workstations are supported under Dasharo Community Support
 
-    - [Asus KGPE-D16](../asus_kgpe_d16/overview)
-    - [Raptor CS Talos II](../talos_2/overview)
+    - [Asus KGPE-D16](asus_kgpe_d16/overview.md)
+    - [Raptor CS Talos II](talos_2/overview.md)
 
 ## Servers
 
 * Following servers are supported under Dasharo Community Support
 
-    - [Supermicro X11 LGA1151 Series](../supermicro_x11_lga1151_series/overview)
+    - [Supermicro X11 LGA1151 Series](supermicro_x11_lga1151_series/overview.md)
diff --git a/docs/variants/pc_engines/overview.md b/docs/variants/pc_engines/overview.md
index 6797f0bfcc..6f87d79f52 100644
--- a/docs/variants/pc_engines/overview.md
+++ b/docs/variants/pc_engines/overview.md
@@ -33,10 +33,10 @@ Engines decided to discontinue its sponsorship for open-source firmware.
 Dasharo Team working on creating a sustainable path forward for PC Engines'
 open-source firmware through a subscription and donation model. For more
 details please check [Post EOL firmware
-announcement](../post-eol-fw-announcement), contact us
+announcement](post-eol-fw-announcement.md), contact us
 [directly](mailto:contact@dasharo.com) or through [community
 chat](https://matrix.to/#/#dasharo:matrix.org).
 
 ## References
 
-* [Post-EOL firmware announcement](../post-eol-fw-announcement)
+* [Post-EOL firmware announcement](post-eol-fw-announcement.md)
diff --git a/docs/variants/protectli_ptx01/firmware-update.md b/docs/variants/protectli_ptx01/firmware-update.md
index c3b7906412..d6b73910a7 100644
--- a/docs/variants/protectli_ptx01/firmware-update.md
+++ b/docs/variants/protectli_ptx01/firmware-update.md
@@ -9,7 +9,7 @@ The update process may be different, depending on the currently installed
 Dasharo firmware version.
 
 For simplicity of the update process, we recommend using
-[Dasharo Tools Suite](../../../dasharo-tools-suite/overview).
+[Dasharo Tools Suite](../../dasharo-tools-suite/overview.md).
 
 Before starting the update procedure be sure to disable Secure Boot:
 
@@ -17,7 +17,7 @@ Before starting the update procedure be sure to disable Secure Boot:
 2. While the device is booting, hold the `DELETE` key to enter the UEFI Setup
    Menu.
 3. Enter the `Device Manager` menu.
-4. Enter the [Secure Boot Configuration](../../../dasharo-menu-docs/device-manager/#secure-boot-configuration)
+4. Enter the [Secure Boot Configuration](../../dasharo-menu-docs/device-manager.md#secure-boot-configuration)
    submenu.
 5. Verify that the `Current Secure Boot State` field says Disabled - if not,
    unselect the `Attempt Secure Boot` option below then press `F10` to save
diff --git a/docs/variants/protectli_ptx01/initial-deployment.md b/docs/variants/protectli_ptx01/initial-deployment.md
index 75e63b0145..61d1a60f4d 100644
--- a/docs/variants/protectli_ptx01/initial-deployment.md
+++ b/docs/variants/protectli_ptx01/initial-deployment.md
@@ -7,7 +7,7 @@ installing and running flashrom on Ubuntu 22.04.
 ## Deploy using Dasharo Tools Suite
 
 For simplicity we recommend using
-[Dasharo Tools Suite](../../../dasharo-tools-suite/overview) to
+[Dasharo Tools Suite](../../dasharo-tools-suite/overview.md) to
 omit all compilation steps and deploy the Dasharo firmware seamlessly.
 
 1. Boot Dasharo Tools Suite.
@@ -20,7 +20,7 @@ This concludes Dasharo deployment process using DTS.
 
 ## Build flashrom
 
-Please follow generic guide for [Dasharo flashrom fork](../../../osf-trivia-list/deployment/#how-to-install-dasharo-flashrom-fork).
+Please follow generic guide for [Dasharo flashrom fork](../../osf-trivia-list/deployment.md#how-to-install-dasharo-flashrom-fork).
 
 ## Reading flash contents
 
diff --git a/docs/variants/protectli_vp2410/initial-deployment.md b/docs/variants/protectli_vp2410/initial-deployment.md
index c0d64dffd8..ac1da9f3aa 100644
--- a/docs/variants/protectli_vp2410/initial-deployment.md
+++ b/docs/variants/protectli_vp2410/initial-deployment.md
@@ -7,7 +7,7 @@ installing and running flashrom on Ubuntu 22.04.
 ## Deploy using Dasharo Tools Suite
 
 For simplicity we recommend using
-[Dasharo Tools Suite](../../../dasharo-tools-suite/overview) to
+[Dasharo Tools Suite](https://docs.dasharo.com/dasharo-tools-suite/overview) to
 omit all compilation steps and deploy the Dasharo firmware seamlessly.
 Be sure to disable the BIOS lock in the AMI firmware setup utility:
 
@@ -38,7 +38,7 @@ This concludes Dasharo deployment process using DTS.
 
 ## Build flashrom
 
-Please follow generic guide for [Dasharo flashrom fork](../../../osf-trivia-list/deployment/#how-to-install-dasharo-flashrom-fork).
+Please follow generic guide for [Dasharo flashrom fork](../../osf-trivia-list/deployment.md#how-to-install-dasharo-flashrom-fork).
 
 ## Reading flash contents
 
diff --git a/docs/variants/protectli_vp2420/firmware-update.md b/docs/variants/protectli_vp2420/firmware-update.md
index b4e346a4b9..62daf2b657 100644
--- a/docs/variants/protectli_vp2420/firmware-update.md
+++ b/docs/variants/protectli_vp2420/firmware-update.md
@@ -6,7 +6,7 @@ firmware please refer to the [Initial deployment](initial-deployment.md)
 documentation.
 
 For simplicity of the update process, we recommend using
-[Dasharo Tools Suite](../../../dasharo-tools-suite/overview).
+[Dasharo Tools Suite](https://docs.dasharo.com/dasharo-tools-suite/overview).
 
 Before starting the update procedure be sure to disable Dasharo BIOS Boot medium
 lock, SMM BIOS Write Protection and Secure boot:
@@ -15,14 +15,14 @@ lock, SMM BIOS Write Protection and Secure boot:
 1. While the device is booting, hold the `DELETE` key to enter the UEFI Setup
    Menu.
 1. Enter the `Dasharo System Features` menu using the arrow keys and Enter.
-1. Enter the [Dasharo Security Options](../../../dasharo-menu-docs/dasharo-system-features/#dasharo-security-options)
+1. Enter the [Dasharo Security Options](https://docs.dasharo.com/dasharo-menu-docs/dasharo-system-features/#dasharo-security-options)
    submenu.
 1. Verify the state of the `Lock the BIOS boot medium` and
    `Enable SMM BIOS write protection` options - if any of those are set, press
    `Space` to unselect them and then `F10` to save the changes.
 1. Go back to the main menu using the `ESC` key.
 1. Enter the `Device Manager` menu.
-1. Enter the [Secure Boot Configuration](../../../dasharo-menu-docs/device-manager/#secure-boot-configuration)
+1. Enter the [Secure Boot Configuration](https://docs.dasharo.com/dasharo-menu-docs/device-manager/#secure-boot-configuration)
    submenu.
 1. Verify that the `Current Secure Boot State` field says Disabled - if not,
    unselect the `Attempt Secure Boot` option below then press `F10` to save the
diff --git a/docs/variants/protectli_vp2420/initial-deployment.md b/docs/variants/protectli_vp2420/initial-deployment.md
index 7052fb3474..9930248865 100644
--- a/docs/variants/protectli_vp2420/initial-deployment.md
+++ b/docs/variants/protectli_vp2420/initial-deployment.md
@@ -7,7 +7,7 @@ installing and running flashrom on Ubuntu 22.04.
 ## Deploy using Dasharo Tools Suite
 
 For simplicity we recommend using
-[Dasharo Tools Suite](../../../dasharo-tools-suite/overview) to
+[Dasharo Tools Suite](https://docs.dasharo.com/dasharo-tools-suite/overview) to
 omit all compilation steps and deploy the Dasharo firmware seamlessly.
 Be sure to disable the BIOS lock in the AMI firmware setup utility:
 
@@ -23,7 +23,7 @@ Now you are ready to use Dasharo Tools Suite (DTS):
 
 ## Build flashrom
 
-Please follow generic guide for [Dasharo flashrom fork](../../../osf-trivia-list/deployment/#how-to-install-dasharo-flashrom-fork).
+Please follow generic guide for [Dasharo flashrom fork](../../osf-trivia-list/deployment.md#how-to-install-dasharo-flashrom-fork).
 
 ## Reading flash contents
 
diff --git a/docs/variants/protectli_vp2420/releases.md b/docs/variants/protectli_vp2420/releases.md
index 047575c9c7..39f9c4080e 100644
--- a/docs/variants/protectli_vp2420/releases.md
+++ b/docs/variants/protectli_vp2420/releases.md
@@ -18,14 +18,14 @@ Test results for this platform can be found
 
 ### Added
 
-- [USB stack and mass storage enable/disable option](../../../dasharo-menu-docs/dasharo-system-features/#usb-configuration)
-- [SMM BIOS write protection enable/disable option](../../../dasharo-menu-docs/dasharo-system-features/#dasharo-security-options)
+- [USB stack and mass storage enable/disable option](https://docs.dasharo.com/dasharo-menu-docs/dasharo-system-features/#usb-configuration)
+- [SMM BIOS write protection enable/disable option](https://docs.dasharo.com/dasharo-menu-docs/dasharo-system-features/#dasharo-security-options)
 
 ### Changed
 
-- [Updating from v1.0.x requires flashing the WP_RO recovery partition](../../protectli_vp2420/firmware-update/#updating-minor-versions-v1xy)
+- [Updating from v1.0.x requires flashing the WP_RO recovery partition](../protectli_vp2420/firmware-update.md#updating-minor-versions-v1xy)
 - [Firmware version v1.1.x are signed with a new key](https://raw.githubusercontent.com/3mdeb/3mdeb-secpack/master/customer-keys/protectli/release-keys/dasharo-release-1.1.x-for-protectli-signing-key.asc)
-- [Keys must be provisioned prior enabling Secure Boot](../../../dasharo-menu-docs/device-manager/#secure-boot-configuration)
+- [Keys must be provisioned prior enabling Secure Boot](https://docs.dasharo.com/dasharo-menu-docs/device-manager/#secure-boot-configuration)
 
 ### Fixed
 
@@ -106,7 +106,7 @@ using [this key](https://raw.githubusercontent.com/3mdeb/3mdeb-secpack/master/cu
 ### Added
 
 - Support for VP2420 platform
-- [Vboot Verified Boot](../../../guides/vboot-signing/)
+- [Vboot Verified Boot](https://docs.dasharo.com/guides/vboot-signing/)
 - [TPM Measured Boot](https://docs.dasharo.com/unified-test-documentation/dasharo-security/203-measured-boot/)
 - [Vboot recovery notification in UEFI Payload](https://docs.dasharo.com/unified-test-documentation/dasharo-security/201-verified-boot/)
 - [UEFI Shell](https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/30P-uefi-shell/)
diff --git a/docs/variants/protectli_vp46xx/firmware-update.md b/docs/variants/protectli_vp46xx/firmware-update.md
index 95ab853847..c15a70a154 100644
--- a/docs/variants/protectli_vp46xx/firmware-update.md
+++ b/docs/variants/protectli_vp46xx/firmware-update.md
@@ -9,7 +9,7 @@ The update process may be different, depending on the currently installed
 Dasharo firmware version.
 
 For simplicity of the update process, we recommend using
-[Dasharo Tools Suite](../../../dasharo-tools-suite/overview).
+[Dasharo Tools Suite](https://docs.dasharo.com/dasharo-tools-suite/overview).
 
 Before starting the update procedure be sure to disable Dasharo BIOS Boot medium
 lock and Secure Boot:
@@ -18,13 +18,13 @@ lock and Secure Boot:
 1. While the device is booting, hold the `DELETE` key to enter the UEFI Setup
    Menu.
 1. Enter the `Dasharo System Features` menu using the arrow keys and Enter.
-1. Enter the [Dasharo Security Options](../../../dasharo-menu-docs/dasharo-system-features/#dasharo-security-options)
+1. Enter the [Dasharo Security Options](https://docs.dasharo.com/dasharo-menu-docs/dasharo-system-features/#dasharo-security-options)
    submenu.
 1. Verify the state of the `Lock the BIOS boot medium` option - if the option
    is chosen, press `Space` and then `F10` to save the changes.
 1. Go back to the main menu using the `ESC` key.
 1. Enter the `Device Manager` menu.
-1. Enter the [Secure Boot Configuration](../../../dasharo-menu-docs/device-manager/#secure-boot-configuration)
+1. Enter the [Secure Boot Configuration](https://docs.dasharo.com/dasharo-menu-docs/device-manager/#secure-boot-configuration)
    submenu.
 1. Verify that the `Current Secure Boot State` field says Disabled - if not,
    unselect the `Attempt Secure Boot` option below then press `F10` to save the
diff --git a/docs/variants/protectli_vp46xx/initial-deployment.md b/docs/variants/protectli_vp46xx/initial-deployment.md
index ec12e51aac..fe91cd413b 100644
--- a/docs/variants/protectli_vp46xx/initial-deployment.md
+++ b/docs/variants/protectli_vp46xx/initial-deployment.md
@@ -7,7 +7,7 @@ installing and running flashrom on Ubuntu 22.04.
 ## Deploy using Dasharo Tools Suite
 
 For simplicity we recommend using
-[Dasharo Tools Suite](../../../dasharo-tools-suite/overview) to
+[Dasharo Tools Suite](https://docs.dasharo.com/dasharo-tools-suite/overview) to
 omit all compilation steps and deploy the Dasharo firmware seamlessly.
 Be sure to disable the BIOS lock in the AMI firmware setup utility:
 
@@ -38,7 +38,7 @@ This concludes Dasharo deployment process using DTS.
 
 ## Build flashrom
 
-Please follow generic guide for [Dasharo flashrom fork](../../../osf-trivia-list/deployment/#how-to-install-dasharo-flashrom-fork).
+Please follow generic guide for [Dasharo flashrom fork](../../osf-trivia-list/deployment.md#how-to-install-dasharo-flashrom-fork).
 
 ## Reading flash contents
 
diff --git a/docs/variants/protectli_vp46xx/overview.md b/docs/variants/protectli_vp46xx/overview.md
index bb35fa8c35..8a105a58c8 100644
--- a/docs/variants/protectli_vp46xx/overview.md
+++ b/docs/variants/protectli_vp46xx/overview.md
@@ -19,7 +19,6 @@ For more information please refer to the references below.
 
 ## References
 
-* [VP4630 announcement](https://protectli.com/news/vp4630-launch/)
 * [Buy VP4630 in Protectli shop](https://protectli.com/product/vp4630/)
 
 ## Documentation sections
diff --git a/docs/variants/protectli_vp46xx/releases.md b/docs/variants/protectli_vp46xx/releases.md
index 71681bed81..e127bb2364 100644
--- a/docs/variants/protectli_vp46xx/releases.md
+++ b/docs/variants/protectli_vp46xx/releases.md
@@ -158,7 +158,7 @@ Test results for this release can be found
 
 ### Added
 
-- [Tools for resigning Vboot images with one RW partition](../../../guides/vboot-signing/)
+- [Tools for resigning Vboot images with one RW partition](https://docs.dasharo.com/guides/vboot-signing/)
 
 ### Changed
 
@@ -203,7 +203,7 @@ Test results for this release can be found
 
 ### Added
 
-- [Vboot Verified Boot](../../../guides/vboot-signing/)
+- [Vboot Verified Boot](https://docs.dasharo.com/guides/vboot-signing/)
 - [TPM Measured Boot](https://docs.dasharo.com/unified-test-documentation/dasharo-security/203-measured-boot/)
 - [Vboot recovery notification in UEFI Payload](https://docs.dasharo.com/unified-test-documentation/dasharo-security/201-verified-boot/)
 - [UEFI Shell](https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/30P-uefi-shell/)
diff --git a/docs/variants/supermicro_x11_lga1151_series/building-manual.md b/docs/variants/supermicro_x11_lga1151_series/building-manual.md
index 3bc54024e7..1a9ac4f204 100644
--- a/docs/variants/supermicro_x11_lga1151_series/building-manual.md
+++ b/docs/variants/supermicro_x11_lga1151_series/building-manual.md
@@ -1,6 +1,6 @@
 # Supermicro X11 LGA1151 Series - building manual
 
-**Please read the [overview page](../overview) first!**
+**Please read the [overview page](../overview.md) first!**
 
 <!--
 To build Dasharo compatible with Supermicro X11 LGA1151 Series, follow the
diff --git a/docs/variants/supermicro_x11_lga1151_series/faq.md b/docs/variants/supermicro_x11_lga1151_series/faq.md
index 4b7f89edcb..58ec0bd79b 100644
--- a/docs/variants/supermicro_x11_lga1151_series/faq.md
+++ b/docs/variants/supermicro_x11_lga1151_series/faq.md
@@ -1,6 +1,6 @@
 # FAQ
 
-**Please read the [overview page](../overview) first!**
+**Please read the [overview page](../overview.md) first!**
 
 ## How to identify my mainboard model?
 
diff --git a/docs/variants/supermicro_x11_lga1151_series/firmware-update.md b/docs/variants/supermicro_x11_lga1151_series/firmware-update.md
index 99de1f1b34..882fd17be6 100644
--- a/docs/variants/supermicro_x11_lga1151_series/firmware-update.md
+++ b/docs/variants/supermicro_x11_lga1151_series/firmware-update.md
@@ -1,6 +1,6 @@
 # Firmware update
 
-**Please read the [overview page](../overview) first!**
+**Please read the [overview page](../overview.md) first!**
 
 Following documentation describe process of Dasharo open-source firmware
 distribution update.
@@ -10,7 +10,7 @@ distribution update.
 ## OS booting
 
 For simplicity we recommend using network booted
-[Dasharo Tools Suite](../../../dasharo-tools-suite/overview).
+[Dasharo Tools Suite](https://docs.dasharo.com/dasharo-tools-suite/overview).
 
 ### Dasharo (coreboot+SeaBIOS) update
 
diff --git a/docs/variants/supermicro_x11_lga1151_series/hardware-matrix.md b/docs/variants/supermicro_x11_lga1151_series/hardware-matrix.md
index 6780e0c92d..9fb4a72b44 100644
--- a/docs/variants/supermicro_x11_lga1151_series/hardware-matrix.md
+++ b/docs/variants/supermicro_x11_lga1151_series/hardware-matrix.md
@@ -1,6 +1,6 @@
 # Hardware configuration matrix
 
-**Please read the [overview page](../overview) first!**
+**Please read the [overview page](../overview.md) first!**
 
 The tables below contain information about current components of the testing
 environment for Supermicro X11 LGA1151 Series available in 3mdeb testing
diff --git a/docs/variants/supermicro_x11_lga1151_series/initial-deployment.md b/docs/variants/supermicro_x11_lga1151_series/initial-deployment.md
index 3522e160b3..95eaa067bd 100644
--- a/docs/variants/supermicro_x11_lga1151_series/initial-deployment.md
+++ b/docs/variants/supermicro_x11_lga1151_series/initial-deployment.md
@@ -14,10 +14,10 @@ following unofficial guides deviating in any way from the official
 instructions.
 
 If you have trouble with the installation process, ask for help on the official
-[Dasharo chat channel](../../../#community). There are almost always people
-around willing to help with it. Before asking for help, make an attempt to
-follow the guide on your own and then ask for help with anything you get stuck
-on.
+[Dasharo chat channel](https://docs.dasharo.com/#community). There are almost
+always people around willing to help with it. Before asking for help, make an
+attempt to follow the guide on your own and then ask for help with anything you
+get stuck on.
 
 ## Hardware preparation
 
@@ -79,7 +79,7 @@ iPXE Shell
 ## Vendor BIOS backup
 
 Please follow [DTS backup
-guide](../../../dasharo-tools-suite/documentation/#bios-backup).
+guide](https://docs.dasharo.com/dasharo-tools-suite/documentation/#bios-backup).
 
 ## Installing Dasharo with DTS
 
diff --git a/docs/variants/supermicro_x11_lga1151_series/overview.md b/docs/variants/supermicro_x11_lga1151_series/overview.md
index 7bb11b8d01..7d04320c12 100644
--- a/docs/variants/supermicro_x11_lga1151_series/overview.md
+++ b/docs/variants/supermicro_x11_lga1151_series/overview.md
@@ -30,8 +30,8 @@ us](mailto:contact@dasharo.com) if you wan to talk about project status.
 Please note that Dasharo compatilbe with Supermicro X11 LGA1151 Series may work
 with various boards from this family, at this stage only X11SSH-F and X11SSH-TF
 can be treated as tested. This state can change when we will enter more mature
-state with transparent validation results published in [Releases](../releases)
-section and [hardware configuration matrix](../hardware-matrix) used for
+state with transparent validation results published in [Releases](releases.md)
+section and [hardware configuration matrix](hardware-matrix.md) used for
 testing. We may also consider CPU, DRAM and GPU HCL sections in documentation.
 
 If you are interested in this project, please consider joining the
diff --git a/docs/variants/supermicro_x11_lga1151_series/recovery.md b/docs/variants/supermicro_x11_lga1151_series/recovery.md
index 8912abbe18..8ea5299f63 100644
--- a/docs/variants/supermicro_x11_lga1151_series/recovery.md
+++ b/docs/variants/supermicro_x11_lga1151_series/recovery.md
@@ -1,6 +1,6 @@
 # Recovery
 
-**Please read the [overview page](../overview) first!**
+**Please read the [overview page](../overview.md) first!**
 
 ---
 
@@ -11,12 +11,12 @@ Following instruction was tested on:
 * X11SSH-TF v1.01
 
 For information how to identify your mainboard model pelase check
-[faq](../faq/#how-to-identify-my-mainboard-model).
+[faq](faq.md#how-to-identify-my-mainboard-model).
 
 Following documentation describes the process of recovering hardware from brick
 state with through BMC BIOS Update feature. This feature can be used also for
-[initial deployment](../initial-deployment) and [Firmware
-Update](../firmware-update).
+[initial deployment](initial-deployment.md) and [Firmware
+Update](firmware-update.md).
 
 ### Requirements
 
@@ -44,7 +44,7 @@ Supermicro proprietary closed source tools:
 * [Supermicro Update
   Manager](https://www.supermicro.com/en/solutions/management-software/supermicro-update-manager)
    please download and unpack archive.
-* [Backup](../../../dasharo-tools-suite/documentation/#bios-backup) or
+* [Backup](../../dasharo-tools-suite/documentation.md#bios-backup) or
   [Supermicro BIOS
   update](https://www.supermicro.com/en/support/resources/downloadcenter/firmware/MBD-X11SSH-TF/BIOS)
    please download and unpack archive.
diff --git a/docs/variants/supermicro_x11_lga1151_series/releases.md b/docs/variants/supermicro_x11_lga1151_series/releases.md
index 5d6b90f094..2a61fefe72 100644
--- a/docs/variants/supermicro_x11_lga1151_series/releases.md
+++ b/docs/variants/supermicro_x11_lga1151_series/releases.md
@@ -1,6 +1,6 @@
 # Dasharo compatible with Supermicro X11 LGA1151 Series
 
-**Please read the [overview page](../overview) first!**
+**Please read the [overview page](../overview.md) first!**
 
 <!--
 Following Release Notes describe status of Open Source Firmware development for
diff --git a/docs/variants/supermicro_x11_lga1151_series/test-matrix.md b/docs/variants/supermicro_x11_lga1151_series/test-matrix.md
index 6a2b91ae45..5898ece6ae 100644
--- a/docs/variants/supermicro_x11_lga1151_series/test-matrix.md
+++ b/docs/variants/supermicro_x11_lga1151_series/test-matrix.md
@@ -1,6 +1,6 @@
 # Test matrix - MSI Z690-A WIFI DDR4
 
-**Please read the [overview page](../overview) first!**
+**Please read the [overview page](../overview.md) first!**
 
 ## About
 
diff --git a/docs/variants/talos_2/test-matrix.md b/docs/variants/talos_2/test-matrix.md
index 79a10f366a..d573788836 100644
--- a/docs/variants/talos_2/test-matrix.md
+++ b/docs/variants/talos_2/test-matrix.md
@@ -13,9 +13,17 @@ subjected from before the release of the new binary.
 | 2.   | [Heads bootloader support][HDS]                   | HDS           | HDS001.001, HDS001.002               |
 | 3.   | [Device Tree][DVT]                                | DVT           | DVT001.001, DVT002.001               |
 
-[CBP]: ../../../unified-test-documentation/dasharo-compatibility/100-coreboot-base-port
-[HDS]: ../../../unified-test-documentation/dasharo-compatibility/31U-heads-bootloader-support
-[DVT]: ../../../unified-test-documentation/dasharo-compatibility/31W-device-tree
+[CBP]: https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/100-coreboot-base-port
+[PBT]: https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/31V-petitboot-payload-support
+[HDS]: https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/31U-heads-bootloader-support
+[DVT]: https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/31W-device-tree
+[UDT]: https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/31O-usb-detect
+[UBT]: https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/31N-usb-boot
+[LBT]: https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/308-debian-stable-and-ubuntu-lts-support
+[CPU]: https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/31T-cpu-status
+[USB]: https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/306-usb-hid-and-msc-support
+[NVM]: https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/312-nvme-support
+[DSP]: https://docs.dasharo.com/unified-test-documentation/dasharo-compatibility/31E-display-ports-and-lcd
 
 ## Module: Dasharo security
 
diff --git a/docs/variants/talos_2/tpm-support.md b/docs/variants/talos_2/tpm-support.md
index 802c7981a9..b1f5f6edb4 100644
--- a/docs/variants/talos_2/tpm-support.md
+++ b/docs/variants/talos_2/tpm-support.md
@@ -106,7 +106,7 @@ TPM2 log entry 9:
 ## Additional information
 
 The Module is available at the official
-[3mdeb store](https://3mdeb.com/shop/modules/tpm-1-2-compatible-with-raptor-computing-systems-talos-ii-mainboard/).
+[3mdeb store](https://shop.3mdeb.com/shop/modules/tpm-1-2-compatible-with-raptor-computing-systems-talos-ii-mainboard/).
 
 You can also buy the product by mailing us at:
 [shopping@3mdeb.com](mailto:shopping@3mdeb.com).
diff --git a/docs/variants/tuxedo_ibs15/installation.md b/docs/variants/tuxedo_ibs15/installation.md
index c5e0221426..544c7f181c 100644
--- a/docs/variants/tuxedo_ibs15/installation.md
+++ b/docs/variants/tuxedo_ibs15/installation.md
@@ -8,7 +8,7 @@ running flashrom on Ubuntu 20.04.
 
 ## Build flashrom
 
-Please follow generic guide for [Dasharo flashrom fork](../../../osf-trivia-list/deployment/#how-to-install-dasharo-flashrom-fork).
+Please follow generic guide for [Dasharo flashrom fork](../../osf-trivia-list/deployment.md#how-to-install-dasharo-flashrom-fork).
 
 ## Reading flash contents
 
diff --git a/mkdocs.yml b/mkdocs.yml
index 54314aa9b6..f5b05d6088 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -76,6 +76,14 @@ plugins:
         - variants/secure-firewall.md
         - variants/custom.md
         - variants/server.md
+        - variants/protectli_ptx01/hardware-matrix.md
+        - variants/protectli_ptx01/test-matrix.md
+        - variants/protectli_ptx01/building-manual.md
+        - variants/protectli_ptx01/firmware-update.md
+        - variants/protectli_ptx01/initial-deployment.md
+        - variants/protectli_ptx01/overview.md
+        - variants/protectli_ptx01/recovery.md
+        - variants/protectli_ptx01/releases.md
 nav:
   - 'Intro':
       - 'About Dasharo': index.md