docs(angular-query): fix links (TanStack#9010)

Author: arnoud-dv

docs/framework/angular/guides/caching.md

@@ -3,7 +3,7 @@ id: caching
 title: Caching Examples
 ---
 
-> Please thoroughly read the [Important Defaults](../important-defaults) before reading this guide
+> Please thoroughly read the [Important Defaults](./important-defaults.md) before reading this guide
 
 ## Basic Example
 
@@ -23,7 +23,7 @@ Let's assume we are using the default `gcTime` of **5 minutes** and the default
 - A second instance of `injectQuery(() => ({ queryKey: ['todos'], queryFn: fetchTodos })` initializes elsewhere.
   - Since the cache already has data for the `['todos']` key from the first query, that data is immediately returned from the cache.
   - The new instance triggers a new network request using its query function.
-    - Note that regardless of whether both `fetchTodos` query functions are identical or not, both queries' [`status`](../../reference/injectQuery) are updated (including `isFetching`, `isPending`, and other related values) because they have the same query key.
+    - Note that regardless of whether both `fetchTodos` query functions are identical or not, both queries' [`status`](../../reference/injectQuery.md) are updated (including `isFetching`, `isPending`, and other related values) because they have the same query key.
   - When the request completes successfully, the cache's data under the `['todos']` key is updated with the new data, and both instances are updated with the new data.
 - Both instances of the `injectQuery(() => ({ queryKey: ['todos'], queryFn: fetchTodos })` query are destroyed and no longer in use.
   - Since there are no more active instances of this query, a garbage collection timeout is set using `gcTime` to delete and garbage collect the query (defaults to **5 minutes**).

docs/framework/angular/guides/invalidations-from-mutations.md

@@ -38,4 +38,4 @@ export class TodosComponent {
 
 [//]: # 'Example2'
 
-You can wire up your invalidations to happen using any of the callbacks available in the [`injectMutation` function](../mutations)
+You can wire up your invalidations to happen using any of the callbacks available in the [`injectMutation` function](../mutations.md)

docs/framework/angular/guides/mutation-options.md

@@ -5,7 +5,7 @@ title: Mutation Options
 
 One of the best ways to share mutation options between multiple places,
 is to use the `mutationOptions` helper. At runtime, this helper just returns whatever you pass into it,
-but it has a lot of advantages when using it [with TypeScript](../../typescript#typing-query-options).
+but it has a lot of advantages when using it [with TypeScript](../../typescript#typing-query-options.md).
 You can define all possible options for a mutation in one place,
 and you'll also get type inference and type safety for all of them.
 

docs/framework/angular/overview.md

@@ -110,4 +110,4 @@ interface Response {
 
 ## You talked me into it, so what now?
 
-- Learn TanStack Query at your own pace with our amazingly thorough [Walkthrough Guide](../installation) and [API Reference](../reference/functions/injectquery)
+- Learn TanStack Query at your own pace with our amazingly thorough [Walkthrough Guide](../installation.md) and [API Reference](../reference/functions/injectquery.md)