docs: also add benchmarking in tab nav

Author: riteshshukla04

README.md

@@ -375,7 +375,7 @@ These numbers are **without prefetch** — a common misconception is that nitro-
 | Average (10 runs) | 192 ms | 147 ms | **23.2%** (1.30×) |
 | Median (10 runs) | 190 ms | 148 ms | **22.0%** (1.28×) |
 
-Try it yourself in the example app → **Benchmark V2** (release build). See [Benchmarks](https://fetch.margelo.com/docs/benchmarks) for the method and full table. Concerns about the benchmark? [Open an issue](https://github.com/margelo/react-native-nitro-fetch/issues).
+Try it yourself in the example app. See [Benchmarks](https://fetch.margelo.com/docs/benchmarks) for the method and full table. Concerns about the benchmark? [Open an issue](https://github.com/margelo/react-native-nitro-fetch/issues).
 
 ## Limitations & Alternatives
 

docs-website/docs/benchmarks.md

@@ -27,6 +27,6 @@ Example 10-run head-to-head (14 public endpoints, alternating order, stall-corre
 | **Median** | **190** | **148** | **22.0%** | **1.28×** | 22 total |
 | **Average** | **192** | **147** | **23.2%** | **1.30×** | — |
 
-Numbers are device-, network-, and time-specific. **Try it yourself** in the example app → **Benchmark V2** (`example/src/screens/BenchmarkV2Screen.tsx`), on a release build.
+Numbers are device-, network-, and time-specific. **Try it yourself** in the example app → the **Benchmark V2** screen (or the **Benchmark** section in the tab navigator), on a release build.
 
 If you have any concerns about the benchmark methodology, please [open an issue](https://github.com/margelo/react-native-nitro-fetch/issues).