diff --git a/content/en/real_user_monitoring/browser/frustration_signals.md b/content/en/real_user_monitoring/browser/frustration_signals.md
index 635b15a32dcfe..f966f1694459b 100644
--- a/content/en/real_user_monitoring/browser/frustration_signals.md
+++ b/content/en/real_user_monitoring/browser/frustration_signals.md
@@ -32,6 +32,8 @@ Dead Clicks
 Error Clicks
 : A user clicks on an element right before a JavaScript error occurs.
 
+By enabling frustration signals, Datadog collects all three signal types by default.
+
 ## Requirements
 
 First, you need the Browser RUM SDK version >= 4.14.0.
@@ -137,18 +139,14 @@ For more information, see the [Real User Monitoring Monitor documentation][9].
 
 ## Troubleshooting
 
-### Why is a rage click not created when a user presses a key (like Delete) on the keyboard?
+### Rage clicks are not being created when a user presses a key (like Delete) on the keyboard
 
 Frustration signals are generated from mouse clicks, not keyboard strokes.
 
-### Why does the side panel show that a session has a different number of frustration signals than in the event timeline?
+### The side panel does not show that a session has a different number of frustration signals than in the event timeline
 
 If a session is live, it is fetching information and may cause the banners to reflect a different number than those in the timeline.
 
-### Can I pick and choose what signals to track?
-
-By enabling frustration signals, Datadog collects all three signal types by default. Contact your [Customer Success Manager][10] for more information.
-
 <div class="alert alert-warning">
 To provide feedback or submit a feature request, contact <a href="/help/">Datadog Support</a>.
 </div>
diff --git a/content/en/real_user_monitoring/guide/setup-feature-flag-data-collection.md b/content/en/real_user_monitoring/guide/setup-feature-flag-data-collection.md
index ca44e903badf4..93befdbede690 100644
--- a/content/en/real_user_monitoring/guide/setup-feature-flag-data-collection.md
+++ b/content/en/real_user_monitoring/guide/setup-feature-flag-data-collection.md
@@ -819,17 +819,15 @@ Filtering your **Errors** with the `@feature_flags.{flag_name}` attribute, you c
 
 ## Troubleshooting
 
-### Why doesn't my feature flag data reflect what I expect to see?
+### Feature flag data is not reflecting the expected information
 Feature flags show up in the context of events where they are evaluated, meaning they should show up on the views that the feature flag code logic is run on.
 
 Depending on how you've structured your code and set up your feature flags, you may see unexpected feature flags appear in the context of some events.
 
 For example, to see what **Views** your feature flag is being evaluated on, you can use the RUM Explorer to make a similar query:
 
-
 {{< img src="real_user_monitoring/guide/setup-feature-flag-data-collection/feature_flag_view_query.png" alt="Search Views for Feature Flags in the RUM Explorer" style="width:75%;">}}
 
-
 Here are a few examples of reasons why your feature flag is being evaluated on unrelated Views that can help with your investigations:
 
 - A common react component that appears on multiple pages which evaluates feature flags whenever they run.