Fix typo

[bangjiehan]

Standard only state that auto-commit happen after requests finished and results handled.
Results handle by related events so implementation might wait for event queue to be empty.

When a transaction has been started and it can no longer become active, the implementation must attempt to commit it, as long as the transaction has not been aborted. This usually happens after all requests placed against the transaction have been executed and their returned results handled, and no new requests have been placed against the transaction.

from indexeddb api 2.0

[Copilot]

Pull Request Overview

This PR corrects terminology inconsistencies in the IndexedDB documentation regarding microtasks vs macrotasks and their relationship to transaction auto-commit behavior.

• Corrects the description of when IndexedDB transactions auto-commit (macrotasks queue instead of microtasks queue)
• Fixes the classification of fetch as a microtask instead of macrotask
• Updates the explanation of transaction timing behavior to use consistent terminology

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

This change is incorrect. fetch is a macrotask, not a microtask. The original text was correct - fetch creates a macrotask and transactions are closed before macrotasks execute.

Suggested change

	That's because `fetch` is an asynchronous operation, a microtask. Transactions are closed before the browser starts doing microtasks.
	That's because `fetch` is an asynchronous operation, a macrotask. Transactions are closed before the browser starts doing macrotasks.

[Copilot]

This change introduces an error. fetch is a macrotask, not a microtask. The sentence should read 'So if we put a macrotask like fetch' to be technically accurate.

Suggested change

	As we already know, a transaction auto-commits as soon as the browser is done with the current code and macrotasks. So if we put a *microtask* like `fetch` in the middle of a transaction, then the transaction won't wait for it to finish. It just auto-commits. So the next request in it would fail.
	As we already know, a transaction auto-commits as soon as the browser is done with the current code and macrotasks. So if we put a *macrotask* like `fetch` in the middle of a transaction, then the transaction won't wait for it to finish. It just auto-commits. So the next request in it would fail.