docs: fix TanStack capitalization (#10128)

Author: pavan-sh

docs/framework/react/guides/migrating-to-v5.md

@@ -228,7 +228,7 @@ Since the only supported syntax now is the object syntax, this rule is no longer
 
 We have removed the `keepPreviousData` option and `isPreviousData` flag as they were doing mostly the same thing as `placeholderData` and `isPlaceholderData` flag.
 
-To achieve the same functionality as `keepPreviousData`, we have added previous query `data` as an argument to `placeholderData` which accepts an identity function. Therefore you just need to provide an identity function to `placeholderData` or use the included `keepPreviousData` function from Tanstack Query.
+To achieve the same functionality as `keepPreviousData`, we have added previous query `data` as an argument to `placeholderData` which accepts an identity function. Therefore you just need to provide an identity function to `placeholderData` or use the included `keepPreviousData` function from TanStack Query.
 
 > A note here is that `useQueries` would not receive `previousData` in the `placeholderData` function as argument. This is due to a dynamic nature of queries passed in the array, which may lead to a different shape of result from placeholder and queryFn.
 
@@ -250,7 +250,7 @@ const {
 });
 ```
 
-An identity function, in the context of Tanstack Query, refers to a function that always returns its provided argument (i.e. data) unchanged.
+An identity function, in the context of TanStack Query, refers to a function that always returns its provided argument (i.e. data) unchanged.
 
 ```ts
 useQuery({

docs/framework/react/guides/prefetching.md

@@ -369,7 +369,7 @@ Because data fetching in the component tree itself can easily lead to request wa
 
 In this approach, you explicitly declare for each _route_ what data is going to be needed for that component tree, ahead of time. Because Server Rendering has traditionally needed all data to be loaded before rendering starts, this has been the dominating approach for SSR'd apps for a long time. This is still a common approach and you can read more about it in the [Server Rendering & Hydration guide](./ssr.md).
 
-For now, let's focus on the client side case and look at an example of how you can make this work with [Tanstack Router](https://tanstack.com/router). These examples leave out a lot of setup and boilerplate to stay concise, you can check out a [full React Query example](https://tanstack.com/router/latest/docs/framework/react/examples/basic-react-query-file-based) over in the [Tanstack Router docs](https://tanstack.com/router/latest/docs).
+For now, let's focus on the client side case and look at an example of how you can make this work with [TanStack Router](https://tanstack.com/router). These examples leave out a lot of setup and boilerplate to stay concise, you can check out a [full React Query example](https://tanstack.com/router/latest/docs/framework/react/examples/basic-react-query-file-based) over in the [TanStack Router docs](https://tanstack.com/router/latest/docs).
 
 When integrating at the router level, you can choose to either _block_ rendering of that route until all data is present, or you can start a prefetch but not await the result. That way, you can start rendering the route as soon as possible. You can also mix these two approaches and await some critical data, but start rendering before all the secondary data has finished loading. In this example, we'll configure an `/article` route to not render until the article data has finished loading, as well as start prefetching comments as soon as possible, but not block rendering the route if comments haven't finished loading yet.
 

docs/reference/notifyManager.md

@@ -3,7 +3,7 @@ id: NotifyManager
 title: NotifyManager
 ---
 
-The `notifyManager` handles scheduling and batching callbacks in Tanstack Query.
+The `notifyManager` handles scheduling and batching callbacks in TanStack Query.
 
 It exposes the following methods: