From 9687575c86e08547f82ce119860cce00c70d18a3 Mon Sep 17 00:00:00 2001 From: Resynth Date: Fri, 17 Jul 2020 10:45:29 +0000 Subject: [PATCH] =?UTF-8?q?Change=20Riot=20=E2=86=92=20Element=20in=20docs?= =?UTF-8?q?/feature-flags.md?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/feature-flags.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/feature-flags.md b/docs/feature-flags.md index f2b29c9313..115c3b25f2 100644 --- a/docs/feature-flags.md +++ b/docs/feature-flags.md @@ -1,6 +1,6 @@ # Feature flags -When developing new features for Riot, we use feature flags to give us more +When developing new features for Element, we use feature flags to give us more flexibility and control over when and where those features are enabled. For example, flags make the following things possible: @@ -88,7 +88,7 @@ and configs. **Warning:** While this does mean the feature is enabled by default for -https://riot.im and official Riot Desktop builds, it will not be enabled by +https://app.element.io and official Element Desktop builds, it will not be enabled by default for self-hosted installs, custom desktop builds, etc. To cover those cases as well, the best options at the moment are converting to a regular setting defaulted on or to remove the flag. Simply enabling the existing flag by