docs: fix link to new reference page

Author: x0rgus

docs/docs/feature-flag-lifecycle/long-lived-flags.md

@@ -29,7 +29,7 @@ if (flagsmith.hasFeature("maintenance_mode")) {
 
 ### 2. Feature Management
 
-Use flags with [segments](/basic-features/segments.md) to control feature access:
+Use flags with [segments](./segments.md) to control feature access:
 
 - Toggle features by subscription tier
 - Enable features for specific user groups

docs/docs/feature-flag-lifecycle/short-lived-flags.md

@@ -16,15 +16,15 @@ The most common use case for short-lived flags is to decouple feature deployment
 1. Create and implement the flag while developing the feature
 2. Deploy the code with the feature behind the flag
 3. Test the feature in production with limited exposure
-4. Gradually roll out to more users using [segments](/basic-features/segments.md)
+4. Gradually roll out to more users using [segments](./segments.md)
 5. Once fully rolled out, remove the flag
 
 ### 2. A/B Testing and Experimentation
 
 Short-lived flags are perfect for temporary experiments:
 
 1. Create a [multivariate flag](/basic-features/managing-features.md#multi-variate-flags) for your test variants
-2. Run your experiment using [percentage splits](/basic-features/segments.md#operator-details)
+2. Run your experiment using [percentage splits](./segments.md#special-operators)
 3. Collect data through your analytics platform
 4. Once the experiment concludes, implement the winning variant
 5. Remove the flag