diff --git a/docs/sources/reference/components/loki.rules.kubernetes.md b/docs/sources/reference/components/loki.rules.kubernetes.md
index ccb822271d..89f74c541a 100644
--- a/docs/sources/reference/components/loki.rules.kubernetes.md
+++ b/docs/sources/reference/components/loki.rules.kubernetes.md
@@ -1,4 +1,5 @@
 ---
+canonical: https://grafana.com/docs/alloy/latest/reference/components/loki.rules.kubernetes/
 title: loki.rules.kubernetes
 labels:
   stage: experimental
diff --git a/docs/sources/reference/config-blocks/remotecfg.md b/docs/sources/reference/config-blocks/remotecfg.md
index afc85b493a..b5766b1563 100644
--- a/docs/sources/reference/config-blocks/remotecfg.md
+++ b/docs/sources/reference/config-blocks/remotecfg.md
@@ -1,5 +1,5 @@
 ---
-canonical: remotecfgs://grafana.com/docs/alloy/latest/reference/config-blocks/remotecfg/
+canonical: https://grafana.com/docs/alloy/latest/reference/config-blocks/remotecfg/
 description: Learn about the remotecfg configuration block
 menuTitle: remotecfg
 title: remotecfg block
diff --git a/docs/sources/shared/stability/experimental.md b/docs/sources/shared/stability/experimental.md
index 6028ba3cdd..ca64f2e8d6 100644
--- a/docs/sources/shared/stability/experimental.md
+++ b/docs/sources/shared/stability/experimental.md
@@ -8,4 +8,4 @@ headless: true
 > components are subject to frequent breaking changes, and may be removed with
 > no equivalent replacement.
 
-[experimental]: ../../../stability/#experimental
+[experimental]: https://grafana.com/docs/release-life-cycle/
diff --git a/docs/sources/stability.md b/docs/sources/stability.md
deleted file mode 100644
index 20da5017b2..0000000000
--- a/docs/sources/stability.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-canonical: https://grafana.com/docs/alloy/latest/stability/
-description: Alloy features fall into one of three stability categories, experimental, public preview, or generally available
-title: Stability
-weight: 600
-_build:
-  list: false
-noindex: true
----
-
-# Stability
-
-Stability of functionality usually refers to the stability of a _use case,_ such as collecting and forwarding OpenTelemetry metrics.
-
-Features within the {{< param "FULL_PRODUCT_NAME" >}} project will fall into one of three stability categories:
-
-* **Experimental**: A new use case is being explored.
-* **Public preview**: Functionality covering a use case is being matured.
-* **Generally available**: Functionality covering a use case is believed to be stable.
-
-The default stability is stable.
-Features are explicitly marked as experimental or public preview if they aren't stable.
-
-## Experimental
-
-The **experimental** stability category is used to denote that maintainers are
-exploring a new use case, and would like feedback.
-
-* Experimental features are subject to frequent breaking changes.
-* Experimental features can be removed with no equivalent replacement.
-* Experimental features may require enabling feature flags to use.
-
-Unless removed, experimental features eventually graduate to public preview.
-
-## Public preview
-
-The **public preview** stability category is used to denote a feature which is being matured.
-
-* Beta features are subject to occasional breaking changes.
-* Beta features can be replaced by equivalent functionality that covers the same use case.
-* Beta features can be used without enabling feature flags.
-
-Unless replaced with equivalent functionality, public preview features eventually graduate to generally available.
-
-## Generally available
-
-The **generally available** stability category is used to denote a feature as stable.
-
-* Breaking changes to stable features are rare, and will be well-documented.
-* If new functionality is introduced to replace existing stable functionality, deprecation and removal timeline will be well-documented.
-* Stable features can be used without enabling feature flags.