Convert Runtime Targeting to h4 heading in Feature Flags docs

[Copilot]

"Runtime Targeting" in the Feature Flags documentation was bold text instead of a heading, preventing anchor link generation and breaking the document outline.

Changes

• Changed **Runtime Targeting** to #### Runtime Targeting in /pages/docs/featureflags.mdx
• Establishes correct heading hierarchy: h3 "Rollout Groups" → h4 "Runtime Targeting"
• Generates anchor link #runtime-targeting for navigation

-**Runtime Targeting**
+#### Runtime Targeting

Original prompt

Fix Mixpanel docs page for Feature Flags to make “Runtime Targeting” a proper header with an anchor link.

Context:

• In the Mixpanel docs page at https://docs.mixpanel.com/docs/featureflags
• Right below the section “3. Rollout Groups”, there is currently a bold line reading “Runtime Targeting”.
• This should instead be a header with an anchor link.
• The header should be one size smaller than its parent section header (“3. Rollout Groups”).

Requirements:

1. Locate the source MDX file in the mixpanel/docs repository that generates https://docs.mixpanel.com/docs/featureflags.
2. In the “Rollout Groups” section, replace the bold “Runtime Targeting” line with an actual heading element appropriate for the doc’s heading hierarchy (one level smaller than the parent heading).
3. Ensure the heading renders with an anchor link (i.e., it is a markdown heading that the docs site turns into an id/anchor).
4. Ensure the resulting anchor is sensible (e.g., #runtime-targeting).
5. Update any surrounding formatting if needed so spacing looks correct.
6. Add/adjust any local links or table-of-contents entries if the docs system requires it.

Acceptance criteria:

• “Runtime Targeting” appears as a heading (not bold text) under “Rollout Groups”.
• The heading has an anchor link on the rendered docs site.
• The heading level is correct relative to “Rollout Groups”.
• A pull request is opened with the change and a clear description referencing issue Runtime targeting should be a header with an anchor link #2367.

Issue reference:

• Runtime targeting should be a header with an anchor link #2367

This pull request was created from Copilot chat.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Feb 10, 2026 0:10am

[joshua-koehler]

Run
git restore public/robots.txt .gitignore package-lock.json

All I want is the change to the page

[Copilot]

Run
git restore public/robots.txt .gitignore package-lock.json
...

Done. Reverted those files in commit 0b1c366. The PR now contains only the featureflags.mdx change.

[joshua-koehler]

LGTM, wish an h4 (Rollout Groups is an h3) wasn't assigned a number, but so it is. We need to anchor link to this frequently, so pros outweigh minor con, also in hindsight it's not that unnatural of a separation.