diff --git a/packages/docs/src/components/benchmarks/server-side-throughput-tests/Description.mdx b/packages/docs/src/components/benchmarks/server-side-throughput-tests/Description.mdx
index 5fc4390c..ce35dbf6 100644
--- a/packages/docs/src/components/benchmarks/server-side-throughput-tests/Description.mdx
+++ b/packages/docs/src/components/benchmarks/server-side-throughput-tests/Description.mdx
@@ -1 +1,3 @@
 Methodology: [Server Side Throughput Tests](/methodology/#server-side-throughput-tests).
+
+Measures how many requests each framework's server handler can process per second when rendering a 1,000-row table, and how long each response takes. Requests bypass network overhead to focus on server rendering performance.
diff --git a/packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx b/packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx
index 32ecc641..5e38c6b9 100644
--- a/packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx
+++ b/packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx
@@ -1,6 +1,7 @@
 Methodology: [SSR Load Test](/methodology/#ssr-load-test).
 
-Each runtime app renders the same 1,000-row, three-column table using ordinary
-`<a>` links. This compares server rendering under HTTP load without the extra work
-of rendering framework router link components. Requests still pass through each
-framework’s server routing. No browser runs and no links are clicked.
+Measures server throughput and response latency as concurrent connections increase, with each request rendering a 1,000-row table.
+
+This version uses ordinary `<a>` links to measure server rendering without the extra work of rendering framework router link components.
+
+Compare it with the [router link load test](/run-time/#ssr-router-link-load-test) to see how framework router link components affect server rendering performance.
diff --git a/packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx b/packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx
index 0ca266fc..4b0d28a3 100644
--- a/packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx
+++ b/packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx
@@ -1,4 +1,7 @@
 Methodology: [SSR Router Link Load Test](/methodology/#ssr-router-link-load-test).
 
-The same load test using framework router link components, showing how rendering
-those components affects server performance compared with ordinary HTML links.
+Measures server throughput and response latency as concurrent connections increase, with each request rendering a 1,000-row table using framework router link components.
+
+Compare it with the [plain link load test](/run-time/#ssr-load-test) to see how these components affect server rendering performance. These tests make HTTP requests only; they do not measure browser navigation or prefetching.
+
+Frameworks without a router link component are excluded.
diff --git a/packages/docs/src/components/setup/RunTimeSetup.mdx b/packages/docs/src/components/setup/RunTimeSetup.mdx
index 73f72802..36600fb0 100644
--- a/packages/docs/src/components/setup/RunTimeSetup.mdx
+++ b/packages/docs/src/components/setup/RunTimeSetup.mdx
@@ -1,4 +1,5 @@
-Runtime apps implement comparable benchmark routes across frameworks. See [Default
-Benchmark Setup](/methodology/#default-benchmark-setup) for the shared environment
-and each framework's build tool and adapter. Test-specific differences are
-documented in the linked methodology sections below.
+Run Time benchmarks use each meta-framework’s `app-*` package.
+
+Currently, each test uses a different route in its app, configured to meet each test's requirements.
+
+See [Default Benchmark Setup](/methodology/#default-benchmark-setup) for the base set-up. Each test's specific setup is linked in the methodology with links in each section.