From 7e843c839993ff4102bdb3af4d1eddb520b2fa5e Mon Sep 17 00:00:00 2001
From: Uncle Silva <114862835+Silva-Mo@users.noreply.github.com>
Date: Mon, 4 Aug 2025 14:41:56 +0400
Subject: [PATCH] Update solution.md

fix small typo
---
 1-js/11-async/08-async-await/04-promise-all-failure/solution.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/1-js/11-async/08-async-await/04-promise-all-failure/solution.md b/1-js/11-async/08-async-await/04-promise-all-failure/solution.md
index 9fda8e000f..5e1e111e17 100644
--- a/1-js/11-async/08-async-await/04-promise-all-failure/solution.md
+++ b/1-js/11-async/08-async-await/04-promise-all-failure/solution.md
@@ -1,7 +1,7 @@
 
 The root of the problem is that `Promise.all` immediately rejects when one of its promises rejects, but it do nothing to cancel the other promises.
 
-In our case, the second query fails, so `Promise.all` rejects, and the `try...catch` block catches this error.Meanwhile, other promises are *not affected* - they independently continue their execution. In our case, the third query throws an error of its own after a bit of time. And that error is never caught, we can see it in the console.
+In our case, the second query fails, so `Promise.all` rejects, and the `try...catch` block catches this error. Meanwhile, other promises are *not affected* - they independently continue their execution. In our case, the third query throws an error of its own after a bit of time. And that error is never caught, we can see it in the console.
 
 The problem is especially dangerous in server-side environments, such as Node.js, when an uncaught error may cause the process to crash.