chore: fix links that were moved (#10520)

runspired · web-flow · commit bff6629f9ffa · 2026-04-20T12:54:38.000-07:00
diff --git a/guides/index.md b/guides/index.md
@@ -183,7 +183,7 @@ heavy immutability tricks such as spread, slice, and map.
 
 ## Mutation Management {#mutations}
 
-[Mutation](./the-manual/concepts/mutations.md) is handled within controlled contexts. The data to edit is "checked out" for editing, giving access to a mutable version. Local edits are seamlessly preserved if the user navigates away and returns without saving, and the changes are buffered from appearing elsewhere in your app until they are also committed to the server.
+[Mutation](./the-manual/mutations) is handled within controlled contexts. The data to edit is "checked out" for editing, giving access to a mutable version. Local edits are seamlessly preserved if the user navigates away and returns without saving, and the changes are buffered from appearing elsewhere in your app until they are also committed to the server.
 
 ```ts
 import { checkout } from '@warp-drive/core/reactive';
diff --git a/guides/migrating/index.md b/guides/migrating/index.md
@@ -247,8 +247,8 @@ const user = store.push<User>({ // [!code ++]
 **Additional Resources**
 
 - [Typing Requests](/guides/the-manual/requests/typing-requests)
-- [Typing Models](/guides/the-manual/misc/typescript/typing-models)
-- [Why Brands](/guides/the-manual/misc/typescript/why-brands)
+- [Typing Models](/guides/the-manual/typescript/typing-models)
+- [Why Brands](/guides/the-manual/typescript/why-brands)
 
 ### Step 6 - fix other type issues that arise
 
diff --git a/guides/migrating/two-store-migration.md b/guides/migrating/two-store-migration.md
@@ -30,13 +30,13 @@ Mirror packages are available for versions `^4.13.0 | >=5.3.8`.
 
 ## TypeScript
 
-All mirror packages are also versions which ship their own types. To use those types, configure your `tsconfig.json` to be able to find them [as shown here](../the-manual/misc/typescript/configuration.md#using-native-types), adding the appropriate `-mirror` appendage to each package name (PS: you can have distinct types for both your older and your newer version!).
+All mirror packages are also versions which ship their own types. To use those types, configure your `tsconfig.json` to be able to find them [as shown here](../the-manual/typescript/configuration.md#using-native-types), adding the appropriate `-mirror` appendage to each package name (PS: you can have distinct types for both your older and your newer version!).
 
 ## Caveat Emptor
 
 Utilizing the two-store approach has a few tradeoffs:
 
-1. If you want compatible type signatures for use by your components, you should upgrade your app to make use of native types first, likely using the [types-package approach](../the-manual/misc/typescript/installation.md#using-types-packages).
+1. If you want compatible type signatures for use by your components, you should upgrade your app to make use of native types first, likely using the [types-package approach](../the-manual/typescript/installation.md#using-types-packages).
 
 In fact, it is likely that if you want typescript for the v2 store that you are *forced* to remove the `@types/ember*` packages from your project entirely and upgrade to using native types for ember-source and ember-data. This is because the native types for WarpDrive depend on ember's native types.
 
diff --git a/guides/the-manual/caching/index.md b/guides/the-manual/caching/index.md
@@ -277,7 +277,7 @@ By default, The Graph uses **upsert semantics** for a relationship payload with
 
 This means that a field being absent from a relationship payload is semantically different from that field being present but with a value of `null` or an empty array. Being not-present means we do not replace the existing value.
 
-The Graph also has the ability to receive op-codes that deliver more granular modifications to relationships to add or remove specific values. For instance, if your application were to use WebSockets to receive streaming changes to a relationship, those changes could be applied directly without needing to fully replace the existing value. We'll cover these operations in the guide for [RealTime Support](../concepts/realtime.md).
+The Graph also has the ability to receive op-codes that deliver more granular modifications to relationships to add or remove specific values. For instance, if your application were to use WebSockets to receive streaming changes to a relationship, those changes could be applied directly without needing to fully replace the existing value. We'll cover these operations in the guide for [RealTime Support](../realtime).
 
 ## What about Mutation?
 
diff --git a/guides/the-manual/misc/terminology.md b/guides/the-manual/misc/terminology.md
@@ -92,7 +92,7 @@ However, every specific automobile belongs to a more specialized type. For insta
 }
 ```
 
-In this case, we can refer to both type `pickup` and type `racecar` as satisfying type `automobile`. We refer to `pickup` and `racecar` as "concrete types" and to `automobile` as an `abstract type`. For more, read about [polymorphism in depth](./relational-data/features/polymorphism.md).
+In this case, we can refer to both type `pickup` and type `racecar` as satisfying type `automobile`. We refer to `pickup` and `racecar` as "concrete types" and to `automobile` as an `abstract type`. For more, read about [polymorphism in depth](./../relational-data/features/polymorphism.md).
 
 ### Field
 
diff --git a/guides/the-manual/reactivity/misc.md b/guides/the-manual/reactivity/misc.md
@@ -13,8 +13,8 @@ Data in the cache is conceptualized as belonging to one of three forms
 
 Each form of data can be accessed and managed reactively through one of two modes
 
-- *(upcoming, default in v6)* [PolarisMode](../../schemas/resources/polaris-mode.md)
-- *(current, default in v5)* [LegacyMode](../../schemas/resources/legacy-mode.md)
+- *(upcoming, default in v6)* [PolarisMode](./../schemas/resources/polaris-mode.md)
+- *(current, default in v5)* [LegacyMode](./../schemas/resources/legacy-mode.md)
 
 These modes are interoperable. The reactive object (record) for a resource in PolarisMode can relate to
 a record in LegacyMode and vice-versa. This interoperability is true whether the record in LegacyMode is
diff --git a/guides/the-manual/relational-data/configuration/many-to-many.md b/guides/the-manual/relational-data/configuration/many-to-many.md
@@ -9,7 +9,7 @@ graph LR;
 
 > **Note** In our charts we use dotted lines for singular relationships and thick solid lines for collection relationships.
 
-Or, maybe more accurately since this is a [*reflexive*](../../terminology.md#reflexive) relationship:
+Or, maybe more accurately since this is a [*reflexive*](../../misc/terminology.md#reflexive) relationship:
 
 ```mermaid
 graph LR;
diff --git a/guides/the-manual/relational-data/index.md b/guides/the-manual/relational-data/index.md
@@ -6,7 +6,7 @@ title: Overview
 
 ## Feature Overview
 - [Inverses](./features/inverses.md)
-- [LinksMode](../links-mode.md)
+- [LinksMode](../misc/links-mode.md)
 - [Polymorphism](./features/polymorphism.md)
 
 <!--
@@ -42,4 +42,4 @@ title: Overview
 
 # Misc
 
-- [Terminology](../terminology.md#relationships)
+- [Terminology](../misc/terminology.md#relationships)

Original file line number	Diff line number	Diff line change
`@@ -92,7 +92,7 @@ However, every specific automobile belongs to a more specialized type. For insta`
`92`	`92`	`}`
`93`	`93`	```
`94`	`94`
`95`		-In this case, we can refer to both type `pickup` and type `racecar` as satisfying type `automobile`. We refer to `pickup` and `racecar` as "concrete types" and to `automobile` as an `abstract type`. For more, read about [polymorphism in depth](./relational-data/features/polymorphism.md).
	`95`	+In this case, we can refer to both type `pickup` and type `racecar` as satisfying type `automobile`. We refer to `pickup` and `racecar` as "concrete types" and to `automobile` as an `abstract type`. For more, read about [polymorphism in depth](./../relational-data/features/polymorphism.md).
`96`	`96`
`97`	`97`	`### Field`
`98`	`98`