From 67f9277b2554d0e97efc3f5bc314c00dea5a96c3 Mon Sep 17 00:00:00 2001
From: sebastian-unleash <101799760+sebastian-unleash@users.noreply.github.com>
Date: Tue, 3 May 2022 10:16:02 +0200
Subject: [PATCH] docs: Add link to kill switch best practices blog post.
 (#1554)

---
 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 22cdd35177..eadf8a7581 100644
--- a/website/docs/advanced/feature-toggle-types.md
+++ b/website/docs/advanced/feature-toggle-types.md
@@ -26,7 +26,7 @@ Here's the list of the feature toggle types that Unleash supports together with
 - **Release** -  Enable trunk-based development for teams practicing Continuous Delivery. _Expected lifetime 40 days_
 - **Experiment** - Perform multivariate or A/B testing. _Expected lifetime 40 days_
 - **Operational** - Control operational aspects of the system's behavior. _Expected lifetime 7 days_
-- **Kill switch** - Gracefully degrade system functionality. _(permanent)_
+- **Kill switch** - Gracefully degrade system functionality. You can read about [kill switch best practices](https://www.getunleash.io/blog/kill-switches-best-practice) on our blog. _(permanent)_
 - **Permission** - Change the features or product experience that certain users receive. _(permanent)_
 
 ## Deprecating feature toggles {#deprecate-a-feature-toggle}