From 707b09bb1895251aafa552e2507c8dc6458ad7f5 Mon Sep 17 00:00:00 2001
From: Niklas <mc.taucher2003@gmail.com>
Date: Fri, 23 Sep 2022 18:21:41 +0000
Subject: [PATCH] Revise contributed suggestion

Bring closer to tone and style, and use the full
name of the specific API.
---
 doc/administration/feature_flags.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/doc/administration/feature_flags.md b/doc/administration/feature_flags.md
index c96a398bb77e2..4f8f7c22a554b 100644
--- a/doc/administration/feature_flags.md
+++ b/doc/administration/feature_flags.md
@@ -27,8 +27,9 @@ Features behind flags can be gradually rolled out, typically:
 1. The feature flag is removed.
 
 These features can be enabled and disabled to allow or prevent users from using
-them. It can be done by GitLab administrators with access to GitLab Rails
-console.
+them. It can be done by GitLab administrators with access to the
+[Rails console](#how-to-enable-and-disable-features-behind-flags) or the
+[Feature flags API](../api/features.md).
 
 When you disable a feature flag, the feature is hidden from users and all of the functionality is turned off.
 For example, data is not recorded and services do not run.
-- 
GitLab