Fixed broken links in data fetching docs (#33250)

Found some broken links in the updated Data Fetching docs. Fixed all of these.

## Documentation / Examples

- [x] Make sure the linting passes by running `yarn lint`


Co-authored-by: Lee Robinson <9113740+leerob@users.noreply.github.com>

Author: MaedahBatool

docs/basic-features/data-fetching/client-side.md

@@ -47,7 +47,7 @@ The team behind Next.js has created a React hook library for data fetching calle
 
 Using the same example as above, we can now use SWR to fetch the profile data. SWR will automatically cache the data for us and will revalidate the data if it becomes stale.
 
-For more information on using SWR, check out the [SWR docs](https://swr.vercel.app/docs).
+For more information on using SWR, check out the [SWR docs](https://swr.vercel.app/docs/getting-started).
 
 ```jsx
 import useSWR from 'swr'

docs/basic-features/data-fetching/get-server-side-props.md

@@ -45,7 +45,7 @@ Take the following example. An API route is used to fetch some data from a CMS.
 
 ## Fetching data on the client side
 
-If your page contains frequently updating data, and you don’t need to pre-render the data, you can fetch the data on the [client side](/docs/basic-features/client-side.md). An example of this is user-specific data:
+If your page contains frequently updating data, and you don’t need to pre-render the data, you can fetch the data on the [client side](/docs/basic-features/data-fetching/client-side.md). An example of this is user-specific data:
 
 - First, immediately show the page without data. Parts of the page can be pre-rendered using Static Generation. You can show loading states for missing data.
 - Then, fetch the data on the client side and display it when ready.