Format JavaScript roadmap content (#2378)

* Adding information on QA SDLC Delivery Model node

* Update content/roadmaps/113-qa/content/101-qa-sdlc/readme.md

* Tweaking files in the Chrome Dev Tools section - JS roadmap

* Tweaking format on files from Memory Management - JS roadmap

* Fixed issue with one of the Free Contents - CommonJS readme

* Format tweak on Callback nodes - JS Roadmap

Co-authored-by: Kamran Ahmed <kamranahmed.se@gmail.com>

content/roadmaps/106-javascript/content/112-javascript-asynchronous-javascript/103-callbacks/100-callback-hell.md

@@ -2,4 +2,5 @@
 
 The callback hell is when we try to write asynchronous JavaScript in a way where execution happens visually from top to bottom, creating a code that has a pyramid shape with many }) at the end.
 
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
 <BadgeLink colorScheme='yellow' badgeText='Read' href='http://callbackhell.com/'>Callback Hell</BadgeLink>

content/roadmaps/106-javascript/content/112-javascript-asynchronous-javascript/103-callbacks/readme.md

@@ -2,5 +2,6 @@
 
 A callback function is a function passed into another function as an argument, which is then invoked inside the outer function to complete some kind of routine or action.
 
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
 <BadgeLink colorScheme='yellow' badgeText='Read' href='https://javascript.info/callbacks'>Callbacks in JavaScript</BadgeLink>
 <BadgeLink colorScheme='yellow' badgeText='Read' href='https://developer.mozilla.org/en-US/docs/Glossary/Callback_function'>Callback Functions</BadgeLink>

content/roadmaps/106-javascript/content/115-javascript-modules/100-commonjs.md

@@ -4,6 +4,6 @@ CommonJS modules are the original way to package JavaScript code for Node.js. No
 
 <ResourceGroupTitle>Free Content</ResourceGroupTitle>
 <BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.freecodecamp.org/news/modules-in-javascript/#commonjsmodules'>Modules in Javascript: CJS Section</BadgeLink>
-<BadgeLink colorScheme='yellow' basw2dgeText='Read' href='https://nodejs.org/api/modules'>Node.js documentation for CJS modules</BadgeLink>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://nodejs.org/api/modules'>Node.js documentation for CJS modules</BadgeLink>
 <BadgeLink colorScheme='yellow' badgeText='Read' href='https://blog.risingstack.com/node-js-at-scale-module-system-commonjs-require/'>How the CJS Module System Works</BadgeLink>
 <BadgeLink colorScheme='purple' badgeText='Watch' href='https://www.youtube.com/watch?v=XTND4rjATXA'>How to Import and Export Modules in CJS</BadgeLink>

content/roadmaps/106-javascript/content/116-javascript-memory-management/101-garbage-collection.md

@@ -2,5 +2,6 @@
 
 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.
 
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
 <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>

content/roadmaps/106-javascript/content/116-javascript-memory-management/readme.md

@@ -2,5 +2,6 @@
 
 Low-level languages like C, have manual memory management primitives such as malloc() and free(). In contrast, JavaScript automatically allocates memory when objects are created and frees it when they are not used anymore (garbage collection). This automaticity is a potential source of confusion: it can give developers the false impression that they don't need to worry about memory management.
 
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
 <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>

content/roadmaps/106-javascript/content/117-javascript-chrome-dev-tools/100-debugging-issues.md

@@ -4,4 +4,5 @@ When you're just starting out with JavaScript development, you might use a lot o
 
 However, for quicker, more complex and easier to handler debugging (which also doesn't litter your codebase with `console.log()`s), breakpoints and the sources panel is your friend.
 
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
 <BadgeLink colorScheme='yellow' badgeText='Read' href='https://developer.chrome.com/docs/devtools/javascript/'>Debugging JavaScript in the sources panel</BadgeLink>

content/roadmaps/106-javascript/content/117-javascript-chrome-dev-tools/101-debugging-memory-leaks.md

@@ -2,6 +2,7 @@
 
 In JavaScript, memory leaks commonly occur within heap allocated memory, where short lived objects are attached to long lived ones and the Garbage Collector cannot safely de-allocate that memory as it is still referenced from the root set (the global object).
 
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
 <BadgeLink colorScheme='yellow' badgeText='Read' href='https://medium.com/coding-blocks/catching-memory-leaks-with-chrome-devtools-57b03acb6bb9'>Catching memory leaks with Chrome DevTools</BadgeLink>
 <BadgeLink colorScheme='yellow' badgeText='Read' href='https://medium.com/swlh/effective-javascript-debugging-memory-leaks-75059b2436f6'>Effective Javascript Debugging </BadgeLink>
 <BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.debugbear.com/blog/debugging-javascript-memory-leaks'>Debugging JavaScript memory leaks</BadgeLink>

content/roadmaps/106-javascript/content/117-javascript-chrome-dev-tools/readme.md

@@ -6,5 +6,6 @@ To enter the dev tools, right click and click **Inspect** (or press `ctrl+shift+
 
 NOTE: This isn't a chrome-specific feature, and most browsers (Chromium based or otherwise) will have their own, largely-similar set of devtools.
 
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
 <BadgeLink colorScheme='yellow' badgeText='Read' href='https://developer.chrome.com/docs/devtools/overview/'>Official Docs</BadgeLink>
 <BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.freecodecamp.org/news/mastering-chrome-developer-tools-next-level-front-end-development-techniques-3ac0b6fe8a3/'>Mastering Chrome Dev Tools</BadgeLink>