diff --git a/src/data/roadmaps/angular/content/zone-pollution@pRSR5PEbkJXAJ1LPyK-EE.md b/src/data/roadmaps/angular/content/zone-pollution@pRSR5PEbkJXAJ1LPyK-EE.md
index 790b8d56a..32c415a9c 100644
--- a/src/data/roadmaps/angular/content/zone-pollution@pRSR5PEbkJXAJ1LPyK-EE.md
+++ b/src/data/roadmaps/angular/content/zone-pollution@pRSR5PEbkJXAJ1LPyK-EE.md
@@ -1 +1,10 @@
-# Zone Pollution
\ No newline at end of file
+# Zone Pollution
+
+`Zone.js` is a signaling mechanism that Angular uses to detect when an application state might have changed. In some cases, scheduled tasks or microtasks don’t make any changes in the data model, which makes running change detection unnecessary. Common examples are `requestAnimationFrame`, `setTimeout` and `setInterval`. You can identify change detection with Angular DevTools, and you can run code outside the Angular zone to avoid unnecessary change detection calls.
+
+Visit the following resources to learn more:
+
+- [@official@Angular Official Docs - Zone Pollution](https://angular.dev/best-practices/zone-pollution)
+- [@official@Angular Official Docs - DevTools](https://angular.dev/tools/devtools)
+- [@video@NgZone in Angular - Improve Performance by Running Code Outside Angular](https://www.youtube.com/watch?v=7duYY9IFIuw)
+- [@video@4 Runtime Performance Optimizations](https://www.youtube.com/watch?v=f8sA-i6gkGQ)
\ No newline at end of file