You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 6-async/04-promise-api/01-promise-errors-as-results/solution.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Promise.all(
12
12
13
13
Here we have an array of `fetch(...)` promises that goes to `Promise.all`.
14
14
15
-
We can't change the way `Promise.all` works: if it detects an error, then it rejects with it. So we need to prevent any error from occuring. Instead, if a `fetch` error happens, we need to treat it as a "normal" result.
15
+
We can't change the way `Promise.all` works: if it detects an error, then it rejects with it. So we need to prevent any error from occurring. Instead, if a `fetch` error happens, we need to treat it as a "normal" result.
An `XMLHttpRequest` object travels them in the order `0` -> `1` -> `2` -> `3` -> ... -> `3` -> `4`. State `3` repeats every time a data packet is received over the network.
244
244
245
-
The example above demostrates these states. The server answers the request `digits` by sending a string of `1000` digits once per second.
245
+
The example above demonstrates these states. The server answers the request `digits` by sending a string of `1000` digits once per second.
0 commit comments