From 1f6c91b5174205bfd52faede88437d01386cb17a Mon Sep 17 00:00:00 2001 From: olav Date: Tue, 1 Feb 2022 15:52:21 +0100 Subject: [PATCH] docs: link directly to the markdown file Co-authored-by: Thomas Heartman --- website/docs/advanced/feature-toggle-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/advanced/feature-toggle-types.md b/website/docs/advanced/feature-toggle-types.md index ad50510fea..22cdd35177 100644 --- a/website/docs/advanced/feature-toggle-types.md +++ b/website/docs/advanced/feature-toggle-types.md @@ -33,7 +33,7 @@ Here's the list of the feature toggle types that Unleash supports together with You can mark feature toggles as `stale`. This is a way to deprecate a feature toggle without removing the active configuration for connected applications. Use this to signal that you should stop using the feature in your applications. Stale toggles will show as stale in the ["technical debt dashboard"](../user_guide/technical_debt). -When you mark a toggle as stale, Unleash will emit an event. You can use [an addon](/addons) to integrate this with your systems, for instance to post a message in a Slack channel. +When you mark a toggle as stale, Unleash will emit an event. You can use [an addon](../addons/addons.md) to integrate this with your systems, for instance to post a message in a Slack channel. Additionally, with some extra work, you can also use the `stale` property to: