diff --git a/docs/dasharo-naming-convention.md b/docs/dasharo-naming-convention.md
index cdd08de2bf..784ba84c90 100644
--- a/docs/dasharo-naming-convention.md
+++ b/docs/dasharo-naming-convention.md
@@ -38,7 +38,7 @@ Available options:
 
 - `platform`: Indicates the target platform for the package. Platform is
 mandatory in public names. Platform name should follow [supported hardware
-list](/variants/overview).
+list](variants/overview.md).
 - `edition`: Community | Pro | Enterprise (edition codes: DCP, DPP, DEP)
 
 - `release`: Rapid | Assured | LTS. Defines QA scope and support cadence. Codes
diff --git a/docs/osf-trivia-list/dasharo.md b/docs/osf-trivia-list/dasharo.md
index 4d07de6de1..e42be26bba 100644
--- a/docs/osf-trivia-list/dasharo.md
+++ b/docs/osf-trivia-list/dasharo.md
@@ -147,25 +147,6 @@ There is also a libre, POWER9-based server/workstation Talos II by Raptor
 Computing Systems, which also do not use any binary blobs, however it is more
 expensive than x86 platforms.
 
-## What is Dasharo non-LTS release?
-
-Dasharo non-LTS release is a release that is validated with a reduced set of
-tests. The non-LTS name is adopted from distributions which mark their Long
-Term Support (LTS) releases as extensively validated/higher quality assurance. For
-example see [Ubuntu documentation](https://ubuntu.com/about/release-cycle).
-
-The reduced set of tests includes the test cases marked with
-`minimal-regression` tag in the [OSFV
-repository](https://github.com/Dasharo/open-source-firmware-validation/blob/develop/docs/adding-and-naming-test-cases.md#test-workflow-tag-guidelines).
-Tagging the tests allow to run a subset of tests with given tag. Example
-command, how to run `minimal-regression` tests can be found
-[here](https://github.com/Dasharo/open-source-firmware-validation/blob/develop/README.md#running-regression-tests-with-additional-arguments).
-
-Dasharo releases which are not marked as non-LTS undergo a full set of
-regression tests applicable for a platform. To check results of the tests or
-the test scope for given release, visit [OSFV results
-repository](https://github.com/Dasharo/osfv-results).
-
 ## Why Dasharo?
 
 ### Open-source firmware ecosystem problems
diff --git a/docs/variants/msi_z690/releases.md b/docs/variants/msi_z690/releases.md
index 6c06d580a9..a9a7ce1ce4 100644
--- a/docs/variants/msi_z690/releases.md
+++ b/docs/variants/msi_z690/releases.md
@@ -25,8 +25,8 @@ For details about our release process please read
 
 ## v1.1.5 - 2025-09-18
 
-This is a [non-LTS
-release](../../osf-trivia-list/dasharo.md#what-is-dasharo-non-lts-release) and
+This is a [Rapid
+release](../../dasharo-naming-convention.md) and
 has a reduced scope of tests.
 
 Test results for this release can be found
diff --git a/docs/variants/msi_z790/releases.md b/docs/variants/msi_z790/releases.md
index a78063d36a..034df0c2fd 100644
--- a/docs/variants/msi_z790/releases.md
+++ b/docs/variants/msi_z790/releases.md
@@ -25,8 +25,8 @@ recommend seeing our [FAQ](../../unified/msi/faq.md).
 
 ## v0.9.3 - 2025-09-18
 
-This is a [non-LTS
-release](../../osf-trivia-list/dasharo.md#what-is-dasharo-non-lts-release) and
+This is a [Rapid
+release](../../dasharo-naming-convention.md) and
 has a reduced scope of tests.
 
 Test results for this release can be found