Skip to content

Commit e3fb566

Browse files
authored
docs: Fix typo (#2850)
1 parent f904557 commit e3fb566

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/src/pages/guides/initial-query-data.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ By default, `initialData` is treated as totally fresh, as if it were just fetche
5555
- So what if your `initialData` isn't totally fresh? That leaves us with the last configuration that is actually the most accurate and uses an option called `initialDataUpdatedAt`. This option allows you to pass a numeric JS timestamp in milliseconds of when the initialData itself was last updated, e.g. what `Date.now()` provides. Take note that if you have a unix timestamp, you'll need to convert it to a JS timestamp by multiplying it by `1000`.
5656
```js
5757
function Todos() {
58-
// Show initialTodos immeidately, but won't refetch until another interaction event is encountered after 1000 ms
58+
// Show initialTodos immediately, but won't refetch until another interaction event is encountered after 1000 ms
5959
const result = useQuery('todos', () => fetch('/todos'), {
6060
initialData: initialTodos,
6161
staleTime: 60 * 1000 // 1 minute

0 commit comments

Comments
 (0)