From 9a7357363985298220497f25616b26d95f02b5f7 Mon Sep 17 00:00:00 2001
From: Julio Maniratunga <694912+julio73@users.noreply.github.com>
Date: Fri, 16 Jul 2021 11:52:44 +0300
Subject: [PATCH] docs: remove unnecessary apostrophe (#2464)

---
 docs/src/pages/guides/initial-query-data.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/pages/guides/initial-query-data.md b/docs/src/pages/guides/initial-query-data.md
index 05d075e77a..ff04ff9264 100644
--- a/docs/src/pages/guides/initial-query-data.md
+++ b/docs/src/pages/guides/initial-query-data.md
@@ -64,7 +64,7 @@ By default, `initialData` is treated as totally fresh, as if it were just fetche
     })
   }
   ```
-  This option allows the staleTime to be used for it's original purpose, determining how fresh the data needs to be, while also allowing the data to be refetched on mount if the `initialData` is older than the `staleTime`. In the example above, our data needs to be fresh within 1 minute, and we can hint to the query when the initialData was last updated so the query can decide for itself whether the data needs to be refetched again or not.
+  This option allows the staleTime to be used for its original purpose, determining how fresh the data needs to be, while also allowing the data to be refetched on mount if the `initialData` is older than the `staleTime`. In the example above, our data needs to be fresh within 1 minute, and we can hint to the query when the initialData was last updated so the query can decide for itself whether the data needs to be refetched again or not.
 
 > If you would rather treat your data as **prefetched data**, we recommend that you use the `prefetchQuery` or `fetchQuery` APIs to populate the cache beforehand, thus letting you configure your `staleTime` independently from your initialData