diff --git a/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/readme.md b/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/readme.md
index 21bbaaae6..56a966cc8 100644
--- a/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/readme.md
+++ b/content/roadmaps/107-nodejs/content/116-nodejs-more-debugging/100-memory-leaks/readme.md
@@ -1 +1,8 @@
-# Memory leaks
\ No newline at end of file
+# Memory Leaks
+
+Memory leaks are caused when your Node.js app’s CPU and memory usage increases over time for no apparent reason. In simple terms, a Node.js memory leak is an orphan block of memory on the Heap that is no longer used by your app because it has not been released by the garbage collector. It’s a useless block of memory. These blocks can grow over time and lead to your app crashing because it runs out of memory.
+
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
+<BadgeLink badgeText='Website' colorScheme="yellow" href='https://sematext.com/blog/nodejs-memory-leaks/'>Memory leaks in Node.js</BadgeLink>
+<BadgeLink badgeText='Read' colorScheme="yellow" href='https://sematext.com/blog/nodejs-memory-leaks/#what-causes-them-common-node-js-memory-leaks'>Memory leaks causes</BadgeLink>
+<BadgeLink badgeText='Documentation' colorScheme="yellow" href='https://sematext.com/blog/nodejs-memory-leaks/#node-js-memory-leak-detectors'>Memory leaks detectors</BadgeLink>