From 3c56bfa99251d984a0215b03ba73e2766ea135da Mon Sep 17 00:00:00 2001 From: Alvin Bryan <107407814+alvinometric@users.noreply.github.com> Date: Thu, 13 Jun 2024 12:15:00 +0100 Subject: [PATCH] Fixed typo in `11 Principles` articles (#7381) Thanks @nunogois for catching it. --- .../docs/topics/feature-flags/feature-flag-best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/topics/feature-flags/feature-flag-best-practices.md b/website/docs/topics/feature-flags/feature-flag-best-practices.md index 6cf6585790..7a3c260932 100644 --- a/website/docs/topics/feature-flags/feature-flag-best-practices.md +++ b/website/docs/topics/feature-flags/feature-flag-best-practices.md @@ -4,7 +4,7 @@ title: 11 Principles for building and scaling feature flag systems import Figure from '@site/src/components/Figure/Figure.tsx' -Feature flags, sometimes called feature flags or feature switches, are a software development technique that allows engineering teams to decouple the release of new functionality from software deployments. With feature flags, developers can turn specific features or code segments on or off at runtime, without the need for a code deployment or rollback. Organizations who adopt feature flags see improvements in all key operational metrics for DevOps: Lead time to changes, mean-time-to-recovery, deployment frequency, and change failure rate. +Feature flags, sometimes called feature toggles or feature switches, are a software development technique that allows engineering teams to decouple the release of new functionality from software deployments. With feature flags, developers can turn specific features or code segments on or off at runtime, without the need for a code deployment or rollback. Organizations who adopt feature flags see improvements in all key operational metrics for DevOps: Lead time to changes, mean-time-to-recovery, deployment frequency, and change failure rate. There are 11 principles for building a large-scale feature flag system. These principles have their roots in distributed systems architecture and pay particular attention to security, privacy, and scale that is required by most enterprise systems. If you follow these principles, your feature flag system is less likely to break under load and will be easier to evolve and maintain.