diff --git a/docs/docs/getting-started/overview.md b/docs/docs/getting-started/overview.md
index b70f228..15df8e4 100644
--- a/docs/docs/getting-started/overview.md
+++ b/docs/docs/getting-started/overview.md
@@ -5,14 +5,14 @@ id: overview
 
 # Overview
 
-Fl-Query is a asynchronous data manager for Flutter that caches, fetches, automatically refetches stale data. Basically, its [React-Query](react-query.tanstack.com/) but for Flutter. But that doesn't mean it's a direct port of React-Query. Instead the concept of React-Query is implemented by Fl-Query
+Fl-Query is a asynchronous data manager for Flutter that caches, fetches, automatically refetches stale data. Basically, its [React-Query](https://react-query.tanstack.com/) but for Flutter. But that doesn't mean it's a direct port of React-Query. Instead the concept of React-Query is implemented by Fl-Query
 
 ## What does it offer?
 
 - Async data caching & invalidation
 - Smart refetch in the background every time data becomes stale
 - Declarative way to define asynchronous operations
-- Code & data reusability because of persisted data & Query/Mutation [Job](/basic/job) API
+- Code & data reusability because of persisted data & Query/Mutation **Job** API
 - Optimistic data support
 - Lazy Loading/Fetching support
 - Zero Configuration out of the box & never have to touch any Global Store
@@ -29,7 +29,7 @@ Some Questions and their answers:
   Yes but it is only if your commercial server has huge load of power & you're made of money or your app is simple or mostly offline & barely requires internet connection
   `FutureBuilder` isn't good for data persistency & its impossible to share data across the entire application using it. Also if you call your fetching function directly in the `build` method as `future: getData("random-id")` it'll run every time the component rebuilds & it can be mitigated only if you call the method inside `initState` which involves lots of boilerplate
 
-- **`FutureProvider` from [riverpod](riverpod.dev/) or [provider](https://github.com/rrousselGit/provider) should be enough, right?**
+- **`FutureProvider` from [riverpod](https://riverpod.dev/) or [provider](https://github.com/rrousselGit/provider) should be enough, right?**
   
   Yeah, indeed its more than enough for many applications but what if your app needs Optimistic Updates & proper server-state synchronization or simply want a custom `cacheTime`? Although `FutureProvider` is a viable solution for most of the `Future` but still you've to manually manage the cache & it still have no support for _Lazy Loading_.
   
diff --git a/docs/docusaurus.config.js b/docs/docusaurus.config.js
index c7fdfcc..ec89d53 100644
--- a/docs/docusaurus.config.js
+++ b/docs/docusaurus.config.js
@@ -99,7 +99,7 @@ const config = {
             items: [
               {
                 label: 'Documentation',
-                to: '/docs/intro',
+                to: '/docs/getting-started/overview',
               },
             ],
           },