docs: restructure directories and flatten sidebar navigation

Reorganize 7 old directories into 3 new ones: - test-lifecycle/ + test-authoring/ → writing-tests/ - advanced/ + customization-extensibility/ + extensions/ + experimental/ → extending/ - parallelism/ → execution/ (merged in) - advanced/performance-best-practices.md → guides/performance.md Rewrite sidebars.ts: - Remove emoji from all category labels - Promote Assertions to top-level (was buried 3 levels deep) - Flatten max nesting from 5 levels to 3 - Dissolve "Platform-Specific Scenarios" catch-all - Merge Extensibility + Customization + Extensions into one section Update all internal cross-references across 14 files. Add missing frontmatter to 5 assertion docs. Delete 4 stale _category_.json files.
thomhurst · thomhurst · Feb 26, 2026 · Feb 26, 2026 · Feb 26, 2026 · Feb 26, 2026
commit 93ec7e5ed85795ff939e3cf3126ef483e0fe3d55
diff --git a/docs/docs/assertions/awaiting.md b/docs/docs/assertions/awaiting.md
@@ -1,3 +1,7 @@
+---
+sidebar_position: 1
+---
+
 # Awaiting
 
 In TUnit you `await` your assertions, and this serves two purposes:

diff --git a/docs/docs/assertions/extensibility/extensibility-chaining-and-converting.md b/docs/docs/assertions/extensibility/extensibility-chaining-and-converting.md
@@ -1,3 +1,7 @@
+---
+sidebar_position: 3
+---
+
 # Chaining and Converting
 
 TUnit allows you to chain assertions that change the type being asserted, enabling fluent and expressive test code.

diff --git a/docs/docs/assertions/extensibility/extensibility-returning-items-from-await.md b/docs/docs/assertions/extensibility/extensibility-returning-items-from-await.md
@@ -1,3 +1,7 @@
+---
+sidebar_position: 4
+---
+
 # Returning Data via `await`
 
 Sometimes, you may want your assertion to return a value, such as an item found in a collection, so you can use it in further assertions or logic.

diff --git a/docs/docs/assertions/member-assertions.md b/docs/docs/assertions/member-assertions.md
@@ -1,3 +1,7 @@
+---
+sidebar_position: 12
+---
+
 # Member Assertions
 
 The `.Member()` method allows you to assert on object properties while maintaining the parent object's context for chaining. This is useful when you need to validate multiple properties of the same object.

diff --git a/docs/docs/assertions/regex-assertions.md b/docs/docs/assertions/regex-assertions.md
@@ -1,3 +1,7 @@
+---
+sidebar_position: 13
+---
+
 # Regex Assertions
 
 The `.Matches()` method allows you to validate strings against regular expressions and assert on capture groups, match positions, and match lengths. This is useful when you need to validate structured text like emails, phone numbers, dates, or extract specific parts of a string.

diff --git a/docs/docs/benchmarks/methodology.md b/docs/docs/benchmarks/methodology.md
@@ -285,6 +285,6 @@ Found an issue with the benchmarks? [Open an issue](https://github.com/thomhurst
 
 - [BenchmarkDotNet Documentation](https://benchmarkdotnet.org/articles/overview.html)
 - [.NET Performance Best Practices](https://learn.microsoft.com/en-us/dotnet/framework/performance/)
-- [TUnit Performance Best Practices](/docs/advanced/performance-best-practices)
+- [TUnit Performance Best Practices](/docs/guides/performance)
 
 *Last updated: {new Date().toISOString().split('T')[0]}*
diff --git a/docs/docs/comparison/_category_.json b/docs/docs/comparison/_category_.json
diff --git a/docs/docs/examples/_category_.json b/docs/docs/examples/_category_.json
diff --git a/docs/docs/parallelism/not-in-parallel.md → docs/docs/execution/not-in-parallel.md b/docs/docs/parallelism/not-in-parallel.md → docs/docs/execution/not-in-parallel.md
diff --git a/docs/docs/parallelism/parallel-groups.md → docs/docs/execution/parallel-groups.md b/docs/docs/parallelism/parallel-groups.md → docs/docs/execution/parallel-groups.md
diff --git a/docs/docs/parallelism/parallel-limiter.md → docs/docs/execution/parallel-limiter.md b/docs/docs/parallelism/parallel-limiter.md → docs/docs/execution/parallel-limiter.md
diff --git a/docs/docs/execution/test-filters.md b/docs/docs/execution/test-filters.md
@@ -35,7 +35,7 @@ or
 
 `dotnet run --treenode-filter /*/*/*/AcceptCookiesTest` - To run all tests with the name `AcceptCookiesTest`
 
-TUnit also supports filtering by your own [properties](../test-lifecycle/properties.md). So you could do:
+TUnit also supports filtering by your own [properties](../writing-tests/test-context.md#custom-properties). So you could do:
 
 `dotnet run --treenode-filter /*/*/*/*[MyFilterName=*SomeValue*]`
 

diff --git a/docs/docs/experimental/_category_.json b/docs/docs/experimental/_category_.json
diff --git a/...tion-extensibility/argument-formatters.md → docs/docs/extending/argument-formatters.md b/...tion-extensibility/argument-formatters.md → docs/docs/extending/argument-formatters.md
diff --git a/docs/docs/extensions/extensions.md → docs/docs/extending/built-in-extensions.md b/docs/docs/extensions/extensions.md → docs/docs/extending/built-in-extensions.md
diff --git a/docs/docs/extensions/code-coverage.md → docs/docs/extending/code-coverage.md b/docs/docs/extensions/code-coverage.md → docs/docs/extending/code-coverage.md
diff --git a/...n-extensibility/data-source-generators.md → .../docs/extending/data-source-generators.md b/...n-extensibility/data-source-generators.md → .../docs/extending/data-source-generators.md
diff --git a/...tomization-extensibility/display-names.md → docs/docs/extending/display-names.md b/...tomization-extensibility/display-names.md → docs/docs/extending/display-names.md
@@ -28,7 +28,7 @@ The above would generate two test cases with their respective display name as:
 - "Test with: foo 1 True"
 - "Test with: bar 2 False"
 
-If you have custom classes, you can combine this with [Argument Formatters](customization-extensibility/argument-formatters.md) to specify how to show them.
+If you have custom classes, you can combine this with [Argument Formatters](argument-formatters.md) to specify how to show them.
 
 :::info
 If you want to include a literal `$` in your display name, escape it as `$$`.  

diff --git a/docs/docs/experimental/dynamic-tests.md → docs/docs/extending/dynamic-tests.md b/docs/docs/experimental/dynamic-tests.md → docs/docs/extending/dynamic-tests.md
diff --git a/docs/docs/advanced/exception-handling.md → docs/docs/extending/exception-handling.md b/docs/docs/advanced/exception-handling.md → docs/docs/extending/exception-handling.md
diff --git a/docs/docs/advanced/extension-points.md → docs/docs/extending/extension-points.md b/docs/docs/advanced/extension-points.md → docs/docs/extending/extension-points.md
@@ -509,7 +509,7 @@ public class MyTests
 }
 ```
 
-See [Property Injection - Discovery Phase Initialization](../test-lifecycle/property-injection.md#discovery-phase-initialization) for detailed guidance and best practices.
+See [Property Injection - Discovery Phase Initialization](../writing-tests/property-injection.md#discovery-phase-initialization) for detailed guidance and best practices.
 
 ## Best Practices
 

diff --git a/.../customization-extensibility/libraries.md → docs/docs/extending/libraries.md b/.../customization-extensibility/libraries.md → docs/docs/extending/libraries.md
diff --git a/...cs/customization-extensibility/logging.md → docs/docs/extending/logging.md b/...cs/customization-extensibility/logging.md → docs/docs/extending/logging.md
diff --git a/docs/docs/advanced/test-variants.md → docs/docs/extending/test-variants.md b/docs/docs/advanced/test-variants.md → docs/docs/extending/test-variants.md
@@ -483,8 +483,7 @@ for (int i = 0; i < 10000; i++)  // Creates 10,000 tests!
 
 ## See Also
 
-- [Test Context](../test-lifecycle/test-context.md) - Understanding TestContext and StateBag
-- [Dynamic Tests](../experimental/dynamic-tests.md) - Pre-execution test generation
+- [Test Context](../writing-tests/test-context.md) - Understanding TestContext and StateBag
+- [Dynamic Tests](dynamic-tests.md) - Pre-execution test generation
 - [Retrying](../execution/retrying.md) - Built-in retry mechanism comparison
-- [Properties](../test-lifecycle/properties.md) - Test metadata and custom properties
-- [Event Subscribing](../test-lifecycle/event-subscribing.md) - Test lifecycle event receivers
+- [Event Subscribing](../writing-tests/event-subscribing.md) - Test lifecycle event receivers
diff --git a/docs/docs/extensions/_category_.json b/docs/docs/extensions/_category_.json
diff --git a/docs/docs/getting-started/installation.md b/docs/docs/getting-started/installation.md
@@ -81,8 +81,8 @@ dotnet run --configuration Release --coverage --report-trx
 **Important:** Do **not** install `coverlet.collector` or `coverlet.msbuild`. These packages are incompatible with TUnit because they require the VSTest platform, while TUnit uses the modern Microsoft.Testing.Platform.
 
 For more details, see:
-- [Code Coverage Documentation](../extensions/extensions.md#code-coverage)
-- [Extensions Overview](../extensions/extensions.md)
+- [Code Coverage Documentation](../extending/built-in-extensions.md#code-coverage)
+- [Extensions Overview](../extending/built-in-extensions.md)
 
 That's it. We're ready to write our first test.
 

diff --git a/docs/docs/getting-started/running-your-tests.md b/docs/docs/getting-started/running-your-tests.md
@@ -4,7 +4,7 @@ As TUnit is built on-top of the newer Microsoft.Testing.Platform, and combined w
 
 :::info
 
-Please note that for the coverage and trx report, you need to install [additional extensions](../extensions/extensions.md)
+Please note that for the coverage and trx report, you need to install [additional extensions](../extending/built-in-extensions.md)
 
 :::
 
@@ -98,16 +98,16 @@ To continue your journey with TUnit, explore these topics:
 
 **Core Testing Concepts:**
 - **[Assertions](../assertions/getting-started.md)** - Learn TUnit's fluent assertion syntax
-- **[Test Lifecycle](../test-lifecycle/setup.md)** - Set up and tear down test state with hooks
-- **[Data-Driven Testing](../test-authoring/arguments.md)** - Run tests with multiple input values
+- **[Test Lifecycle](../writing-tests/hooks-setup.md)** - Set up and tear down test state with hooks
+- **[Data-Driven Testing](../writing-tests/arguments.md)** - Run tests with multiple input values
 
 **Common Tasks:**
-- **[Mocking](../test-authoring/mocking/index.md)** - Use mocks and fakes in your tests
+- **[Mocking](../writing-tests/mocking/index.md)** - Use mocks and fakes in your tests
 - **[Best Practices](../guides/best-practices.md)** - Write maintainable, reliable tests
 - **[Cookbook](../guides/cookbook.md)** - Common testing patterns and recipes
 
 **Advanced Features:**
-- **[Parallelism](../parallelism/not-in-parallel.md)** - Control how tests run in parallel
+- **[Parallelism](../execution/not-in-parallel.md)** - Control how tests run in parallel
 - **[CI/CD Integration](../execution/ci-cd-reporting.md)** - Integrate TUnit into your pipeline
 
 Need help? Check the [Troubleshooting & FAQ](../troubleshooting.md) guide.

diff --git a/docs/docs/guides/best-practices.md b/docs/docs/guides/best-practices.md
@@ -658,7 +658,7 @@ TUnit is designed for performance at scale. Follow these guidelines to keep your
 ### Optimize Test Discovery
 
 - Use AOT mode for faster test discovery and lower memory usage
-- Keep data sources lightweight (see [Performance Best Practices](../advanced/performance-best-practices.md))
+- Keep data sources lightweight (see [Performance Best Practices](performance.md))
 - Limit matrix test combinations to avoid test explosion
 
 ### Optimize Test Execution
@@ -692,7 +692,7 @@ public async Task GetUserData()
 }
 ```
 
-For detailed performance guidance, see [Performance Best Practices](../advanced/performance-best-practices.md).
+For detailed performance guidance, see [Performance Best Practices](performance.md).
 
 ## Summary
 

diff --git a/docs/docs/guides/cookbook.md b/docs/docs/guides/cookbook.md
@@ -328,7 +328,7 @@ public class OrderServiceTUnitMocksTests
 - **AOT-compatible** — source-generated mocks work with Native AOT, trimming, and single-file publishing
 - **Built-in capture** — every `Arg<T>` automatically captures values for inspection via `.Values` and `.Latest`
 
-See the full [TUnit.Mocks documentation](../test-authoring/mocking) for setup, verification, argument matchers, and more.
+See the full [TUnit.Mocks documentation](../writing-tests/mocking) for setup, verification, argument matchers, and more.
 :::
 
 ### Partial Mocks and Spy Pattern

diff --git a/...cs/advanced/performance-best-practices.md → docs/docs/guides/performance.md b/...cs/advanced/performance-best-practices.md → docs/docs/guides/performance.md
diff --git a/docs/docs/migration/mstest.md b/docs/docs/migration/mstest.md
@@ -464,7 +464,7 @@ public async Task TestWithAttachment()
 }
 ```
 
-For more information about working with test artifacts, including session-level artifacts and best practices, see the [Test Artifacts guide](../test-lifecycle/artifacts.md).
+For more information about working with test artifacts, including session-level artifacts and best practices, see the [Test Artifacts guide](../writing-tests/artifacts.md).
 
 ### Assert.Fail
 
@@ -1124,4 +1124,4 @@ public class ContextTests
 
 TUnit includes built-in code coverage support. Do **not** use Coverlet — it is incompatible with TUnit's Microsoft.Testing.Platform.
 
-See the [Code Coverage guide](../extensions/code-coverage.md) for setup and configuration.
+See the [Code Coverage guide](../extending/code-coverage.md) for setup and configuration.
diff --git a/docs/docs/migration/nunit.md b/docs/docs/migration/nunit.md
@@ -394,7 +394,7 @@ public async Task TestWithAttachment()
 }
 ```
 
-For more information about working with test artifacts, including session-level artifacts and best practices, see the [Test Artifacts guide](../test-lifecycle/artifacts.md).
+For more information about working with test artifacts, including session-level artifacts and best practices, see the [Test Artifacts guide](../writing-tests/artifacts.md).
 
 ### Combinatorial Testing
 
@@ -840,4 +840,4 @@ public static class AssemblyHooks
 
 TUnit includes built-in code coverage support. Do **not** use Coverlet — it is incompatible with TUnit's Microsoft.Testing.Platform.
 
-See the [Code Coverage guide](../extensions/code-coverage.md) for setup and configuration.
+See the [Code Coverage guide](../extending/code-coverage.md) for setup and configuration.
diff --git a/docs/docs/migration/xunit.md b/docs/docs/migration/xunit.md
@@ -859,7 +859,7 @@ public class TestWithAttachments
 }
 ```
 
-For more information about working with test artifacts, including session-level artifacts and best practices, see the [Test Artifacts guide](../test-lifecycle/artifacts.md).
+For more information about working with test artifacts, including session-level artifacts and best practices, see the [Test Artifacts guide](../writing-tests/artifacts.md).
 
 ### Traits and Categories
 
@@ -1170,4 +1170,4 @@ public class UserServiceTests(DatabaseFixture dbFixture)
 
 TUnit includes built-in code coverage support. Do **not** use Coverlet — it is incompatible with TUnit's Microsoft.Testing.Platform.
 
-See the [Code Coverage guide](../extensions/code-coverage.md) for setup and configuration.
+See the [Code Coverage guide](../extending/code-coverage.md) for setup and configuration.
diff --git a/docs/docs/reference/command-line-flags.md b/docs/docs/reference/command-line-flags.md
@@ -2,7 +2,7 @@
 
 :::info
 
-Please note that for the coverage and trx report, you need to install [additional extensions](../extensions/extensions.md)
+Please note that for the coverage and trx report, you need to install [additional extensions](../extending/built-in-extensions.md)
 
 :::
 

diff --git a/docs/docs/troubleshooting.md b/docs/docs/troubleshooting.md
@@ -274,7 +274,7 @@ public class Fixture : IAsyncDiscoveryInitializer  // Changed from IAsyncInitial
 
 **Performance note:** Solution 1 is preferred because discovery happens frequently (IDE reloads, project switches, `--list-tests`), and you want to avoid expensive operations during discovery when possible.
 
-For detailed examples, see [Property Injection - Discovery Phase Initialization](test-lifecycle/property-injection.md#discovery-phase-initialization).
+For detailed examples, see [Property Injection - Discovery Phase Initialization](writing-tests/property-injection.md#discovery-phase-initialization).
 
 ## Test Execution Issues
 

diff --git a/.../docs/test-authoring/aot-compatibility.md → docs/docs/writing-tests/aot.md b/.../docs/test-authoring/aot-compatibility.md → docs/docs/writing-tests/aot.md
diff --git a/docs/docs/test-authoring/arguments.md → docs/docs/writing-tests/arguments.md b/docs/docs/test-authoring/arguments.md → docs/docs/writing-tests/arguments.md
diff --git a/docs/docs/test-lifecycle/artifacts.md → docs/docs/writing-tests/artifacts.md b/docs/docs/test-lifecycle/artifacts.md → docs/docs/writing-tests/artifacts.md
diff --git a/.../docs/test-authoring/class-data-source.md → docs/docs/writing-tests/class-data-source.md b/.../docs/test-authoring/class-data-source.md → docs/docs/writing-tests/class-data-source.md
@@ -8,7 +8,7 @@ It also takes an optional `Shared` argument, controlling whether you want to sha
 
 Avoid mutating the state of shared objects within tests. Because tests run concurrently, the execution order is unpredictable, and shared mutable state leads to flaky tests.
 
-The `SharedType` parameter controls how instances are shared across tests. See [Property Injection -- Sharing Strategies](../test-lifecycle/property-injection.md#sharing-strategies) for full details on the available options (`None`, `PerClass`, `PerAssembly`, `PerTestSession`, `Keyed`).
+The `SharedType` parameter controls how instances are shared across tests. See [Property Injection -- Sharing Strategies](property-injection.md#sharing-strategies) for full details on the available options (`None`, `PerClass`, `PerAssembly`, `PerTestSession`, `Keyed`).
 
 ## Initialization and TearDown
 If you need to do some initialization or teardown for when this object is created/disposed, simply implement the `IAsyncInitializer` and/or `IAsyncDisposable` interfaces

diff --git a/...cs/test-authoring/combined-data-source.md → ...ocs/writing-tests/combined-data-source.md b/...cs/test-authoring/combined-data-source.md → ...ocs/writing-tests/combined-data-source.md
diff --git a/docs/docs/test-authoring/culture.md → docs/docs/writing-tests/culture.md b/docs/docs/test-authoring/culture.md → docs/docs/writing-tests/culture.md
diff --git a/...cs/test-lifecycle/dependency-injection.md → ...ocs/writing-tests/dependency-injection.md b/...cs/test-lifecycle/dependency-injection.md → ...ocs/writing-tests/dependency-injection.md
@@ -30,7 +30,7 @@ public class MyTestClass(SomeDependency dep)
 }
 ```
 
-The `ClassConstructorMetadata` parameter provides context about the test being constructed, including the test's data-source arguments and metadata. You can also implement [event-subscribing interfaces](test-lifecycle/event-subscribing.md) on the same class to get notified when a test finishes — useful for disposing objects after the test completes.
+The `ClassConstructorMetadata` parameter provides context about the test being constructed, including the test's data-source arguments and metadata. You can also implement [event-subscribing interfaces](event-subscribing.md) on the same class to get notified when a test finishes — useful for disposing objects after the test completes.
 
 ## DependencyInjectionDataSourceAttribute
 

diff --git a/.../docs/test-lifecycle/event-subscribing.md → docs/docs/writing-tests/event-subscribing.md b/.../docs/test-lifecycle/event-subscribing.md → docs/docs/writing-tests/event-subscribing.md
diff --git a/docs/docs/test-authoring/explicit.md → docs/docs/writing-tests/explicit.md b/docs/docs/test-authoring/explicit.md → docs/docs/writing-tests/explicit.md
diff --git a/...docs/test-authoring/generic-attributes.md → .../docs/writing-tests/generic-attributes.md b/...docs/test-authoring/generic-attributes.md → .../docs/writing-tests/generic-attributes.md
diff --git a/docs/docs/test-lifecycle/cleanup.md → docs/docs/writing-tests/hooks-cleanup.md b/docs/docs/test-lifecycle/cleanup.md → docs/docs/writing-tests/hooks-cleanup.md
diff --git a/docs/docs/test-lifecycle/setup.md → docs/docs/writing-tests/hooks-setup.md b/docs/docs/test-lifecycle/setup.md → docs/docs/writing-tests/hooks-setup.md
diff --git a/...docs/test-lifecycle/lifecycle-overview.md → docs/docs/writing-tests/lifecycle.md b/...docs/test-lifecycle/lifecycle-overview.md → docs/docs/writing-tests/lifecycle.md
diff --git a/docs/docs/test-authoring/matrix-tests.md → docs/docs/writing-tests/matrix-tests.md b/docs/docs/test-authoring/matrix-tests.md → docs/docs/writing-tests/matrix-tests.md
diff --git a/...docs/test-authoring/method-data-source.md → .../docs/writing-tests/method-data-source.md b/...docs/test-authoring/method-data-source.md → .../docs/writing-tests/method-data-source.md
@@ -271,4 +271,4 @@ public class MyTests
 1. **Preferred:** Return predefined values that don't require initialization
 2. **Alternative:** Use `IAsyncDiscoveryInitializer` if you need discovery-time initialization
 
-See [Property Injection - Discovery Phase Initialization](../test-lifecycle/property-injection.md#discovery-phase-initialization) for detailed guidance and examples.
+See [Property Injection - Discovery Phase Initialization](property-injection.md#discovery-phase-initialization) for detailed guidance and examples.
diff --git a/docs/docs/test-authoring/mocking/advanced.md → docs/docs/writing-tests/mocking/advanced.md b/docs/docs/test-authoring/mocking/advanced.md → docs/docs/writing-tests/mocking/advanced.md
diff --git a/...st-authoring/mocking/argument-matchers.md → ...riting-tests/mocking/argument-matchers.md b/...st-authoring/mocking/argument-matchers.md → ...riting-tests/mocking/argument-matchers.md
diff --git a/docs/docs/test-authoring/mocking/http.md → docs/docs/writing-tests/mocking/http.md b/docs/docs/test-authoring/mocking/http.md → docs/docs/writing-tests/mocking/http.md
diff --git a/docs/docs/test-authoring/mocking/index.md → docs/docs/writing-tests/mocking/index.md b/docs/docs/test-authoring/mocking/index.md → docs/docs/writing-tests/mocking/index.md
diff --git a/docs/docs/test-authoring/mocking/logging.md → docs/docs/writing-tests/mocking/logging.md b/docs/docs/test-authoring/mocking/logging.md → docs/docs/writing-tests/mocking/logging.md
diff --git a/docs/docs/test-authoring/mocking/setup.md → docs/docs/writing-tests/mocking/setup.md b/docs/docs/test-authoring/mocking/setup.md → docs/docs/writing-tests/mocking/setup.md
diff --git a/...cs/test-authoring/mocking/verification.md → ...ocs/writing-tests/mocking/verification.md b/...cs/test-authoring/mocking/verification.md → ...ocs/writing-tests/mocking/verification.md
diff --git a/...ocs/test-authoring/nested-data-sources.md → ...docs/writing-tests/nested-data-sources.md b/...ocs/test-authoring/nested-data-sources.md → ...docs/writing-tests/nested-data-sources.md
diff --git a/docs/docs/test-authoring/depends-on.md → docs/docs/writing-tests/ordering.md b/docs/docs/test-authoring/depends-on.md → docs/docs/writing-tests/ordering.md
diff --git a/...docs/test-lifecycle/property-injection.md → .../docs/writing-tests/property-injection.md b/...docs/test-lifecycle/property-injection.md → .../docs/writing-tests/property-injection.md
diff --git a/docs/docs/test-authoring/skip.md → docs/docs/writing-tests/skip.md b/docs/docs/test-authoring/skip.md → docs/docs/writing-tests/skip.md
diff --git a/docs/docs/test-lifecycle/test-context.md → docs/docs/writing-tests/test-context.md b/docs/docs/test-lifecycle/test-context.md → docs/docs/writing-tests/test-context.md
diff --git a/docs/docs/test-authoring/test-data-row.md → docs/docs/writing-tests/test-data-row.md b/docs/docs/test-authoring/test-data-row.md → docs/docs/writing-tests/test-data-row.md
@@ -197,4 +197,4 @@ public class DatabaseTests
 - [Arguments Attribute](./arguments.md) - For compile-time constant data with inline metadata
 - [Method Data Sources](./method-data-source.md) - For dynamic test data generation
 - [Class Data Sources](./class-data-source.md) - For class-based test data
-- [Display Names](../customization-extensibility/display-names.md) - For global display name formatting
+- [Display Names](../extending/display-names.md) - For global display name formatting
diff --git a/docs/docs/test-authoring/things-to-know.md → docs/docs/writing-tests/things-to-know.md b/docs/docs/test-authoring/things-to-know.md → docs/docs/writing-tests/things-to-know.md
-Original file line number
+Diff line change
@@ Expand Up / @@ -509,7 +509,7 @@ public class MyTests @@
     }
     ```
-    See [Property Injection - Discovery Phase Initialization](../test-lifecycle/property-injection.md#discovery-phase-initialization) for detailed guidance and best practices.
+    See [Property Injection - Discovery Phase Initialization](../writing-tests/property-injection.md#discovery-phase-initialization) for detailed guidance and best practices.
     ## Best Practices
@@ Expand Down @@