Fix broken "group cohort targeting" anchor on Feature Flags page

changelogs.mdx

@@ -1211,7 +1211,7 @@ Get all the latest updates in your inbox.
 
   Group cohorts follow the same ~2-hour refresh cadence as user cohorts.
 
-  [Learn more about Group Cohort Targeting →](/docs/featureflags#rollout-groups)
+  [Learn more about Group Cohort Targeting →](/docs/featureflags#targeting-&-identity-management)
 </Update>
 
 <Update label="2026-01-30">
@@ -1367,7 +1367,7 @@ Get all the latest updates in your inbox.
   - **Stay accurate:** Ensure flag decisions always reflect a user’s current state
   - **Reduce overhead:** No persistence, no backfills, no user history required
 
-  Ship more precise rollouts with runtime targeting. [Learn More →](/docs/featureflags#rollout-groups)
+  Ship more precise rollouts with runtime targeting. [Learn More →](/docs/featureflags#targeting-&-identity-management)
 
   Note: Runtime targeting is available as part of the Feature Flagging add-on for Enterprise customers. Reach out to your account team to learn more.
 </Update>

docs/featureflags.mdx

@@ -46,7 +46,7 @@ Enterprise customers who need Feature Flags without Experiments can [contact us]
   - **Cohort Filter** - a targeting method that uses Mixpanel cohorts to target users or group entities
   - **Runtime Filter** - a targeting method that checks data available at runtime against a Runtime Property or Runtime Event
   - **Rollout %** — percentage of the audience that receives the flag if they are eligible for the rollout group
-- **Runtime Properties** — any key/value attributes your application passes as properties in a `custom_properties` object nested within the flag-evaluation `context` at request time; the flag compares these values directly (e.g. equals / contains). They are not limited to device or platform values — any attribute your app can supply at request time, such as `organization_id`, works. Use Runtime Properties when you need **immediate**, per-request targeting on these values (e.g. organization- or account-based targeting). If periodic cohort refresh is acceptable, [group cohort targeting](#rollout-groups) is an alternative for org/account-based use cases.
+- **Runtime Properties** — any key/value attributes your application passes as properties in a `custom_properties` object nested within the flag-evaluation `context` at request time; the flag compares these values directly (e.g. equals / contains). They are not limited to device or platform values — any attribute your app can supply at request time, such as `organization_id`, works. Use Runtime Properties when you need **immediate**, per-request targeting on these values (e.g. organization- or account-based targeting). If periodic cohort refresh is acceptable, [group cohort targeting](#targeting-&-identity-management) is an alternative for org/account-based use cases.
 - **Runtime Events** — event-based targeting (e.g., user clicked button, completed purchase) used to target users immediately after they perform actions.
 - **Assignment vs Exposure** — assignment is deciding the variant; exposure is when your app **uses** that variant to render.
 - **Feature Flag API Request** - is a call made to a feature flag API to retrieve the current state or configuration of one or more feature flags. This request allows an application to dynamically determine which features should be active for a user
@@ -138,7 +138,7 @@ We support the following types of Flags:
 
     This method enables targeting users immediately based on arbitrary key/value attributes your application sends as properties in a `custom_properties` object nested within the flag-evaluation `context` at request time. The flag compares these values directly (e.g. equals / contains) for immediate, per-request decisions.
 
-    - Runtime Properties are **not** limited to device or platform values. They can be any attribute your frontend or app supplies at request time — for example, `platform`, `path`, `country`, or a custom value like `organization_id`. This makes them the right tool for **immediate**, per-request targeting, such as organization- or account-based targeting where you need decisions to take effect right away. If a periodic cohort refresh (approximately every 2 hours) is acceptable, [group cohort targeting](#rollout-groups) is an alternative approach for org/account-based use cases.
+    - Runtime Properties are **not** limited to device or platform values. They can be any attribute your frontend or app supplies at request time — for example, `platform`, `path`, `country`, or a custom value like `organization_id`. This makes them the right tool for **immediate**, per-request targeting, such as organization- or account-based targeting where you need decisions to take effect right away. If a periodic cohort refresh (approximately every 2 hours) is acceptable, [group cohort targeting](#targeting-&-identity-management) is an alternative approach for org/account-based use cases.
     - These attributes should be passed to the SDK as properties in a `custom_properties` object that is a sub-node of the feature flag `context`, at the time the flag is evaluated.
 
     #### Data types for runtime values