From e8fee92838915d80c2ab2ead476be852f55eb8b2 Mon Sep 17 00:00:00 2001
From: Mateusz Kwasniewski <kwasniewski.mateusz@gmail.com>
Date: Fri, 6 Sep 2024 12:45:06 +0200
Subject: [PATCH] feat: explain complete feature name (#8120)

---
 .../FeatureLifecycle/MarkCompletedDialogue.tsx       | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/frontend/src/component/feature/FeatureView/FeatureOverview/FeatureLifecycle/MarkCompletedDialogue.tsx b/frontend/src/component/feature/FeatureView/FeatureOverview/FeatureLifecycle/MarkCompletedDialogue.tsx
index a405a9f89a..4cd9188e31 100644
--- a/frontend/src/component/feature/FeatureView/FeatureOverview/FeatureLifecycle/MarkCompletedDialogue.tsx
+++ b/frontend/src/component/feature/FeatureView/FeatureOverview/FeatureLifecycle/MarkCompletedDialogue.tsx
@@ -72,12 +72,12 @@ export const MarkCompletedDialogue = ({
                         mb: 4,
                     }}
                 >
-                    Marking the feature flag as complete does not affect any
-                    configuration, but it moves the feature flag into it’s next
-                    life cycle stage and is an indication that you have learned
-                    what you needed in order to progress with the feature. It
-                    serves as a reminder to start cleaning up the feature flag
-                    and removing it from the code.
+                    Marking the feature <b>{featureId}</b> as complete does not
+                    affect any configuration, but it moves the feature flag into
+                    it’s next life cycle stage and is an indication that you
+                    have learned what you needed in order to progress with the
+                    feature. It serves as a reminder to start cleaning up the
+                    feature flag and removing it from the code.
                 </Box>
 
                 <Typography