Repository: vercel/next.js
Pull request: Update 07-fetching-data.mdx

Promise.all or any of the other 3 static concurrency methods don't actually run requests in parallel, rather they execute concurrently.

[Parallelism vs Concurrency](https://wiki.haskell.org/Parallelism_vs._Concurrency)
[Promise Concurrency](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise#promise_concurrency)

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the PR.
- Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to understand the PR)
- When linking to a Slack thread, you might want to share details of the conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic behind a change

### What?
[Concurrency was confused as parallelism](https://wiki.haskell.org/Parallelism_vs._Concurrency)
### Why?
Might confuse others, especially those still learning on how promises work. 
### How?
Promise.all or any of the other 3 static concurrency methods don't actually run requests in parallel, rather they execute [concurrently](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise#promise_concurrency).
Closes NEXT-
Fixes #

-->


Changed files:
filename: docs/01-app/01-getting-started/07-fetching-data.mdx
patch: @@ -504,7 +504,7 @@ export default async function Page({ params }) {
 }
 ```
 
-You can initiate requests in parallel by defining them outside the components that use the data, and resolving them together, for example, with [`Promise.all`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/all):
+Start multiple requests by calling `fetch`, then await them with [`Promise.all`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/all). Requests begin as soon as `fetch` is called.
 
 ```tsx filename="app/artist/[username]/page.tsx" highlight={3,8,23} switcher
 import Albums from './albums'
@@ -525,10 +525,11 @@ export default async function Page({
   params: Promise<{ username: string }>
 }) {
   const { username } = await params
+
+  // Initiate requests
   const artistData = getArtist(username)
   const albumsData = getAlbums(username)
 
-  // Initiate both requests in parallel
   const [artist, albums] = await Promise.all([artistData, albumsData])
 
   return (
@@ -555,10 +556,11 @@ async function getAlbums(username) {
 
 export default async function Page({ params }) {
   const { username } = await params
+
+  // Initiate requests
   const artistData = getArtist(username)
   const albumsData = getAlbums(username)
 
-  // Initiate both requests in parallel
   const [artist, albums] = await Promise.all([artistData, albumsData])
 
   return (