From 21fdc05b6bdece07eb6d93bdcc2fa04b663a34da Mon Sep 17 00:00:00 2001
From: Arya Singh <72375247+ARYASINGHBJC@users.noreply.github.com>
Date: Fri, 21 Oct 2022 20:49:16 +0530
Subject: [PATCH] fixes typo and spacing (#2622)

---
 .../content/103-nodejs-error-handling/104-async-errors.md     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/roadmaps/107-nodejs/content/103-nodejs-error-handling/104-async-errors.md b/content/roadmaps/107-nodejs/content/103-nodejs-error-handling/104-async-errors.md
index affaa2ea6..3c63c4d6e 100644
--- a/content/roadmaps/107-nodejs/content/103-nodejs-error-handling/104-async-errors.md
+++ b/content/roadmaps/107-nodejs/content/103-nodejs-error-handling/104-async-errors.md
@@ -1,6 +1,6 @@
 # Async errors
 
-Errors must always be handled. If you are using synchronous programming you could use a try catch. But this does not work if you work asynchronous!Async errors will only be handled inside the callback function!
+Errors must always be handled. If you are using synchronous programming you could use a try catch. But this does not work if you work asynchronous! Async errors will only be handled inside the callback function!
 
 <ResourceGroupTitle>Free Content</ResourceGroupTitle>
-<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.mariokandut.com/handling-errors-in-asynchronous-functions-node-js/'>Asyn Errors</BadgeLink>
\ No newline at end of file
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.mariokandut.com/handling-errors-in-asynchronous-functions-node-js/'>Async Errors</BadgeLink>