From 8fb137cb409764ef5b1113e4f1539e238cddecf7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ivar=20Conradi=20=C3=98sthus?= Date: Fri, 22 Oct 2021 09:31:57 +0200 Subject: [PATCH] Update feature-toggle-types.md --- websitev2/docs/advanced/feature-toggle-types.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/websitev2/docs/advanced/feature-toggle-types.md b/websitev2/docs/advanced/feature-toggle-types.md index 431f101900..0122bc4d06 100644 --- a/websitev2/docs/advanced/feature-toggle-types.md +++ b/websitev2/docs/advanced/feature-toggle-types.md @@ -19,7 +19,7 @@ Feature toggle types currently supported by Unleash: ### Deprecate a feature toggle {#deprecate-a-feature-toggle} -Feature toggles can now also be marked as `stale` (deprecated). This allows us to clearly signal that we should stop using the feature toggle in our applications. +Feature toggles can now also be marked as `stale`. You can think of this as a way to deprecate a feature toggle, without removing the active configuration for connected applications. This allows us to clearly signal that we should stop using the feature toggle in our applications. The `stale` property can utilized to help us manage "feature toggle debt" in various ways: