docs: Typo fixes in Markdown files (#2910)

Author: emzoumpo

docs/src/pages/guides/migrating-to-react-query-3.md

@@ -335,7 +335,7 @@ If you do not want to refetch immediately, you can define a `staleTime`.
 
 ### The `QueryOptions.forceFetchOnMount` option has been replaced by `refetchOnMount: 'always'`
 
-Honestly, we were acruing way too many `refetchOn____` options, so this should clean things up.
+Honestly, we were accruing way too many `refetchOn____` options, so this should clean things up.
 
 ### The `QueryOptions.refetchOnMount` options now only applies to its parent component instead of all query observers
 
@@ -348,7 +348,7 @@ The `queryFnParamsFilter` option has been removed because query functions now ge
 
 Parameters can still be filtered within the query function itself as the `QueryFunctionContext` also contains the query key.
 
-### The `QueryOptions.notifyOnStatusChange` option has been superceded by the new `notifyOnChangeProps` and `notifyOnChangePropsExclusions` options.
+### The `QueryOptions.notifyOnStatusChange` option has been superseded by the new `notifyOnChangeProps` and `notifyOnChangePropsExclusions` options.
 
 With these new options it is possible to configure when a component should re-render on a granular level.
 
@@ -585,7 +585,7 @@ const fetches = useIsFetching(['posts'])
 
 #### Core separation
 
-The core of React Query is now fully separated from React, which means it can also be used standalone or in other frameworks. Use the `react-query/core` entrypoint to only import the core functionality:
+The core of React Query is now fully separated from React, which means it can also be used standalone or in other frameworks. Use the `react-query/core` entry point to only import the core functionality:
 
 ```js
 import { QueryClient } from 'react-query/core'

docs/src/pages/guides/query-cancellation.md

@@ -115,7 +115,7 @@ return (
 
 ## Old `cancel` function
 
-Don't worry! The previous cancellation functionality will continue to work. But we do recommend that you move away from [the withdrawn cancelable promise proposal](https://github.com/tc39/proposal-cancelable-promises) to the [new `AbortSignal` interface](#_top) which has been [stardardized](https://dom.spec.whatwg.org/#interface-abortcontroller) as a general purpose construct for aborting ongoing activities in [most browsers](https://caniuse.com/abortcontroller) and in [Node](https://nodejs.org/api/globals.html#globals_class_abortsignal). The old cancel function might be removed in a future major version.
+Don't worry! The previous cancellation functionality will continue to work. But we do recommend that you move away from [the withdrawn cancelable promise proposal](https://github.com/tc39/proposal-cancelable-promises) to the [new `AbortSignal` interface](#_top) which has been [standardized](https://dom.spec.whatwg.org/#interface-abortcontroller) as a general purpose construct for aborting ongoing activities in [most browsers](https://caniuse.com/abortcontroller) and in [Node](https://nodejs.org/api/globals.html#globals_class_abortsignal). The old cancel function might be removed in a future major version.
 
 To integrate with this feature, attach a `cancel` function to the promise returned by your query that implements your request cancellation. When a query becomes out-of-date or inactive, this `promise.cancel` function will be called (if available).
 

docs/src/pages/guides/ssr.md

@@ -179,7 +179,7 @@ ReactDOM.hydrate(
 
 ### Only successful queries are included in dehydration
 
-Any query with an error is automatically excluded from dehydration. This means that the default behaviour is to pretend these queries were never loaded on the server, usually showing a loading state instead, and retrying the queries on the queryClient. This happens regardless of error.
+Any query with an error is automatically excluded from dehydration. This means that the default behavior is to pretend these queries were never loaded on the server, usually showing a loading state instead, and retrying the queries on the queryClient. This happens regardless of error.
 
 Sometimes this behavior is not desirable, maybe you want to render an error page with a correct status code instead on certain errors or queries. In those cases, use `fetchQuery` and catch any errors to handle those manually.
 

docs/src/pages/guides/window-focus-refetching.md

@@ -34,7 +34,7 @@ In rare circumstances, you may want to manage your own window focus events that
 
 ```js
 focusManager.setEventListener(handleFocus => {
-  // Listen to visibillitychange and focus
+  // Listen to visibilitychange and focus
   if (typeof window !== 'undefined' && window.addEventListener) {
     window.addEventListener('visibilitychange', handleFocus, false)
     window.addEventListener('focus', handleFocus, false)

docs/src/pages/plugins/createAsyncStoragePersistor.md

@@ -43,7 +43,7 @@ persistQueryClient({
 
 ### `createAsyncStoragePersistor`
 
-Call this function to create an asyncStoragePersistor that you can use later with `persisteQueryClient`.
+Call this function to create an asyncStoragePersistor that you can use later with `persistQueryClient`.
 
 ```js
 createAsyncStoragePersistor(options: CreateAsyncStoragePersistorOptions)
@@ -55,9 +55,9 @@ createAsyncStoragePersistor(options: CreateAsyncStoragePersistorOptions)
 interface CreateAsyncStoragePersistorOptions {
   /** The storage client used for setting an retrieving items from cache */
   storage: AsyncStorage
-  /** The key to use when storing the cache to localstorage */
+  /** The key to use when storing the cache to localStorage */
   key?: string
-  /** To avoid localstorage spamming,
+  /** To avoid localStorage spamming,
    * pass a time in ms to throttle saving the cache to disk */
   throttleTime?: number
   /** How to serialize the data to storage */

docs/src/pages/reference/QueryClient.md

@@ -91,7 +91,7 @@ try {
 
 **Options**
 
-The options for `fetchQuery` are exactly the same as those of [`useQuery`](./useQuery), except the following: `enabled, refetchInterval, refetchIntervalInBackground, refetchOnWindowFocus, refetchOnReconnect, notifyOnChangeProps, notifyOnChangePropsExclusions, onSuccess, onError, onSettled, useErrorBoundary, select, suspense, keepPreviousData, placeholderData`; which are stictly for useQuery and useInfiniteQuery. You can check the [source code](https://github.com/tannerlinsley/react-query/blob/361935a12cec6f36d0bd6ba12e84136c405047c5/src/core/types.ts#L83) for more clarity.
+The options for `fetchQuery` are exactly the same as those of [`useQuery`](./useQuery), except the following: `enabled, refetchInterval, refetchIntervalInBackground, refetchOnWindowFocus, refetchOnReconnect, notifyOnChangeProps, notifyOnChangePropsExclusions, onSuccess, onError, onSettled, useErrorBoundary, select, suspense, keepPreviousData, placeholderData`; which are strictly for useQuery and useInfiniteQuery. You can check the [source code](https://github.com/tannerlinsley/react-query/blob/361935a12cec6f36d0bd6ba12e84136c405047c5/src/core/types.ts#L83) for more clarity.
 
 **Returns**
 

docs/src/pages/reference/focusManager.md

@@ -21,7 +21,7 @@ Its available methods are:
 import { focusManager } from 'react-query'
 
 focusManager.setEventListener(handleFocus => {
-  // Listen to visibillitychange and focus
+  // Listen to visibilitychange and focus
   if (typeof window !== 'undefined' && window.addEventListener) {
     window.addEventListener('visibilitychange', handleFocus, false)
     window.addEventListener('focus', handleFocus, false)

docs/src/pages/reference/hydration.md

@@ -5,7 +5,7 @@ title: hydration
 
 ## `dehydrate`
 
-`dehydrate` creates a frozen representation of a `cache` that can later be hydrated with `Hydrate`, `useHydrate`, or `hydrate`. This is useful for passing prefetched queries from server to client or persisting queries to localstorage or other persistent locations. It only includes currently successful queries by default.
+`dehydrate` creates a frozen representation of a `cache` that can later be hydrated with `Hydrate`, `useHydrate`, or `hydrate`. This is useful for passing prefetched queries from server to client or persisting queries to localStorage or other persistent locations. It only includes currently successful queries by default.
 
 ```js
 import { dehydrate } from 'react-query'

docs/src/pages/reference/useMutation.md

@@ -69,7 +69,7 @@ mutate(variables, {
 - `useErrorBoundary: undefined | boolean | (error: TError) => boolean`
   - Defaults to the global query config's `useErrorBoundary` value, which is `undefined`
   - Set this to `true` if you want mutation errors to be thrown in the render phase and propagate to the nearest error boundary
-  - Set this to `false` to disable the behaviour of throwing errors to the error boundary.
+  - Set this to `false` to disable the behavior of throwing errors to the error boundary.
   - If set to a function, it will be passed the error and should return a boolean indicating whether to show the error in an error boundary (`true`) or return the error as state (`false`)
 
 **Returns**

docs/src/pages/reference/useQuery.md

@@ -176,7 +176,7 @@ const result = useQuery({
 - `useErrorBoundary: undefined | boolean | (error: TError) => boolean`
   - Defaults to the global query config's `useErrorBoundary` value, which is `undefined`
   - Set this to `true` if you want errors to be thrown in the render phase and propagate to the nearest error boundary
-  - Set this to `false` to disable `suspense`'s default behaviour of throwing errors to the error boundary.
+  - Set this to `false` to disable `suspense`'s default behavior of throwing errors to the error boundary.
   - If set to a function, it will be passed the error and should return a boolean indicating whether to show the error in an error boundary (`true`) or return the error as state (`false`)
 - `meta: Record<string, unknown>`
   - Optional

src/react/utils.ts

@@ -8,7 +8,7 @@ export function shouldThrowError<TError>(
     return _useErrorBoundary(error)
   }
 
-  // Allow useErrorBoundary to override suspense's throwing behaviour
+  // Allow useErrorBoundary to override suspense's throwing behavior
   if (typeof _useErrorBoundary === 'boolean') return _useErrorBoundary
 
   // If suspense is enabled default to throwing errors