docs: improve prefetching definition for clarity

Problem:
The current definition, "Prefetching is the process of loading a route in the background..." relies on somewhat unclear terminology. The phrase "loading a route" comes across as rather ambiguous.

Solution:
Aligned with the updated definition: "Prefetching is the process of preloading route data and components in the background..." This phrase explains what prefetching does, i.e.,.
i. Route data (from data fetching functions)
ii. Components (JavaScript bundles and React components)

Benefits: The updated definition aligns with NextJS's actual prefetching behavior

Author: kingmaker9841

docs/01-app/01-getting-started/04-linking-and-navigating.mdx

@@ -35,7 +35,7 @@ The trade-off of server rendering is that the client must wait for the server to
 
 ### Prefetching
 
-Prefetching is the process of loading a route in the background before the user navigates to it. This makes navigation between routes in your application feel instant, because by the time a user clicks on a link, the data to render the next route is already available client side.
+Prefetching is the process of preloading route data and components in the background before the user navigates to it. This makes navigation between routes in your application feel instant, because by the time a user clicks on a link, the data to render the next route is already available client side.
 
 Next.js automatically prefetches routes linked with the [`<Link>` component](/docs/app/api-reference/components/link) when they enter the user's viewport.