From 8006ba4546a96683ec1a00343f275a9c8944b9b1 Mon Sep 17 00:00:00 2001
From: Kamran Ahmed <kamranahmed.se@gmail.com>
Date: Sun, 18 Sep 2022 14:29:58 +0400
Subject: [PATCH] Add garbage collection content

---
 .../100-memory-leaks/100-garbage-collection.md             | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/100-garbage-collection.md b/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/100-garbage-collection.md
index 2e9dd7ee1..4a41d0419 100644
--- a/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/100-garbage-collection.md
+++ b/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/100-garbage-collection.md
@@ -1 +1,6 @@
-# Garbage collection
\ No newline at end of file
+# Garbage Collection
+
+Memory management in JavaScript is performed automatically and invisibly to us. We create primitives, objects, functions… All that takes memory. The main concept of memory management in JavaScript is reachability.
+
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://javascript.info/garbage-collection'>JavaScript Garbage Collection</BadgeLink>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://developer.mozilla.org/en-US/docs/Web/JavaScript/Memory_Management'>Memory Management in JavaScript</BadgeLink>