Skip to content

Commit 7cb634b

Browse files
authored
docs: typo (#8932)
1 parent bab9165 commit 7cb634b

File tree

4 files changed

+4
-4
lines changed

4 files changed

+4
-4
lines changed

docs/framework/react/guides/request-waterfalls.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -233,7 +233,7 @@ function GraphFeedItem({ feedItem }) {
233233
}
234234
```
235235

236-
The second query `getGraphDataById` is dependent on it's parent in two different ways. First of all, it doesn't ever happen unless the `feedItem` is a graph, and second, it needs an `id` from the parent.
236+
The second query `getGraphDataById` is dependent on its parent in two different ways. First of all, it doesn't ever happen unless the `feedItem` is a graph, and second, it needs an `id` from the parent.
237237

238238
```
239239
1. |> getFeed()

docs/framework/react/guides/ssr.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -165,7 +165,7 @@ Setting up the full hydration solution is straightforward and does not have thes
165165

166166
## Using the Hydration APIs
167167

168-
With just a little more setup, you can use a `queryClient` to prefetch queries during a preload phase, pass a serialized version of that `queryClient` to the rendering part of the app and reuse it there. This avoid the drawbacks above. Feel free to skip ahead for full Next.js pages router and Remix examples, but at a general level these are the extra steps:
168+
With just a little more setup, you can use a `queryClient` to prefetch queries during a preload phase, pass a serialized version of that `queryClient` to the rendering part of the app and reuse it there. This avoids the drawbacks above. Feel free to skip ahead for full Next.js pages router and Remix examples, but at a general level these are the extra steps:
169169

170170
- In the framework loader function, create a `const queryClient = new QueryClient(options)`
171171
- In the loader function, do `await queryClient.prefetchQuery(...)` for each query you want to prefetch

docs/framework/react/guides/suspense.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ id: suspense
33
title: Suspense
44
---
55

6-
React Query can also be used with React's Suspense for Data Fetching API's. For this, we have dedicated hooks:
6+
React Query can also be used with React's Suspense for Data Fetching APIs. For this, we have dedicated hooks:
77

88
- [useSuspenseQuery](../reference/useSuspenseQuery.md)
99
- [useSuspenseInfiniteQuery](../reference/useSuspenseInfiniteQuery.md)

docs/reference/streamedQuery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,5 +23,5 @@ const query = queryOptions({
2323
- `refetchMode?: 'append' | 'reset'`
2424
- optional
2525
- when set to `'reset'`, the query will erase all data and go back into `pending` state when a refetch occurs.
26-
- when set ot `'append'`, data will be appended on a refetch.
26+
- when set to `'append'`, data will be appended on a refetch.
2727
- defaults to `'reset'`

0 commit comments

Comments
 (0)