more proofreading, adding links, and reorganizing the left-hand nav

Author: sarahxsanders

website/pages/docs/_meta.ts

@@ -19,6 +19,15 @@ const meta = {
   'constructing-types': '',
   'oneof-input-objects': '',
   'defer-stream': '',
+  '-- 2.5': {
+    type: 'separator',
+    title: 'Testing',
+  },
+  'testing-graphql-servers': '',
+  'testing-approaches': '',
+  'testing-operations': '',
+  'testing-resolvers': '',
+  'testing-best-practices': '',
   '-- 3': {
     type: 'separator',
     title: 'FAQ',

website/pages/docs/testing-approaches.mdx

@@ -23,6 +23,8 @@ When you write unit tests, you’re checking that the resolver:
 - Handles errors properly
 - Returns the correct result
 
+### When to use unit tests
+
 Unit tests are fast and provide tight feedback loops. They're especially useful when:
 
 - Developing new resolvers
@@ -151,17 +153,7 @@ Unit and integration tests are complementary, not competing.
 Start with unit tests when building new features, then layer in integration tests 
 to validate schema wiring and catch regressions as your API grows.
 
-## When E2E tests add value
-
-E2E tests simulate full-stack conditions. Use them when:
-
-- Testing authentication and authorization flows
-- Validating infrastructure behavior such as networking and retries
-- Coordinating between multiple services and APIs
-
-E2E tests are slower and require full setup, so reserve them for critical flows.
-
-## Choosing the right balance
+## Choose a testing approach
 
 There is no single correct approach to testing. Instead, a layered approach
 works best. In general:

website/pages/docs/testing-graphql-servers.mdx

@@ -3,8 +3,6 @@ title: Testing GraphQL Servers
 sidebarTitle: Testing GraphQL Servers
 ---
 
-import { Tabs } from 'nextra/components';
-
 # Testing GraphQL Servers
 
 ## Why testing matters
@@ -74,7 +72,7 @@ Beyond simulating failures, consider testing resilience patterns like retries or
 
 ## Next steps
 
-- Learn different types of tests for GraphQL servers to choose the right strategy for your project.
-- Explore how to test operations without running a server.
-- Understand how to unit test resolvers to catch logic errors early.
-- Apply best practices to scale testing to production.
+- Learn different [testing approaches](\..\testing-approaches.mdx) to choose the right strategy for your project.
+- Explore how to [test operations](\..\testing-operations.mdx) without running a server.
+- Understand how to [test resolvers](\..\testing-resolvers.mdx) to catch logic errors early.
+- Apply [best practices](\..\testing-best-practices.mdx) to scale testing to production.