From d1b2ec16f4e7d4ec759d411b6d9af3e3ecf1928a Mon Sep 17 00:00:00 2001
From: Kurt King <kurtaking@gmail.com>
Date: Tue, 29 Nov 2022 07:41:59 -0600
Subject: [PATCH] revert documentation back to original state

Signed-off-by: Kurt King <kurtaking@gmail.com>
Signed-off-by: Kurt King <kurt.king@procore.com>
---
 docs/plugins/feature-flags.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/docs/plugins/feature-flags.md b/docs/plugins/feature-flags.md
index c796058ace..738bc5e6aa 100644
--- a/docs/plugins/feature-flags.md
+++ b/docs/plugins/feature-flags.md
@@ -51,9 +51,6 @@ import { FeatureFlagged } from '@backstage/core-app-api'
   <PreviousFeatureComponent />
 </FeatureFlagged>
 ```
-
-If you use a `<FeatureFlagged>` component, you do not need to pass `featureFlags: [{ name: 'show-example-feature' }],` into the `createPlugin()` like done at the top of this page. Doing so will cause duplicate entries to appear under `Settings` > `Feature Flags`.
-
 ## Evaluating Feature Flag State
 
 It is also possible to test the feature flag state using the [FeatureFlags Api](https://backstage.io/docs/reference/core-plugin-api.featureflagsapi).